What is a redirect?
A redirect tells the browser and search engines that a page has moved from one URL to another. Instead of showing the old page, the server sends visitors to the new one.
In business terms, a redirect is like forwarding mail from an old office to a new one. If the forwarding is configured correctly, customers still find you. If not, deliveries get lost.
Why business owners should care
Redirects are not just a technical detail. They affect revenue, lead generation, user trust, and how much of your existing SEO value survives site changes.
Traffic protection
If old URLs still receive organic visits and they start returning 404 errors, you can lose qualified traffic that was already working for the business.
Lead and sales continuity
Product pages, service pages, and landing pages often keep generating demand long after they were first published. Broken redirects can interrupt that flow.
Preserving authority
Backlinks, internal links, and historical signals often point to old URLs. Redirects help transfer users and search engines to the correct new destination.
Operational clarity
A migration without URL mapping creates confusion across teams: SEO, content, product, paid media, and customer support all feel the consequences.
Main types of redirects
301 redirect: permanent
A 301 redirect tells search engines that a page has permanently moved. This is usually the right choice when a page has a clear replacement and you want the old URL to be replaced by the new one over time.
302 redirect: temporary
A 302 means the move is temporary. It can be appropriate for short-term testing, limited promotions, or temporary replacement pages. It is usually not the right default choice during a full CMS migration.
404: page not found
A 404 means the requested page does not exist. That is not always wrong. Sometimes a page should disappear. But if important pages become 404 by accident, it can damage organic performance and create a poor user experience.
410: intentionally gone
A 410 is stronger than a 404. It tells search engines that the page is intentionally gone and not coming back. This can be useful when a page has no relevant replacement and should leave the index.
What often happens during a CMS migration
During a CMS migration, page templates change, URLs are rewritten, categories are renamed, and old structures disappear. The new site may look clean on the surface, while underneath, old URLs that Google still knows about stop working.
This is a common pattern:
- Old URLs are indexed in Google
- Internal teams launch the new CMS
- Some old URLs are no longer mapped
- Those pages return 404 instead of redirecting
- Traffic drops quietly on affected landing pages
A practical example: postal delivery company
Imagine a delivery and parcel company migrating to a new CMS. The business keeps the same services, but the URL structure changes.
On the old website, service pages and location pages had built up visibility over time. After migration, some of those pages no longer existed under the same path. Search engines and users were still trying to access the old URLs, but several of them returned 404.
Example redirect audit table
| Old URL | What happened after migration | Recommended destination | Recommended action | Why it matters |
|---|---|---|---|---|
| /express-shipping | 404 | /services/express-delivery | 301 redirect | Old service page may still receive branded and non-branded search traffic |
| /same-day-delivery-madrid | 404 | /locations/madrid/same-day-delivery | 301 redirect | Users searching local services should land on the equivalent page, not an error |
| /track-your-package | Redirected to homepage | /tracking | Replace weak redirect with direct 301 | Sending users to the homepage creates friction and wastes intent |
| /pricing-2023 | 404 | No true replacement | Keep 404 or return 410 | If the page is outdated and irrelevant, it may be better to remove it cleanly |
| /business-shipping-solutions | Still live but linked internally to old URLs | /solutions/business-shipping | Update internal links + 301 redirect | Redirects help, but internal links should also point directly to the final destination |
What this means in plain business language
If a service page that used to rank in Google suddenly becomes a 404, you may lose the visitors who were already discovering you through search. If the page had strong intent, you may also lose enquiries or sales from users who were close to converting.
If a page is redirected to the homepage instead of the correct equivalent page, users may not find what they wanted. Search engines also get a weaker signal because the redirect is less relevant.
And if your internal links, sitemap, and navigation still point to old URLs, search engines waste time crawling outdated paths instead of focusing on the pages that matter now.
When a 404 is acceptable
Not every missing page should be redirected. If a page is outdated, has no useful replacement, and is no longer part of the business, a 404 or 410 can be the correct choice.
The important question is this: does the old page still have value?
- If the page has a clear equivalent, redirect it
- If the page still gets traffic, review it carefully
- If the page has backlinks, avoid wasting that value
- If the page has no useful replacement, it may be fine to let it go
What to check in a redirect audit
A proper redirect audit usually goes beyond “do redirects exist?”. It checks whether the redirect logic actually protects business value.
1. Indexed URLs
Check whether URLs already known by Google are still live, redirected correctly, or returning 404.
2. High-value pages
Review service pages, product pages, location pages, and lead-generation pages first, because these are the ones most likely to affect revenue.
3. Internal links
Even with redirects in place, internal links should point directly to the final destination whenever possible.
4. Redirect chains
Avoid sequences like old URL → temporary URL → final URL. These slow down the path and create unnecessary complexity.
5. Sitemaps and canonical signals
Make sure XML sitemaps and canonical tags reflect the new live URLs, not outdated ones.
6. Real destination relevance
A redirect should send users to the closest relevant page, not just “somewhere on the site”.
My view in practice
Redirect work is often underestimated because the issue is not always visible in the design. A new site can look better while performing worse underneath. That is why redirect audits matter most around redesigns, CMS migrations, content consolidation, and changes in site structure.
The goal is not to redirect everything blindly. The goal is to preserve the pages that matter, remove what no longer serves the business, and make sure users and search engines always reach the most relevant destination.
Need help reviewing redirects or migration risks?
If you have changed CMS, redesigned key sections, or suspect that valuable pages are now broken or misrouted, I can help review the situation and identify the highest-priority issues.
This is not a promise to fix every issue instantly. It is a practical first review to understand what is happening, what is at risk, and what should be prioritized.