After launch, monitor four things: whether the site is reachable, whether search engines can crawl it without errors, whether it stays fast, and whether the forms that bring in enquiries actually deliver. The last one matters most and is the one most often left unchecked. A site can look perfect while its contact form quietly fails.
The four layers to watch
| Layer | The question | Typical tool type |
|---|---|---|
| Availability | Is the site up from outside your network? | External uptime checker |
| Crawl health | Can Google reach pages without errors? | Search Console |
| Performance | Are real visitors getting a fast page? | Field data, PageSpeed Insights |
| Conversions | Do forms and key actions still work? | Analytics events plus test submissions |
Availability: check from outside
Your own browser tells you little, because caches and logged-in sessions hide problems. Use an external monitor that requests your home page and one or two key pages every few minutes and alerts a real person by email or SMS. Point it at a page that exercises the full stack, not a static file served by a cache, and check that the response contains an expected phrase rather than just a 200 code. Also monitor the SSL certificate expiry date and the domain renewal date, since lapses there look like outages to visitors.
Crawl health: what Google sees
Google’s documentation explains that 5xx errors and 429 responses cause its crawlers to slow down, and that URLs that keep returning server errors are eventually dropped from the index. In contrast, 4xx responses (apart from 429) are treated as content that does not exist, so a page removed by accident will fall out of the index too. See Google’s guide to HTTP status codes and network errors.
Search Console’s Crawl Stats report is the practical place to look. It shows host status (green, yellow or red depending on recent availability problems), server connectivity failures, DNS resolution problems, robots.txt fetch failures and the mix of response codes. A rising share of 5xx responses or a robots.txt that starts failing is an early warning worth acting on the same day.
Forms: the silent failure
Forms break for dull reasons: an email provider rejecting messages, a changed spam filter, a plugin update, a required field added without anyone noticing. Build a routine:
- Submit a test enquiry weekly, from a device and network that is not your office, and confirm it arrives in the real inbox, not only in a database.
- Track form activity in analytics. Google Analytics enhanced measurement can record form_start and form_submit events, and comparing them shows how many people began a form against how many finished it. Per Google’s documentation, you need custom dimensions to report on the parameters, and you must make sure no personally identifiable information is collected.
- Set an alert for the unusual: zero submissions over a period when you normally receive some.
- Keep a fallback visible, such as a phone number or email address next to the form.
A simple routine
- Daily (automated): uptime alerts, certificate and domain expiry warnings.
- Weekly (10 minutes): test form submission, glance at Search Console for new errors, check the analytics events still fire.
- Monthly: review field performance, broken links, and any pages that changed unexpectedly after plugin or content updates.
- After every release: repeat the weekly checks immediately.
Related reading: website speed and Core Web Vitals covers the performance layer, what makes a business website convert explains why forms deserve this attention, and planning a redesign without losing SEO value lists the checks needed in the first weeks after a major launch.
Limitations
Monitoring tells you something broke, not why. Free tiers of uptime tools usually check less often, and an external check cannot see a form that submits successfully but routes to a spam folder. Test the whole path, end to end.
Where Radiance Impact fits
Radiance Impact’s Technology division builds business websites and offers maintenance and care. If you want help setting up monitoring or a launch checklist, see /technology or get in touch.
Sources
- HTTP status codes, network and DNS errors, and Google Search, Google Search Central
- Crawl Stats report, Google Search Console Help
- Automatically collected events: form interactions, Google Analytics Help
