Hosting Migration SEO Checklist: Verify the Move Without Changing URLs

For a hosting move that keeps your URLs, verify continuity rather than inventing a new URL migration. The website should remain available at the same public addresses with its intended content and search controls. New infrastructure is not, by itself, a reason to rename pages.

Separate the two migration types

Write down what changes: server, host, CDN, DNS or application configuration. Confirm whether the domain, scheme and paths remain the same. If the URLs also change, add the redirect mapping workflow instead of assuming this narrower checklist covers it.

Google provides separate guidance for hosting changes without URL changes. Its recommendations include testing the new infrastructure and verifying crawler access. Match your move to that scope before choosing a Search Console migration action.

Build a before-and-after sample

Choose key entry pages, a recent article, an older page, a category page and important assets. Include a form or store workflow separately. Record existing content, response behavior, canonical values and intended indexing controls before cutover.

Test the new environment using the host’s supported preview method. A temporary preview URL may have different security and canonical behavior, so do not treat every preview response as the intended public configuration. Keep staging isolated and record what must change at release.

Verify the actual public cutover

After the DNS or infrastructure change, request the real public pages without administrator privileges. Compare the intended site with what is served. Check HTTPS, representative assets and any relevant redirects that already existed.

Review canonical declarations and indexing directives on several templates. A clone may retain temporary hostnames or a staging noindex value. Use the canonical checklist and visibility-control checklist to locate the responsible output before correcting it.

Check discovery and search observations

Verify the public sitemap and representative entries, then use Search Console to inspect important URLs where you have access. Record whether you are looking at a live check or a processed observation from before the move.

Google notes that crawler activity can change temporarily when infrastructure changes. Do not turn a short-term fluctuation into a claim that the migration succeeded or failed. Compare access errors and actual page behavior with the search data, and investigate persistent faults.

Keep recovery and business checks alongside SEO

Retain the old environment until the approved recovery and data-reconciliation conditions are met. For a store, newer orders matter; for a business site, email and form delivery matter. A successful crawl check does not establish that checkout or mailbox routing is healthy.

Close with the sample results, unresolved issues, monitoring owner and cancellation criteria for the old service. This checklist verifies technical continuity for unchanged URLs. It does not promise unchanged rankings or eliminate the need for a separate content and performance review.

Keep an unchanged-URL move narrow

For a hypothetical host-only migration, preserve the existing URL set and compare the same sample before and after cutover: response, canonical, indexing directives and business workflow. Unexpected URL or canonical changes become explicit defects to investigate, rather than assumed parts of the move. If URLs intentionally change, add redirect mapping and the separate URL-change migration procedure.

Sources and scope

Official documentation checked October 6, 2026: Google: Changing hosting and SEO; Google: URL-changing site moves. This is HRL’s verification checklist, not a report of a completed migration or a guarantee of crawling, indexing or rankings.

Related guides

Plan the wider migration · Check DNS and email · Know when to cancel the old host