Post-Migration SEO Audit: What to Check After Go-Live

The riskiest moment in any website migration is not the launch itself, it is the first 72 hours after go-live. That is when broken redirect chains, blocked crawlers, missing canonical tags, and dropped meta data quietly erode the equity you spent years building. Search engines do not wait for you to notice, they recrawl, reindex, and recalculate rankings based on whatever they find the moment your new site is live.

A disciplined post-migration SEO audit is your safety net. It is a systematic pass across crawlability, indexation, redirects, on-page signals, technical health, and analytics, run immediately after launch and again over the following weeks. This companion guide walks through exactly what to check, in what order, and how to confirm each item is actually correct rather than merely present. If you are still planning the cutover, our website migration services team runs this audit as a standard part of every project.

Work through the sections below in sequence. The early checks (crawlability and redirects) gate everything downstream, so do not skip ahead. Where a check can be automated, we note the tool that verifies it fastest.

1. Confirm Crawlability and Indexability First

Before anything else, make sure search engines can access the new site and are permitted to index it. The single most common catastrophic migration error is shipping the staging environment's noindex tag or a Disallow: / robots.txt directive into production. Everything else is irrelevant if Google is being told to stay out.

• robots.txt — Fetch /robots.txt directly in a browser. Confirm there is no site-wide Disallow: / and that your XML sitemap is referenced.
• Meta robots and X-Robots-Tag — View source on key templates (home, category, product, blog post) and confirm no <meta name="robots" content="noindex">. Check the HTTP response headers too, since X-Robots-Tag can noindex a page invisibly.
• HTTP status codes — Every indexable URL should return 200. Crawl the site with Screaming Frog or Sitebulb and filter for anything returning 3xx, 4xx, or 5xx.
• Password protection and IP allowlists — Confirm staging-era HTTP auth is fully removed from production.
• Rendering — For JavaScript-heavy builds, use Google's URL Inspection tool to view the rendered HTML and confirm content and links actually appear to the crawler.

2. Validate Every Redirect Rule

Redirects are how you transfer ranking equity from old URLs to new ones. If a migration changed URL structures, every legacy URL that had traffic, links, or rankings must 301 redirect to its closest new equivalent. Getting this wrong is the fastest way to lose organic visibility.

Build a master list of old URLs from your pre-migration crawl, XML sitemaps, Google Search Console's Pages report, and your backlink profile (Ahrefs or Semrush). Then test that list against production.

• Status must be 301, not 302 — Temporary 302s do not pass equity reliably. Confirm each redirect returns a permanent 301.
• No redirect chains or loops — Old URL should hop once to the final destination. Chains (A→B→C) dilute equity and slow crawling. A→B→A loops break the page entirely.
• One-to-one relevance — A product page should redirect to the equivalent product, not blanket-redirected to the homepage. Mass homepage redirects are treated as soft 404s and pass almost no value.
• HTTPS and www consistency — Confirm http→https and your chosen www/non-www variant all resolve with a single 301 to the canonical version.

Redirect logic often lives in application code or CDN rules rather than a plain file, which is one reason we handle it inside the custom development workflow where the rules can be tested programmatically before launch.

3. Audit On-Page Elements and Metadata

Migrations frequently strip or reset on-page SEO signals when content moves between systems. A template that forgets to output the migrated title tag will silently replace thousands of optimized titles with a generic default. Crawl the live site and compare against your pre-migration baseline.

• Title tags and meta descriptions — Confirm they carried over and are unique per page, not duplicated site-wide defaults.
• Heading structure — Each page should retain a single, descriptive H1 and a logical heading hierarchy.
• Canonical tags — Every page should self-canonical to its own live HTTPS URL. Watch for canonicals still pointing at the old domain or the staging subdomain, a classic migration bug.
• Image alt text and file references — Confirm images load (no broken src paths) and alt attributes survived.
• Internal links — Update hardcoded internal links pointing at old URLs so they hit the new destination directly instead of relying on redirects.
• Structured data — Re-validate JSON-LD schema in the Rich Results Test; migrations often break Organization, Product, Article, and Breadcrumb markup.

4. Resubmit Sitemaps and Recrawl Signals

Once crawlability and redirects are verified, actively prompt the search engines to reprocess the site rather than waiting for a natural recrawl.

• Generate a fresh XML sitemap containing only live, indexable, canonical 200-status URLs. Remove old URLs, redirected URLs, and noindex pages.
• Submit in Google Search Console and Bing Webmaster Tools, and confirm the reported "discovered" and "indexed" counts climb over the following days.
• Keep the old domain's Search Console property if you changed domains, and use the Change of Address tool to formally signal the move.
• Request indexing for your most important pages via URL Inspection to accelerate recrawl.
• Update the sitemap reference inside robots.txt to the new sitemap URL.

5. Check Technical Performance and Core Web Vitals

A new platform can change page speed dramatically, for better or worse. Because Core Web Vitals are a ranking signal and directly affect conversion, treat performance as an audit item, not an afterthought. A rebuilt site that loads slower than its predecessor can lose rankings even with perfect redirects.

• Largest Contentful Paint (LCP) — Aim for under 2.5 seconds. Check hero images are optimized and served in modern formats (WebP/AVIF).
• Cumulative Layout Shift (CLS) — Aim for under 0.1. Reserve dimensions for images, ads, and embeds to prevent jumping.
• Interaction to Next Paint (INP) — Aim for under 200ms; audit heavy third-party scripts and unused JavaScript.
• HTTPS and mixed content — Confirm the SSL certificate is valid and no assets load over insecure http.
• Mobile usability — Verify responsive rendering, tap-target spacing, and readable font sizes on mobile.
• Caching and CDN — Confirm caching headers and CDN delivery are configured on the new environment.

Run PageSpeed Insights and Lighthouse on representative templates, and compare field data in the Core Web Vitals report once real-user data accumulates. Performance regressions are often the hidden cost of a migration that focused only on visuals, which is why we bake speed budgets into our website development process from the start.

6. Verify Analytics, Tracking, and Search Console

You cannot detect a migration problem you cannot measure, so confirm your instrumentation survived the move before you rely on the data to make decisions.

• Analytics tag — Confirm GA4 (or your platform) fires on every template. Use realtime reports and the Tag Assistant to verify events register.
• Conversion and goal tracking — Re-test form submissions, purchases, calls, and any event-based goals end to end.
• Search Console verification — Confirm ownership is still verified for the new domain and, if applicable, the new HTTPS/www property.
• Third-party pixels — Verify ad platform, heatmap, and CRM tracking scripts reinstalled correctly.
• Annotate the launch date in analytics so future traffic analysis accounts for the migration.

7. Monitor Continuously for Weeks, Not Days

The launch-day audit catches configuration errors. The multi-week monitoring window catches ranking and indexation drift that only surfaces as Google recrawls the full site. Treat post-migration monitoring as a scheduled process, not a one-time task.

• Coverage/Pages report — Watch for spikes in "Crawled - currently not indexed," "Excluded by noindex," or soft 404s in Search Console.
• Crawl stats and errors — Monitor server error rates and crawl anomalies weekly.
• Rankings and impressions — A modest, temporary dip is normal; a sustained decline beyond 2 to 4 weeks signals an unresolved problem to investigate immediately.
• Organic traffic and conversions — Compare week-over-week against the pre-migration baseline segmented by landing page.
• Backlinks — Confirm high-value inbound links resolve through your redirects to live pages.

Document every finding and fix in a shared tracker so nothing falls through the cracks. A structured post-migration SEO audit turns launch anxiety into a checklist, and a checklist is something you can actually finish.