Why websites lose traffic after a redesign
| Mistake | What happens | How to avoid it |
|---|---|---|
| URLs changed with no redirects | Old links and rankings lead to 404 errors | Map and 301-redirect every old URL |
| All old URLs redirected to the home page | Google may treat them as soft 404s | Redirect each page to its closest new equivalent |
| Ranking pages shortened or removed | Google no longer sees the content it ranked | Keep or improve the text on top pages |
| Staging noindex or robots.txt block left live | The whole site can drop out of Google | Remove blocks at launch and test immediately |
| New site is slower | Worse user experience and Core Web Vitals | Set a speed target and test before launch |
| Domain, CMS and design changed at once | Problems are hard to trace and fix | Change one thing at a time |
Google’s own site-move guide recommends that last point directly: if you plan a new domain, a new CMS and a new design, do them one after another.
Phase 1: Before you design anything
- Benchmark your traffic. Export the last 12 months of clicks and impressions by page from Google Search Console, and sessions and conversions by page from Google Analytics.
- List your money pages. Mark the 20 to 50 pages that bring the most traffic, leads or sales.
- Find pages with backlinks. Use Search Console’s Links report to see which pages other sites link to.
- Find pages AI engines already cite. Check Search Console’s Generative AI report and Bing Webmaster Tools’ AI Performance report. Treat these pages as protected.
- Crawl the old site. Use a crawler such as Screaming Frog to export every URL, title, meta description and H1, plus images and PDFs.
Phase 2: While the new site is built
- Keep URLs the same wherever you can. Unchanged URLs need no redirects and carry the least risk.
- Build a redirect map in a spreadsheet, one row per old URL:
| Old URL | New URL | Redirect type | Notes |
|---|---|---|---|
| /services/seo/ | /seo-services/ | 301 | Merged into one service page |
| /blog/old-post-name/ | /blog/new-post-name/ | 301 | Same content, new slug |
| /offer-2023/ | (none) | 410 | Expired, no equivalent page |
- Protect your content. Carry over the text, headings, internal links and structured data of your top pages. Redesign the look, not the substance.
- Block the staging site with a password, or noindex, and note every block you must remove at launch.
- Set a speed budget, for example mobile Largest Contentful Paint under 2.5 seconds, and test key templates with PageSpeed Insights.
- Update internal links to point at the new URLs directly, not through redirects.
Phase 3: Launch day
- Launch during your lowest-traffic period.
- Switch on the 301 redirects and test a sample, plus all money pages.
- Remove staging noindex tags and robots.txt blocks.
- Check every page has a self-referencing canonical tag on the new URL.
- Submit the new XML sitemap in Search Console and Bing Webmaster Tools.
- Use Search Console’s Change of Address tool only if the domain or subdomain changed.
- Make sure analytics and Search Console verification still work on the new site.
Phase 4: The first 8 weeks after launch
- Week 1: check Search Console daily for 404 errors and indexing problems, and fix broken redirects at once.
- Weeks 2 to 4: compare clicks and rankings for your money pages against the benchmark.
- Weeks 4 to 8: check Core Web Vitals, AI citations and conversions. Ask sites that link to you to update their links.
Google says a small to medium site usually takes a few weeks for most pages to move to new URLs, and rankings can fluctuate meanwhile. Keep redirects in place for at least a year, and ideally permanently.
Changing platforms: Wix, Shopify or custom to WordPress (and back)
Platform moves almost always change URL patterns. Blog posts may move from /post/title to /blog/title, products from /products/item to /shop/item, and image URLs change completely. Treat a platform move as a full site move:
- Export every URL from the old platform, including blog posts, category pages, images and PDFs.
- Map old patterns to new ones, then check exceptions one by one.
- Recreate titles, meta descriptions and alt text, which often don’t migrate automatically.
- Rebuild forms, tracking codes and structured data on the new platform.
- Test that old URLs redirect with a 301, not a 302 or a JavaScript redirect.
How to build a redirect map quickly
- Export all URLs from a crawl of the old site and from Search Console’s Pages report.
- Add traffic (Search Console clicks) and backlinks (Links report) to each row.
- Sort by importance and map the top 20% by hand: these carry most of your traffic.
- Use pattern rules for the rest, such as a whole blog folder moving.
- Mark pages with no equivalent as 410 (gone) or redirect them to the closest relevant page, never all to the home page.
- Test every mapped URL after launch with a crawler set to list mode.
Pre-launch QA checklist
| Check | Pass condition |
|---|---|
| Redirects | All mapped URLs return a single 301 to the right page |
| Indexing | No noindex tags on live pages; robots.txt allows crawling |
| Canonicals | Every page points to its own new URL |
| Content | Top pages keep their text, headings and internal links |
| Metadata | Titles and descriptions transferred |
| Structured data | Organization, Article and other schema present and valid |
| Speed | Key templates meet Core Web Vitals targets |
| Tracking | Analytics, conversion tags and Search Console verification working |
| Forms | Every form submits and reaches the right inbox or CRM |
| AI crawlers | Key content visible in raw HTML; search bots not blocked |
What to do if traffic drops after launch
- Check for blocks first: robots.txt, noindex tags and password protection left from staging.
- Check redirects: look for 404 spikes in Search Console and fix missing redirects.
- Compare money pages: see whether specific pages lost rankings and whether their content changed.
- Check rendering: use URL Inspection to confirm Google sees the full content.
- Give it time: if everything is correct, small fluctuations usually settle within a few weeks.
Redesigning for AI search: extra checks
A redesign is the best moment to make your site easier for AI engines to read and cite:
- Keep pages AI engines already cite. Check Search Console’s Generative AI report and Bing’s AI Performance report before you change them, and keep their core answers intact.
- Render content on the server. New themes and frameworks sometimes load text through JavaScript; most AI crawlers won’t see it.
- Don’t block AI search crawlers in the new robots.txt or security settings.
- Restate key facts clearly on the About and service pages: what you do, for whom, where and at what price.
- Carry over or add Organization schema with links to your official profiles.
- Verify the new site in Bing Webmaster Tools, since Bing’s index feeds Microsoft Copilot.
Tell the world about the change
Google’s site-move guide recommends updating links you control as soon as the move starts. After launch, update:
- The website link on your Google Business Profile.
- Links on LinkedIn, Instagram, Facebook, YouTube and other profiles.
- Directory listings that point to old URLs.
- Final URLs in Google Ads, Meta ads and other campaigns.
- Email signatures, WhatsApp Business profile links and printed QR codes where possible.
- Important backlinks: ask partners linking to old pages to update them.
Typical timeline for a small-business redesign
| Week | Activity |
|---|---|
| 1 | Benchmark traffic, crawl the old site, list money pages and backlinked pages |
| 2 to 3 | Design and content planning; draft the redirect map |
| 4 to 6 | Build on staging; carry over content, metadata and schema |
| 7 | Pre-launch QA: redirects, indexing, speed, tracking and forms |
| 8 | Launch during a quiet period; submit sitemaps |
| 9 to 16 | Monitor Search Console daily at first, then weekly; fix issues fast |
Larger sites with thousands of pages need longer, and Google recommends moving them in sections if that’s technically possible.
Content decisions: keep, improve, merge or remove
A redesign is a chance to clean up content, but every decision should be based on data:
| Page situation | Decision | What to do with the URL |
|---|---|---|
| Brings traffic, leads or links | Keep, and improve if possible | Keep the same URL, or 301 to its new URL |
| Useful but outdated | Improve and update | Keep the URL; refresh content and date |
| Several thin pages on one topic | Merge into one strong page | 301 each old URL to the merged page |
| No traffic, no links, no purpose | Remove | Return 404 or 410 |
| Seasonal or campaign page that may return | Keep but hide from navigation | Keep the URL live |
Use Search Console clicks and the Links report to decide, not opinions about which pages “look old”.
Tools you’ll need for a safe redesign
| Tool | What you use it for |
|---|---|
| Google Search Console | Benchmarks, Links report, Pages report, URL Inspection, sitemap submission |
| Bing Webmaster Tools | Bing indexing and Copilot citation data |
| A site crawler (such as Screaming Frog) | Exporting old URLs and testing redirects in bulk |
| A redirect manager (server rules or a WordPress redirect plugin) | Implementing 301 redirects reliably |
| PageSpeed Insights | Checking Core Web Vitals on key templates |
| Google Analytics 4 | Comparing traffic and conversions before and after launch |
Most of these are free, and Google’s own site-move guide points to crawler-based testing as the way to confirm redirects work as expected.
Keep your tracking working through the switch
A redesign can quietly break the tools that tell you whether it worked. If analytics stops recording for a week, you can’t tell a real traffic drop from a tracking gap. Before launch, list everything that measures the site, test each item on the staging site, and test it again on launch day:
- Google Analytics 4: the tag fires on every template, including blog posts, landing pages and thank-you pages.
- Key events: form submissions, phone clicks, WhatsApp clicks and purchases are still recorded, with the same event names, so reports compare cleanly.
- Search Console: verification still works. A domain property verified through DNS survives a redesign; verification by HTML file or meta tag can disappear with the old theme.
- Advertising tags: Google Ads, Meta and LinkedIn conversion tags still fire on the right pages.
- Forms: every form delivers to the right inbox or CRM, and auto-replies still go out.
- Links you don’t control on the site: call-tracking numbers and UTM-tagged links in emails, ads and your Google Business Profile still land on live pages.
Record the launch date wherever your team reads reports, so anyone looking at the numbers later knows when the new site went live. Then compare the four weeks after launch with the four weeks before, page by page, using the redirect map to match old URLs to new ones. If your business is seasonal, compare with the same weeks last year as well.
Frequently asked questions
Will redesigning my website hurt my SEO?
Not if you keep URLs or redirect them properly, keep the content that ranks, and remove staging blocks at launch. A well-planned redesign often improves rankings through better speed and structure.
How long does it take to recover rankings after a redesign?
Small fluctuations usually settle within a few weeks. A large drop that lasts longer usually points to missing redirects, removed content or blocked pages, so audit those first.
Should I use 301 or 302 redirects?
Use 301 (or 308) permanent redirects for pages that have moved for good. Google confirms that permanent redirects do not lose PageRank.
Do I need to tell Google about my redesign?
Submit your new sitemap in Search Console. Use the Change of Address tool only if you move to a new domain or subdomain.
How long should I keep redirects?
Google recommends at least one year, and for users, ideally forever. Avoid chains: point each old URL straight to its final destination.
Should I change my domain and redesign at the same time?
Google recommends changing one thing at a time. Move the domain first, let it settle, then launch the new design, so any problems are easier to trace.
Do I need to redirect image and PDF URLs?
Yes, if they get traffic or links. Google’s site-move guide recommends including images, downloads and other files in your move plan.
Can I delete old pages during a redesign?
Yes, but delete deliberately. Return a 404 or 410 for pages with no replacement, and redirect pages that have a close equivalent. Don’t delete pages that bring traffic or links without a plan.
Will changing my website’s design alone affect rankings?
A visual change with the same URLs and content usually has little effect. Rankings change when URLs, content, internal links, speed or technical settings change, so those are what to protect.
Who should own SEO during a redesign?
Named responsibility matters. Give one person, in-house or at your agency, ownership of the redirect map, pre-launch QA and post-launch monitoring, with authority to delay launch if checks fail.
Planning a redesign? See our website redesign service or get a free pre-launch SEO check.
