Table of Contents
A website redesign is one of the most common causes of a sudden, unexpected drop in Google rankings. The redesign launches, the site looks better than ever, and two weeks later the traffic report shows organic visits have fallen by 40%.
It doesn't have to happen this way. A redesign can be executed cleanly — with no loss of ranking and no organic traffic disruption — if the SEO work is done properly before, during, and after the migration. This is exactly how we do it.
Step 1: Audit the Current Site Before You Touch Anything
Before any design work begins, audit what you have. Document every URL that has organic traffic in Google Search Console. Export your current page rankings. Note which pages have backlinks pointing to them. Record the current Core Web Vitals and PageSpeed scores. This is your baseline — everything in the new site needs to be mapped against it.
Most ranking drops after a redesign are caused by someone changing URLs without implementing redirects. The audit prevents this by making the existing URL structure visible before the redesign changes it.
Step 2: Map All URL Changes with 301 Redirects
If the new site changes any URLs — and most redesigns do — every old URL needs a 301 redirect to the equivalent new URL. A 301 tells Google the page has moved permanently and transfers the ranking signals (and backlink equity) to the new location. Without 301 redirects, any URL that changes becomes a 404 for Google — and any rankings associated with it are lost.
Create a redirect map before development begins: old URL on the left, new URL on the right. Implement it in WordPress before the site goes live. Test every redirect before launch.
Step 3: Migrate All Meta Data to the New Site
Every page's meta title and meta description should be migrated to the new site — not rewritten wholesale unless there's a specific reason. Your existing meta titles have accumulated ranking signals over time. Changing them all at once introduces unnecessary variables into a migration that already has enough moving parts.
Step 4: Implement Schema Markup on the New Site
If the old site had schema markup, verify it's correctly implemented on the new one. If it didn't, the redesign is an ideal time to add it. Organization, ProfessionalService, BreadcrumbList, and FAQPage schema should be implemented and validated with Google's Rich Results Test before the new site launches.
Step 5: Manage the Launch Day Properly
Go-live day needs to be managed in a specific order: implement all 301 redirects before switching DNS, switch DNS, verify the redirects are live, resubmit the XML sitemap in Google Search Console, request indexing of key pages, and verify that all important pages are not accidentally blocked in robots.txt. Monitor Search Console for coverage errors in the first 72 hours. Any new 404s should be investigated and redirected immediately.
Step 6: Monitor Performance for 4–6 Weeks Post-Launch
A properly executed redesign should see organic traffic stabilise within 2–4 weeks. Some fluctuation is normal as Google re-crawls the site. If you see significant drops that don't recover after 4 weeks, check: are all redirects in place? Are all important pages indexed? Are any pages incorrectly blocked? Has the site's Core Web Vitals performance changed significantly?
Tell Us Where You're Based and What You Need
Frequently Asked Questions
The most common causes: URLs changed without 301 redirects (pages become 404s and lose their ranking history), meta titles and descriptions rewritten unnecessarily (changes to ranking signals), pages accidentally blocked by robots.txt during development and not unblocked on launch, significant performance changes that affect Core Web Vitals scores, and removal of content that had accumulated ranking signals.
A 301 redirect is a permanent redirect from one URL to another. It tells Google that the page has moved and transfers the ranking signals (including backlink equity) from the old URL to the new one. Without 301 redirects for any URL that changes during a redesign, those URLs become 404 errors and any rankings associated with them are lost.
For a properly-executed redesign, rankings typically stabilise within 2–4 weeks. Some short-term fluctuation is normal as Google re-crawls and re-evaluates the site. Significant drops that persist beyond 4–6 weeks indicate a technical issue that needs investigation — usually missing redirects or indexing problems.
Only if there's a good reason — and always with 301 redirects in place. Changing URLs for the sake of it introduces unnecessary risk. If the existing URL structure is SEO-appropriate (descriptive slugs, logical hierarchy), keep it. If the existing URLs are poor (random numbers, session parameters, or duplicate structures), a redesign is a good time to fix them — with redirects from every old URL.
Yes. A redesign done correctly — with a pre-launch audit, full redirect map, meta data migration, schema implementation, and a managed launch process — should maintain organic rankings. We've executed dozens of redesigns without meaningful ranking loss. The key is treating the SEO work as part of the project, not an afterthought.
A domain migration carries more risk than a same-domain redesign. It requires every URL on the old domain to redirect to the new domain, a domain change declaration in Google Search Console, and typically a longer recovery period. Only migrate domains if there's a compelling business reason. If you do, manage it as a separate project from the redesign.
Before go-live: verify all 301 redirects are live, confirm robots.txt is not blocking important pages, validate XML sitemap is correct and submitted to Search Console, test Core Web Vitals on mobile and desktop, validate schema markup, test meta titles and descriptions on all key pages, check mobile responsiveness on real devices, and confirm contact forms and CTAs are working.
Compare Google Search Console performance data (impressions and clicks) before and after the launch. Look for pages that had consistent traffic that have dropped to zero — these are usually redirect or indexing issues. Also run a crawl of the new site to check for 404 errors and compare the URL list to your pre-launch audit.
Not directly — Google doesn't rank pages on visual design. But design decisions affect conversion rates and user engagement signals (time on page, bounce rate), which Google interprets as relevance signals. A redesign that significantly worsens user experience can affect rankings indirectly over time.
Yes. Every redesign project we take on includes a pre-launch SEO audit, full redirect mapping, meta data migration, schema implementation, and a managed launch process. We've handled redesigns across hundreds of sites without meaningful organic traffic loss.
