Managing Redirects and URL Changes During a Website Migration

When a consultancy site is restructured, moving from old URLs to new ones can undo years of SEO progress if handled poorly. Broken links frustrate users, dilute authority, and signal instability to search engines. The fix is a rigorous redirect strategy: map every old URL to a relevant new one, implement 301s, and monitor performance.

Why URL Changes Threaten Search Visibility

Search engines treat each URL as a distinct entity. A sudden change without redirects means lost backlinks, dropped rankings, and users hitting 404s. For consultancies, where authority is built on thought leadership and case studies, that loss can be crippling. Even with redirects, poor mapping causes irrelevant matches that confuse algorithms and visitors alike.

The goal is to preserve link equity and user experience. Every old URL should point to the closest possible new page, not just the homepage. That requires a full inventory before you touch the site structure.

Step 1: Audit and Inventory Old URLs

Start with a complete crawl of the existing site using tools like Screaming Frog or a simple XML sitemap export. Collect every URL, including those buried in old blog posts, PDFs, and service pages. Then identify high-value pages by traffic and backlinks.

Use a table to prioritise. For example:

This table forces decisions: which redirects are essential, which can be consolidated, and which can be retired.

Step 2: Map Old URLs to New Ones

Mapping is not always one-to-one. Sometimes several old pages merge into one new page, or a page is split. For merged pages, redirect all old URLs to the single new page. For splits, redirect to the most relevant child page. Use 301 redirects (permanent) for SEO value.

Here is a simple process:

1. Export old URLs from your audit.
2. Match each to a new URL by topic and intent.
3. Flag any unmatched old URLs for manual review.
4. Implement redirects in your server config or CMS.

Never redirect everything to the homepage. That is a soft 404 and search engines will ignore the redirect value.

Step 3: Implement and Test Redirects

Use server-level redirects (e.g., in .htaccess or Nginx config) for speed. For large sites, a redirect map file works well. After implementation, test a sample of old URLs with a tool like HTTP Status Checker.

Common pitfalls include redirect chains (A to B to C) and loops. Keep it to a single hop. Also, update internal links to point directly to new URLs, reducing reliance on redirects.

"A redirect is a bridge, not a destination. Build it once, build it right, then let it retire."

Remember to update your sitemap and canonical tags. Submit the new sitemap to Google Search Console and monitor the Coverage report for 404s or soft 404s.

Step 4: Preserve Authority and Monitor

After launch, keep an eye on key metrics: organic traffic, rankings for target keywords, and crawl errors. Use a tool like Ahrefs or Semrush to track backlink changes. If a high-value old URL loses its redirect, fix it immediately.

Also, consider a temporary 302 redirect for pages that might return. But for permanent restructuring, 301 is correct. Finally, communicate changes to clients and partners who may link to old URLs.

• Audit all old URLs
• Map each to a relevant new URL
• Implement 301 redirects server-side
• Test for chains and loops
• Update internal links and sitemap
• Monitor search console for errors

With careful mapping and testing, you protect the search visibility your consultancy has earned. A migration is a chance to improve structure, not lose ground.