Why website redesigns lose rankings, and the migration checklist that prevents it

A redesign is the most common way a business damages its own search visibility. The new site looks better, loads faster, and three weeks after launch enquiries drop because half the pages Google was ranking no longer exist. The fix is unglamorous: inventory, mapping, validation. This is the checklist we run.

Before you touch anything

Inventory every URL. Crawl the live site, export Search Console's "Pages" report, and check the Wayback Machine for pages that have been quietly deleted over the years. The crawl alone misses orphaned pages that still rank.

Find out which pages matter. From Search Console and analytics: which URLs receive impressions, clicks and conversions, and which have external links pointing at them (the "Links" report, or a backlink tool). These pages must either keep their URL or redirect to a close equivalent.

Record the metadata. Titles, meta descriptions, canonical tags, structured data and image alt text for every page that matters. You will want to reuse the good ones.

Decide what to retire. Thin pages, template demo content, duplicate "about-us-2" pages and doorway pages for every city dilute the site. Retiring them helps, provided it is done with the right status code (410 for gone, 301 only where a real successor exists).

Build the map

Every old URL gets exactly one of three fates:

1. Keep the same URL (best for ranking pages).
2. Redirect permanently (301) to the single most relevant new page. Not the homepage; a redirect to an unrelated page is treated as a soft 404.
3. Retire with a 410 Gone, so search engines drop it quickly.

Write the map down and review it with whoever knows the business. A developer will not know that the "digitizing" page is a real service and "pricing-3" is a leftover template.

During the build

• Keep trailing-slash and www/non-www behaviour consistent, with one canonical form.
• Generate the sitemap from the content model, not by hand, and exclude anything noindexed.
• Preserve or improve titles and descriptions; do not let a CMS default overwrite them.
• Carry over structured data (Organization, FAQ, Breadcrumb, Service, Article) where it is eligible.
• Keep internal links pointing at final URLs, never through redirect chains.
• Stage the site somewhere search engines cannot index it, and test the redirect map there with a script, not by clicking.

Launch day

• Deploy redirects and the new site together; a gap of hours is enough to create 404s in the index.
• Submit the new sitemap in Search Console and request indexing for the key pages.
• Check robots.txt is the production version, not the staging "disallow all".
• Verify analytics and conversion tracking fire on the new pages with the same event names.

After launch, for at least eight weeks

• Watch Search Console daily for the first week: Coverage errors, "Page with redirect", and 404s from URLs you missed.
• Compare clicks and impressions for the mapped pages week over week; some fluctuation is normal, a sustained drop on a specific page means its redirect or content needs attention.
• Check that external links still resolve, and ask referring sites to update important ones.
• Keep the redirects in place indefinitely. Removing them a year later reopens the wound.

The one thing people skip

Access. The person doing the migration needs Search Console and analytics access before planning, not after launch. Without data, every decision about which pages matter is a guess, and guesses are how rankings get lost.

If you are planning a redesign and want the inventory and redirect map handled properly, talk to us. The mapping work is a fraction of the project cost and the cheapest insurance you can buy for the traffic you already have.