FAQPage schema
What this is
If this is a frequently-asked-questions page, we look for FAQ markup in the page code (FAQPage structured data: a fixed, machine-readable list of each question and its answer).
Why it matters
Google now shows expandable FAQ answers in search results for almost no ordinary sites, so the effect on how you look in Google is small. The main benefit is helping AI engines tell which text is a question and which is its answer.
What counts as passing
Passes when FAQPage markup lists at least 1 question and every question has an answer; markup with missing answers is a partial pass. Not scored when the page does not look like an FAQ (fewer than 3 H2/H3 subheadings ending in a question mark and no /faq in the URL). Note: structured data nested inside @graph isn't read yet, so this can be misjudged.
Evidence
| Detected as FAQ page | No |
|---|---|
| FAQ markup found | No |
| Questions in markup | 0 |
Raw data
Check ID aeo.faq.schema
{
"isFaqPage": false,
"schemaFound": false,
"questionCount": 0
}Suggestion
Pro plan onlyComplete FAQPage schema
This FAQ-like page (question headings or /faq URL) is missing or has incomplete FAQPage JSON-LD (0 Question entries). Add schema.org/FAQPage with acceptedAnswer.
Before / After
(none)
<script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"What is X?","acceptedAnswer":{"@type":"Answer","text":"X is ..."}}]}</script>