After a Website Relaunch: What to Monitor in the First 30 Days
Short answer: For the first month after a relaunch, check the site on a schedule rather than waiting for complaints. On day one, crawl the site for broken links and 404s, confirm old URLs redirect to the right new pages, and send a test through every form. During week one, watch redirect hits and 404 logs daily, submit the new sitemap and look at Search Console for indexing and crawl errors. In weeks two to four, compare traffic and conversions in GA4 with the same weeks before launch, track the pages that used to bring in enquiries, and fix anything that drifts. Agree in advance what would make you roll back a specific change.
Before you start: capture the baseline
You can only spot a drop if you know where you started. Ideally before launch, or as soon as possible after:
- Export the top 50 landing pages by organic traffic for the previous three months from GA4 or your old analytics.
- Export Search Console performance data for pages and queries for the same period.
- Note monthly enquiries, calls or orders from the website.
- Keep the list of old URLs and where each one now redirects.
Store this in one folder. Everything below compares against it.
Day 1: the launch-day sweep
Do these on the day the new site goes live, ideally within the first few hours.
Crawl for broken links and 404s
Run a crawler (desktop crawlers have free tiers that cover small sites) across the new site. Look for:
- Internal links returning 404, often from old menu items or links in blog posts.
- Images that fail to load.
- Pages accidentally set to noindex, a frequent leftover from the staging site.
- A robots.txt that still blocks everything from staging.
Test the redirects
Take the list of old URLs and run it through the crawler in list mode, or check the top 50 by hand. Each should return a single 301 redirect to the most relevant new page, not to the home page and not through a chain of several hops. Google's guidance on site moves with URL changes explains why one-to-one redirects matter.
Submit every form
A Manchester physiotherapy clinic relaunched with a beautiful new booking request form, and for nine days its submissions went to an inbox that no longer existed. Test each form with a real submission, confirm the email arrives at the right address, the autoresponder sends, and any CRM or booking integration receives the data. Repeat on a phone.
Quick checks
- Contact phone number taps to call on mobile.
- Analytics tag fires on all page templates (use GA4 DebugView or Realtime).
- Cookie banner works and does not block the site.
- HTTPS works on both the www and non-www versions, with one redirecting to the other.
Week 1: watch daily
Redirect hits and 404 log
Your host, CDN or a redirect plugin may log 404 errors. Check them daily during the first week. You will find old URLs you forgot: PDFs linked from other sites, URLs from email campaigns, old blog paths with dates. Add redirects for any that receive visits.
Search Console
- Submit the new XML sitemap.
- If the domain changed, use the Change of Address tool.
- Use URL Inspection on your five most important pages to confirm Google can fetch and render them.
- Check the Page indexing report for spikes in "Not found (404)", "Blocked by robots.txt" or "Excluded by noindex".
Search Console data lags by a few days, so do not panic about missing numbers on day two.
Speed and stability
New sites sometimes ship with heavy images or scripts. Check a few key pages with PageSpeed Insights and keep an eye on the Core Web Vitals report as field data arrives over the following weeks. The Web Vitals overview explains what each metric measures.
Weeks 2 to 4: compare and correct
GA4 comparisons
Compare each week with the same week before launch, and if you have it, the same week last year to allow for seasonality. Look at:
- Total sessions and organic sessions.
- Key events such as form submissions, calls and purchases.
- Landing pages: which old top pages have new equivalents receiving similar traffic, and which have fallen away.
A dip of some size in the first couple of weeks is common while search engines process redirects. A steady decline after week three, or a fall concentrated on specific pages, needs investigation.
Rankings for your money pages
Pick 10 to 20 queries that matter commercially ("sports massage Manchester", "physio near Didsbury"). Track their average position in Search Console week by week. If one drops sharply, compare old and new versions of the page: did content get cut, the title change, or the page move deeper in the navigation?
Conversion paths
Walk through the main journey as a customer each week. Small issues creep in after launch as content editors make changes: a broken button, a booking widget that fails on Safari, a phone number typo.
A simple monitoring table
Keep one row per check per week:
| Check | Day 1 | Week 1 | Week 2 | Week 3 | Week 4 |
|---|---|---|---|---|---|
| Crawl: 404s found | |||||
| Redirect sample OK | |||||
| Forms tested | |||||
| Search Console errors | |||||
| Organic sessions vs baseline | |||||
| Enquiries vs baseline |
A shared sheet is enough. The point is that someone looks every week.
When to roll back a change
Rolling back the whole site is rarely the right answer, but individual changes sometimes need reversing. Agree rules before launch, for example:
- If enquiries from the website fall by a clearly significant amount for two consecutive weeks with no seasonal explanation, review the contact page and forms first, and restore the old contact flow if the new one is the cause.
- If a key landing page loses most of its organic traffic for two weeks while the old URL redirects properly, compare content and restore the missing sections.
- If a new feature (chat widget, booking tool) causes errors or slow loads, switch it off until fixed.
Write the rule, the owner and the deadline for a decision. It avoids arguments in a stressful week.
FAQ
How long until traffic recovers after a relaunch?
It varies with the size of the changes. Sites with clean one-to-one redirects and unchanged content often settle within a few weeks; bigger structural changes take longer.
Should we remove old redirects after a month?
No. Keep them for at least a year, ideally permanently. Other websites and bookmarks keep sending visitors to old URLs.
Our old site had no analytics. What can we compare against?
Search Console usually holds 16 months of data even for older sites, and your enquiry records or booking system give you a business baseline.
Who should own the monitoring?
One named person, even if checks are shared. Without an owner, the weekly review slips by week two.
If your relaunch is coming up or has just happened and you want a second pair of eyes on redirects, forms and tracking, book a review with us.