FAQ Schema Detection

FAQ Schema Detection scores the quality of your homepage FAQPage JSON-LD, not merely whether it exists. friendly4AI parses the FAQPage block, counts the Question entries in mainEntity, measures the average length of questions and answers, and compares each question against your body content for duplication. Those five readings roll up into one composite score from 0 to 100.

What does this parameter measure?

It measures how well-formed your FAQPage JSON-LD is. The scanner reads the FAQPage block, counts Question entries in mainEntity, takes the average length of questions and answers, and checks each question against your page body for duplication. Having the schema present is the floor, not the goal. A thin or copy-pasted FAQ helps AI systems far less than a well-built one, which is why the result is a composite rather than a yes/no flag.

Why does FAQ schema matter for AI-readiness?

FAQPage schema lines your answers up against the questions users actually ask, which is the exact shape AI assistants want to quote. A focused set of well-sized question-answer pairs hands ChatGPT, Gemini, and Perplexity clean, citable units they can lift straight into a response. The signal is engine-relevant for Bing's structured-data pipeline.

The reverse is just as true. One-question stubs, bloated answers, or questions that simply restate your body text leave the model nothing distinct to extract, so the schema earns little credit. Pair this parameter with structured-data-coverage and content-type-schema-match to build a coherent entity layer.

How is FAQ Schema Detection scored?

Under the v4.5 methodology, this Discovery parameter runs on a five-part composite. The published Binary rubric is superseded by the v4.3 composite the processor actually executes. Each part carries its own weight:

• Presence — 50%
• Question count — 15%
• Question length — 10%
• Answer length — 10%
• Low body-duplication — 15%

Any valid FAQ with at least one question banks the presence credit, so a presence-only FAQ scores 50 and lands in partial. To pass, a richer FAQ has to clear 80: that means the 4-8 question sweet spot, 8-20 word questions, 40-80 word answers, and little duplication against the body. A FAQ fails if it won't parse, carries no Question in mainEntity, or scores below 30 — typically one-question stubs, oversized answers, or near-total duplication, which land at composite 0 or just above it. Push the count to 16 questions or more and the scanner reads it as spam, so it adds nothing to the count sub-score.

How do I fix common FAQ schema issues?

• Add FAQPage JSON-LD with real Question/acceptedAnswer pairs in mainEntity. Presence alone moves you off a hard fail.
• Aim for 4 to 8 questions. Fewer weakens the count band, and 16 or more is penalised as spam.
• Keep questions concise (roughly 8-20 words) and answers substantive but tight (roughly 40-80 words).
• Write answers that add information instead of echoing your page body. High overlap with body text triggers the duplication penalty.
• Validate the block at search.google.com/test/rich-results so a malformed FAQ doesn't score zero.
• Re-scan after publishing to confirm the composite has moved into the pass band.