Website migration SEO checklist for small businesses.

Published September 10, 2026 · By Decent4

The short answer

A website migration SEO checklist should cover six things: inventory existing URLs, map each changed page to its replacement, preserve important content, test redirects and indexing settings, update links and the sitemap, and monitor the live site after launch. The acceptance test is not just whether the homepage looks right. Old links must still take customers to the right information.

This guide focuses on the move itself. For preparing copy and business facts, use the website content checklist before a redesign. For recurring checks after the migration, see the website maintenance plan.

1. Identify what is actually changing

A hosting-only move keeps the same public URLs but changes where the site runs. A domain or path change creates new public addresses and needs an old-to-new mapping. A platform switch can be either: changing the website builder does not necessarily require changing page URLs.

• Same URLs, new host: test the copied site, HTTPS, forms, and crawler access; plan the DNS change and monitor both hosts. Do not add redirects solely because the hosting provider changed.
• New paths on the same domain: preserve existing paths where practical and redirect changed ones to their corresponding replacements.
• New domain: plan redirects from the old domain, verify the appropriate Search Console properties, and use Google's Change of Address tool when the move is eligible.

Google recommends changing one major thing at a time when possible. Separating a domain move from a CMS replacement or major redesign makes problems easier to isolate. Its hosting-only migration guide and URL-change migration guide describe these different paths.

2. Inventory pages before rebuilding them

Collect URLs from the existing sitemap, a site crawl, Search Console, analytics, and known external links. Include service pages, location pages, articles, PDFs, images with valuable inbound links, contact pages, and campaign landing pages. A menu is not a complete inventory.

Save a pre-launch baseline of important landing pages, search clicks and impressions, and meaningful inquiries or bookings where tracking exists. Record the date range and any seasonal or campaign context. Keep a copy of the old site and identify who controls the domain, DNS, hosting, and recovery process.

For each URL, record its destination, intended status, content owner, and test result. Choose one outcome: keep the URL, move to an equivalent page, consolidate into a genuinely relevant page, or retire it because there is no replacement.

3. Make redirects preserve the customer's intent

For a permanent page move, Google recommends a server-side permanent redirect such as 301 or 308. A redirect sends the visitor to another address; a canonical tag identifies the preferred URL for indexing and does not move the visitor. They are not interchangeable.

Do not send every removed service page to the homepage. Google warns that irrelevant redirects can be treated as soft 404 errors. Avoid redirect chains: an old address should go directly to the final destination, not through several previous redesigns. Test actual HTTP responses, including common host and trailing-slash variants, rather than checking only a spreadsheet.

Google advises keeping redirects for as long as possible, generally at least a year. Keeping useful old links working longer can help returning visitors. Budget for continued control of the old domain and a working redirect service; do not cancel them as soon as the new homepage appears.

4. Set a launch acceptance checklist

Ask the builder to demonstrate these checks on representative pages and every critical customer path. For a small site, testing the full URL map is usually practical.

• Destinations: new public pages return HTTP 200 with the intended content; nonexistent pages return an actual 404 rather than an error message with a success status.
• Indexing: remove staging-only noindex rules and crawl blocks from pages meant to appear in search. Check both HTML and HTTP headers; retain intentional restrictions on private areas.
• Canonicals: each new indexable canonical page identifies its final production URL, not a staging host or old address.
• Links and sitemap: internal links point directly to final destinations, and the sitemap lists the current canonical URLs intended for indexing.
• Content: important service descriptions, contact details, headings, and images survived the move and remain readable on mobile.
• Business paths: submit a test inquiry, confirm it arrives, and check phone links, booking flows, and conversion tracking where enabled.
• Recovery: name the launch owner and agree on how to recover if the site is unavailable or inquiries cannot reach the business.

These are deliverables to put in a migration scope, not a promise of rankings. A quote should state who prepares the URL map, implements redirects, tests production, and handles problems after launch.

5. Monitor the move before closing it

Submit the new sitemap in Search Console and inspect key URLs. Watch indexing, crawl errors, server errors, search landing pages, and actual inquiries. Where a domain changes, monitor both old and new properties and update business profiles, ads, and important external links to the final addresses.

Decent4's recommended working rhythm is a launch-day check, a next-business-day check, and regular checks over the following weeks, adjusted to the site's size and activity. This is an operational recommendation, not a Google recovery deadline. Google notes that rankings may fluctuate while it recrawls and reindexes a moved site.

Investigate a decline in context. A broken analytics tag can look like lost traffic; a failed form can hide working search traffic from the business. Check live pages and lead delivery alongside search reports before attributing every change to ranking loss.

Common buyer questions

Can a website redesign keep the same URLs?

Yes, if the new platform supports them. Keeping useful existing URLs avoids unnecessary address changes, though content, rendering, and performance changes still need review.

Does changing hosting require Google's Change of Address tool?

No, not when the public domain and URLs stay the same. Google's URL-move guidance reserves that tool for eligible domain or subdomain moves, not ordinary path changes or a move from HTTP to HTTPS.

Can a builder guarantee no SEO loss?

A responsible scope can promise specific checks and fixes, not unchanged rankings. Require evidence of correct redirects, accessible content, and working customer paths instead of an unsupported traffic guarantee.

Primary sources

The technical guidance above is based on these Google Search Central documents, checked September 10, 2026. The inventory format, buyer acceptance checks, and monitoring rhythm are Decent4 recommendations.

• Site moves with URL changes — mapping, redirects, canonicals, sitemaps, retention, and monitoring.
• Changing hosting infrastructure — preparation, DNS, crawler access, and traffic checks when URLs stay the same.
• Redirects and Google Search — permanent and temporary redirect behavior.