Web Design
Website Redesign Without Losing SEO: A Step-by-Step Migration Checklist
A new website should lift your visibility, not reset it. Here’s how to plan, launch and monitor a redesign so rankings and backlinks carry over.
Key takeaways
- Most traffic losses after a redesign come from changed URLs without redirects, lost content and broken tracking.
- Build a complete inventory of old URLs — including ones only backlinks still point to — before you design anything.
- Every old URL needs a 301 redirect to its closest new equivalent, not to the homepage.
- Watch Search Console and broken backlinks daily for two weeks after launch.
Why redesigns lose rankings
Search engines rank URLs, not designs. When a redesign changes URLs, removes pages or rewrites content without a plan, the signals those pages earned — links, history, relevance — don’t automatically follow. The result is the familiar post-launch traffic drop.
What usually goes wrong
- URLs change with no redirects
- Pages that ranked are cut or merged carelessly
- Content is shortened for the new design
- Redirects point everything to the homepage
- Analytics and conversion tracking break
- The staging site’s noindex goes live
What a good migration does
- Keeps URLs where possible
- Maps every old URL to its best new match
- Preserves or improves ranking content
- Uses page-to-page 301 redirects
- Re-tests tracking before launch
- Monitors daily after launch
What’s really at stake
A website that has been live for years has accumulated value you can’t see in the design: pages Google trusts for specific searches, links from other sites pointing at exact URLs, and content AI engines have learned to cite. None of that is stored in your theme. It lives in your URLs and your content — which is exactly what a careless redesign changes.
The good news is that protecting it is mostly process, not budget. A spreadsheet, a crawler, a few hours of careful mapping and two weeks of monitoring are enough for most small business sites. Skipping them is how a beautiful new website ends up with fewer enquiries than the old one.
Before you design: the inventory
Crawl the current site
Export every live URL with its title, status and word count using a crawler such as Screaming Frog or Sitebulb.
Add URLs from Search Console
The Pages and Performance reports show URLs Google knows about and which ones bring clicks — including some your crawl misses.
Add URLs that only backlinks point to
Ahrefs or Semrush show external links to old addresses — often pages you forgot existed. These carry authority you don’t want to lose.
Rank pages by value
Mark the pages that bring traffic, enquiries or backlinks. These must survive the redesign with their content intact or improved.
Build the redirect map
The redirect map is a simple spreadsheet: old URL in one column, new URL in the next. Every old URL gets a destination. The rules are short:
| Old page | Redirect to | Avoid |
|---|---|---|
| Page kept, URL changed | Its new URL (301) | Changing URLs you don’t need to change |
| Two pages merged | The merged page (301) | Losing the unique content from either |
| Page removed, topic covered elsewhere | Closest relevant page (301) | Redirecting to the homepage |
| Page removed, nothing relevant | Let it 404 or 410 | Mass redirects to unrelated pages |
| Old blog base (/articles/ → /blog/) | Pattern rule for every post | Redirecting only the top posts |
# Old blog base -> new blog base (keeps the post slug)
RedirectMatch 301 ^/articles/(.+)$ /blog/$1During the build
- Keep ranking content — rewrite to improve it, don’t trim it to fit a design.
- Carry over metadata — titles, descriptions and headings for pages that rank.
- Rebuild structured data — Organization, Service, Breadcrumb and FAQ markup (see schema for small businesses).
- Block staging from indexing — and write down who removes the block at launch.
- Recreate tracking — analytics, conversion events and call tracking, tested on staging.
Content: improve it, don’t trim it
Designers often want shorter pages. But the pages that rank usually rank because of their content — the detail, the answers, the specific terms customers search. Cutting a 1,200-word service page to 300 words for a cleaner layout is one of the most common causes of post-launch traffic loss.
The better approach is to design for the content: accordions, tabs and well-structured sections can keep long pages easy to read. If you’re rewriting, improve the substance — add pricing guidance, FAQs and proof — rather than reducing it. Our guide to Business Profiles covers the local signals worth keeping consistent through the change.
Launch day checklist
- Remove noindex / password protection from the live site
- Upload and test redirects — spot-check the top 50 old URLs
- Submit the new XML sitemap in Search Console
- Check robots.txt allows search and AI crawlers
- Test forms, calls-to-action and confirmation emails
- Confirm analytics and conversion events fire
- Update your Google Business Profile link if URLs changed
Common post-launch problems — and quick fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Traffic falls sharply overnight | Site-wide noindex left on, or robots.txt blocking | Remove the block, resubmit the sitemap |
| Spike in 404 errors in Search Console | Missing redirects | Add page-to-page 301s from the redirect map |
| Specific pages drop in rankings | Content cut or headings changed | Restore the key content and on-page signals |
| Enquiries drop but traffic is stable | Broken forms or tracking | Test forms end-to-end; check events fire |
| Old URLs still in Google weeks later | Redirect chains or soft 404s | Redirect directly to the final URL |
Almost every one of these is visible within days if someone is looking. That’s why the first two weeks after launch need daily checks, not a monthly report.
After launch: the first 90 days
- Days 1–14
Watch daily
Search Console coverage errors, 404s, crawl stats and conversions. Fix anything broken immediately.
- Weeks 3–6
Expect some movement
Rankings often fluctuate as Google recrawls. Compare against your pre-launch baseline, not yesterday.
- Weeks 6–12
Check backlinks and recover
Run a broken-backlink report and redirect anything still pointing at old URLs. Review which pages gained and lost.
Frequently asked questions
Will a redesign always cause a traffic drop?
No. With URLs preserved or redirected, content kept and tracking tested, many redesigns improve visibility. Short-term fluctuation is normal while Google recrawls.
How long should redirects stay in place?
Keep them permanently where possible. Old backlinks and bookmarks keep sending visitors for years.
Should I change my domain at the same time?
Only if necessary. Combining a domain change with a redesign makes problems harder to diagnose. If you do, use Search Console’s Change of Address tool.
Is redirecting everything to the homepage OK?
No. Search engines tend to treat irrelevant redirects like broken pages. Redirect each old URL to its closest relevant equivalent.
What about AI search after a migration?
The same rules apply: keep content, structured data and crawler access intact so AI engines can keep citing your pages.
Founder of Catnapweb and Professor at the Department of Marketing and Commerce, Comenius University. Author of 170+ research publications on AI in marketing and search visibility, cited 1,705 times. Full profile →
Services mentioned in this article
- AI-ready websitesMigration planned in from day one.→
- SEO servicesProtect and grow rankings after launch.→
- AI SEO servicesKeep AI engines citing your new site.→
