# What should I monitor after a website migration? > After a website migration, monitor the handful of signals that reveal whether the move is settling cleanly or breaking something, and watch them closely for the first few weeks. The core things to track are index coverage in Search Console, so you see if pages are being indexed or dropping out; crawl errors and 404s, which flag URLs that were not redirected; your rankings, impressions, and clicks against your pre-migration baseline; redirect health, confirming your 301s actually resolve; and Core Web Vitals, so a performance regression does not hurt you. You also watch organic traffic and conversions in analytics, and server errors or downtime. Expect some fluctuation as engines recrawl and reprocess the site, which is normal, and distinguish that from a sustained drop that signals a real problem. WPBuildAI hands over the migration with the redirect map, sitemap, and baseline in place, so you know exactly what to watch and can confirm the move settled cleanly. Source: https://wpbuildai.com/what-to-monitor-after-a-website-migration/ By lawrence-arya ยท 2026-06-08 --- After a website migration, monitor the handful of signals that reveal whether the move is settling cleanly or breaking something, and watch them closely for the first few weeks. The core things to track are index coverage in Search Console, so you see if pages are being indexed or dropping out; crawl errors and 404s, which flag URLs that were not redirected; your rankings, impressions, and clicks against your pre-migration baseline; redirect health, confirming your 301s actually resolve; and Core Web Vitals, so a performance regression does not hurt you. You also watch organic traffic and conversions in analytics, and server errors or downtime. Expect some fluctuation as engines recrawl and reprocess the site, which is normal, and distinguish that from a sustained drop that signals a real problem. WPBuildAI hands over the migration with the redirect map, sitemap, and baseline in place, so you know exactly what to watch and can confirm the move settled cleanly. ## Indexing is the first thing to watch The highest-priority signal is whether your pages stay indexed, because a deindexed site loses everything at once and fast. Watch the [Page Indexing report](https://support.google.com/webmasters/answer/7440203) in Search Console for pages dropping out of the index or newly excluded, and confirm your sitemap is processed. This is where the most catastrophic migration problems show first, a stray noindex, a robots.txt block, or unredirected URLs, well before a traffic report would reveal them. If pages are being indexed and coverage looks stable, the foundation is sound; if pages are falling out, that is the emergency to chase, since it points to the kind of issue behind a [site going deindexed after migration](/why-is-my-site-deindexed-after-migration). Check indexing early and often in the first weeks. ## Crawl errors, 404s, and redirect health The next layer is the plumbing of your URLs. Watch Search Console and your server logs for crawl errors and 404s, because those flag URLs that were not redirected, and each is a page losing its traffic and value until fixed. Alongside that, actively confirm redirect health: your 301s should resolve to the right destinations, cleanly, without chains or loops, exactly as a [careful site move](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) intends. A migration's most common repairable damage is a redirect that was missed or points to the wrong place, so spot-checking your important URLs and watching the 404 report catches it. Since traffic concentrates on a minority of pages, as the [Ahrefs study](https://ahrefs.com/blog/search-traffic-study/) shows, prioritize confirming that your highest-value URLs redirect correctly first. ## Rankings and traffic against the baseline To judge the real effect of the migration, compare performance to the baseline you captured beforehand. Track rankings, impressions, and clicks in Search Console's Performance report, and organic traffic in your analytics, against the before picture, so you are measuring rather than guessing. This is where the pre-migration baseline pays off: without it, normal fluctuation and real change are indistinguishable. Watch the trend rather than any single day, and pay particular attention to your top pages, whose movement matters most. Keeping your [Search Console access and data intact through the move](/keep-google-search-console-data-after-migration) is what makes this comparison possible, so verify that access survived the migration before you rely on these reports. ## Performance, conversions, and uptime Round out the watch with the signals beyond search. Monitor [Core Web Vitals](https://web.dev/articles/vitals) so a performance regression in the new build does not quietly hurt experience and rankings; a rebuild should improve these, but confirm it did. Watch server errors and uptime, since a shaky launch can produce 5xx errors that harm both users and crawling. And if you run a store or rely on conversions, track those and the checkout, because a technically indexed site that stopped converting is still a failure. These are the signals that catch problems search reports would miss, and together with indexing and redirects they give you a complete picture of whether the migration succeeded, not just whether Google can see it. ## Distinguish normal settling from a real problem The interpretive skill that ties monitoring together is telling noise from damage. Some ranking and traffic movement in the first weeks is normal as engines recrawl and reprocess the site, and it usually trends back toward the baseline, so early wobble is not cause for panic if the fundamentals are intact. A real problem looks different: a sustained, sizable drop that does not recover, pages leaving the index, a wave of 404s, or broken redirects, which connects to knowing [how long SEO takes to recover](/how-long-seo-recover-after-website-migration). So read the monitoring calmly: if indexing, redirects, and Core Web Vitals are sound, give recrawling time; if they are broken, act immediately. Overreacting to normal settling by changing things can do more harm than the settling itself. ## Steps to monitor after a migration 1. **Check index coverage** in Search Console frequently in the early weeks. 2. **Watch crawl errors and 404s**, and confirm your important redirects resolve. 3. **Compare rankings and organic traffic** to your pre-migration baseline. 4. **Monitor Core Web Vitals, server errors, and uptime.** 5. **Track conversions and checkout** if you run a store. 6. **Distinguish normal settling from a sustained drop**, and act only on the latter. ## Worked example: catching a redirect gap early Consider a team that set up monitoring the day they launched. Within days, Search Console's index report and 404 log showed a cluster of errors on a set of old blog URLs, and the pages were dropping from coverage. Because they were watching indexing and 404s closely, they spotted that one section's redirects had been missed, mapped them within hours, and requested recrawling. Their rankings, checked against the baseline, wobbled briefly and then recovered, and Core Web Vitals confirmed the new site was faster. The problem was small precisely because monitoring caught it in days rather than the drop being discovered months later as a mysterious traffic loss. ## Limitation: monitoring reveals problems, it does not fix them It is honest to bound this. Diligent monitoring tells you whether the migration is settling and surfaces problems early, but it does not repair them; that still takes action, mapping a missed redirect, removing a stray noindex, fixing a performance regression. Search data also lags, so index and ranking reports reflect the state from recent crawls rather than this minute, which means give changes time to appear before concluding. And some fluctuation is genuinely unresolvable noise. So treat monitoring as your early-warning system that pairs with the ability to act, and with knowing how to [tell whether a migration truly hurt your SEO](/how-to-tell-if-a-migration-hurt-my-seo), rather than as a fix in itself. ## Key points After a migration, monitor the signals that reveal whether it is settling or breaking, closely for the first few weeks: index coverage first, since a deindexed site loses the most fastest; crawl errors, 404s, and redirect health, to catch unredirected URLs; rankings and organic traffic against your pre-migration baseline; and Core Web Vitals, server errors, uptime, and, for stores, conversions. Prioritize indexing and redirects, because those cause the biggest, fastest losses, then work down to smaller signals. Expect normal recrawl fluctuation that trends back to baseline, and distinguish it from a sustained drop, deindexing, or broken redirects that demand action. Remember monitoring surfaces problems but does not fix them, and search data lags, so act on real issues and give changes time to show. WPBuildAI hands over the migration with the redirect map, sitemap, and baseline in place, so you know exactly what to watch and can confirm the move settled cleanly. Send your web address for a free analysis. Not affiliated with WordPress, Lovable, Webflow, Shopify, Wix, or Squarespace.