What we monitor

One clear signal with the cause: noindex in meta robots or in the X-Robots-Tag header, a canonical pointing to another URL, or a robots.txt block for Googlebot. A cause present since the first check is the existing state, not a change.

The canonical changed, but the page still points to itself (or the canonical disappeared). We show what it was and what it is now.

The Indexability tab shows how many monitored pages can appear in Google and, for each non-indexable one, why.

A new Disallow rule blocked monitored pages for Googlebot. Each one gets an indexability-lost event naming the rule.

The file returns a server error (5xx) or doesn't respond. Google then pauses crawling the whole site. Pages are still assessed against the last content we read.

Which lines disappeared, which were added and how many monitored URLs the new version blocks. If it blocks any — a warning.

On a URL that used to return 200. A series of server errors (5xx) is reported right away, others after confirmation in the next check.

A URL that used to respond on its own started redirecting. We show the target.

The chain returns to a URL it already visited — the page will never load.

A URL that had a problem responds like the baseline again. The case closes itself.

We compare the text character by character. Changes limited to numbers (prices, dates, product counts) don't trigger an alert.

Same as title: every change in wording, without noise from numbers.

The first H1 heading changed its text.

The page had an H1 heading and now it doesn't.

A second title, description, canonical, meta robots or H1 on the page. We only report new duplicates — if a site has always had two canonicals, we won't flood you with it every day.

The file stopped responding or returns an error.

The file is there, but it isn't valid sitemap XML (e.g. an error page instead of the sitemap).

By default when the count changes by 10% or more. Set a percentage and an absolute threshold per project.

A sudden jump can be a wave of junk pages. You can raise it to a warning.

Another file appeared in the sitemap index.

By default when the response time triples compared with the median of recent checks. Change the factor per project.

The project's average response time day by day and a fixed speed sample: page weight and its components.

For every site we check whether the title, canonical or H1 after rendering differ from the raw HTML.

If content is swapped, we monitor the version a browser and a rendering crawler see — not the empty template.