Complete SEO Migration Checklist

Migration Strategy

• Define the purpose of the migrationDocument why the website is being migrated and what the project is expected to achieve.
• Identify every element being changedConfirm whether the migration affects the domain, CMS, URL structure, content, design, navigation, hosting, JavaScript framework or HTTPS configuration.Note - Minimise drastic changes asap. For example, think twice before doing a brand/domain change with full content, design and URL change.
• Define what must remain unchangedReduce unnecessary SEO risk by preserving URLs, page content, metadata and site architecture where changes are not required.
• Create a migration timelineDivide the migration into planning, development, testing, launch and post-launch monitoring phases.
• Assign ownership for each migration taskIdentify who is responsible for redirects, development, content, analytics, DNS, quality assurance and SEO monitoring.
• Identify high-risk migration elementsFlag changes involving high-traffic pages, high-value backlinks, international pages, JavaScript rendering or complex URL parameters.
• Establish approval checkpointsRequire SEO approval before development sign-off, before launch and after the first post-launch crawl.
• Create a rollback planDocument how the previous website or configuration can be restored if a critical issue occurs.
• Schedule the migration during a lower-risk periodAvoid launching during major sales periods, campaigns or historically high-traffic dates.
• Prevent uncontrolled website changesIntroduce a temporary content and development freeze before the final migration crawl.

Historical Performance Data

• Export historical organic traffic dataUse historical traffic data to establish a performance baseline for comparing the old and new websites.
• Record organic conversions and revenueCapture leads, sales, transactions, conversion rates and other business outcomes generated through organic search.
• Export page-level landing page performanceIdentify the pages responsible for the highest levels of organic traffic and conversions.
• Record current keyword rankingsTrack priority commercial, informational, branded and local search queries before migration.
• Export Google Search Console performance dataDownload page, query, country, device and search appearance data.
• Export the Google Search Console Index Coverage dataRecord valid pages, excluded pages, indexing errors and discovered URLs.
• Save existing XML sitemapsRetain copies of all current sitemap files and the URLs contained within them.
• Save the existing robots.txt fileDocument the current crawling rules before making changes.
• Export current Core Web Vitals dataRecord page speed and user experience performance for key templates.
• Benchmark mobile responsivenessTest important templates across mobile screen sizes and devices.

Current Website Inventory

• Crawl the complete live websiteCreate an inventory of indexable and non-indexable URLs, internal links, status codes, canonicals and metadata.
• Export all indexable URLsCombine crawl data, XML sitemap URLs, Google Search Console URLs, analytics landing pages and backlink destinations.
• Identify orphan pagesFind pages receiving traffic or backlinks that are not connected through the internal linking structure.
• Record existing URL structure rulesDocument folder structures, trailing slashes, uppercase characters, parameters and pagination formats.
• Export existing meta tagsSave title tags, meta descriptions, robots directives and social metadata.
• Export canonical tagsIdentify self-referencing canonicals, cross-page canonicals and potential canonical inconsistencies.
• Export hreflang implementationRecord language and regional targeting annotations, return links and x-default usage.
• Export structured data markupSave the schema types and properties used on each template.
• Document the current site architectureMap navigation levels, category relationships, content hubs and important internal linking pathways.
• Analyse the internal linking structureIdentify how PageRank and contextual relevance are distributed across the website.

Backlinks and Crawling

• Export the backlink profileIdentify external links pointing to URLs that may change during migration.
• Prioritise high-authority backlink destinationsFlag pages with valuable external links for direct one-to-one redirects.
• Perform log file analysisUse server logs to identify Googlebot crawl patterns, frequently crawled URLs and wasted crawl activity.
• Identify high-value pages for crawl prioritisationPrioritise pages generating traffic, conversions, backlinks or strategic business value.
• Record crawl budget issuesIdentify faceted URLs, parameters, duplicate pages and redirect chains that consume unnecessary crawl resources.
• Back up the existing websiteCreate a complete backup of website files, databases, media, configurations and redirect rules.

Site Architecture

• Design the new site architecture before developmentDefine how categories, services, products and informational content will relate to one another.
• Keep important pages close to the homepageAvoid unnecessarily increasing the number of clicks required to reach high-value pages.
• Preserve valuable content relationshipsMaintain topic clusters, category structures and contextual internal links where they currently perform well.
• Prevent orphan pages in the new architectureEnsure every indexable page can be reached through internal navigation or contextual links.
• Review navigation labelsUse clear labels that communicate page topics to users and search engines.
• Plan breadcrumb navigationMake sure breadcrumbs accurately represent the new site hierarchy.
• Plan internal PageRank distributionUse the internal linking structure to direct authority towards priority pages.
• Prevent excessive navigation depthAvoid creating important pages that can only be reached through several layers of navigation.

URL Structure

• Create the final URL structureDefine the exact format for service, product, category, location and content URLs.
• Preserve existing URLs where possibleDo not change URLs solely for cosmetic reasons.
• Use consistent URL formattingStandardise lowercase characters, trailing slashes, hyphens and folder structures.
• Avoid unnecessary URL parametersPrevent tracking, filtering and sorting parameters from creating crawlable duplicate URLs.
• Resolve duplicate URL versionsDetermine the preferred version for HTTP, HTTPS, www, non-www and trailing slash variations.
• Prevent multiple URLs from serving identical contentUse URL rules, canonical tags or redirects to consolidate duplicate versions.
• Document all intentionally removed pagesDecide whether each removed page should be redirected, replaced, consolidated or return a 404 or 410 response.

Redirect Strategy

• Create a complete old-to-new URL redirect mapMap every valuable old URL to the most relevant new destination.
• Use one-to-one 301 redirectsRedirect each old page directly to the closest equivalent new page.
• Preserve link equity through 301 redirectsEnsure pages with backlinks, traffic or rankings transfer their signals to relevant destinations.
• Avoid redirecting every removed page to the homepageOnly redirect a URL when a relevant replacement exists.
• Avoid redirect chainsEvery old URL should redirect directly to its final destination.
• Avoid redirect loopsTest that redirects do not repeatedly send users and crawlers between URLs.
• Consolidate previous redirect chainsUpdate historical redirects so they point directly to the new final URL.
• Map HTTP URLs directly to final HTTPS URLsAvoid separate HTTP-to-HTTPS and old-to-new redirect steps.
• Map www and non-www versions directlySend all hostname variations to the final preferred URL.
• Include parameter and trailing slash variationsAccount for alternate versions that receive traffic, links or search engine crawling.
• Include uppercase and lowercase URL variationsPrevent important legacy URLs from returning errors due to case sensitivity.
• Redirect old PDF and media URLs where requiredPreserve valuable links pointing to downloadable files and media assets.
• Document URLs that should return 404 or 410 responsesDo not redirect removed content when no relevant replacement exists.
• Review redirects for topical relevanceThe destination should satisfy the same or closely related user intent as the old page.
• Keep migration redirects active indefinitely where practicalDo not remove redirects simply because the migration has been completed.

Staging Environment Controls

• Create a dedicated staging environmentTest the complete migration before making the new website publicly available.
• Prevent staging pages from being indexedUse password protection or server-level authentication rather than relying only on robots.txt.
• Prevent staging canonical tags from referencing staging URLsConfigure canonicals to use the intended production URLs.
• Prevent staging URLs from appearing in XML sitemapsOnly final production URLs should be included in launch-ready sitemap files.
• Prevent analytics contaminationExclude staging traffic from production analytics reporting.
• Prevent external links to staging URLsReview preview links, emails and project documents before launch.

CMS and Template Configuration

• Configure the content management system correctlyMake sure the CMS generates the intended URLs, canonicals, meta tags and robots directives.
• Test title tag outputConfirm every indexable page can have a unique and relevant title tag.
• Test meta description outputConfirm descriptions can be controlled at page and template level.
• Test robots meta directivesMake sure indexable pages are not accidentally marked noindex or nofollow.
• Test canonical tag outputEvery indexable page should reference the correct preferred URL.
• Test pagination and faceted navigation rulesPrevent filters, sorting and combinations from creating uncontrolled indexable URLs.
• Test category and archive templatesConfirm important category pages contain unique content, metadata and internal links.
• Test media URL behaviourPrevent unwanted attachment pages or duplicate media URLs from being indexed.
• Test structured data markupConfirm templates generate valid and accurate structured data.
• Preserve structured data properties from the old websiteDo not remove useful Product, Article, Breadcrumb, Organisation, LocalBusiness or other relevant markup during migration.

Content Parity

• Maintain content parity between old and new pagesPreserve the main content, headings, images, FAQs and supporting information responsible for existing rankings.
• Retain important heading structuresAvoid removing or significantly weakening relevant H1, H2 and H3 content.
• Retain important text contentDo not replace detailed, valuable content with shorter design-led copy without SEO review.
• Retain important image assets and alt textPreserve useful images, descriptive filenames and relevant alternative text.
• Retain trust and credibility contentPreserve author details, reviews, qualifications, policies, references and business information.
• Retain conversion elementsEnsure forms, calls to action, ecommerce functionality and contact options remain available.
• Review duplicate content introduced by templatesPrevent repeated headings, descriptions or boilerplate text from dominating page content.

Internal Linking Structure

• Update all internal links to final URLsInternal links should not rely on redirects.
• Update navigation linksCheck header, footer, sidebar, mobile and mega-menu navigation.
• Update contextual content linksReplace old URLs in articles, service pages, product descriptions and FAQs.
• Update image and button linksCheck linked images, banners, buttons and calls to action.
• Update breadcrumb linksMake sure breadcrumbs follow the final architecture.
• Update hreflang URLsAll hreflang references must point to final indexable URLs.
• Update canonical URLsCanonical tags should not point through redirects.
• Update structured data URLsSchema properties should use final production URLs.

JavaScript and Rendering

• Review the JavaScript frameworkIdentify whether important content depends on client-side JavaScript rendering.
• Confirm important content appears in rendered HTMLSearch engines should be able to access headings, links, product information and primary copy.
• Test server-side rendering or pre-renderingUse rendering methods that make critical content available efficiently.
• Test JavaScript-generated internal linksLinks should use crawlable anchor elements and valid destination URLs.
• Test lazy-loaded content and imagesEnsure important content can load without requiring unsupported user interactions.
• Test JavaScript error handlingConfirm page content remains accessible when scripts fail or load slowly.
• Measure JavaScript impact on page speedLarge scripts should not significantly delay rendering or user interaction.

Full Staging Crawl

• Crawl the complete staging websiteReview all URLs, status codes, metadata, canonicals, directives and internal links.
• Compare the staging crawl with the live website crawlIdentify missing pages, missing content and unexpected URL changes.
• Confirm all intended pages are accessibleNo priority page should return a 404, 403 or 500 response.
• Confirm all indexable pages return a 200 statusPages should not depend on redirects to become accessible.
• Identify broken internal linksFix links leading to errors, redirects or removed content.
• Identify orphan pagesConfirm every important page is connected to the new site architecture.
• Review crawl depthCheck that high-value pages remain easily accessible.

Redirect Testing

• Test the complete redirect mappingCheck every old URL against the planned destination.
• Confirm permanent 301 status codesAvoid temporary 302 or 307 redirects unless intentionally required.
• Identify redirect chainsUpdate redirects so each old URL resolves directly to the final destination.
• Identify redirect loopsResolve any URLs that repeatedly redirect between destinations.
• Test high-traffic URLs manuallyVerify the pages most responsible for traffic and conversions.
• Test backlink destination URLs manuallyConfirm high-value external links resolve to relevant final pages.
• Test redirect behaviour with query parametersCheck tracking, filtering and campaign URL variations.

Indexing Controls

• Review the robots.txt fileConfirm important CSS, JavaScript, image and page resources are crawlable.
• Remove staging disallow rules before launchDo not transfer sitewide crawling restrictions to production.
• Review all noindex directivesConfirm no priority pages are accidentally excluded from indexing.
• Review canonical tagsConfirm canonicals point to indexable, final, 200-status URLs.
• Confirm self-referencing canonicalsUse self-referencing canonicals on standard indexable pages where appropriate.
• Remove canonicals pointing to old URLsNo new page should canonicalise to a redirected or retired URL.
• Review duplicate content handlingConfirm alternate and parameter URLs consolidate to the preferred version.

XML Sitemap

• Generate a new XML sitemapInclude only final, canonical and indexable URLs.
• Exclude redirected URLs from the sitemapOld URLs should not remain in the new XML sitemap.
• Exclude 404 and non-indexable URLsEvery sitemap URL should return a valid 200 response.
• Exclude canonicalised duplicate URLsOnly preferred canonical URLs should be submitted.
• Split large sitemaps logicallyUse separate sitemaps for products, categories, services, articles or languages where useful.
• Add the sitemap location to robots.txtReference the final production sitemap index.

Hreflang Implementation

• Validate hreflang language and region codesUse supported ISO language and regional combinations.
• Confirm hreflang return linksEach language version should reference the other corresponding versions.
• Confirm self-referencing hreflang annotationsEach page should include its own language and regional version.
• Review x-default implementationUse x-default where a neutral or language-selection page is available.
• Remove hreflang references to redirected URLsAll annotations should point directly to final indexable pages.
• Confirm canonical and hreflang alignmentEach language page should normally canonicalise to itself.

Structured Data

• Validate structured data markupCheck syntax, required properties and supported schema types.
• Confirm structured data matches visible page contentDo not include information in markup that users cannot see on the page.
• Update all structured data URLsReplace old domains, logos, images and page references.
• Test breadcrumb structured dataConfirm breadcrumb items reflect the new site architecture.
• Test product and availability dataVerify prices, stock status, currency and product identifiers.
• Test organisation and local business informationConfirm names, addresses, phone numbers, logos and social profiles are accurate.

Performance and Mobile Testing

• Test page speed on key templatesMeasure the homepage, categories, products, services, articles and conversion pages.
• Review Core Web VitalsIdentify issues affecting loading, interaction responsiveness and visual stability.
• Optimise image deliveryUse appropriately sized, compressed and modern image formats.
• Reduce render-blocking resourcesReview unnecessary scripts, stylesheets and third-party tools.
• Test mobile responsivenessCheck content, navigation, forms, tables and interactive elements on mobile devices.
• Confirm mobile content parityThe mobile version should contain the same important content and links as the desktop version.
• Test tap targets and font sizesMake sure mobile users can interact with the website comfortably.

Analytics and Tracking

• Install analytics tracking on staging for testingVerify tracking without contaminating production reports.
• Test Google Tag Manager containersConfirm the correct container will be published at launch.
• Test conversion eventsValidate form submissions, calls, purchases, bookings and other key actions.
• Test ecommerce trackingConfirm product views, add-to-cart events, checkout steps and purchases.
• Preserve campaign attributionCheck that redirects and domain changes do not unnecessarily remove tracking parameters.
• Create migration annotationsRecord the launch date in analytics, ranking and reporting systems.

Launch Readiness

• Verify Google Search Console ownershipConfirm access to both the old and new domain properties when a domain changes.
• Prepare the new XML sitemap for submissionHave the production sitemap URL ready before launch.
• Prepare DNS configuration changesDocument the required DNS records, nameservers, TTL values and rollback settings.
• Reduce DNS TTL before launch where appropriateThis can help DNS changes propagate more quickly.
• Verify SSL certificate configurationConfirm the certificate covers all required domains and subdomains.
• Test HTTPS resourcesPrevent mixed content warnings caused by HTTP images, scripts or stylesheets.
• Create a final launch-day checklistDocument the exact order in which development, SEO, DNS and tracking changes will be deployed.
• Receive final stakeholder approvalConfirm the website has passed SEO, development, content and conversion testing.

Deployment

• Publish the production websiteConfirm the final site is available on the intended domain and protocol.
• Implement all 301 redirects at launchRedirects should be active as soon as the new website becomes accessible.
• Apply the final DNS configurationConfirm the domain resolves to the correct hosting environment.
• Activate the final SSL certificateVerify all website versions resolve securely through HTTPS.
• Remove staging access restrictionsProduction pages must be accessible to users and search engine crawlers.
• Publish the production robots.txt fileConfirm important sections are not accidentally blocked.
• Publish the new XML sitemapMake sure the sitemap contains only final production URLs.
• Publish the final analytics configurationConfirm analytics and tag management systems are collecting live data.

Immediate Launch Validation

• Test the homepage and priority templatesConfirm pages load correctly across desktop and mobile devices.
• Test a representative sample of old URLsVerify old pages redirect directly to their mapped destinations.
• Test the complete redirect list programmaticallyIdentify failed redirects, chains, loops and incorrect destinations.
• Check for server errorsMonitor 500, 502, 503 and other server-level failures.
• Check HTTPS and domain variationsConfirm HTTP, www and non-www versions resolve directly to the preferred version.
• Check canonical tags on productionMake sure staging domains and old URLs are not referenced.
• Check hreflang annotations on productionConfirm language references use final production URLs.
• Check structured data on productionVerify markup remains valid after deployment.
• Check analytics and conversionsComplete test submissions or transactions to confirm tracking.
• Check mobile responsivenessConfirm deployment has not introduced layout or interaction issues.

Search Engine Communication

• Submit the new XML sitemap in Google Search ConsoleUse the sitemap to guide search engine crawling towards the final URLs.
• Use the Change of Address tool when applicableUse this for a qualifying domain migration after redirects and verification are complete.
• Inspect priority URLs in Google Search ConsoleConfirm Google can access, render and index representative pages.
• Request indexing for priority pages where appropriatePrioritise the homepage and important commercial pages rather than submitting every URL manually.
• Retain the old Google Search Console propertyContinue monitoring old URLs, links, errors and redirect behaviour.
• Submit sitemaps to other relevant search enginesUpdate Bing Webmaster Tools and other applicable platforms.

Technical Monitoring

• Crawl the complete live website immediately after launchCompare the production crawl with the final staging crawl.
• Monitor Google Search Console Index CoverageWatch for indexing errors, excluded pages and unexpected canonical selections.
• Monitor sitemap processingCompare submitted, discovered and indexed URL counts.
• Monitor server logsUse log file analysis to understand Googlebot crawl patterns after migration.
• Monitor crawl budget allocationConfirm search engines are prioritising high-value pages rather than parameters, errors or redirect chains.
• Monitor 404 errorsIdentify missing redirect mappings and broken internal links.
• Monitor server errorsInvestigate recurring 5xx errors immediately.
• Monitor redirect chainsCorrect chains that waste crawl budget and slow user navigation.
• Monitor canonical selectionCheck whether Google is selecting unexpected old, duplicate or alternate URLs.
• Monitor robots.txt accessConfirm crawlers are not blocked from important pages or resources.
• Monitor page renderingCheck that search engines can access content produced by the JavaScript framework.
• Monitor page speed and Core Web VitalsCompare production performance with the pre-migration baseline.

Performance Monitoring

• Monitor organic traffic dailyCompare overall and page-level traffic with historical performance.
• Monitor organic conversions and revenueConfirm the migration has not disrupted business outcomes.
• Monitor priority keyword rankingsLook for significant losses across important search queries.
• Monitor branded search performanceCheck whether users can still find the business and key brand pages.
• Monitor high-traffic landing pagesInvestigate unexpected declines affecting priority URLs.
• Monitor mobile organic performanceIdentify device-specific traffic, rendering or usability issues.
• Compare old and new page performanceUse redirect mapping to analyse performance at page level.

Link Reclamation

• Identify external links still pointing to redirected URLsUse the backlink profile to find valuable links that can be updated.
• Contact high-value linking websitesRequest that important backlinks be changed to the final destination URL.
• Update owned external profilesChange links on social profiles, directories, partner websites and business listings.
• Update paid campaign destination URLsPrevent advertising traffic from passing through unnecessary redirects.
• Update email and marketing linksReplace old URLs in automated emails, downloadable documents and campaign templates.
• Update internal links across related websitesChange links from sister websites, subdomains and microsites.
• Monitor lost and broken backlinksIdentify backlinks pointing to pages that were not included in the redirect mapping.
• Review backlink relevance after consolidationConfirm consolidated pages still satisfy the context of inherited backlinks.

Indexation and Crawling

• Track the indexing of new URLsCompare submitted URLs with indexed URLs over time.
• Track the removal of old URLs from search resultsOld URLs should gradually be replaced by their final destinations.
• Investigate old URLs that remain indexedReview redirects, canonicals, internal links and sitemap references.
• Investigate new pages that remain unindexedCheck content quality, crawl access, canonical tags and internal linking.
• Review crawl frequency using log filesConfirm search engines are increasingly crawling the new URL structure.
• Review crawl budget efficiencyReduce unnecessary crawling of parameters, duplicates, redirect chains and low-value pages.
• Keep old XML sitemaps temporarily where usefulOld sitemaps can help search engines discover redirects during a large migration, but they should not remain the primary submitted sitemap indefinitely.

Traffic and Ranking Recovery

• Compare organic traffic with the historical baselineAccount for seasonality, campaigns, algorithm changes and market conditions.
• Compare page-level performanceMatch old URLs to new URLs rather than relying only on sitewide totals.
• Compare keyword visibilityReview ranking changes by page type, topic, country and device.
• Compare organic conversionsCheck whether traffic quality and conversion performance have been preserved.
• Investigate pages with significant lossesReview content parity, redirect relevance, internal links, canonicals and rendering.
• Investigate sections with indexing declinesLook for shared template, architecture or CMS configuration problems.
• Monitor competitor and search result changesSeparate migration-related losses from wider ranking changes.

Final Optimisation

• Strengthen internal links to underperforming pagesAdd relevant contextual links from authoritative pages.
• Restore missing content elementsReintroduce useful text, FAQs, media, headings or trust elements removed during migration.
• Improve pages with weak content parityEnsure new pages continue satisfying the same search intent as the previous versions.
• Correct metadata issuesResolve duplicate, missing or truncated title tags and meta descriptions.
• Correct canonical inconsistenciesMake sure canonical tags reflect the intended indexable URL structure.
• Correct hreflang errorsResolve missing return links, incorrect codes and non-indexable destinations.
• Correct structured data errorsUpdate invalid or incomplete markup introduced during development.
• Improve page speedAddress scripts, images, fonts, third-party tools and server performance issues.
• Improve mobile responsivenessResolve layout shifts, hidden content and difficult mobile interactions.
• Remove internal links to redirected URLsThe final internal linking structure should point directly to 200-status pages.
• Update the redirect map with newly discovered URLsAdd missing legacy URLs found through logs, backlinks, analytics or Google Search Console.
• Keep monitoring high-value pagesContinue tracking the pages responsible for the greatest traffic, authority and conversions.

• Prepare a final migration performance reportSummarise traffic, rankings, conversions, indexing, crawling and technical outcomes.
• Compare results with the pre-migration baselineMeasure whether organic visibility and business performance have recovered.
• Document unresolved migration issuesAssign owners and deadlines for remaining technical or content tasks.
• Document successful migration decisionsRecord the methods, configurations and processes that worked well.
• Retain all migration documentationKeep crawls, redirect maps, benchmarks, backups, launch notes and monitoring reports.
• Continue maintaining redirectsDo not remove valuable 301 redirects after reporting has ended.
• Schedule a future technical SEO auditReview the website again after search engines have fully processed the migration.