Local SEO Website Migration Checklist: Change Domains Without Losing Important Signals

A redesign can improve a local business website, but changing URLs, domains, content, tracking, and templates all at once makes problems harder to diagnose. A migration is not just a visual launch. It is a controlled transfer of URLs, content, internal links, tracking, and user journeys.

No checklist can guarantee zero ranking fluctuation. Google notes that significant site moves can cause temporary changes while URLs are recrawled and reprocessed. The goal is to reduce avoidable errors, preserve useful signals, and identify issues quickly.

Decide what kind of migration you are doing

Different projects have different risks:

• Design refresh: same URLs, new templates or styles.
• CMS or framework change: same domain, possibly different HTML and routing.
• URL restructuring: paths change while the domain remains.
• Domain change: old domain moves to a new domain.
• HTTPS migration: protocol changes.
• Consolidation: several sites or sections become one.
• Content cleanup: pages are removed, merged, or rewritten.

Write down every change. If possible, avoid combining a domain change, full redesign, content rewrite, and URL restructure in one release. Smaller controlled changes make diagnosis easier.

Build the URL map before launch

Export the existing URLs from your sitemap, crawler, analytics, Search Console, and known backlink sources. Do not rely on the sitemap alone; it may omit pages that still receive traffic or links.

For every old URL, assign one clear destination:

• Same content, same URL: keep it.
• Same content, new URL: redirect to the new equivalent.
• Several genuinely overlapping pages merged: redirect each old URL to the most relevant consolidated page.
• Content no longer exists and has no suitable replacement: return an appropriate not-found or gone response instead of redirecting everything to the homepage.

A redirect map should be explicit and testable. Redirecting every removed page to the homepage is not a good substitute for relevant destinations.

Prepare a pre-launch baseline

Record at least:

• Important landing pages and their current URLs.
• Organic clicks and impressions for a comparable period.
• Leads and conversion events, if reliable.
• Current sitemap and robots.txt behavior.
• Canonical URLs and indexability settings.
• High-value backlinks and referral sources.
• Google Business Profile website and appointment links.
• Analytics tags, call tracking, and form destinations.

Save the baseline so the team can distinguish a migration problem from normal seasonality or demand changes.

Technical pre-launch checklist

Before the switch:

1. Build and test the new site in a protected staging environment.
2. Verify that staging is not accidentally indexable.
3. Confirm each planned destination returns the intended content and a successful status.
4. Test mobile layouts, forms, phone links, booking flows, and payment or quote requests.
5. Check title tags, meta descriptions, canonical tags, robots directives, and structured data.
6. Verify internal links point directly to the final preferred URLs.
7. Generate a clean sitemap containing only canonical URLs that should be indexed.
8. Confirm robots.txt does not block critical pages or required resources.
9. Test redirects from old URLs to the exact new destinations.
10. Ensure analytics and conversion events work before the old setup is removed.

For a framework migration, test rendered content and status codes as well as the visible design.

Launch-day procedure

Choose a period when the team can monitor the site and traffic is reasonably manageable. Keep the old URL list and redirect map accessible.

At launch:

• Deploy the new site and redirects together.
• Check a representative sample of old and new URLs.
• Test the homepage, top service pages, location pages, contact page, and lead forms.
• Verify that old URLs do not create redirect loops or long chains.
• Confirm the production domain, HTTPS certificate, canonical host, and robots directives.
• Submit the new sitemap in Search Console.
• If the domain itself changed, follow Google's Search Console site-move guidance and verify both properties. A change-of-address process applies to eligible domain moves, not every redesign or URL change.
• Update important external profiles and campaigns to point to the new URLs.

Do not remove redirects immediately after the launch. Google's site-move guidance recommends keeping redirects for a long period—generally at least a year—and user experience may justify retaining them longer.

Update local business destinations

Local businesses often forget links outside the website. Review:

• Google Business Profile website link.
• Appointment, menu, order, or booking links where applicable.
• Social profiles.
• Email signatures and digital business cards.
• Directory listings you control.
• Local association, chamber, partner, and supplier profiles.
• Paid ads and email campaigns.
• QR codes on printed material, if the destination changed.

Prioritize high-visibility profiles and URLs that customers actually use. Do not assume a website migration automatically updates the links in third-party platforms.

The first 48 hours

Run a technical crawl and compare the results with your baseline. Check:

• Unexpected 404 and 5xx responses.
• Redirect chains and loops.
• Old URLs returning 200 with the wrong content.
• New pages canonicalizing to old URLs by mistake.
• noindex accidentally left on production pages.
• Sitemap entries that redirect, return errors, or are not canonical.
• Missing titles or identical metadata across important routes.
• Form failures and broken phone or booking links.
• Analytics events missing after the deployment.

A sudden drop in recorded conversions may be a tracking failure rather than a real demand decline. Test the full lead path before drawing conclusions.

Monitor for the following weeks

Compare Search Console clicks and impressions by page and query, not only sitewide totals. Check whether old URLs are gradually replaced by new URLs, whether important pages remain indexed, and whether traffic is returning to expected patterns. Monitor business leads separately from search metrics.

Do not panic over every short-term fluctuation. Investigate a sustained or page-specific decline, especially when it aligns with a technical issue. Search systems process moves URL by URL and timelines vary.

Migration decision matrix

Symptom	First investigation	Avoid
Many new URLs not indexed	robots, canonicals, status codes, sitemap, rendered content	Repeated indexing requests without fixing blockers
Old URLs show 404	redirect map and deployment rules	Redirecting every URL to homepage
Traffic falls but leads seem stable	analytics and tracking changes	Assuming rankings alone explain the gap
Leads fall after redesign	forms, phone links, booking flow, mobile UX	Waiting weeks before testing conversions
Both old and new versions appear	redirects, canonicals, internal links, sitemap	Leaving duplicate versions indefinitely

FAQ

Will a redesign automatically hurt SEO?

No. A redesign can preserve or improve search performance, but changes to URLs, content, internal links, rendering, and technical settings can introduce risk.

Should I change the domain and redesign at the same time?

If practical, separate major changes so you can isolate problems. Sometimes business constraints require a combined move; in that case, prepare a thorough URL map and testing plan.

Should I redirect every old URL to the homepage?

No. Redirect to a genuinely equivalent destination where one exists. Irrelevant redirects can confuse users and fail to preserve the page's intent.

How long should redirects stay live?

Google recommends keeping redirects for a long period, generally at least one year for site moves. Keeping them longer can help visitors who use old bookmarks or links.

Should I resubmit the sitemap?

Yes, submit the new sitemap after launch and ensure it contains the canonical URLs you want indexed.

Related Chamko guides

• Sitemap guide for small business websites
• Google Search Console for local SEO
• Why local pages are not indexed
• Local SEO audit checklist
• Local SEO measurement dashboard

Official references

• Google: Site moves with URL changes
• Google: Build and submit a sitemap
• Google: SEO Starter Guide