How to Redirect a Renamed Page on Cloudflare Pages

Keep the old address if you only need to change the visible name. If the address must change permanently, publish the replacement and send the old path directly to it with an HTTP 301. On a static Cloudflare Pages route, put the rule in the deployed _redirects file.

Write down the old and new addresses

Start with one pair. For example, a business may replace /spring-services/ with /seasonal-services/ after broadening the same offer. Match the replacement to what visitors expected at the old address. If the original page is gone and there is no useful equivalent, handle it as a removed page rather than sending everyone to your homepage.

List every version you know people use. Check whether old emails used a trailing slash, whether a QR code points to an older path, and whether any campaign link uses a query string your site needs. Keep separate addresses separate when they lead to different content.

Add the permanent redirect to the deployed output

Put one rule in the _redirects file that reaches Cloudflare’s asset output. A buildless project may publish from its repository root. A framework may copy the file from a public assets folder into the final output. Check the actual deployment directory before editing.

Deploy the new page and rule together. Put specific paths ahead of any matching wildcard. If an older URL already redirects to the page you are renaming, point its rule directly at the final destination so customers do not take an extra hop. Use a permanent redirect for a permanent move and a temporary redirect for a temporary substitution.

Point your own links at the final address

• Update navigation, resource cards, service links, and any call-to-action buttons that use the old address.
• Give the replacement page a canonical that uses its final production URL.
• Replace the old URL in the sitemap source and regenerate the sitemap if your project uses a build script.
• Update listings or profiles you control when they link directly to the renamed page.

If you are changing several pages at once, use the website redesign SEO checklist to plan the wider launch. The BUILD • PUBLISH • OWN IT guide covers the broader DIY workflow for building, reviewing, and publishing your site.

Check the redirect and the destination after publishing

Open the old address in a fresh window and confirm it lands at the right page. In your browser’s Network panel, look for a 301 on the old request and a 200 on the replacement. Test the exact slash and query variants your customers use. Check any campaign or form attribution separately if it depends on parameters reaching the destination.

Then open the live sitemap, check that it lists the replacement URL, and follow a link to the page from your own navigation. Inspect the replacement in Search Console if you have access. Keep the redirect in place so old bookmarks and links remain useful.

If the old address is handled by a Pages Function

Cloudflare’s static _redirects rules do not apply to responses served by Pages Functions. If a function handles the old URL, implement the redirect in the appropriate function or use your project’s established routing approach. Confirm how middleware passes requests to static assets before choosing where the rule belongs. Preview the exact change before relying on it in production.