What happens to every ranking, backlink, and lead-generating page you've built when the new site goes live? Service business owners often assume those assets transfer with the domain. They do not. A page that earned calls for years can vanish because nobody mapped its URL, a designer stripped the copy that made it rank, or a staging noindex tag survived launch day.
Migrations fail in predictable ways. The losses come from missing redirect maps, broken forms, blocked crawlers, and nobody checking whether phone calls and form fills still arrive. Recovery from a domain change can be slow, and the GreenGeeks migration checklist builds that delay into planning rather than treating launch as a clean cutover. Plan for a long tail, not a single switchover date.
This website migration SEO checklist is built for small and mid-sized service businesses, law firms, dentists, roofers, and HVAC companies, where a lost ranking means lost inquiries, not just lost pageviews. It covers pre-launch inventory, launch day controls, and post-launch monitoring in eight steps. Platform details vary. The guide for brands returning to native Shopify covers that move, but the preservation logic stays the same: protect the URL, the content, and the conversion path together.
Table of Contents
- 1. Full URL Inventory and Crawl Audit of the Existing Site
- 2. 301 Redirect Mapping From Old URLs to New URLs
- 3. Content and On-Page Parity Between Old and New Pages
- 4. Technical Blocking Controls for Robots Noindex and Staging Safeguards
- 5. XML Sitemaps and Search Console Submission
- 6. Internal Linking and Information Architecture Preservation
- 7. Structured Data and Answer Engine Readiness
- 8. Post-Launch Monitoring, Performance, and Conversion Continuity
- 8 Steps of a Website Migration SEO Checklist at a Glance
- Launch With a Checklist, Not Crossed Fingers
1. Full URL Inventory and Crawl Audit of the Existing Site
You can't preserve what you haven't listed. Crawl the live site before anyone touches development and export every indexable and non-indexable URL with its status code, title tag, meta description, canonical, internal link count, and organic performance. That spreadsheet becomes your baseline and your rollback evidence.
A crawler alone misses pages. Combine Screaming Frog or Sitebulb output with Google Search Console landing pages, analytics, XML sitemap entries, and backlink reports. Google's guidance on 301 redirects supports exporting indexed URLs, organic landing pages, canonical URLs, sitemap entries, internal links, and externally linked pages before mapping destinations. Pages buried outside navigation often carry the backlinks you most need to save.
Tag Every URL Before Development Starts
Say a law firm exports all practice area pages with ranking and lead data attached. Each one gets tagged keep, merge, redirect, or retire before a developer builds anything. A roofer doing the same work often finds dozens of old city pages with backlinks. Those shouldn't be deleted on sight. Consolidate them into stronger service area pages and record the decision.
Flag low-traffic pages that still matter, like an intake form linked by a referral partner. Our technical SEO audit checklist covers the crawl side in depth, and larger organizations sometimes bring in SEO support for enterprise brands for the same inventory discipline. Save dated copies of the sitemap, robots.txt, and performance exports. You'll compare against them for months.
Practical rule: If a URL earned a click, a link, or a lead, it needs a named destination. No exceptions, no assumptions.
2. 301 Redirect Mapping From Old URLs to New URLs
Where do most migrations lose rankings? In the redirect map. A redirect map is data engineering, not a CMS toggle you flip at launch. Pair every valuable old URL with the closest topically equivalent new URL in a spreadsheet, then implement permanent server-side redirects on staging and test them before DNS changes.
Google's guidance is direct: map each old URL to its corresponding new destination and use permanent server-side redirects, typically HTTP 301 or 308, when URLs change, according to Google's site move documentation. A 302 sends a temporary signal and doesn't do the same job. Chains waste crawl effort too, so point each old URL directly at the final destination in a single hop.
Relevance Beats Convenience Every Time
Say a dental practice maps each old treatment page to its nearest new service page. Retired posts go to relevant current articles, not the homepage. An HVAC company consolidating city pages sends each one to its service area hub. Sending many unrelated URLs home confuses visitors, and Google may treat those destinations as soft 404s. Content with no real equivalent should return a proper 404 or 410.
I recommend crawling the full old URL list after launch and verifying single-hop responses ending in 200 status, with no loops. The redirect layer is server-side, but the surrounding build still has to hold up. Presidio's work for Sightglass Coffee shows that level of craft on the design and development side.
Redirect gaps are much harder to fix after launch, because errors only surface once live visitors and crawlers hit the old URLs. Digital Skyrocket, a web design in Tyler, TX agency, plans, builds, and optimizes lead-generating sites, so it sees the old-to-new URL decisions while the new pages are still being designed.
3. Content and On-Page Parity Between Old and New Pages
Redesigns delete the words that made pages rank. A cleaner layout tempts everyone to cut service details, swap descriptive headings for vague slogans, and shrink a strong practice area page into three sentences and a stock photo. Google ranks the words on the page. Remove them and you've removed the relevance signal.
Content parity doesn't mean copying old copy word for word. It means the new page keeps the core topics, headings, terminology, and local references that earned the ranking, while you improve clarity and calls to action around them.
Compare Old and New Side by Side
Build a spreadsheet with each priority page's title tag, H1, primary keyword, and word count, old version beside new. Gaps become obvious fast. Check these elements before staging sign-off:
- Title tags and meta descriptions: Carried over or deliberately improved, never blank or duplicated by a template default.
- Headings and body copy: Service terminology, city and county names, and process details still present.
- Image alt text and anchor text: Descriptive language preserved, not replaced with file names or "learn more" everywhere.
Say a personal injury firm keeps its practice area terminology and expands each page with clearer case process information. That's parity plus improvement. A roofer keeps storm repair and roof replacement headings intact while strengthening the estimate CTA. Update facts for accuracy, add what's missing, but don't strip topics that already pull traffic and calls.
4. Technical Blocking Controls for Robots Noindex and Staging Safeguards
This is the step that can erase a site from Google in one afternoon. Staging environments carry noindex tags and robots.txt blocks for good reason. Push those settings to production and your live site asks Google to drop it. The opposite error hurts too. An unprotected staging subdomain that gets indexed creates a duplicate site competing with your real one.
Block staging with password authentication first, not robots.txt alone. A robots rule stops crawling but doesn't stop a URL from being indexed if it's linked. Authentication stops both visitors and bots properly.
Verify Every Control on Launch Day
Check robots.txt rules, meta robots tags, X-Robots-Tag headers, canonical tags, and password protection against the migration plan, before and after launch. Headers catch people out. A PDF can return 200 while a header blocks indexing. Use the URL Inspection tool in Search Console to confirm live templates are indexable, and search for your staging subdomain to confirm it isn't.
Say a law firm launches on WordPress and finds a staging noindex still active sitewide. With a written launch checklist, that's fixed within hours instead of discovered weeks later in a traffic report. Note that a hosting-only move is different. Google identifies changing DNS settings to point to new hosting as the step that starts a move with no URL changes in its site move without URL changes guide. Different move, different controls, same need to verify.
5. XML Sitemaps and Search Console Submission
Your sitemap is a declaration of which URLs matter now. Generate a fresh one after redirects and canonicals are final, containing only final, indexable, canonical URLs. A sitemap full of redirected or noindexed pages teaches Google to distrust the file.
Submit the new sitemap in Google Search Console and Bing Webmaster Tools, then watch the Page Indexing and Sitemaps reports. You want new URLs discovered and indexed, and old URLs dropping out as redirects get processed. Check weekly for the first month at minimum.
Domain Changes Need One Extra Step
If the domain itself changes, use Search Console's Change of Address tool alongside your redirects. It supplements redirects, it doesn't replace them. Google recommends implementing a 301 redirect from the old homepage to the new homepage and redirecting canonical pages on the old site, per its Change of Address support guidance. Deleted or merged pages without an equivalent should return 404 or 410 rather than redirect somewhere irrelevant.
Say a dental group submits its rebuilt sitemap and watches coverage until every new service page shows as indexed. A firm moving domains runs Change of Address and monitors both properties for several weeks, old and new side by side.
Submit the sitemap you'd want judged. If a URL shouldn't rank, it shouldn't be in the file.
6. Internal Linking and Information Architecture Preservation
Migrations reshuffle menus and hierarchies without anyone modeling the damage. A service page that sat one click from the homepage ends up buried under a resources hub. Its internal link count drops, its authority drops, and the ranking follows. Nobody changed the page itself, which makes the loss hard to diagnose.
Export internal link counts for your top pages during the inventory step, then compare them against staging. Any priority page that loses links needs a deliberate fix, either restored navigation placement or new contextual links from related content.
Keep Money Pages Close and Connected
I recommend keeping important service pages within three clicks of the homepage. Descriptive anchor text does real work here. A phrase like web design in Tyler, TX pointing home tells Google and visitors exactly what that destination is, which beats a row of "click here" links.
Say a roofer links storm damage articles to the roof replacement service page with anchors naming the service. Those articles rank for informational searches and pass readers, and authority, to the page that books estimates. A multi-location HVAC business organizes city pages under a regional hub so each one stays reachable and interlinked.
Update internal links to point directly at final URLs, never through redirects. Relying on redirects internally is slow, sloppy, and hides mapping errors you'd otherwise catch.
7. Structured Data and Answer Engine Readiness
Schema markup can break during migrations. A template rebuild drops the LocalBusiness block, a plugin swap renames fields, and your review stars and FAQ eligibility disappear with no error anywhere obvious. Audit existing structured data before migration and document exactly which types each template must carry over.
For local service sites, that usually means Organization, LocalBusiness, Service, FAQPage, and Article markup in JSON-LD. Our breakdown of local business schema markup walks through the local types in detail.
Validate Templates, Not Just the Homepage
Run every template type through Google's Rich Results Test on staging and again after launch. Homepage-only testing misses the location template where the markup broke.
Say a law firm preserves attorney and practice area markup, then adds FAQ content answering common injury questions in plain language. That structured Q and A supports featured results and AI-generated answers, which increasingly shape which firms get considered. A dentist's new location pages carry LocalBusiness markup matching the Google Business Profile exactly.
Consistency is the part people skip. Business name, address, and phone must match across the website, schema, and Business Profile. Mismatches muddy the entity signals answer engines rely on. Treat NAP data like a redirect map. Verify it field by field instead of assuming the new theme pulled it correctly.
8. Post-Launch Monitoring, Performance, and Conversion Continuity
Most sites take several weeks to settle after a move, and larger sites often take longer. Rankings, calls, and form fills can move around in that window even when the new pages look fine. For a domain move, I recommend keeping 301 redirects for at least a year, and longer while old URLs still draw search traffic.
Build the shared dashboard before launch. Record baseline clicks, impressions, indexed pages, rankings, calls, and form submissions. Review crawl errors and indexing daily for the first two weeks, then weekly.
An HVAC company sees impressions drop on one service page, traces the drop to a redirect aimed at the homepage, and fixes the target before qualified calls thin out.
Test the Lead Paths Like a Customer
Submit every form for real and confirm it lands in the right inbox or CRM. Tap every click-to-call link on a phone. A roofer that runs the estimate form on iPhone and Android before the public switch finds a broken submit button while the fix is still free.
Measure Core Web Vitals in PageSpeed Insights and Search Console against the pre-launch baseline. Where scores slipped, work through our guidance on how to improve site speed. Log every fix with a date. When performance or inquiries move, the log shows why.
8 Steps of a Website Migration SEO Checklist at a Glance
| Checklist Item | Migration Phase | Key Tools | Risk Prevented |
|---|---|---|---|
| Full URL Inventory and Crawl Audit of the Existing Site | Pre-migration | Screaming Frog, Sitebulb, Google Search Console, analytics platform | Loss of valuable pages, rankings, and baseline data |
| 301 Redirect Mapping From Old URLs to New URLs | Planning and launch | Redirect map, crawler, 301 redirects | Broken visitor paths, lost link equity, and redirect chains |
| Content and On-Page Parity Between Old and New Pages | Content migration | Content comparison spreadsheet, keyword data | Ranking losses from removed or weakened content |
| Technical Blocking Controls: Robots, Noindex, and Staging Safeguards | Staging and launch | robots.txt, meta robots, X-Robots-Tag, URL Inspection | Live-site deindexing or staging-site indexing |
| XML Sitemaps and Search Console Submission | Launch and post-launch | XML sitemap, Google Search Console, Bing Webmaster Tools | Delayed discovery and confusing indexing signals |
| Internal Linking and Information Architecture Preservation | Site structure migration | Crawl reports, navigation, breadcrumbs, internal links | Important pages becoming hard to find or disconnected |
| Structured Data and Answer Engine Readiness | Template migration and validation | JSON-LD, Schema.org validator, Rich Results Test | Broken or inconsistent structured data |
| Post-Launch Monitoring, Performance, and Conversion Continuity | Post-launch | Google Search Console, Google Analytics, Lighthouse, PageSpeed Insights | Unnoticed traffic, technical, or conversion losses |
Launch With a Checklist, Not Crossed Fingers
Migrations don't lose rankings because of bad luck. They lose them because someone skipped the inventory, rushed the redirect map, let a redesign strip ranking content, or pushed staging controls live. Every failure in this checklist is preventable, and every one of them shows up the same way for a service business. Fewer calls, fewer form fills, fewer qualified inquiries, while competitors keep the spots you vacated.
Run each phase with a named owner and a date. Inventory before development. Redirect mapping before staging sign-off. Parity checks before content freeze. Blocking controls, sitemaps, and internal links verified on launch day itself, not the week after. Schema validated per template. Monitoring scheduled before launch, with baselines already saved, so the first two weeks produce answers instead of arguments about what changed.
The trade-off is honest. This work adds days to a project timeline. Skipping it can add months of recovery, and some pages never fully come back because the content or links that supported them are gone. For a law firm, dentist, roofer, or HVAC company, one lost service page in one city can mean a real drop in booked work. The checklist costs less than the leads.
We build these steps into every redesign we run for service businesses. That starts with an SEO audit to baseline the existing site before anything moves, so preservation targets are explicit. SEO is included in our website package rather than sold as a separate purchase, which means redirect mapping, parity checks, and technical verification aren't optional extras a client can accidentally decline. They're part of the build.
After launch, our conversion rate optimization work monitors how visitors move through the new site and adjusts layouts, calls to action, and form flows so preserved rankings turn into calls and submissions. A migration that holds traffic but halves form completions isn't a success, and we don't treat it as one.
If you're planning a redesign or platform move in one of our service areas, including if you're looking for a web design agency in Longview, TX, start with a Fit Meeting. We'll look at your current rankings, traffic, and lead paths first, then tell you plainly what a safe migration requires. Owners and marketing directors outside Texas are welcome too. The checklist travels. The discipline is the point.
If your service business is planning a redesign, we can baseline your current site with an SEO audit, build the redirect map and migration controls into the new build, and keep optimizing after launch so rankings turn into calls and form submissions. Start with a Fit Meeting at Digital Skyrocket and bring your current traffic and lead numbers.
