Home / Blog / Same-domain site restructure: an SEO checklist
SEO · 7 November 2026 · Louise Sylvester
How does a site restructure keep its rankings?
A same-domain site restructure keeps its organic traffic when every old URL redirects in one hop to the page with the same intent, nothing unplanned is indexed, and performance is monitored closely for six to eight weeks after launch.
- Build the URL inventory from crawls, Search Console, analytics and backlinks
- Map every old URL to its closest match by intent
- Crawl staging fully before launch
- Monitor coverage, redirects and rankings by template after launch
A same-domain restructure, such as a redesign, a new URL structure or a replatform, is where organic traffic is most often lost by accident. The domain stays the same, so teams assume search engines will cope. They usually do, if every old URL lands in one hop on the right new page and nothing unexpected gets indexed. When those details slip, rankings that took years to build can disappear in a week.
Done well, a restructure can do the opposite. ElevenLabs grew revenue by 48.2% in the 90 days after its site restructure, and Insense increased qualified leads by 79%, as the ElevenLabs and Insense case studies show. This checklist is the process behind both.
Before launch
1. Build a complete URL inventory
A crawl alone misses pages, because orphaned URLs, old campaign pages and pages linked only from external sites don't show up. Combine five sources: a full crawl of the live site, Search Console pages with impressions over the last 16 months, analytics landing pages over the same period, pages with backlinks from a link tool, and every XML sitemap still submitted. De-duplicate the list and keep it as the master record for the project.
2. Benchmark performance
Before anything changes, record clicks, impressions, rankings, conversions and revenue by URL and by template. Save a crawl of the live site with titles, meta descriptions, canonicals, headings and structured data. Without a benchmark, it is impossible to tell after launch whether a drop is normal turbulence or a real problem.
3. Map every old URL by intent
Send each URL to the new page that answers the same intent. A product goes to the same product, a guide to the same guide, a category to its closest equivalent. Redirecting everything to the homepage or a top-level category is treated as a soft 404, and the rankings go with it. Mark pages removed on purpose and decide whether they should return 410.
4. Keep redirects to one hop
Check the new map against existing redirects. Sites that have been redesigned before often have chains, where URL A redirects to B, which redirects to C. Point every original URL straight at its final destination. Each extra hop slows crawling and leaks signals.
5. Protect the content that ranks
Redesigns often shorten copy, merge pages or move text into tabs and images. Compare the content on the top-performing pages before and after. If a page ranks because it answers a question in detail, the new version needs to keep that detail in readable text.
6. Crawl staging properly
Keep staging out of search with authentication or noindex, but crawl it fully. Compare canonicals, internal links, hreflang, structured data, titles and meta descriptions against the live site. Check that JavaScript-rendered content appears in the rendered HTML, and that templates don't introduce new duplicate URLs. A technical SEO audit of staging catches most problems while they are still cheap to fix.
Launch day
- Remove the staging noindex and check the production robots.txt.
- Crawl the old URL list and confirm each returns a single 301 to a 200 page.
- Submit new sitemaps in Search Console and Bing Webmaster Tools.
- Check analytics and conversion tracking on the new templates.
- Confirm staging, test and app subdomains aren't indexable.
- Spot-check the top 50 pages by revenue for titles, canonicals and content.
After launch
Monitor the Search Console Pages report and crawl stats daily for two weeks, then weekly until coverage settles, which usually takes six to eight weeks. Compare performance by template against the benchmark rather than looking only at sitewide totals, because a problem on one template can hide inside overall numbers.
Watch for four warning signs: unplanned 404 spikes, Google choosing a different canonical than intended, old URLs still ranking weeks after launch, and drops concentrated on a single template. Each has a specific cause and fix. Keep redirects in place for at least a year, and longer for pages with strong backlinks.
Common restructure mistakes
- Launching on a Friday. Problems surface over the weekend with nobody available to fix them. Launch early in the week.
- Changing everything at once. New URLs, new copy, new templates and a new platform in one release make it hard to see what caused a drop. Where possible, change URLs and content in separate phases.
- Forgetting images and PDFs. Image search traffic and linked documents need redirects too.
- Dropping internal links. New navigation often removes links to deep pages that used to rank. Compare internal link counts for key pages before and after.
- Removing redirects too early. Old URLs keep receiving visits from bookmarks, emails and backlinks for years.
- Ignoring Bing. Sitemaps and URL submissions in Bing Webmaster Tools are easy to skip, but Bing feeds ChatGPT and Copilot.
Most of these mistakes are invisible on launch day. They show up two to four weeks later as a slow slide in traffic, by which point the cause is harder to trace.
Restructures and AI search
AI platforms cache and cite URLs too. After a restructure, old URLs can keep appearing in ChatGPT, Perplexity and AI Overviews answers for weeks. Clean one-hop redirects make sure those citations still land on the right page. It's also a good moment to check that AI search crawlers can reach the new templates, and that the new copy still names the brand in the passages AI platforms quote.
How long recovery takes
Even a well-run restructure causes some movement. Rankings often wobble for two to four weeks while search engines recrawl the old URLs, follow the redirects and reassess the new pages. A clean project usually recovers to the benchmark within six to eight weeks, then grows as the improved structure takes effect. A drop that is still deepening after four weeks is a sign that something specific has gone wrong, and the benchmark by template is the fastest way to find it.
Platform-specific notes
Shopify restructures bring fixed URL prefixes, collection-based product paths and app-generated pages, covered in Shopify SEO. SaaS restructures often involve marketing sites moving between frameworks, with app subdomains and documentation needing careful handling, covered in SaaS SEO.
Planning a restructure? See website migration SEO for how we run it end to end.