Reading a report
A walkthrough of the report viewer — the summary, every tab, and how issues are grouped so you can act on them.
The summary
Every report opens on the Overview: the three scores (Health, GEO, A11y — see How scoring works), total pages crawled, and the error and warning counts. It also shows what the crawl discovered about the site itself: whether a robots.txt, sitemap (with its URL count), and llms.txt were found.
The tabs
| Tab | What’s in it |
|---|---|
| Overview | Scores, summary, charts, and top issues. |
| Issues | Every finding, grouped by rule — each with a count, affected URLs, why it matters, and how to fix it. |
| Pages | The full page index: every URL crawled, with status and per-page findings. |
| Link graph | Your internal link structure, ranked — which pages your own site treats as most important. |
| Insights | Higher-level observations across the crawl. |
| Redirects | Every redirect encountered, including chains. |
| Rules | Results from your workspace’s custom rules. |
| Extraction | Output from custom extractors, if configured. |
How issues are grouped
Issues are grouped by rule, not by page — one row per problem type, with every affected URL under it. Fixing is usually one change (a template, a config) applied across many pages, so this is the shape you actually work in. Rows are ranked by severity (error → warning → notice), then by how many pages they affect.
Freshness
Reports don’t go stale silently: if a newer crawl of the same site exists, the older report shows an Outdated badge with a jump to the latest one.
Next steps
- Comparing crawls — see what changed between two reports.
- Sharing reports — send a report to someone without an account.
Still stuck? Email us — a human replies, usually within a day.