Methodology

Schema Markup Completeness

Technical Optimization · Near-zero weight for AI (kept for classic search)

What this check reads on your page

Every JSON-LD script on the page is parsed, separating those that parse and declare something from those with a syntax error, and the distinct schema.org types declared at the top level and inside @graph are counted. The check looks for an Organization node, or any of its subtypes such as LocalBusiness, that carries a name and a logo or url, and it checks for Open Graph title, description and image tags. It reports which of Organization, WebSite, FAQPage, Article and BreadcrumbList are missing, recognising subtypes such as BlogPosting for Article. A page with no valid JSON-LD at all is capped at 70.

Our verdict on the evidence

Near-zero weight for AI (kept for classic search) Controlled tests show no AI-citation lift from schema.org markup, and Google states no special structured data is needed for AI features. Near-zero weight is kept only for classic rich results and Bing grounding.

Ahrefs controlled schema test (1,885 treated pages vs matched controls) · Google Search Central guidance on AI features (no special schema needed, no ideal page length)

What this score tells you is whether the markup parses and which of five types are present; it says nothing about whether an AI answer will cite the page, because the tests that looked found no such link. Treat a low number here as housekeeping rather than a visibility problem. The one item on this page worth an afternoon is a block with a syntax error, which every parser that meets it reads as plain text.

What it is worth

5% of Technical Optimization, which is 1 points of the overall 100.

How audited pages score on it

Based on 30,738 audited pages.

The median page scores 40, and the middle half of pages score between 20 and 80.

  • Good (75 to 100)8,634 (28%)
  • Moderate (50 to 74)2,842 (9%)
  • Needs work (25 to 49)10,607 (35%)
  • Critical (0 to 24)8,655 (28%)

63% of audited pages score below 50 on it.

Where it fails most and least

Industries that fail it most

Industries that fail it least

How to fix it

  • Fix any JSON-LD block that fails to parse; an engine that cannot parse it reads it as plain text.
  • Declare the publisher as its own Organization node with name, url and logo, at the top level of the JSON-LD or inside @graph, not only nested as the article's publisher.
  • Add the page-level types that fit: Article or BlogPosting for a post, BreadcrumbList for the path, WebSite for the site.
  • Set og:title, og:description and og:image so link previews and Bing grounding have something to show.

What has changed in this factor

5 versions describe changes that could not be attributed to individual factors, so any of them may have changed this one; they are on the full changelog.

The other factors

All factors, and how the score is built