Site migration · 21 Nov 2026 · 5 min read
SEO migration monitoring: what to watch after a site move
The launch is the start of the risky period, not the end. This guide lists what to check each day, what to check each week and how to tell a normal dip from a real fault.
The short answer
Check the basics straight after launch: pages load, redirects work, nothing is blocked, and tracking records visits. Then watch Search Console and analytics daily at first, weekly later. A small dip is normal as Google reprocesses the site. A sharp, lasting fall on important pages points to a fault. Recovery time varies and cannot be promised.
Why monitoring matters after a move
A migration changes addresses, templates, hosting or platform, and often several together. Even a careful plan misses things: a redirect with a typo, a template that drops a title, a staging setting left switched on. Most of these are cheap to fix if found in a day and expensive if found in a month.
Search engines also need time. They must find the new addresses, follow the redirects, crawl the new pages and update what they store. During that time traffic may move around even when everything is right. Monitoring helps you tell that normal movement from a fault.
The advice here assumes you already made a redirect plan and tested the new site beforehand on a copy. Our guide to a staging site explains why testing before launch catches problems that would otherwise appear in search.
The first hour after launch
Before any reports, check the things that cause the worst damage if they are wrong.
- The site is not set to noindex and is not blocked by the robots file. A setting meant for staging often survives into the live site.
- The home page, a few key pages and the contact page load over a secure connection with no errors.
- Old addresses redirect to the right new pages. Test a sample of the most visited ones, not just the home page.
- Titles, headings, canonical tags and structured data are present on new templates.
- The sitemap is updated and lists the new addresses, and it has been submitted in Search Console.
- Analytics and any tag manager setup records visits and key actions.
- Forms, carts and automated emails work. An automation such as an abandoned cart reminder can fail silently after a platform change, so send a test, as discussed in abandoned cart emails.
Which reports should I check daily?
For the first week or two, a short daily routine is enough. Keep it small enough that it actually happens.
| Where | What to look at | What would worry you |
|---|---|---|
| Search Console, page indexing | New not-indexed reasons, not-found and redirect errors | A sudden growth in errors or in blocked pages |
| Search Console, performance | Clicks and impressions for the whole site and top pages | A sharp fall on pages that matter |
| Search Console, crawl stats | Server errors and response time | Repeated server errors |
| Analytics | Visits by landing page and source | Zero visits on pages that normally have some |
| Uptime and speed | Site available and responsive | Outages or slowdowns |
| Site search | New zero-result queries | Searches for pages that visitors cannot find |
Report names and layouts in Search Console change, so check the current documentation if something is not where you expect it.
The last row deserves attention. Visitors who cannot find a moved page often search for it, and the queries show you exactly what broke. Our guide on internal search data explains how to read them.
What to check weekly
After the first fortnight, move to a weekly rhythm.
- Compare clicks and impressions for the top pages with the weeks before the move. Compare the same days of the week, because traffic varies through the week.
- Review the list of addresses with errors and fix the ones that matter, especially those that have links or past visitors.
- Look for redirect chains and loops, where an old address passes through several steps before reaching the new one.
- Check that new pages are being indexed, using the URL inspection tool on a sample.
- Review internal links, which can break or point to old addresses after a move.
- Read the rankings of a short list of important searches, but do not read too much into daily changes.
- Keep a log of what you saw and changed, with dates.
The log is useful later. If traffic changes in a month's time, you can tell what happened before it.
How long does a recovery take?
Nobody can give an honest fixed answer. Google's documentation on site moves says that it can take time for its systems to process a move, and that the length depends on the size of the site and how well the move was done. A small site with clean redirects may settle quickly. A large site with many changes, such as new titles, new structure and new content, may take longer.
Several things influence it.
- How many addresses changed, and how accurate the redirects are.
- Whether content, titles and structure also changed. A move that keeps content the same is easier for search engines to follow than a redesign that rewrites everything at once.
- How fast and stable the new site is.
- How often Google normally crawls the site.
- Whether anything unrelated happened at the same time, such as a core update.
Plan for a period of lower traffic and do not promise a date to anyone. If the business depends on search enquiries, tell the team in advance that a dip is possible and agree what you will watch.
When is a drop a real problem?
Think about shape, size and where it is.
- A small, gradual dip across the whole site in the first days is common and often settles.
- A sharp drop on launch day suggests a technical fault: a block, an error or a redirect failure. Investigate at once.
- A drop only on certain sections points to a template or redirect problem in that section.
- A steady slide over several weeks with no recovery suggests lost relevance, weaker content or poor internal linking on the new site.
- A drop that matches a known Google update may not be caused by your move at all.
When you find a fault, fix it, then give the fix time to be picked up. Changing many things at once makes it hard to know what worked. Where a page was removed on purpose, do not expect it to hold traffic.
After the dust settles
Once traffic has stabilised, tidy up. Remove temporary redirects you no longer need, update links inside your own pages to point straight to the new addresses, and keep the old redirects in place for a long time, because outside links and old bookmarks continue to arrive.
Seasonal and expired pages are often casualties of a move, since nobody remembers them. Our guide on expired and seasonal pages helps decide what to keep. A site move is also a good time to plan ongoing care, in the same way an app needs a plan after launch, as set out in app maintenance after launch.
If you want help planning or checking a move, our SEO service covers migration reviews.
Related guides
- SEO services
- Staging site what it is and why to use one
- SEO for Expired and Seasonal Pages: What to Do After the Season
- Internal Search Data: How Your Site Search Shows What to Write
Questions and answers
How long does a recovery take?
It varies. Google says processing a site move takes time and depends on the size of the site and how well the move was done. Small, clean moves can settle quickly, while larger ones with content changes take longer. No one can promise a date.
Which reports should I check daily?
In the first one or two weeks, look at the Search Console page indexing and performance reports, crawl stats for server errors, your analytics landing pages and an uptime check. Keep the routine short enough to do every day.
When is a drop a real problem?
A sharp fall on launch day, a drop on one section only, or a steady slide with no recovery suggests a fault or lost relevance. A small, broad dip in the first days is common and often settles. Check for technical blocks first.
Should I keep old redirects?
Yes, for a long time. Outside links and bookmarks continue to arrive at old addresses. Remove only ones you are sure no one uses, and check first.
Do I need to tell Google about the move?
For a change of domain, Google documents extra steps in Search Console. For a move on the same domain, redirects, an updated sitemap and good internal links matter most. Check the current documentation for your type of move.
What if traffic drops and never recovers?
Compare pages before and after, check for lost content, missing redirects and weaker internal links, and review whether the new pages answer the same questions. If it is unclear, get a technical review.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.