301 Redirects: Merge and Move Pages Safely

Websites change. Posts are merged, services are renamed, old campaign pages are retired and duplicates created by a publishing tool need cleaning up. Every time a URL stops being the right home for its content, you face a choice: delete it, leave it or send visitors and search engines somewhere better. Permanent 301 redirects are usually the right answer when content has moved for good. Done well, they preserve the value of old links and bookmarks and tell search engines which URL to show. Done badly, they create chains, loops and dead ends. This guide explains how 301 redirects work, when to use them instead of other options, how to plan a batch of them and how to check they behave as intended.

What a 301 redirect tells search engines

A 301 status code means a page has moved permanently. Google's documentation on redirects explains that Google Search uses certain types of redirect as a signal that the redirect target should be canonical, and that permanent redirects show the new target in search results while temporary ones show the source page (Google Search Central: Redirects and Google Search). It lists HTTP 301 and 308 as permanent server-side redirects and says to use permanent redirects when you are sure the redirect will not be reverted.

Users rarely notice the difference between redirect types, but search engines do, so choose deliberately.

When to use 301 redirects

Use permanent redirects when the old URL has a clear successor:

• Two or more posts on the same topic are merged into one.
• A page moves to a new URL structure, such as a cleaner slug.
• A service or product is renamed and its page moves.
• A site moves to a new domain or from HTTP to HTTPS.

Do not redirect everything to the home page. A redirect should point to the page that best answers what visitors to the old URL wanted. If no good replacement exists, returning a 404 or 410 status is more honest than sending people somewhere irrelevant.

Redirects or canonical tags for duplicates

Duplicates can be handled with redirects or with canonical tags. Google's guide to consolidating duplicate URLs lists methods in order of how strongly they influence canonicalisation: redirects are a strong signal that the target should become canonical, rel="canonical" link annotations are also a strong signal and sitemap inclusion is a weak signal (Google Search Central: Consolidate duplicate URLs).

The practical difference is whether the duplicate needs to stay reachable. If there is no reason for anyone to visit the duplicate, redirect it. If both versions must remain, such as a printable version, use a canonical tag. The same guide warns against using robots.txt for canonicalisation, because Google may still index disallowed URLs without their content.

Avoid chains and loops

A redirect chain happens when URL A redirects to B, which redirects to C. Google's guide to site moves advises avoiding chained redirects, noting that while Googlebot can follow up to 10 hops, it is better to redirect to the final destination directly (Google Search Central: Site moves with URL changes). Chains also slow visitors down and are easy to break.

When you add new redirects, update older ones that point to URLs which now redirect, so that every old URL goes straight to its final destination. Loops, where redirects point back to each other, make a page unreachable; test for them before release.

Keep redirects in place

Redirects are not a short-term fix. The same site moves guide recommends keeping redirects for as long as possible, generally at least one year, to give Google time to transfer signals and recrawl links that point to the old URLs. For links on other websites, bookmarks and old emails, keeping them indefinitely is often sensible if your platform makes that easy.

Update everything you control

A redirect catches visitors who arrive at the old URL, but you should stop sending them there yourself. After redirecting, update internal links, navigation, your XML sitemap, email templates and any ads to use the final URL. Google's guide to duplicate URLs recommends linking to the canonical URL rather than a duplicate when linking within your site. Our guide to the XML sitemap covers how to keep redirected URLs out of the sitemap.

Worked example: a redirect map for merged posts

The table below is a hypothetical redirect map for a blog that is merging duplicate posts. It shows the columns worth keeping for each URL, so that the plan can be reviewed before anything changes.

Old URLReasonRedirect targetTypeChecks/blogs/topic-guide-copyExact duplicate of a kept post/blogs/topic-guide301Target returns 200; no chain/blogs/topic-guide-datedOlder version of the same topic/blogs/topic-guide301Internal links updated/blogs/old-service-nameService renamed/services/new-service-name301Navigation updated/blogs/retired-campaignCampaign ended, no successorNone410Removed from sitemap/blogs/printable-guideNeeds to stay reachableNoneCanonical to /blogs/topic-guideCanonical tag present

Keep the map in version control or a shared spreadsheet, and record who approved each change. When a redirect later causes a question, such as a visitor landing somewhere unexpected, the map shows why it was set up and who to ask.

Implement at the server or platform level

Google's redirect documentation recommends server-side redirects where possible, and says to use JavaScript redirects only if you cannot do server-side or meta refresh redirects. Configure redirects in your web server, hosting platform or CMS redirect manager, keep the list in one place and avoid mixing several systems that each redirect some URLs.

Test before and after release

Before release, run the full redirect map through a script that requests each old URL and records the status code, the number of hops and the final URL. Every row should return 301 or 308, reach its target in one hop and land on a page that returns 200. Run the same check after release, and again a few weeks later. In Search Console, the Page indexing report lists redirected URLs under page with redirect, which helps confirm that Google has seen them. Our guide to Next.js migration covers the same checks in the context of moving a whole site.

Frequently Asked Questions

What is a 301 redirect?

It is an HTTP response telling browsers and search engines that a page has moved permanently to another URL, which they should use instead.

Should I redirect duplicate pages or use canonical tags?

Redirect duplicates that nobody needs to visit. Use a canonical tag when both versions must stay reachable. Google treats both as strong signals.

How long should 301 redirects stay in place?

Google's site move guidance says to keep redirects for as long as possible, generally at least one year. Many sites keep them indefinitely.

Is it fine to redirect old pages to the home page?

Usually not. Redirect to the page that best replaces the old content. If nothing does, a 404 or 410 status is the more accurate response.

Restructure your site without losing ground

We plan redirect maps, merge duplicate content and test every redirect before and after release. See our technical SEO and content publishing service, or talk to us about 301 redirects.

About the Author

Manav Sharma is the founder of Insyrge and a CRM solutions architect. He works across Zoho, Salesforce, HubSpot, Odoo and more, designing the CRM setups, integrations and automations that keep sales and operations teams working from the same data.