301 Redirects: The Migration Step That Saves SEO

301 redirects are the step that protects your SEO during a website migration because they tell browsers and search engines where each old URL moved. Skip them, and the move that looked fine on launch day can quietly throw away rankings, backlinks, and enquiries.

A lot of owners only hear about redirects late in the job, which is a red flag. If someone is rebuilding or migrating your site and they have not talked about URL mapping, they are either assuming too much or they have not done enough migrations. Redirects are not polish. They are part of the move.

What is a 301 redirect in plain words?

A 301 redirect is mail forwarding for the internet. Someone goes to the old address, and the web sends them to the new one permanently.

That matters for humans and for Google. A visitor who clicks an old link still reaches the right page instead of a dead end. Google also gets a strong signal that the old page moved, which helps transfer relevance and link value over time.

Without that forwarding, the old page becomes a 404 or lands somewhere unrelated. The business owner often says, “but the new site is live and looks better”. That can be true while the search equity gets damaged underneath. Design and migration health are different things.

I cover the broader process in platform migration and in the project examples under work. Redirects are the detail that often decides whether those migrations feel smooth or painful.

How do you build the redirect map?

You build it in a spreadsheet before launch. One old URL, one destination URL, one clear status. Do not try to remember it in your head on cutover day.

Start by crawling or exporting every meaningful page from the current site. That includes main pages, blog posts, service pages, location pages, and anything that has traffic, backlinks, or business value. Then line them up against the new site structure. Most migrations fail here because people only map the top-level pages and forget the long-tail pages that still rank.

The good version of this process is calm. You can see gaps before launch. Maybe the new site does not yet have a page that matches an old article. Maybe two old services have been merged into one page. Fine, but document it intentionally. A redirect map is not only technical admin. It forces the migration to admit what content is moving, merging, or dying.

If the site has years of content, the spreadsheet can be long. That is still better than guessing live. When someone says “we’ll just redirect everything to the homepage”, that is not a shortcut. It is a bad migration.

When do exact redirects beat pattern redirects?

Exact redirects are better when the old pages matter individually. Pattern redirects help when the structure is clean and repeating. Most real migrations use both.

An exact redirect says this specific old page goes to this specific new page. That is ideal for service pages, blog posts that rank, and anything with backlinks. It preserves intent. A person looking for one article should not land on a broad category page if a matching article exists.

Pattern redirects help with cleaner structural changes. If a whole blog moved from one folder to another and the slugs stayed consistent, a pattern can save time. The risk is that owners or rushed developers use patterns where the content no longer lines up. Then lots of URLs point somewhere roughly related but not actually right.

The honest rule is simple. If accuracy matters, map it exactly. If the structure is genuinely consistent, pattern rules can help. Use them because the content fits, not because the spreadsheet feels long.

How should you test redirects before launch?

Test every important redirect before launch and test again after cutover. A redirect only counts when it actually resolves correctly.

I like checking the map in batches. Open the old URLs, confirm they land on the intended pages, and make sure there is no chain or loop. A chain is when one redirect points to another redirect before the final page. It can still work, but it is messy and weak compared with a direct route.

Testing also catches the human mistakes. A typo in one slug. A trailing slash mismatch. A page that was meant to exist on the new site but was never built. The migration spreadsheet tells you what should happen. The test tells you what actually happens.

This matters just as much on staging as on launch. If you can prove the redirect logic on staging, the live cutover becomes much less dramatic. That is one reason I prefer parallel builds and controlled swaps instead of chaotic rebuilds in place.

How long should redirects stay live?

Redirects should stay live for years, not weeks. If an old page had links, bookmarks, or search history behind it, the redirect is still doing useful work long after launch day.

Owners sometimes ask if they can clean them up after a month because the migration feels finished. Usually that is too early. Old blog posts can keep attracting visitors. Other sites can keep linking to old URLs for years. Printed materials, old email campaigns, and saved browser bookmarks all continue existing after the developer moves on.

Redirects are cheap compared with lost visibility. Unless there is a very specific reason to remove one, leave it in place. The internet has a long memory.

If you are planning a move and want the whole cutover handled properly, read this next with pricing so the migration scope includes the boring but important bits. The clean migration is the one that feels boring to the customer.

Quick answers

What does a missing redirect cost?

It can cost lost rankings, broken backlinks, and frustrated visitors. Sometimes the damage is small, sometimes it hits pages that were quietly bringing leads for years.

Redirect chains: how bad?

They are not ideal. One extra hop may still work, but a direct redirect is cleaner, faster, and easier for search engines to understand.

Can I redirect everything to the homepage?

No, not if you care about user intent or SEO. A redirect should send people to the closest relevant page, not a generic catch-all.

Thinking of moving? Send me your site on WhatsApp and I’ll tell you what a clean migration needs: platform migration.