The horror story is common because it’s real: a business redesigns its website, the new site looks great, and within six weeks organic traffic is down 60%. The design didn’t cause it. The migration nobody did caused it. A website redesign and good SEO are not in conflict; they only collide when nobody owns the move. Here’s the complete process for redesigning without losing what Google has already given you.
Google doesn’t rank your design. It ranks your URLs, and a redesign that changes them without a map is starting over on purpose.
Before the redesign: inventory what you’re protecting
Open Google Search Console and export every page that received clicks in the last 12 months. Add every URL with backlinks. This list is your protected inventory. Every URL on it either survives the redesign at the same address or gets a 301 redirect to its closest replacement. Pages with zero traffic and zero links can die freely; pages with either cannot.
Where to find the full list
- Search Console Performance report: filter to the last 12 months and export the Pages tab.
- Search Console Links report: the top linked pages show which URLs other sites point to.
- Your analytics: landing pages that bring in visitors from email, ads or social, not just search.
- A crawl of the current site: the complete list of URLs, so nothing is forgotten because it had a quiet year.
The URL decision: keep or map
The safest redesign keeps URLs identical: same content at the same addresses, new design around it. When URLs must change (new structure, merged pages, renamed services), build a spreadsheet: old URL in column A, new URL in column B, one row per protected page. No wildcards for important pages, redirect each URL to its most relevant counterpart, not everything to the homepage. Mass homepage redirects are treated as soft 404s and the equity evaporates.
Point every redirect straight at its final address. A chain of old URL to interim URL to new URL slows crawling and wastes visits. Google’s guide to redirects and Google Search explains why permanent server-side redirects are the right tool for a move.
Carry the metadata, not just the content
Title tags and meta descriptions took years to earn their click-through rates. Migrate them field by field. The same goes for heading structure on your ranking pages: if a page ranks with an H1 that says "Contractor Website Design," the redesigned page keeps that H1, the design around it can change completely.
The less visible details travel too: image alt text, structured data, canonical tags and internal links. Update internal links to the new URLs directly instead of leaving them to redirects. Check that canonicals point to the live domain, not the staging address the site was built on.
Test on staging before launch
Most launch-day problems can be caught a week earlier. While the new site is still on staging, run these checks:
- Load the old URLs from your spreadsheet against the new site and confirm each one lands on the right page.
- Compare titles, descriptions and headings on your top pages with the old versions.
- Test the new design’s speed on a phone. A redesign is the cheapest moment to get Core Web Vitals right, before content is poured into a slow template.
- Submit every form and confirm the messages arrive.
Launch day: the technical checklist
Redirects live before anything else
The 301 map goes live the same minute the new site does. Every hour of gap is 404s served to Google.
Kill the accidental blockers
The classic redesign disaster: the staging site’s "discourage search engines" setting or a blanket noindex ships to production. Check robots.txt and the indexing settings within the first hour.
Resubmit and re-verify
Submit the new XML sitemap in Search Console, keep the old sitemap available briefly so Google can process the redirects, and run a crawl (Screaming Frog’s free tier covers small sites) to catch broken internal links and redirect chains.
The two weeks after: watch like it’s your job
Search Console’s Coverage (now called Page indexing) and Performance reports tell you within days if something’s wrong: spiking 404s mean missed redirects; falling impressions on a specific page mean its redirect or content lost something important. Small dips for 2 to 4 weeks are normal while Google re-crawls: sustained drops on specific pages are fixable signals, but only if someone is watching.
Google’s own site move documentation is worth reading before any migration; it’s the closest thing to the referee’s rulebook. If a page is still missing from results well after the dip, work through why a website is not ranking on Google to find the cause.
The part nobody budgets: content parity
Redesigns love to "clean up" pages by cutting text. That 800-word service page ranking for a dozen long-tails becomes a sleek 150-word section, and the rankings go with the words. Modern design and substantial content are not enemies; collapsible sections, tabs, and good typography carry full content beautifully.
Website redesign SEO mistakes to avoid
- Changing everything at once. A new domain, new URLs and new content in one launch makes any drop impossible to diagnose. Change as little as the project allows.
- Deleting pages without a redirect. Even an old page with a few backlinks deserves a 301 to its closest match.
- Relying on the homepage as a catch-all. It hides the problem from you, not from Google.
- Stopping after launch week. Plugins, forms and redirects still need watching. Fold the new site into a routine like my website maintenance checklist.
A redesign done this way typically comes out of the dip ahead, because the new site is faster and better structured than the old one. That’s the standard my redesign service is built around: every project includes the full migration map, and keeping your rankings is part of the deliverable, not an add-on.
