New here? Quattr measures search for enterprise teams. Its MCP assembles reports like this one inside Claude, ChatGPT and Cursor, you ask, it builds. This page defines what belongs in it. What the MCP is → Watch it answer →

Monthly

Technical SEO audit report

also called Site crawl reportTechnical health auditIndexability reportSite health report

The crawl-side inventory: what is reachable, what is indexable, where canonicals disagree with reality, where redirect chains and error responses sit, and which templates carry the problem. It is scoped to structural faults rather than performance, Core Web Vitals and linking each have their own report, and it is ordered by how much search value sits behind the fault, not by fault count.

Who it is for, and what it settles

Audience: Technical SEO
Job to be done: Give engineering a ranked list of structural faults blocking pages from being fetched, indexed or consolidated correctly.
Cadence: Monthly

The metrics, in three tiers

Headline numbers carry the story. Diagnostics explain a headline that moved. Guardrails stop a wrong conclusion. Every row links to the definition, the formula, the caveats and what the metric is not all live on the metric page.

Headline What you lead with 3

Diagnostic Reached for when a headline moves 4

Guardrail Stops the wrong conclusion 4

Required data sources

Skills that produce or interpret it

Method rungs covered

R1 Reachable , covered
R2 Retrieved , not covered
R3 Referenced , not covered
R4 Represented , not covered
R5 Rewarded , not covered

It covers the bottom rung, so this report can tell you whether the numbers above it are sound in the first place.

Why measurement is ordered →

Ask for it in one sentence

The prompt pack for this report, copy one, or watch it play in the simulator.

"What technical issues are blocking our pages?" Simulate this → Prompt gallery →
"Which pages are not indexable and should be?" Simulate this → Prompt gallery →
"Where do our canonicals disagree with what ranks?" Simulate this → Prompt gallery →
"How deep are our important pages buried?" Simulate this → Prompt gallery →

What to say out loud when you present it

A crawl is a snapshot with a start URL, a depth limit and a page budget, say what it covered before calling anything site-wide. Deep crawl coverage is population-gated on some properties, so an empty section can mean 'not collected' rather than 'no issues'. A fault count is not a priority list; weight by the impressions and clicks sitting behind the affected pages.