Site Audit URL dossier
Start from the issue, page, or link evidence that led to this URL so the investigation keeps its original scope.
Bounded crawl
Traceable evidence
Comparable verification
Confirm URL, site, run, and retention state
The header identifies the saved inventory URL and crawl context. The stat strip shows the page score, issue count, HTTP status, response time, word count, inlinks, and outlinks where retained. These values summarize one URL snapshot, not the live page today.
A summary-only historical run can retain aggregate evidence while page detail has expired. Treat missing detail after compaction as unavailable, not clean.
Use the seven dossier tabs
| Tab | Evidence |
|---|---|
| Overview | Readiness groups, severity counts, and recent change handoffs. |
| Issues | Page findings with severity, rule evidence, filters, and pagination. |
| Links | Crawl path, inbound and outbound relationships, anchors, and target states. |
| Assets | Images, resources, and hreflang references observed for the page. |
| Schema | Retained markup items, types, feature profiles, and validation issues. |
| Changes | Saved page-level differences against a previous comparable run. |
| Technical | HTTP, metadata, robots, performance, content, and response facts. |
Overview is a router, not a diagnosis
Overview groups signals such as crawlability, indexability, content, links, schema, security, and performance and links to the deeper tab. The displayed score is a page heuristic based on status, issue count, and URL depth; it is not the site-level Health score or a ranking probability.
Issues shows the page's loaded finding set
Findings can be filtered by severity and loaded in bounded pages, currently ten rows per incremental request by default. Compare total count with loaded rows before copying evidence. A resolved or ignored status belongs to the saved finding record and does not update the live page.
Links keeps relationships and totals apart
The tab shows crawl path, inbound and outbound rows, anchors, placements, follow state, response state, redirects, canonicalization, and indexability context. Summary totals can be exact while loaded relationship samples remain paginated. Inspect both endpoints before changing a navigation or contextual link.
Assets includes more than images
Images, scripts, stylesheets, fonts, documents, media, iframes, manifests, and other retained references can carry element, attribute, placement, alt, loading, render-blocking, response, and issue evidence. Hreflang references are shown alongside these page-bound resources but have their own semantic rules.
Schema shows bounded markup snapshots
The page joins retained JSON-LD, Microdata, and RDFa item snapshots with validation issues by item index. It can show types, properties, Google feature profiles, required or recommended gaps, parse errors, and truncation.
A URL can have at most 25 retained item snapshots, with per-item and total JSON budgets. The original page source remains the final reference when a stored value was shortened.
Interpret markup findings with the structured-data validation guide before equating a clean result with rich-result eligibility.
Changes needs an earlier comparable page
The tab compares retained URL facts across runs and groups bounded rows by change type. If there is no previous comparable run or the URL was not matched, no delta is inferred. A recorded technical change still does not prove a traffic or ranking effect.
Check crawl comparability and retained history when deciding whether a page change is supported by earlier evidence.
Technical keeps raw facts and performance evidence together
Technical exposes response time, HTML size, content density, word count, HTTP and redirect state, indexability, canonical, robots, metadata, headings, cache and response headers, and available performance evidence. Missing CrUX field data, missing lab data, and a good field rating are distinct states.
Performance can mix field, lab, and crawl clocks
CrUX can be URL- or origin-scoped field evidence. PageSpeed or Lighthouse measurements are strategy-specific lab observations and can be sampled. Crawl response time is the crawler's own request observation. Compare source, scope, strategy, capture time, and coverage before combining them in one explanation.
Previous and next follow the stored investigation set
Page Explorer can store up to 100 inventory IDs for URL-page navigation in one browser-session context, with up to ten retained contexts. Previous and next move through that bounded set, not the entire crawl. Browser history preserves linked-page investigation separately.
Copied agent context is deliberately bounded
Agent prompts limit root causes, target URLs, evidence findings, array items, fields, lines, and characters. They help carry checked evidence into another workflow. They do not authorize automatic production changes or prove that omitted rows do not exist.
Investigate one URL without losing context
Example: Why a key page lost visibility
A strategist opens the dossier of an important category page. The Links tab shows that it now receives far fewer internal links than in the previous crawl, and the Changes tab lists a modified canonical.
Both facts go into one handoff with the run ID and URL, so the developer can check the template change behind them.
Frequently asked questions
Which tabs does the URL dossier have?
Overview, Issues, Links, Assets, Schema, Changes and Technical. Overview routes you to the tab that holds the evidence for each signal.
Is the page score a Google score?
No. It is a page heuristic based on status, issue count and URL depth to help you orient yourself. Decisions should rest on the evidence tabs.
Why do performance values differ?
CrUX field data, PageSpeed or Lighthouse lab tests and the crawler's own response time are different sources with different scopes and dates. Compare them by source, not as one number.