Indexing Collapsed After a Redesign: How to Recover
Key takeawayA post-redesign indexing collapse usually traces to three kinds of change: the URL structure changed, the content templates changed, or the rendering method changed. The key to recovery is not "resubmitting" but locating each change point and correcting it.
When this applies
- Sites with a clear indexing drop after a redesign launch
- Sites where GSC shows many pages as "Discovered - currently not indexed"
- Sites that switched themes or rewrote the frontend framework
- Sites that changed category hierarchy or navigation structure
| Change type | Typical symptom | Severity | Recovery action |
|---|---|---|---|
| URL structure change | Mass 404s | High | Map each URL with 301s |
| Template change | Page content shrinks or duplicates | High | Restore differentiated content |
| Frontend framework rewrite | Crawlers receive an empty shell | High | Move to server-side rendering |
| Navigation hierarchy change | Internal links broken | Medium | Rebuild internal links |
| Bulk title and description changes | Rankings swing widely on affected pages | Medium | Change in small batches |
| robots or canonical broken | The whole site deindexes | High | Diff every config item before vs. after |
Step-by-step diagnosis
- Export GSC data from before and after the redesign and compare: indexed counts, coverage distribution, average position.
- Diff one copy each of robots.txt, canonical rules, and the sitemap from before and after the redesign to find configuration drift.
- Export all old-site URLs and check their current status codes; build a 301 mapping for every non-200 one.
- Fetch 20 random new pages with curl and confirm body text, titles, and internal links exist in the raw source.
- Check internal links: can every important page be reached within two steps of the homepage on the new site?
- Use "Request Indexing" in GSC and resubmit the new sitemap for recrawling.
- Watch the recovery curve for four weeks in batches, and hold off further structural changes during recovery.
Common mistakes
- Submitting the sitemap right after the redesign and considering it handled — 404s and broken signals do not fix themselves.
- Rewriting content and changing structure in the same redesign — when problems appear you cannot attribute the cause.
- Rolling bulk title changes and structural changes into the same release.
- 404ing the old site before the new site is stable.
- Not saving an old-site URL list before the redesign — with no list, no mapping is possible.
FAQ
How soon after a redesign should indexing start recovering?
After technical fixes, recovery usually starts within 1-2 weeks; full recovery typically takes 4-8 weeks. If nothing moves in two weeks, an undiscovered technical problem remains.
Should the old site stay up during the redesign?
Yes. Keep the old site online with 301s until the new site's indexing is stable, then retire it gradually.
Should titles and descriptions be changed at the same time?
Change them in small, staggered batches. Large-scale title/description changes stack with structural changes and make ranking swings impossible to attribute.
Version notes2026-11-20: first release, compiled from official Google documentation and public technical sources; updated as engine rules change. Engine behaviour details follow the latest official Google documentation.
Related reading
Shopify's Built-in SEO Defects and How to Work Around ThemHow WordPress Plugins End Up Blocking CrawlersAdvanced robots.txt Rules: Blocking Parameters, Pagination, and Useless DirectoriesDomain Migration with 301 Redirects: Preventing Signal LossMultiple Subdomains Under One Domain: The Dilution Risk ExplainedNote: this page is a summary of publicly documented search-engine rules and is for self-check reference only. Engine behaviour is subject to the latest official Google documentation; verify against your own Search Console data.