Website Migration SEO Checklist: Protect Rankings and Leads

Website migration SEO is the process of preserving search visibility, useful content and conversion paths when a website changes its platform, structure, domain or design. A successful migration starts before development: inventory the current site, identify commercially important pages, map old URLs to appropriate destinations, test the new templates and establish measurable launch criteria. After release, monitor crawling, search performance and lead delivery together. A visually polished site is not a successful migration if buyers cannot find it or complete an enquiry.

What counts as a website migration?

A migration is any substantial change that can affect how users or search engines access and understand a website. Some moves change the address of every page. Others keep URLs stable but replace the rendering system, CMS, navigation or templates. The risks depend on what actually changes, not what the project is called.

Hosting and infrastructure changes

A hosting-only move keeps public URLs unchanged. The main checks concern DNS, certificates, server availability, caching, response codes and whether pages and assets are served correctly. There is no reason to invent new page paths merely because the hosting provider changes.

CMS and technology migrations

Moving between platforms can change permalink rules, trailing slashes, image paths, metadata, structured data, pagination and JavaScript rendering. Even when the design appears similar, the generated HTML may differ. Audit the output rather than assuming the CMS settings preserved it.

Redesigns and architecture changes

A redesign can remove useful text, bury high-value pages, replace descriptive links with ambiguous labels or change the conversion journey. SEO and conversion specialists should review wireframes and content decisions before they become expensive to reverse.

Domain changes and site consolidation

A new domain or merger requires careful handling of old addresses, ownership, redirects and brand signals. Where practical, stage major changes so a domain move, CMS replacement and wholesale content rewrite are not all introduced simultaneously. This makes problems easier to isolate.

Set a business case and define migration success

Start with the reason for moving. Better publishing workflows, a faster mobile experience, improved lead routing or a platform that supports international growth are concrete goals. “A more modern website” is too vague to guide trade-offs when launch pressure arrives.

Define success across acquisition, experience and operations. Acquisition measures can include non-brand clicks to priority services and visibility for established page groups. Experience measures can include successful form completion, appointment booking and mobile usability. Operational measures may include editorial independence, release reliability and content maintenance time.

Keep a clear distinction between preservation and improvement. The launch must first preserve essential functionality and valuable search coverage. New growth opportunities can follow an intentional roadmap. Promising immediate ranking increases from a redesign encourages unnecessary changes and makes honest evaluation difficult.

A combined technical SEO review and development plan helps turn the business goal into specific acceptance criteria: which URLs must remain available, which templates must render correctly and which customer actions must reach the right team.

Create a baseline before touching the old website

Export enough evidence to explain what changed after launch. Once the old site disappears, reconstructing its structure, content and performance is harder. Keep dated snapshots and a short explanation of definitions so the team can compare like with like.

Inventory URLs from several sources

Combine a crawl, CMS export, XML sitemaps, analytics landing pages, Search Console pages and known externally linked assets. A crawl alone may miss orphan pages, campaign landing pages, PDFs or historical URLs still receiving visits. Deduplicate the inventory without discarding meaningful URL variants prematurely.

Record page-level SEO elements

Capture status codes, titles, descriptions, H1s, canonical URLs, robots directives, internal links, structured data and primary content. Include hreflang and pagination where relevant. Store important images, downloads and embedded resources, not only HTML pages.

Identify commercially sensitive pages

Mark pages that generate qualified leads, support important deals, receive meaningful links or satisfy valuable search intent. A low-traffic pricing document may matter more to sales than a popular informational article. Use sales feedback alongside analytics rather than ranking pages only by sessions.

Preserve a measurement baseline

Record search clicks, impressions, conversions, lead quality and revenue where available. Segment brand and non-brand demand, device, geography and page group. Note campaigns, seasonality, tracking changes and other events that could affect interpretation. A short pre-launch window is useful operationally, but a longer history helps explain seasonal patterns.

Build a URL migration map with explicit decisions

The URL map is a decision register, not just a spreadsheet of redirects. Each old URL should have a deliberate outcome and an owner who can explain it. Useful fields include old address, current status, page purpose, business priority, destination, planned response, content owner and test result.

Keep valuable addresses when there is no reason to change them

Retaining a sensible established URL reduces work and removes a source of uncertainty. Do not shorten or reorganize every path simply to make the site look tidier. Change architecture when it improves navigation, governance or clarity enough to justify the migration effort.

Redirect to a genuinely equivalent destination

Map an old service page to the new page that satisfies the same need. If several articles are consolidated, the destination should actually contain the useful coverage they previously offered. A redirect is not a substitute for preserving the answer a visitor expected.

Handle retired content honestly

When a page has no replacement and no continuing value, an appropriate not-found or gone response can be more accurate than sending users somewhere unrelated. A custom error page should help visitors navigate while still returning the correct error status.

Test rules as well as individual mappings

Pattern-based rules can save time but may mishandle exceptional paths, capitalization, encoded characters, query strings or trailing slashes. Maintain an exception list and test representative edge cases. Every high-priority old URL deserves a specific verified result.

Preserve search intent while improving content and design

A migration creates an opportunity to remove clutter, but visual simplicity should not remove the information buyers need. Keep the core purpose, service detail, relevant evidence and contextual links of valuable pages. Rewrite confusing content carefully and document substantial changes.

For example, a hypothetical engineering consultancy might replace a detailed inspection-services page with a beautiful hero and three cards. The page may now load attractively while no longer explaining inspection types, suitability, deliverables or geographic coverage. That is a content loss, not simply a design change.

Review page briefs against real buying questions. What is the service? Who is it for? What is included? What happens next? What evidence supports the claim? What objections must be answered before an enquiry? Descriptive headings and clear content hierarchy help readers scan without reducing a detailed service page to fragments.

Use the technical SEO audit checklist for wider diagnostics, while keeping the migration work focused on the exact templates and changes being released.

Test the staging site by template and journey

A staging review should cover both representative templates and critical real pages. A homepage check cannot prove that product variants, resource downloads, industry pages and contact forms work. Build a test matrix with owners and repeatable evidence.

Indexability and URL consistency

Confirm that intended public pages return successful responses, use the intended canonical address and do not inherit staging-domain references. Check robots directives in HTML and headers. Keep staging appropriately restricted, and prepare a separate production configuration so development protections do not accidentally ship.

Rendering and internal links

Inspect initial and rendered HTML for important copy, links and metadata. Test routes opened directly, not only pages reached through client-side navigation. A page that works after clicking from the homepage can still fail when a prospect lands on its URL from search.

Media and structured data

Check image sources, alt text, dimensions, responsive behavior, downloads and video. Validate structured data against visible content and the correct production URLs. Remove stale organization details or unsupported review claims rather than copying every old script blindly.

Mobile performance and accessibility

Test navigation, accordions, forms and sticky elements on narrow screens. Look for horizontal overflow, obscured buttons, unreadable text and layout shifts. Performance tools help identify resource issues, but manually completing the main journey reveals friction a numeric score cannot explain.

Protect lead generation, analytics and CRM routing

SEO can appear stable while a migration silently breaks revenue measurement or enquiry delivery. Treat each important lead path as a system: visitor action, validation, confirmation, notification, CRM record, assignment and follow-up.

Test forms with appropriate non-customer test data, confirm the expected recipient and verify that spam protection does not reject normal submissions. Check click-to-call links, calendar booking, chat, email links and downloadable resources. Establish how test records will be identified so they do not contaminate sales reporting.

Verify analytics events against actual successful actions. A button click is not necessarily a completed lead, and a thank-you page can reload. Check duplicate events, consent behavior, cross-domain journeys and source fields. Preserve landing-page and campaign context through the transition where the measurement design supports it.

The existing conversion tracking guide for GA4, GTM and CRM attribution explains the wider measurement model. For the migration itself, define a small set of observable tests that prove an enquiry reaches its destination and is measured once.

Create a launch-day runbook and go/no-go gate

A runbook replaces assumptions with an ordered sequence. Name the person responsible for deployment, DNS, redirects, content, SEO, analytics and commercial approval. Give each person access to the systems they need before launch, and agree on a communication channel.

Record the exact release state, backup location, rollback procedure and decision authority. Choose a lower-risk launch window based on the business's actual demand pattern, and reserve time for verification. Do not schedule the only knowledgeable developer to leave immediately after deployment.

Block launch when critical journeys fail, priority URLs have no agreed destination, public pages remain accidentally restricted or the recovery process is untested. Lower-priority editorial polish can be assigned to a post-launch list; broken enquiry delivery cannot.

• Confirm the approved content and URL-map version.
• Deploy production configuration and verify certificates.
• Activate tested redirects and inspect priority destinations.
• Check crawl controls, canonicals and production links.
• Complete mobile forms, booking and notification tests.
• Verify analytics and CRM events without duplicates.
• Publish the preferred canonical URLs in the sitemap.
• Record launch time, known issues and responsible owners.

Monitor the transition without misreading normal variation

Begin with immediate operational checks: availability, response errors, key landing pages and lead routing. Then review search and commercial data as reporting becomes available. Search Console and analytics do not necessarily update on the same schedule or use identical definitions.

Compare page groups and matched destinations

Aggregate old and new addresses when evaluating a migrated page. Otherwise, the old URL's decline can look like lost traffic even when visits moved successfully to its replacement. Segment services, articles, products, locations and other meaningful groups to locate the problem.

Separate visibility from conversion problems

If search clicks remain stable but enquiries fall, investigate the page experience, form delivery and measurement before assuming rankings are responsible. If impressions fall for a particular template, inspect indexability, rendering, internal links and content changes on that template.

Use a risk-based review cadence

During the first day, prioritize availability and business-critical journeys. Over the following days, examine errors, discovery and lead quality. Continue scheduled review across the next several weeks, adjusting to site size, sales cycle and observed issues. A fixed recovery deadline is not reliable for every migration.

What to do if traffic or leads fall after launch

Do not respond to a decline by changing everything again. First establish whether the problem is real, which segment changed and whether tracking remained comparable. Annotate the release and compare against appropriate seasonal or campaign context.

1. Check availability and directives. Look for outages, errors, unintended noindex rules and blocked resources.
2. Test old and new URL pairs. Confirm destination relevance, redirect behavior and final successful responses.
3. Inspect affected templates. Compare content, canonicals, links and rendered output with the saved baseline.
4. Trace the conversion journey. Confirm forms, booking, routing and analytics still work.
5. Prioritize by commercial exposure. Repair a failing high-value service template before cosmetic inconsistencies.
6. Document and verify each fix. Recheck the outcome rather than assuming a deployed change solved it.

Use rollback when the defined operational conditions justify it and the team understands the consequences. Repeated unplanned switching between versions can create more inconsistency. A targeted correction is often more appropriate than reversing an otherwise healthy release.

Migration mistakes that create avoidable risk

Involving SEO only at launch: by then, URL and content decisions may already be embedded in development. Include review at inventory, architecture, template and release milestones.

Confusing a successful deployment with a successful journey: a server response cannot prove a buyer can submit an enquiry. Test the complete process.

Retiring the old domain too early: an old address may still serve bookmarks and external links. Maintain domain ownership and redirect infrastructure as part of the operating plan.

Reporting only total sessions: totals can conceal lost non-brand demand, changed attribution or a broken high-value page. Use a small dashboard tied to acquisition and qualified outcomes.

Removing detail to fit a template: design should organize information, not dictate that every service receives the same short paragraph. Preserve distinct buyer questions and meaningful content depth.

What to ask a website migration SEO partner

A useful partner should explain deliverables, dependencies and decisions rather than promise zero volatility. Ask who owns the inventory, URL map, technical acceptance criteria, content review, launch support and monitoring. Establish who implements recommendations and who approves trade-offs.

Request evidence of their testing method: example acceptance criteria, redirect validation, template comparison and a prioritized issue register. Clarify how they will coordinate with development and how they distinguish urgent business risk from minor optimization. The scope should include conversion continuity, not only rankings.

For a redesign, connect this work with website design and development so information architecture, readable content, responsive layouts and technical delivery support the same customer journey.

Authoritative references

Google's migration documentation distinguishes hosting-only changes from URL moves. Its URL-move guidance covers mapping, monitoring and maintaining redirects, while its redirect documentation explains permanent and temporary behavior. Use these technical references alongside the business acceptance process above.

• Google Search Central: site moves with URL changes
• Google Search Central: changing hosting infrastructure
• Google Search Central: redirects and Search

Frequently asked questions