--- title: "Migration SEO Checklist | Pre & Post" site: "Silverback Marketing" domain: "silverbackmarketing.com" type: "Guide" description: "Protect rankings through redesigns and CMS migrations with 89 tasks for redirects, content parity, tracking, schema, launch QA, and 60-day monitoring." canonical: "https://silverbackmarketing.com/resources/website-migration-seo-checklist" markdown: "https://silverbackmarketing.com/resources/website-migration-seo-checklist.md" --- Migration checklist # Website Migration SEO Checklist Protect rankings, traffic, and conversions through a redesign or platform migration. This interactive 2026 checklist covers 89 items across pre-launch discovery, staging QA, redirects, content parity, launch-day execution, and 60-day post-launch monitoring, with progress you can track as you go. Start here ## 00: How to Use This Migration Checklist Pre-launch, launch, and post-launch SEO governance Use this as a project governance document, not just a launch-day QA list. Assign owners and due dates for each section before design and development begin. Treat URL preservation, content parity, internal linking, redirects, analytics, and indexation controls as critical path items. Complete pre-launch validation on staging, complete launch-day QA immediately after go-live, then monitor daily during the first week and weekly for the next 30 to 60 days. - Checklist sections: 12 · Pre-launch through post-launch benchmarks - Checklist items: 89 · Interactive tasks with guidance notes - Migration phases: 3 · Pre-launch, launch day, and 60-day monitoring - Checklist edition: 2026 · Website redesign and migration SEO framework ### Collaboration notes The design team should share wireframes, templates, navigation plans, and URL changes early enough for SEO review before development is final. Silverback should review page templates, content parity, metadata, redirects, schema, analytics, and launch QA before final approval. The client should identify business-critical pages and conversion paths that must be protected even if they are not the highest organic traffic drivers. The development team should confirm how redirects, canonicals, robots directives, XML sitemaps, schema, forms, and tracking will be managed in the new environment. ### 01: Pre-Launch Phase 1–8: Discovery, staging, URL mapping, content parity, architecture, technical SEO, schema, analytics ### 02: Launch Phase 9–10: Pre-launch signoff and launch-day execution checklist ### 03: Post-Launch Phase 11–12: Monitoring for 60 days and capturing baseline benchmarks Section 01 ## 01: Discovery and Redesign Risk Assessment Pre-Launch Phase - **Document what is changing** · Confirm whether the project changes design, CMS, hosting, URLs, templates, navigation, footer, forms, tracking, schema, blog structure, gated assets, or media files. - **Identify critical organic URLs** · Pull priority URLs from GA4, GSC, backlink data, rankings, CRM/conversion data, and paid media landing page usage. - **Create a page-level risk score** · Flag URLs that drive organic traffic, rank for non-branded terms, attract backlinks, generate leads, support paid campaigns, or appear in AI/GEO answers. - **Define URL preservation rules** · Default to preserving current URLs unless there is a clear SEO, UX, or business reason to change them. - **Review proposed information architecture** · Map old navigation, new navigation, footer links, utility links, hub pages, and key landing page pathways. - **Confirm content ownership** · Assign who approves copy, metadata, schema, internal links, redirects, forms, and analytics before launch. - **Confirm launch constraints** · Identify blackout dates, slow-season launch windows, developer availability, DNS/hosting dependencies, and rollback options. Section 02 ## 02: Staging and Crawl Control Pre-Launch Phase ### Important note Important Note: The preferred method is password protection for staging. Do not rely on both robots.txt disallow and noindex as a default strategy, because blocking crawlers can prevent search engines from seeing a noindex directive. - **Password protect staging** · Best practice for dev/staging environments. Verify that staging cannot be accessed or indexed publicly. - **Use noindex carefully when needed** · If password protection is not possible, use noindex on staging pages that can be crawled. Remove before launch. - **Avoid accidental production blocking** · Confirm that no staging robots.txt, noindex, nofollow, or X-Robots-Tag settings migrate to production. - **Prevent duplicate staging URLs** · Block or restrict staging subdomains, preview URLs, CDN URLs, and temporary environments from public indexation. - **Create a staging QA crawl** · Crawl staging with JavaScript rendering enabled where appropriate and compare against the live benchmark crawl. Section 03 ## 03: URL Inventory and 301 Redirect Strategy Pre-Launch Phase - **Export all known current URLs** · Use Screaming Frog, XML sitemaps, GSC indexed/traffic URLs, GA4 landing pages, backlinks, CMS exports, paid media URLs, email URLs, and sales collateral URLs. - **Classify each URL** · Keep, change, consolidate, remove, noindex, or redirect. - **Map every changing URL one-to-one** · Redirect each old URL to the most relevant new URL. Avoid redirecting valuable pages to the homepage unless no relevant destination exists. - **Preserve high-value URLs where possible** · Strongly consider preserving URLs with rankings, backlinks, organic traffic, conversions, or strategic business importance. - **Audit existing redirects** · Identify redirect chains, loops, 302s that should be 301s, invalid destinations, and redirects to pages that will also change. - **Create the new redirect file** · Include legacy redirects plus new redesign redirects. Validate syntax in the destination environment. - **Test redirects before launch where possible** · Use a staging or rules preview environment to verify status codes and destinations. - **Update internal links** · Do not rely only on redirects. Update navigation, body links, XML sitemaps, canonicals, hreflang if applicable, and marketing links to the final URLs. Section 04 ## 04: Content Parity and On-Page Optimization Pre-Launch Phase - **Compare old vs. new priority pages** · Confirm that important body copy, headings, FAQs, proof points, product/service descriptions, trust signals, and conversion CTAs are not unintentionally removed. - **Preserve search intent alignment** · Validate that each redesigned page still satisfies the intent behind the keywords it currently ranks for. - **Create metadata for every indexable page** · Finalize title tags, meta descriptions, H1s, heading structure, canonical URLs, and image alt text. - **Review new pages for SEO opportunity** · Perform keyword and intent research for new pages, then define URL slugs, titles, H1s, FAQs, internal links, and schema. - **Protect existing optimized content** · Do not allow template redesigns to remove optimized intros, supporting copy, FAQs, comparison content, or internal links from high-value pages. - **Check duplicate and thin content risk** · Identify pages that may become too similar after redesign, especially product, solution, location, resource, tag, and category templates. - **Review downloadable and gated assets** · Confirm important PDFs, reports, landing pages, and thank-you pages retain accessible titles, tracking, and internal links where appropriate. Section 05 ## 05: Site Architecture and Internal Linking Pre-Launch Phase - **Review new navigation structure** · Confirm that priority product, solution, service, industry, location, and resource pages remain discoverable through crawlable links. - **Protect homepage and global link equity** · Confirm that redesign changes do not remove important links from the homepage, primary nav, footer, or hub pages. - **Define anchor text strategy** · Use descriptive, crawlable anchor text for priority internal links. Avoid vague labels where SEO context matters. - **Validate hub-and-spoke relationships** · Confirm that parent pages link to child pages and child pages link back to relevant parent or related pages. - **Find lost internal links** · Compare live vs. staging crawls to identify high-value URLs that lose internal links or crawl depth. - **Check body-content links** · Confirm that contextual internal links are present in body copy, not only in navigation modules. - **Verify breadcrumb implementation** · Use visible breadcrumbs where appropriate and align them with BreadcrumbList schema. Section 06 ## 06: Technical SEO and Rendering QA Pre-Launch Phase - **Run live benchmark crawl** · Capture indexability, status codes, titles, meta descriptions, H1s, canonicals, robots directives, internal links, images, schema, and response times. - **Run staging crawl** · Crawl staging with the same settings and compare live vs. staging exports. - **Enable JavaScript rendering checks** · Confirm Googlebot-rendered HTML can access primary copy, navigation, internal links, schema, canonical tags, pagination links, and CTAs. - **Review indexation controls** · Validate robots.txt, meta robots, X-Robots-Tag headers, canonicals, nofollow usage, parameter rules, and sitemap inclusion. - **Check canonical consistency** · Canonical URLs should point to the final preferred URLs, use the correct protocol and host, and not point to staging. - **Check status codes** · Confirm indexable pages return 200, redirected URLs return 301 where appropriate, and removed pages have a deliberate redirect or 404/410 decision. - **Review Core Web Vitals and page speed** · Benchmark live templates, test staging templates, and prioritize mobile performance issues before launch. - **Validate mobile usability and accessibility basics** · Check responsive behavior, tap targets, heading order, form usability, alt text, contrast, and keyboard-friendly navigation. - **Remove outdated pagination requirement** · Do not treat rel prev/next as a Google SEO requirement. Focus on crawlable pagination links, canonicals, and indexation strategy. Section 07 ## 07: Structured Data, Entity Signals, and GEO/AI Visibility Pre-Launch Phase - **Audit existing schema** · Inventory current Organization, WebSite, BreadcrumbList, Article, FAQ, Product, SoftwareApplication, Event, Review, and other structured data. - **Define schema by template type** · Assign the correct schema pattern to homepage, product/service pages, industry pages, resource pages, blog posts, webinars, events, authors, and reviews. - **Validate structured data** · Use Rich Results Test and Schema Markup Validator. Fix missing required fields, broken JSON-LD, duplicate entities, or staging URLs. - **Strengthen entity clarity** · Make sure the site clearly explains who the company is, what it offers, who it serves, and how products/services relate to each other. - **Review AI/GEO answer-readiness** · Add concise answer-style sections, FAQs, comparison language, use cases, stats, and proof points where they help users and AI systems understand the page. - **Surface trust signals in crawlable HTML** · Avoid placing important testimonials, ratings, awards, partner logos, or proof points only in iframes or images. - **Review llms.txt and related files if used** · Update llms.txt or llms-full.txt after launch so priority pages, descriptions, and key answer resources reflect the new site. Section 08 ## 08: Analytics, CRM, Consent, and Conversion Tracking Pre-Launch Phase - **Inventory all tracking requirements** · GA4, GTM, Google Ads, Microsoft Ads, LinkedIn, Meta, HubSpot, Pardot, Salesforce, call tracking, heatmaps, chat, cookie consent, and other tools. - **Define GA4 key events** · Confirm form submissions, phone clicks, demo requests, downloads, video events, chat starts, and other meaningful conversions. - **Test forms end to end** · Submit test leads and confirm source/medium, landing page, GCLID/GBRAID/WBRAID, UTMs, hidden fields, CRM routing, and notification emails. - **Validate consent behavior** · Confirm cookie banner and consent mode do not break analytics, ads tags, CRM tracking, or compliance requirements. - **Preserve paid media tracking** · Update final URLs, landing pages, thank-you pages, conversion actions, offline conversion imports, and remarketing audiences. - **Create GA4 launch annotation** · Add an annotation for the launch date and note major changes such as CMS, URL structure, navigation, or tracking updates. - **Document baseline conversion data** · Capture pre-launch organic leads, key events, conversion rates, call volume, and CRM-qualified outcomes for comparison. Section 09 ## 09: Pre-Launch Signoff Checklist Launch Phase - **Redirect map approved** · All changed URLs are mapped, legacy redirects are accounted for, and priority redirects are tested. - **SEO elements approved** · Titles, meta descriptions, H1s, canonicals, indexation rules, image alt text, and schema are reviewed. - **Content parity approved** · Priority pages retain the content and intent needed to protect rankings, leads, and AI/GEO visibility. - **Crawl comparison completed** · Live and staging crawl differences are reviewed and critical issues are resolved. - **Tracking QA completed** · GA4, GTM, CRM, ad pixels, call tracking, form tracking, and consent behavior are tested. - **XML sitemap prepared** · Final XML sitemap reflects the new indexable URL set and excludes staging, redirects, noindex pages, and non-canonical URLs. - **Robots.txt prepared** · Production robots.txt references the XML sitemap and does not block important site sections. - **Launch QA plan assigned** · Owners are assigned for redirect testing, crawl testing, tracking testing, sitemap submission, and issue escalation. Section 10 ## 10: Launch-Day Checklist Launch Phase - **Remove staging restrictions from production** · Verify production is not password protected and does not contain staging noindex, nofollow, robots.txt disallow, or X-Robots-Tag rules. - **Publish redirects** · Implement the final redirect file immediately at launch. - **Test priority redirects** · Validate status codes and destinations for top organic URLs, top backlink URLs, paid media URLs, and high-risk changed URLs. - **Verify production robots.txt** · Confirm robots.txt is live at the root and references the correct XML sitemap URL. - **Submit XML sitemap** · Submit or resubmit the final sitemap in Google Search Console and Bing Webmaster Tools. - **Run production crawl** · Crawl the live site immediately after launch and prioritize issues affecting indexability, redirects, canonicals, schema, and tracking. - **Validate analytics and conversions** · Confirm real-time GA4 activity, key events, form submissions, phone clicks, CRM records, and ad tags. - **Check top templates manually** · Review homepage, product/service pages, blog/resource pages, contact/demo pages, location pages if applicable, and gated asset flows. - **Create launch annotation** · Add launch annotation in GA4 and document the date, time, and major changes. Section 11 ## 11: Post-Launch Monitoring: First 60 Days Post-Launch Phase - **Daily checks during week one** · Monitor GSC indexing, crawl errors, 404s, redirect issues, analytics activity, conversion tracking, and top landing page performance. - **Weekly checks for 30 to 60 days** · Monitor rankings, organic clicks, impressions, landing pages, conversions, crawl stats, indexed URLs, and page experience trends. - **Resolve 404s with intent** · Redirect valuable or expected URLs to the most relevant page. Do not mass-redirect every 404 to the homepage. - **Monitor ranking volatility** · Expect some short-term fluctuation. Escalate if priority pages lose indexation, content parity, internal links, or relevant redirects. - **Compare organic landing pages** · Watch for unexpected losses in high-value pages and confirm new URLs are replacing old URLs where redirects were used. - **Monitor conversion quality** · Compare organic leads, key events, calls, CRM-qualified outcomes, and paid media conversion quality against baseline. - **Re-crawl after fixes** · Run follow-up crawls after major technical fixes to confirm the issue is resolved and no new issue was introduced. - **Update documentation** · Save final redirect file, sitemap, crawl exports, launch notes, issue log, and post-launch recommendations. Section 12 ## 12: Priority QA Exports and Benchmarks Post-Launch Phase - **GA4 baseline** · Organic sessions, users, engaged sessions, key events, conversion rate, landing pages, and source/medium performance. - **GSC baseline** · Clicks, impressions, CTR, average position, indexed pages, top queries, top pages, and coverage/indexing issues. - **Ranking baseline** · Priority non-branded rankings, branded rankings, local rankings if applicable, and AI/GEO visibility snapshots if available. - **Crawl baseline** · Live crawl export before launch, staging crawl before launch, production crawl after launch, and issue comparison. - **Backlink baseline** · Top linked pages and linked URLs that must be preserved, redirected, or updated. - **Performance baseline** · Core Web Vitals, PageSpeed/Lighthouse snapshots, mobile template performance, and server response trends. - **Conversion baseline** · Forms, calls, demo requests, downloads, CRM-qualified leads, SQLs, and any offline conversion imports. Reference ## 13: Launch Severity Levels Classify issues and set response timelines - Critical: Production noindex, blocked robots.txt, broken sitewide canonicals, missing analytics, major redirect failure, forms not working. · Fix immediately before or during launch window. - High: Priority pages losing content, high-value URLs 404ing, schema broken across key templates, major CWV regression, tracking partially broken. · Fix within 24 to 72 hours. - Medium: Metadata gaps, minor redirect chains, missing image alt text, internal link opportunities, isolated schema warnings. · Fix during first two post-launch weeks. - Low: Cosmetic SEO refinements, secondary copy updates, minor accessibility improvements, documentation cleanup. · Backlog after critical monitoring period. ### Website Migration SEO Silverback runs the full checklist: URL mapping, redirect QA, content parity, tracking validation, and post-launch monitoring. [View migration SEO](/services/website-migration-seo) ### Request a Migration Audit Get a pre-launch risk assessment, redirect map review, and launch-day QA plan before you go live. [Request an audit](/contact/request-an-audit) ### Technical SEO Priority Matrix Pair this checklist with developer-ready P1–P4 fixes for crawl, CWV, schema, and rendering issues. [View priority matrix](/resources/technical-seo-priority-matrix) ### SEO & GEO Audit Interactive Checklist Run a full SEO and GEO baseline audit before or after migration to protect rankings and AI visibility. [View audit interactive checklist](/resources/seo-geo-audit-interactive-checklist)