The week after a website migration: what to monitor each day
Days one to seven after a migration decide whether rankings hold. What to check each day in Search Console, server logs and analytics, and what is normal.
By Sohail Hussain21 November 20265 min read
In the week after a migration, check four things every day: that old URLs redirect in one hop to the right page, that Google is crawling and indexing the new URLs, that search clicks to your top pages are holding, and that forms and tracking still record enquiries. Some dip in traffic is normal; Google says it can take a few weeks or more for a site to show its new URLs. What you are looking for in the first week is the problems that get worse every day they are left: 404s, a leftover noindex, wrong canonicals and broken forms.
This is the monitoring routine we run after every website redesign and migration, and the last stage of the website redesign process. Have the pre-launch baseline open: clicks per page, enquiries per week and Core Web Vitals for the main templates. Without it, nothing below can be judged.
What should you check on launch day?
In the first hours, check the things that would block indexing outright:
- No
noindexon the live site. Runcurl -sI https://www.example.comand look for anX-Robots-Tagheader, then view the source of a few pages for a robots meta tag. Either one left over from staging stops indexing. - The right robots.txt. Open
/robots.txton the live domain and paste it into the robots.txt tester. The staging version often blocks everything. - Canonicals point at the live domain. Check the homepage and one page of each template.
- Redirects work. Test the top 20 pages by clicks and every URL with backlinks first, then the whole map. Redirect mapping has a script that tests every row.
- Sitemap submitted. Submit the new sitemap in Search Console. Google's site move guide also suggests submitting a sitemap of the old URLs, so Google recrawls them and finds the redirects.
- Key pages inspected. Run the homepage and your top ten pages through URL Inspection, use "Test live URL", and request indexing.
- Forms and tracking. Send a real enquiry through every form and confirm it arrives where it should. Check that your analytics real-time report shows your own visit.
What should you check on days two and three?
Search Console is days behind reality. Its Performance data typically lags by about two days, and the Pages report takes longer to reflect a move. Your server logs are real time, so start there.
Old URLs returning 404. Every 404 on an old URL is a missing redirect. On a server with standard Nginx or Apache logs, this lists the most requested missing paths:
awk '$9 == 404 {print $7}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head -50
Add each real page to the redirect map and the server rules the same day. Ignore bot noise such as /wp-login.php on a site that never ran WordPress.
Googlebot activity. In Search Console, Settings, the Crawl stats report shows requests by response code. Expect a rise in crawling and in 301 responses; Google warns that it crawls a moved site more heavily for a while. A rise in 5xx errors means the server is struggling, which slows the whole move.
Top pages in URL Inspection. Check that Google's chosen canonical for each is the new URL, not the old one or the staging address.
What should you check from day four to day seven?
By now Search Console's reports start to reflect the move.
The Pages report. The Page indexing report groups URLs by why they are or are not indexed. After a migration, read it reason by reason:
- "Page with redirect" rises. That is expected: these are your old URLs, correctly redirected.
- "Not found (404)" rising is a missing redirect. Open the examples and add them to the map.
- "Excluded by 'noindex' tag" containing new pages means a staging setting survived somewhere.
- "Alternate page with proper canonical tag" or "Duplicate, Google chose different canonical than user" on new pages points to canonical tags that are wrong or contradict the redirects.
- "Soft 404" on old URLs usually means they redirect to an irrelevant page such as the homepage.
The Sitemaps report. The new sitemap's discovered and indexed counts should climb day by day, and the old sitemap's should fall.
The Performance report. Compare clicks for your top pages with the same weekdays before launch. Look at the new URLs and the old ones together: during the switch, Google shows a mix of both.
Enquiries. Count form submissions, calls and bookings against the baseline week. If traffic is steady and enquiries dropped, the problem is a form, a tracking tag or a changed call to action, not SEO.
Core Web Vitals. The Search Console report uses 28 days of real-visitor data, so it will not reflect the new site for about a month. Use PageSpeed Insights lab tests on the key templates this week, and compare with your baseline.
What is normal, and what is a warning sign?
| Signal | Normal in week one | Investigate if |
|---|---|---|
| Search clicks | Small dip, mixed old and new URLs in results | A drop concentrated in a few pages, or a steep fall across the site |
| Crawl requests | Clear spike, many 301 responses | Rising 5xx errors or slow response times |
| 404s on old URLs | A handful, fixed as they appear | Dozens, or any on top pages |
| "Page with redirect" | Rising steadily | Flat, meaning Google is not recrawling old URLs |
| New URLs indexed | Climbing daily | Flat after five days |
| Enquiries | Same as the baseline week | Down with traffic steady |
A site-wide dip that recovers over a few weeks is the move being processed. A sharp drop in a handful of pages almost always has a specific cause: a missing or wrong redirect, a changed title, content cut in the redesign, or a page that is no longer linked from the menu.
What happens after the first week?
Move to weekly checks for the next month: the Pages report, the Performance report against the baseline, and the logs for new 404s. Keep the old sitemap submitted for a few weeks, then remove it once its indexed count is close to zero.
Keep every redirect for at least a year, as Google recommends, and preferably for good. Update the links you control: Google Business Profile, social profiles, email signatures, and the sites that send you the most referral traffic. If you changed domains, the domain change checklist lists the rest.
If clicks are still well down after four to six weeks, go back to the pages that lost the most and compare them with the old versions: URL, title, heading, body text and internal links. The cause is almost always in that comparison. How to migrate a website without losing SEO covers the steps that should have prevented it, which is worth reading before the next move rather than after.
Was this guide useful?