TL;DR Summary:
URLs Aren’t Enough: Keeping the same URLs during a migration does not guarantee that search rankings will survive.Hidden SEO Risks: Rendering changes, missing canonicals, incorrect status codes, and broken structured data can create serious problems beneath unchanged addresses.Baseline Before Launch: Record HTML, directives, links, schema, and page behavior before migrating, then compare each page type after launch.Monitor By Template: Track rankings, indexing, crawlability, and errors by URL group and shared template to catch issues affecting thousands of pages.Does keeping the same URLs during a site migration protect your search rankings? A new analysis published November 9, 2026, by Bharath Ravishankar says no, and the finding matters because many teams treat URL preservation as proof that rankings are safe. Website migration SEO risk can hide below the URL layer, in rendering, canonicals, and HTTP status codes, even when every address on your site stays exactly the same.
Why Website Migration SEO Risk Starts With Hidden Responsibility Shifts
The report uses a real scenario: moving from WordPress to a headless setup built on Contentful and Next.js. In WordPress, a plugin usually generates canonicals, meta robots tags, sitemaps, and structured data automatically. Once you move to a headless CMS, your frontend code takes over that job. If the mapping between the CMS field and the page output gets missed, a canonical value can sit in your CMS and never reach the actual page. The article also flags a specific failure mode: a deleted page might return a 200 status, meaning “page found,” instead of a proper error code, because fallback logic wasn’t set up to catch it.
Building a Baseline Before You Touch Anything
Before migrating, the article recommends capturing a baseline for every major page type on your site. That means recording HTTP status, the initial HTML, elements that appear after rendering, canonical and robots directives, structured data, internal links, and how the site handles edge cases like deleted or empty pages. For an ecommerce site, that baseline should cover standard products, unavailable products, category pages, and paginated pages. Without this step, you have nothing to compare against after launch, so any website migration SEO issue becomes much harder to trace back to its cause.
Testing the Exact Pieces That Changed Hands
Once you know which platform used to handle which SEO function, your testing should target those same pieces after the move. That includes checking canonicals and structured data wherever the logic moved from plugin to frontend, comparing the initial HTML against the fully rendered output, and confirming that rebuilt navigation still produces links search engines can crawl. Routing needs testing across deleted pages, unavailable products, empty categories, and invalid URLs, since these edge cases often run on different code paths than standard pages. This is also where pages can slip into a crawled-but-not-indexed state or quietly return the wrong HTTP status despite the URL itself looking untouched. A platform like Labrika is built to flag exactly these kinds of crawlability gaps, since URL preservation alone won’t surface them.
One Bug Can Spread Through Shared Templates
The article stresses checking for patterns rather than treating each issue as a one-off. If one product page loses its canonical tag, you should check every other page built on that same template. Shared components, like related-content modules, pagination, or locale settings, can copy a single bug across thousands of URLs at once. Segmenting problems by template, page state, locale, and rendering behavior helps you tell the difference between a handful of manual errors and a systemic website migration SEO problem affecting tens of thousands of pages.
Watching the Right Signals After Launch
Post-launch monitoring should focus on the specific changes made during migration. Track indexing and search performance by page group, recrawl the site to compare internal link counts and crawl depth against your baseline, and check Search Console and server logs for unexpected redirects or 404 errors. The article warns against reading traffic in aggregate, since an overall dip can hide a severe decline in one template while other sections stay stable. If one migrated template starts losing impressions while others hold steady, that timing is a useful lead, though the article is clear it isn’t proof on its own.
The single most important action is building your pre-migration baseline before you change anything, then checking it page type by page type after launch. Watch your performance data by URL group, not as one combined total, since that is where a real website migration SEO problem will first show itself. Tools like Labrika’s site auditor can help here, since it specifically compares indexed pages against crawled pages, surfacing exactly the kind of silent indexing gaps and status-code problems a post-migration baseline check is designed to catch.
