Schema Coverage: which pages have which schema, site-wide

Schema Coverage audits the structured data across a domain (up to 50 pages, or the pages of an earlier crawl): which types each page has, which its page type should have, how complete they are, the quality of your sameAs links, and what blocks rich results.

Updated 2026-11-21
PlanPro and Agency
UsesAbout 2 monthly credits a run
Time1 to 3 minutes
Open Schema Coverage →

Step by step

  1. Open Schema Coverage #

    Find it under Schema & Entities, Coverage, in the left sidebar.

  2. Enter the domain #

    Set the number of pages (up to 50), or use the pages from a previous Site Crawler run.

  3. Run it #

    Every page's JSON-LD is extracted (including @graph) and scored.

  4. Read the map #

    See types present and missing for each page type.

  5. Fill the gaps #

    Generate the missing types with the Schema Generator or Bulk Schema Generator.

Why it matters#

Schema gaps are rarely on one page; they follow templates. Coverage shows the pattern across the site (every service page missing Service, every post missing an author) so you fix the template once.

What it checks#

  • Every JSON-LD block on each page, flattened through @graph and arrays.
  • Recommended types per page type (home, service, product, article and so on), including AI-relevant types.
  • Completeness: field presence, nesting quality and advanced signals.
  • sameAs quality: Wikidata, Wikipedia, LinkedIn and other profiles.
  • Rich result blockers: what stops a page qualifying.

Reading the results#

  • Missing types by page type point at template fixes.
  • Low completeness means the type is there but thin.
  • Weak sameAs means your entity is not tied to authoritative profiles.
Schema Coverage audit summary and missing schema
Example dataA site's schema coverage: pages with schema, rich-result eligibility and completeness, the gaps found, and the missing schema types in priority order.

Implementing the fixes#

  1. Fix templates first: add the recommended type to each page-type template.
  2. Strengthen Organization sameAs with Wikidata and LinkedIn.
  3. Use the Bulk Schema Generator for many pages at once.
  4. Set up Schema Monitor on key pages so fixes stay fixed.

Worked example#

A retailer runs coverage on its latest 200-page crawl.

  • "38 of 200 pages have no schema markup at all": all of them blog posts.
  • Product pages have Product but low completeness: no offers, no brand, no aggregateRating.
  • "Only 12/200 pages use @id entity linking".
  • Weak sameAs: the Organization links only to Facebook.

The fixes, all at template level: Article with author and dates on the blog template, offers and brand on the product template, @id on the site-wide Organization and WebSite nodes, and sameAs to LinkedIn, Wikidata and the store's review profile. Re-run after the next crawl: 0 pages without schema and completeness up across product pages.

Best practice#

Run from a crawl so coverage reflects every page crawlers find, not a sample.

Troubleshooting

The crawl is still running #

The app sayswait for crawl to finish

Coverage reads a finished crawl. Wait for it to complete, then run coverage.

A site you know has schema shows none #

The schema is added by JavaScript after the page loads, so it is not in the HTML the crawl read. Many crawlers miss it for the same reason. Output JSON-LD in the server-rendered HTML.

The crawl cannot be found #

The app saysJob not found or access denied

The crawl belongs to another account or was removed. Run a new crawl from the Site Crawler.

Not listed here? See Common problems for limits, checks, plans and pages that cannot be read.

Questions

How is sameAs scored? #
Links to Wikidata count most, then Wikipedia, then LinkedIn, then other profiles.
Why might a schema-rich site show no schema? #
Some firewalls serve bots a page without schema. Coverage fetches with a browser-like user agent to avoid that, but a strict firewall can still interfere; check with View as AI Crawler.
Does it need a crawl? #
Yes. It reads the pages from a finished Site Crawler crawl, so run a crawl of the domain first.

Something here does not match what you see in the app? Tell us and we will fix the guide.