How to read a supported finding.
Separate the observed condition, the comparison status and the next action. This walkthrough illustrates the supported report scope without presenting unverified customer results.
Evidence before interpretation.
| URL | Collected observation | Example status |
|---|---|---|
| /services | Missing title at baseline; a later comparable crawl found a nonempty title. | FIXED |
| /contact | Earlier comparable page returned 200; the current request returned 404. | NEW |
| /about | No H1 was found in either comparable crawl. | STILL OPEN |
| /repairs | The missing title was fixed in the previous report and is missing again. | REGRESSED |
| /blocked | The current crawl could not collect the page; prior findings cannot be declared fixed. | NOT RECHECKED |
What the full report includes.
Issue ledger
Supported findings with affected URLs, observed evidence and suggested next actions. The full saved report lists the issue ledger; the email highlights priorities.
Baseline and previous report
Separate comparisons help distinguish a new finding from a recurring condition. Coverage limits remain visible.
Separate lab results
Mobile and desktop Lighthouse results identify the tested URL. Unavailable lab data stays unavailable; CrUX real-user data is not collected.
What these observations do not prove.
Keyword rankings, competitors, backlinks, Google Business Profile, Search Console, GA4, call tracking and CRM data are NOT MEASURED by the current monitoring service. It does not submit forms, place calls, test hosting capacity or measure leads and revenue. Real-user CrUX data is not collected. PDF reports and daily checks are not available.