A website rebuild should be accepted against what visitors and search engines actually receive. Keeping the same URL list is only one part of that decision. The platform may preserve the address while changing the content, links or response delivered there.
A November 9 analysis by Bharath Ravishankar brings renewed attention to this migration risk. Use that discussion as the trigger for a release review, not as news of a new Google rule. The checklist below is our proposed acceptance process; its technical foundations come from Google’s documentation on infrastructure changes, JavaScript and crawlable links.
1. Define what the release must preserve
Choose representative page families before checking individual URLs. For a retailer, include a product, a category and a genuinely unavailable destination. For a publisher, include an article, an archive and a deleted page. Add the commercially important exception that a standard template does not cover. A convenient sample is less useful than one that can expose a costly failure.
For each sample, record the intended customer task, expected response, essential content and useful onward links. Name the owner who can accept each result. This creates a small release contract: a category must expose its actual offer, a removed destination must return the intended state, and an enquiry page must still let the customer enquire.
2. Compare delivered behavior, not just screenshots
Save the old response and the new response alongside the rendered page. Google describes crawling, rendering and indexing as distinct phases for JavaScript applications. A visually complete browser view therefore does not replace an inspection of how important content is delivered. Equally, do not assume that content using JavaScript is automatically invisible to Google.
Inspect navigation as well as copy. Google’s link guidance generally calls for an anchor element with an href attribute. A visually convincing button or menu is not sufficient evidence that the intended destination is discoverable. Follow the important paths from the sample page and record missing destinations, incorrect routes and changed page states.
3. Give every output an accountable owner
Build a compact evidence table with five fields: page sample, expected behavior, observed behavior, responsible owner and acceptance decision. Include content availability, indexation controls, canonical output, essential navigation and any structured data the business expects to preserve. This is an editorially proposed control sheet, not a Google certification.
Assign defects to the component that produces the result. A value stored correctly in the CMS does not prove that the public page uses it correctly. Ask the team to demonstrate the delivered output and the fix on the same representative sample. That makes acceptance reviewable and avoids an endless exchange of configuration screenshots.
4. Use explicit release and monitoring rules
Our suggested decision model has three outcomes. Stop if a critical destination cannot deliver its intended task or is unintentionally blocked. Accept conditionally only when a bounded defect has an owner, a deadline and an understood commercial consequence. Accept when the sampled behaviors meet the agreed expectations and the monitoring owner is ready.
Keep scope clear. A hosting change without visible URL changes is not the same project as a CMS rebuild, although a project can contain both. Google’s hosting guide recommends preparation, transition and monitoring, including checking access and removing temporary launch blocks. Adapt those controls to the actual infrastructure work rather than applying DNS instructions to every redesign.
After release, watch the agreed page samples, server responses and search evidence alongside customer outcomes. Preserve the before-and-after record so a later problem has a traceable starting point. Passing the checklist reduces avoidable implementation mistakes; it cannot guarantee unchanged rankings or a fixed recovery time.
Sources
- Website migrations can hurt SEO even when URLs don’t change — fresh expert analysis
- Changing your hosting — Google Search Central
- Understand JavaScript SEO basics — Google Search Central
- Link best practices for Google — Google Search Central
