A client site on a fragile host
Watch uptime and response time so an outage is visible before the monthly report shows a traffic hole.
Site · Monitoring
Uptime
Public URL checks on a schedule
99.9%
Last check
Up
Response
182ms
Look at recent checks when traffic or indexing suddenly looks wrong.
A red check and a slow check are different problems. An outage means new articles, sitemaps, and indexing submissions are pointing at a host that fails. A slow response means the page loads often enough to look up while crawlers and readers time out. The history is what separates a one-off blip from a host that fails every afternoon. A single red dot is a reason to look. A row of them is a reason to stop the publishing queue until the host answers again.
How it works
Uptime monitoring checks the host you publish to and keeps a history of response time. When the site goes quiet, the status is on that site, next to the content calendar. A blog that cannot be fetched cannot be crawled, and readers who hit an error do not come back from search.
Turn monitoring on per site. Pause it by disabling the site when a migration or a DNS change is intentional. Response time history shows a slow host before it becomes a full outage. That matters for the same URLs you just submitted to Google and Bing.
Monitoring is not a replacement for the SEO audit. The checker reads titles, links, and indexability. Monitoring reads whether the server answered. You want both on a domain that is supposed to stay in the index.
Watch uptime and response time so an outage is visible before the monthly report shows a traffic hole.
Confirm the new host answers after the CNAME moves, then keep the check running.
Each site has its own status history, so one client outage does not hide inside a single account-wide graph.
Site monitoring guards the host behind your own domain, the WordPress site, and the public blog. Indexing submissions assume the URL loads. Audience insights only record visits when the site is up.