Schema & SERP: JSON-LD Coverage and Rich Results

The Schema & SERP page summarises JSON-LD structured data across your crawled pages: which types you use, where validation fails, and which rich results Google may eligible for.

Summary

• Crawled pages — Sample size for schema analysis.
• With JSON-LD — Pages containing at least one JSON-LD block.
• Coverage % — Share of crawled pages with structured data.

Low coverage on templates that support rich results (products, articles, FAQs) is a quick win for CTR.

Type coverage tab

Table columns:

• Type — Schema.org type (e.g. Article, Product, FAQPage).
• Pages — Count of URLs using that type.
• Errors — Validation issues detected in crawl.
• Rich results — Eligible rich result features (when inferable).
• Sample — Example URL to inspect in the page viewer.

Prioritise types with high page counts and non-zero errors.

Pages with issues tab

Lists URLs that are missing JSON-LD or have parse/validation errors. Open each in the page viewer to see raw JSON-LD, fix in CMS or tag manager, then re-crawl.

BearAudit vs Google’s Rich Results Test

BearAudit evaluates structured data at crawl scale across your property. Google’s live testers validate single URLs in real time. Use both: BearAudit for inventory and prioritisation; Google’s tools for pre-publish validation of fixes.

Workflow

1. Crawl the site with JSON-LD verification enabled.
2. Fix missing types on high-traffic templates first (Template Analytics).
3. Resolve errors on top types (invalid properties, wrong nesting).
4. Re-crawl and confirm coverage % and error counts drop.
5. Monitor CTR in Search Console after rich results appear.

Competitor context

On the Competitors page, the Schema tab compares JSON-LD coverage vs crawled rivals—useful for benchmarking FAQ, Product, or Article markup in your vertical.

Related reading

• JSON-LD and structured data (blog)
• Verifications — Per-page JSON-LD checks