Overview tab
The Overview tab summarizes a single page — its SEO score, a Google search preview, category scores, what's working, and the full issue list.
The Overview tab is the first thing you see when you open a crawled page. It rolls every other tab into a single verdict: the page's score, how it would look in search, its health by category, what already passes, and the full list of what to fix. It reads top-down. First comes the search preview and a rendering of how the page loads. The page summary follows, then Google's own performance data. Below that are the category scores, what is working, and the issues to act on.
Google search preview
A Google search preview renders the page's title, description, favicon, and
URL as Google would show them for the crawled device (desktop, mobile, or tablet).
Where the page's schema supports them, it adds rich-result affordances: FAQ,
breadcrumb, article, rating, and product. Article rich results only preview on
editorial pages (an og:type of article or a blog-like URL), so a homepage is not
wrongly advised to add Article markup. When a page could not be fetched, the
preview is skipped rather than showing fabricated "missing title" guidance.
Visual rendering
Beside the search preview, a visual rendering thumbnail shows the rendered page for the crawled device, with its Core Web Vitals grades. It puts how the page actually loads next to how it would appear in search.
Page summary
The summary card leads with three hero tiles bound into one verdict band:
- SEO score — 0–100 with a verdict of Good (≥ 80), Needs work (≥ 60), or Poor (below 60). A non-page such as a 404 shows its status rather than a misleading "0 · Poor".
- Issues — the tracked count with Critical, High, Medium, and Low chips.
- Indexability — the audit state (Indexed, Noindex, Soft-404, Canonicalised, Redirect chain, Near-duplicate, 4xx, 5xx, and more).
Below the tiles, a metric grid groups the specifics: Response (status, document size, requests, stack), Content (title and meta length, words, images missing alt), and Links & schema (internal/external links, broken links, schema blocks, freshness).
Google data
When Search Console and GA4 are connected for the project, a Google performance card sits below the summary. It adds the page's real clicks, impressions, average position, sessions, and an indexing verdict. This is the one place per-URL Google data surfaces. It is Google's own verdict on the page, distinct from the crawl's audit score.
Category scores
A category scores card lists clickable bars — Indexability, Content, Headings, Media, Links, Schema, Social, Local SEO, and Performance — each jumping to its tab. A category that does not apply to the page (for example, Local SEO on a non-local page) shows a neutral state rather than a red zero. That way it does not drag down the read.
What's working and page issues
What's working lists the checks the page passed. It is the only place passed checks surface, so the tab is not a wall of red. The page issues panel, expanded by default, lists every finding filterable by severity. Each issue states what it is, why it matters, and how to fix it. It also links to every other page in the crawl with the same issue, so a systemic problem can be fixed once at the template level.
Issues live only on the Overview tab. There is no separate Issues tab. Each per-category tab shows its own findings in a card, but the complete, filterable list for the page is here.
Start from the severity chips. Clear Critical and High findings first, since those are the ones that block indexing or ranking. Then use the "same issue on N pages" links to batch the fix across the site.
Reports & dashboards
Read your crawl — the project dashboard, the Visualizer, audit comparison, and the per-page report with a tab for every area of SEO.
Site health
The Site health view covers the site-wide checks that run once per crawl — robots.txt, sitemaps, SSL, and llms.txt — and feed the Site Architecture score.