Redesign Without the Rankings Crash: A Migration Checklist for 301s and Content Mapping

The most expensive part of a website redesign is rarely the design. It’s the traffic that disappears the week after launch. We’ve audited sites around Metro Vancouver that lost half their organic visits after a rebuild — not because the new site was worse, but because nobody mapped the old URLs to the new ones. Google went looking for pages it had ranked for years, hit 404s, and quietly dropped them. Recovering that usually takes months; preventing it takes an afternoon of spreadsheet work.

Here is the checklist we run on every migration, in the order we run it.

Why do rankings drop after a redesign?

Rankings live at the URL level, not the website level. When your services page moves from /services.html to /what-we-do without a redirect, Google doesn’t see a renamed page — it sees one page dying and an unknown new one appearing. All the link equity, ranking history and indexed status attached to the old URL evaporates instead of transferring.

Three failure modes account for most crashes we see:

• Missing or lazy redirects — no 301s at all, or everything redirected to the homepage (Google treats mass homepage redirects as soft 404s).
• Content deleted without a decision — old blog posts and service pages that quietly ranked get culled because they “look dated.”
• Technical regressions — the new build ships with noindex tags left over from staging, broken canonicals, or a blocked robots.txt. This one is embarrassingly common.

Step one: inventory every URL that matters

Before anyone touches the new site’s structure, export three lists and merge them:

1. A full crawl of the current site (Screaming Frog or similar) — every indexable URL.
2. Search Console performance data, last 12 months — every URL that earned at least one click or meaningful impressions.
3. Backlink targets from Ahrefs, Semrush or Search Console’s links report — every URL another site points to.

The union of these lists is your migration inventory. In our experience, small business sites typically have far more URLs earning search traffic than the owner expects — old blog posts, a location page, sometimes even a PDF. Anything on that list is an asset, not clutter.

How do you build the content mapping sheet?

One spreadsheet, one row per old URL, three columns: old URL, new URL, decision. Every row gets exactly one of three decisions:

• Keep — the page moves to a new URL (or keeps its old one — the best redirect is no redirect). Write a one-to-one 301 to the closest equivalent page.
• Merge — several thin pages combine into one stronger page. 301 each old URL to the merged page.
• Retire — the page has no traffic, no links and no purpose. Let it return a 410 or 404 honestly. Do not redirect junk to your homepage.

The rule that saves rankings: redirect to the page that serves the same intent, not the nearest category. A post about wedding videography pricing should point to the new wedding video page, not a generic “our work” gallery.

What should you check on launch day?

The go-live checklist, in order:

1. Deploy 301s (server-level, not JavaScript) and spot-check your top 20 URLs by traffic manually.
2. Remove staging noindex tags and verify robots.txt allows crawling. Check this twice.
3. Crawl the redirect map: every old URL should return exactly one 301 hop to a 200 page — no chains, no loops.
4. Submit the new XML sitemap in Search Console; keep the property, don’t start a fresh one.
5. Verify analytics and conversion tracking fire on the new templates.

Then watch Search Console daily for two weeks. A dip of a week or two while Google recrawls is normal; 404 spikes and steady decline past week three are not — that’s your cue to find the unmapped URLs.

FAQ

How long should we keep the 301 redirects in place?

Treat them as permanent. Google needs months to fully consolidate signals, and backlinks pointing at old URLs keep paying off only while the redirect lives. Removing redirects after a year is a common way to lose equity twice from one migration.

We’re only changing the design, not the URLs. Are we safe?

Safer, but not safe. Same-URL redesigns still fail through leftover noindex tags, slower templates, thinner on-page copy, or heading structures that drop the keywords the old pages ranked for. Run the launch-day technical checks regardless, and compare old vs. new copy on your top pages before signing off.

We already relaunched and traffic tanked. Can it be recovered?

Usually, yes — if you act quickly. Pull the old URL list from Search Console and the Wayback Machine, build the mapping sheet retroactively, and deploy the missing 301s; most of the equity is recoverable while Google still remembers the old pages. This is work we do regularly at Moncepts, both rescue jobs and redesigns where the checklist runs from day one. If you’re planning a rebuild — or just did one and watched the graph fall — email us at team@moncepts.com and we’ll take a look before more equity leaks away.