WordPress migration post-launch monitoring (weeks 1–4)
What to watch after launching a migrated WordPress site — Search Console, 404s, rankings, redirects, crawl stats and when to panic vs wait. A week-by-week…
verifiedReviewed by Tommy Smith,Content Director
After launch: submit sitemap, snapshot Search Console baseline, watch 404s and indexed count weeks 1–2, compare traffic and rankings weeks 3–4. Minor dips are normal; mass 404s and halved indexation are not.
A clean launch QA pass does not mean the migration is over — it means you are ready to observe. Google needs time to recrawl, rankings fluctuate normally, and the 404 that nobody predicted shows up in Search Console on day nine. Post-launch monitoring is the discipline of watching the right signals, knowing which dips are temporary, and fixing what is actually broken before the client forwards a panicked email. This guide is the week-by-week playbook agencies use after every rebuild.
The migrations that go wrong are not the ones you monitored too much — they are the ones you declared done on launch day.
Day 0 — launch checklist
- 1Submit new XML sitemap in Google Search Console.
- 2Use URL Inspection on homepage and top 10 pages — Request Indexing.
- 3Verify old URLs 301 correctly (curl -I or redirect checker).
- 4Confirm analytics and GTM fire on the new domain.
- 5Snapshot baseline: export Search Console performance (last 28 days) and top landing pages from GA.
- 6Notify the client what to expect: rankings may fluctuate for 2–4 weeks — here is what we are watching.
- 7Confirm staging is noindexed or behind auth — duplicate indexation kills migrations.
Week 1 — catch catastrophic failures
Search Console
- arrow_rightPages report: spike in Not found (404) — investigate every new 404 against your redirect map.
- arrow_rightPages report: spike in Page with redirect on URLs that should be final destinations — fix internal links.
- arrow_rightCoverage: confirm indexed page count is in the right ballpark — not an 80% drop.
- arrow_rightCheck robots.txt and accidental noindex on key templates.
Site crawl
Re-crawl the live site on day 3 and day 7. Zero tolerance for image 404s on top-traffic pages. Check forms still submit. Monitor server error logs for PHP fatals on new templates. Test checkout and lead forms on pages that drive revenue.
When to act in week 1
- arrow_rightAct immediately: mass 404s on ranked URLs, site-wide noindex, checkout broken, forms not delivering leads.
- arrow_rightInvestigate but do not panic: single-page ranking drop, gradual crawl rate change, individual 404 on low-traffic URL.
Week 2 — indexing and redirect hygiene
- 1Compare Search Console indexed count week-over-week.
- 2Export 404 report; add missing redirects for any URL with impressions in the last 90 days.
- 3Check Crawled — currently not indexed for important pages — improve internal links or content if needed.
- 4Verify Yoast or Rank Math sitemaps match indexed content.
- 5Re-test top 20 old URLs still resolve via 301 to correct destination — not homepage.
- 6Confirm Yoast SEO fields migrated correctly on top landing pages.
Weeks 3–4 — rankings and traffic patterns
Organic traffic and rankings often dip slightly in weeks 1–2, then stabilise by weeks 3–4 if redirects and metadata were correct. Compare GA landing pages to your pre-launch baseline — not year-over-year (seasonality confuses the signal).
| Signal | Healthy | Needs action |
|---|---|---|
| Organic traffic vs baseline | Within 10–15% by week 4 | Down 40%+ with correct redirects — audit metadata and content parity |
| Indexed pages | Within 5% of old site | Large drop — check noindex, robots.txt, sitemap |
| Average position (GSC) | Minor fluctuation | Sustained drop on key terms — compare title/description and on-page content |
| 404 count | Flat or falling | Rising — new broken links or missing redirects |
| Core Web Vitals | Stable or improved | Regression — check new theme assets |
When rankings do not recover
- 1Audit content parity: did the new page lose word count, headings or sections vs old?
- 2Check canonicals — accidental noindex or wrong canonical on key pages.
- 3Verify redirects are 301, single-hop, to relevant pages (not all to homepage).
- 4Look for duplicate content: staging still indexed, www/non-www both live.
- 5Compare backlink landing URLs — are they redirecting correctly?
- 6Review structured data — schema regressions after theme change.
404 monitoring workflow
Export Search Console 404s weekly. Cross-reference with your redirect map CSV. Any URL with impressions gets a 301 within 48 hours. Log additions in the shared spreadsheet. After week 4, move to monthly monitoring unless traffic is still unstable. Broken internal links discovered in crawl? See broken internal links after migration.
Analytics: what to compare
- arrow_rightTop 20 landing pages: sessions vs 28-day pre-launch baseline.
- arrow_rightOrganic channel only — paid and direct confuse migration signals.
- arrow_rightForm submissions and key conversion events — traffic without leads is a red flag.
- arrow_rightGeography and device splits — sudden mobile drop may indicate render issues.
- arrow_rightBounce rate on migrated pages — spike may mean content parity problem.
Client reporting template
Send a short update at end of week 1 and week 4: indexed pages (old vs new), 404 count, top 5 landing pages traffic vs baseline, redirects added, and next actions. Proactive reporting prevents 'is the SEO broken?' calls on day five when a temporary fluctuation is normal. Include one Lighthouse before/after if the rebuild targeted performance — clients love measurable wins.
Technical checks beyond SEO
- arrow_rightSSL certificate valid, no mixed content warnings.
- arrow_rightCDN and caching rules updated for new asset paths.
- arrow_rightEmail deliverability — SPF/DKIM unchanged if DNS moved.
- arrow_rightCron jobs and scheduled tasks running (memberships, subscriptions).
- arrow_rightThird-party embeds (maps, calendars, reviews) still loading.
When to keep the old site live
Keep redirects live at minimum — ideally the old hosting serves 301s for 90+ days. Do not leave the old site fully accessible at its old URL without redirects; that is duplicate content. A redirect-only old host is fine. DNS cutover should point to new hosting with redirects loaded before TTL expires.
Agency handover after week 4
If traffic is within 10–15% of baseline and 404s are flat, transition to the client's normal SEO retainer or quarterly health checks. Document what was watched, what was fixed, and the final redirect map. Pre-launch companions: migration QA checklist, rebuild without losing SEO, staging workflow.
Search Console reports to watch
| Report | What to look for | Frequency |
|---|---|---|
| Pages → Not found | New 404s on ranked URLs | Daily week 1, weekly after |
| Pages → Page with redirect | Redirect chains on final URLs | Weekly |
| Indexing → Pages | Indexed count vs old baseline | Weekly |
| Performance | Clicks and impressions trend | Weekly |
| Sitemaps | Submitted URLs vs indexed | Once + after fixes |
| Core Web Vitals | LCP/CLS regression | Once at week 2 |
Redirect chain audit
A single URL should resolve in one hop: old URL → 301 → final new URL. Chains (old → interim → new) dilute link equity and slow crawlers. Redirect loops break crawlers entirely. Test with curl -I or a redirect checker tool on your top 50 old URLs. Fix chains in the redirect plugin before week 2 — Google recrawls frequently in the first month after migration.
Structured data validation
Theme changes break schema silently. Run Google Rich Results Test on homepage, one inner page, and one blog post after launch. FAQ blocks should still emit FAQ schema if your new templates include it. Breadcrumb schema often changes with new theme markup — verify on category and product pages for e-commerce rebuilds.
When to escalate to a full SEO audit
- arrow_rightTraffic still down 30%+ at week 6 with correct redirects.
- arrow_rightIndexed count below 50% of old site without noindex explanation.
- arrow_rightKey money pages ranking for wrong URLs or not ranking at all.
- arrow_rightMassive spike in soft 404 or crawled-not-indexed on important pages.
- arrow_rightClient reporting competitor overtaking on branded terms post-launch.
Monitoring spreadsheet columns
Build a shared Google Sheet at launch with columns: Old URL, New URL, Redirect status (301/302/missing), GSC impressions (28d pre-launch), Current indexed (Y/N), 404 status, Action taken, Owner, Date fixed. Update weekly through week four. This single artefact prevents duplicated fix efforts and gives the client visibility without daily panic emails.
Uptime and server monitoring
SEO monitoring is not enough. Watch server response times, PHP error logs, and uptime on the new host. A migration to faster hosting can mask template bugs; a migration to budget hosting can expose them. Set up UptimeRobot or hosting alerts on homepage, /contact/, and checkout URL if e-commerce. SSL expiry reminders matter if DNS moved.
Week-by-week summary card
| Week | Primary focus | Success signal |
|---|---|---|
| Week 0 (launch) | Sitemap, 301s, baseline snapshot | No site-wide errors, analytics firing |
| Week 1 | 404 spikes, indexation cliff | No mass 404s on ranked URLs |
| Week 2 | Redirect gaps, sitemap parity | Indexed count stabilising |
| Week 3 | Traffic trend vs baseline | Within 15% of pre-launch organic |
| Week 4 | Ranking recovery, client report | Flat or rising trend, 404s falling |
Bing and secondary search engines
Google dominates the conversation but Bing Webmaster Tools matters for clients in B2B and older demographics. Submit the new sitemap to Bing at launch. Monitor Bing 404s in parallel for the first month. DuckDuckGo and other aggregators follow Bing index — fixing Google issues usually fixes them, but Bing has its own crawl schedule.
Document and archive
Archive the pre-launch Search Console export, redirect map CSV, and monitoring spreadsheet in the client project folder. Future developers — and future you — need the baseline when investigating issues six months later.
Launch day is when monitoring starts — not when the project ends.
Frequently asked questions
How long until traffic stabilises after a WordPress migration?expand_more
With correct 301s and preserved metadata, most sites stabilise within 2–4 weeks. Larger sites or those with significant URL changes may take 6–8 weeks. Sustained drops beyond week 6 warrant a full content and redirect audit.
Should I keep the old site live after migration?expand_more
Keep redirects live at minimum — ideally the old hosting serves 301s for 90+ days. Do not leave the old site fully accessible at its old URL without redirects; that is duplicate content.
When is a ranking drop normal vs a migration failure?expand_more
Normal: site-wide minor dip weeks 1–2, individual keyword fluctuation, gradual recovery by week 4. Failure: key landing pages 404, indexed count halved, mass redirects to homepage, or traffic still down 30%+ at week 6 with no recovery trend.
What should I check on launch day?expand_more
Submit sitemap, request indexing on top pages, verify 301s, confirm analytics firing, snapshot Search Console and GA baselines, and set client expectations for a 2–4 week fluctuation period.
How often should I check Search Console after migration?expand_more
Daily in week 1 for 404 spikes, weekly through week 4 for indexation and traffic, then monthly unless issues persist.
What 404s matter most?expand_more
Any URL with Search Console impressions in the last 90 days. Low-traffic 404s on orphaned pages can wait; ranked URL 404s need same-day redirects.
Should I use a rank tracker during migration?expand_more
Helpful for key terms, but Search Console average position and landing page traffic are more reliable than daily rank trackers that overreact to noise.
Can Core Web Vitals changes affect rankings post-migration?expand_more
Vitals are one signal among many. A regression after launch warrants asset optimisation. Improvement from leaving a page builder is often a positive migration outcome — document it for the client.
What if staging is still indexed after launch?expand_more
Noindex staging immediately, remove from sitemap, request removal in Search Console if needed. Duplicate indexation confuses Google and dilutes rankings.
How do I report migration SEO health to clients?expand_more
Week 1 and week 4 short updates: indexed pages, 404 count, top landing page traffic vs baseline, redirects added, next actions. Plain language, no jargon panic.
When should I audit content parity?expand_more
When ranked pages lose sustained traffic despite correct redirects. Compare old vs new word count, heading structure, and key sections. Thinning content is a common hidden cause of post-migration drops.
Ryan Hale
Head of Front End Development
Ryan Hale is Head of Front End Development at AIRA, where he leads the team building the engine that migrates WordPress sites into native ACF blocks. He has spent more than a decade building and rebuilding WordPress sites for agencies, with deep, hands-on expertise in Advanced Custom Fields, Gutenberg block development, and large-scale content migrations that protect search rankings. He writes about ACF, moving off page builders like Elementor and Divi, and the practical craft of shipping fast, maintainable WordPress rebuilds.
Reviewed to our editorial guidelines.
