BlogResearch
Research

81% of AI-cited pages use schema markup. FAQ schema appears in 1.8% of them.

An analysis of 9,000 AI citation sources found that FAQ schema, the most recommended structured data type, appears in almost none of the pages ChatGPT, Perplexity, and Google AI Overviews actually cite. Person schema appears in 58.9%. Here is what the data shows.

FAQ schema appears in 1.8% of the pages AI systems actually cite. It features in nearly every SEO best-practice checklist. Those two facts point in different directions, and the data from 9,000 AI citation sources tells you which one to follow.

58.9%
of AI-cited pages use Person schema
versus 1.8% for FAQ schema. Source: AccuraCast, 9,000 citations, Sep 2025.

AccuraCast analyzed 9,000 AI citation sources across three platforms

AccuraCast published the analysis in September 2025, pulling 9,000 AI citation sources from 2,000 prompts run across ChatGPT, Google AI Overviews, and Perplexity.

The study mapped which structured data types appeared on the pages AI systems actually cited, then compared that pattern against a control set of similar pages that never got cited — isolating schema as one variable rather than assuming a correlation with citation proves it caused one.

81% of cited pages included some form of schema markup, but the distribution across schema types was not what most SEO advice would predict.

Why does FAQ schema appear in only 1.8% of AI-cited pages?

FAQ schema appears in just 1.8% of the 9,000 AI-cited pages AccuraCast analyzed — not a rounding error, but a signal that standard SEO advice and actual AI citation outcomes are disconnected on this specific tactic.

The recommendation is intuitive: if your content answers questions, mark it up as questions and answers so machines can read it. AI systems are question-answering machines, so FAQ schema feels like an obvious fit.

The first reason is a Google policy, not an AI behavior: FAQ rich results are restricted to government and health sites, so FAQPage schema on a commercial page produces no rich result in Google Search and therefore no extra signal feeding Google AI Overviews.

The second reason is how AI crawlers read a page at all. A Writesonic test of on-page elements across six major AI crawlers found none of them parsed embedded JSON-LD reliably — the markup is present in the page's source, but the crawlers are not reading it.

Why is Person schema the most common structured data type in AI-cited pages?

The schema type that actually appears in cited pages is Person schema, which identifies the author of a piece of content — their name, credentials, and a URL that uniquely identifies them as an entity.

58.9% of all AI-cited pages in the AccuraCast dataset include Person schema. For ChatGPT specifically, that number rises to 70.4%.

Person schema's dominance correlates with a separate finding from Presence AI, which tracked 1,200 pages and 3,600 queries across four AI platforms over 90 days. Pages with expert authors and documented credentials achieved a 72% AI citation rate. Pages with no author attribution achieved 25%. That is a 2.9x difference driven entirely by author attribution.

Person schema is not causing the citation. It is reflecting the underlying fact that AI systems favor content produced by identifiable, credentialed humans. The schema makes that entity authority signal machine-readable and consistent across platforms.

Schema typeShare of AI-cited pagesChatGPT share
Person58.9%70.4%
FAQ Page1.8%n/a

Source: AccuraCast, 9,000 citation sources, Sep 2025

Which webpage metadata elements can AI crawlers actually read?

Of the metadata elements Writesonic tested, only the title tag survives contact with AI crawlers — five of six crawlers read it reliably. JSON-LD, meta descriptions, and Open Graph tags all scored zero out of six in the same March 2026 test of 62 webpage elements across those crawlers.

Google recommends JSON-LD as the preferred schema implementation format. Traditional search crawlers read it reliably. But AI crawlers work differently.

JSON-LD schema may still benefit your visibility in traditional Google Search and in Google AI Overviews, which builds on Google Search infrastructure. But for OpenAI, Anthropic, and Perplexity crawlers, visible content is the primary input — schema is not the channel those crawlers use.

What should you implement instead of FAQ schema for AI citations?

Google explicitly recommends an author.url value in Article structured data that ties the page to one identifiable, credentialed author — implement Person schema instead of FAQ schema, since it is the schema type with the strongest observed correlation to AI citation in this dataset.

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your article headline",
  "author": {
    "@type": "Person",
    "name": "Jane Doe",
    "url": "https://example.com/authors/jane-doe",
    "jobTitle": "Senior SEO Analyst",
    "sameAs": ["https://linkedin.com/in/janedoe"]
  },
  "publisher": {
    "@type": "Organization",
    "name": "Your Site Name",
    "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
  }
}

Minimal Article + Person JSON-LD — the combination this dataset found most correlated with citation (Person schema, 58.9% of cited pages). author.url pointing to a real, credentialed author page is the part Google explicitly recommends and this data supports prioritising.

Second, make the author visible in the content itself, not just in metadata: a named byline, a short credentials statement, and a consistent author page all contribute to the underlying signal that schema is trying to communicate.

When AI crawlers cannot read the JSON-LD, they can still read the paragraph that says who wrote the piece and why they are qualified.

Skip FAQ schema unless your site qualifies for Google FAQ rich results (government or health).

Article schema is still worth including — it provides structural context that benefits traditional crawl parsing. But if you are choosing where to invest time, Person schema and visible author credentials produce the observable outcome.

Author credibility, not schema markup, drives AI citations

81% of AI-cited pages carry some form of structured data, but author credibility, not schema markup, is what actually correlates with citation — the schema number describes a correlation, not a cause.

Person schema shows up on 58.9% of AI-cited pages because those pages tend to already be written by identified, credentialed authors — the schema documents an authority signal instead of creating it. FAQ schema shows up on just 1.8%, because it reflects nothing AI systems weight in their retrieval decisions.

Optimize the variable that is actually correlated with citation: the credentialed person behind the content, made visible in the schema and on the page itself.

Frequently asked questions

Does schema markup help AI citations?

Test it on your own site rather than assuming the 81% correlation figure will reproduce for you: track AI citation rate for a batch of pages before and after adding Person schema. If nothing changes after a reasonable window, redirect that implementation time toward the visible author bylines and credentials the schema was meant to document in the first place.

Do I need Person schema on every page, or just the ones I want cited?

Prioritise Person schema on the pages you most want AI systems to cite, not site-wide. Implement it wherever you have a real named author with credentials — typically blog posts, guides, and research pages. Skip it on pages with no clear individual author, like product listings or contact pages, where a fabricated Person entry would misrepresent authorship rather than reinforce it.

Should I add FAQ schema to my content to rank in AI search?

Skip FAQ schema unless you run a government or health site eligible for Google FAQ rich results program. Outside those two verticals, Google does not render the rich result at all, so the markup produces zero downstream benefit for search or, per this dataset, for AI citation either. If FAQ schema is already live from an older SEO push, there is no urgency to remove it, but budget any new markup effort elsewhere.

Should I remove JSON-LD structured data since AI crawlers cannot read it?

Keep your JSON-LD in place — AI crawlers not reading it directly does not make it worthless. It still benefits traditional Google Search rich results and feeds Google AI Overviews indirectly, since that surface builds on Google's own search infrastructure. Removing JSON-LD only matters for AI crawler readability, a fight it was never winning; the actual lever for ChatGPT, Claude, and Perplexity citation is visible on-page content and author credentials, not the schema layer.

BE

BetterAISearch Editorial Team

BetterAISearch

The BetterAISearch team synthesises peer-reviewed studies, platform documentation, and independent research into actionable, scored tactics.

Get the next finding first.

New research moves scores. We send what changed and what it means, before it becomes LinkedIn noise.