What is FAQPage Schema? The Schema.org Markup, Defined

FAQPage schema is a Schema.org structured data type that marks up a list of frequently asked questions and answers on a webpage, helping search engines and LLMs surface the content as rich results and direct citations.

FAQPage schema is a Schema.org structured data type that marks up a list of frequently asked questions and answers on a webpage. It is encoded as JSON-LD or microdata inside the page HTML and helps search engines and LLMs (ChatGPT, Claude, Perplexity, Gemini) surface the content as rich results and direct citations.

What FAQPage schema actually is

The schema is a JSON-LD object embedded in a script tag, typically structured as:

• @context: "https://schema.org"
• @type: "FAQPage"
• mainEntity: an array of Question objects, each with name (the question) and acceptedAnswer.text (the answer)

The full specification is at schema.org/FAQPage. Implementation is mechanical: serialize the Q-A pairs to JSON-LD and include the script in the page. The hygiene rule is that the visible page content must mirror the JSON-LD or search engines and LLMs treat the schema as misleading.

What people confuse it with

• "FAQPage schema gets you Google rich results." Was true through 2023 and partially through early 2026. Google deprecated FAQ rich results on May 7, 2026 and is removing the FAQ report from Search Console in June 2026. The schema is still useful for AEO and LLM citation, but the Google rich-result win is gone.
• "Schema is for SEO, not AI." Wrong. LLM crawlers (ChatGPT, Perplexity, Gemini, Claude) parse Schema.org markup as a structured signal about page content. FAQPage schema is one of the highest-signal structured types for AEO (Answer Engine Optimization).
• "The schema can have content the visible page does not have." Bad pattern. Google rejects schema that does not match visible content, and LLMs read the mismatch as a trustworthiness signal.

When FAQPage schema matters

FAQPage schema matters when:

• The page has real Q-A structure and the schema reflects the visible content.
• The page is optimized for AEO (canonical-answer content that LLMs would cite).
• The site has the engineering maturity to maintain schema alignment as the content evolves.

When FAQPage schema does not help

FAQPage schema does not help when:

• The page is a narrative article without natural Q-A structure, and the schema would require artificially restructuring the content.
• The Q-A content is so thin that adding the schema looks like a manipulation attempt.
• The site has no SSR / SSG and the schema is only present in client-rendered HTML (most crawlers and many LLMs do not execute JavaScript).

How Thinklytics handles FAQPage schema

Every insight article on thinklytics.com emits FAQPage JSON-LD via the SSR shell, with the visible body section mirroring the schema exactly. The runtime mirror test enforces this alignment across all 100+ articles, so a schema-body drift fails CI and blocks merge.

Frequently asked questions

What is FAQPage schema in one sentence?

FAQPage schema is a Schema.org structured data type that marks up a list of frequently asked questions and answers on a webpage, encoded as JSON-LD or microdata, that helps search engines and LLMs (ChatGPT, Claude, Perplexity, Gemini) surface the content as rich results and direct citations.

How is FAQPage schema implemented?

Most commonly as JSON-LD inside a script tag in the HTML head or body. The JSON object has @type: 'FAQPage' and a mainEntity array of Question objects, each with a name (the question text) and acceptedAnswer.text (the answer text). See schema.org/FAQPage for the full specification.

Does FAQPage schema still get rich results in Google?

No, as of May 7, 2026. Google announced that FAQ rich results no longer appear in Google Search, and the FAQ rich result report will be removed from Search Console in June 2026. The schema is still useful for AEO (Answer Engine Optimization) and for LLM citation, but the Google rich-result win is gone.

Why does FAQPage schema matter for AI citation?

LLMs that crawl the web (ChatGPT, Perplexity, Gemini, Claude) parse Schema.org markup as structured signal about page content. A clean FAQPage schema signals 'this page has canonical Q-A answers worth citing.' Pages without schema can still be cited but require the LLM to extract Q-A pairs from prose, which is less reliable.

Does the visible content have to mirror the FAQPage schema?

Yes. Google's FAQ rich-snippet policy requires the visible page content to mirror the JSON-LD or the markup can be rejected. The same hygiene applies to LLM citation: a schema that does not match the visible content reads as misleading and can suppress citation.

How many FAQs should a page have?

Most successful FAQPage implementations have 5 to 10 questions. Fewer than 5 looks sparse; more than 10 dilutes per-question signal. The Thinklytics insight articles target 8 FAQs as the sweet spot.

Should I add FAQPage schema retroactively?

Yes, for any high-value page where the content already includes Q-A patterns or could be naturally restructured to include them. The schema work is low-effort if the visible content exists. Adding fake FAQs solely for the schema is a bad pattern that hurts AEO and can trigger manual actions.

How does Thinklytics handle FAQPage schema?

Every insight article on thinklytics.com emits FAQPage JSON-LD via the SSR shell, with the visible body section mirroring the schema exactly. The runtime mirror test enforces this alignment across all 100+ articles. See data governance consulting for the broader content-governance pattern.