Technical
FAQ Schema Builder
Correct FAQPage markup, and what Google changed
Enter question and answer pairs and get a valid FAQPage JSON-LD block in a script tag, with the markup checked against the answers visible on the page, and a note that Google retired FAQ rich results in May 2026 and removed the documentation in June.
Get early accessWhat it returns
- A FAQPage JSON-LD block wrapped in a script tag, with every question and answer escaped correctly, including answers that contain links or lists.
- Each property labelled required or optional against the schema.org definition, so the block is correct for any consumer that parses it.
- A plain statement of what changed: Google retired FAQ rich results on 7 May 2026 and removed the documentation on 15 June 2026, so this markup will not produce an expanded FAQ in Google results.
- A check that every answer in the markup also appears in the visible page text, which is the rule that still holds whoever is reading the block.
When this matters
A team spent a year adding FAQ blocks to service pages for the expanded result in Google, and that result no longer exists: Google retired FAQ rich results on 7 May 2026 and took the documentation down on 15 June 2026. The question that follows is whether to strip the markup out. Usually not, because it is cheap, it is valid structured data that other consumers and internal systems still parse, and the FAQ content was earning the page something on its own. What has to change is the expectation, and any new block needs to be written for correctness rather than for a feature that was withdrawn.
How to answer this today
Site audit tells you where the markup you already shipped is, which is the first thing you need once a rich result is withdrawn: the crawl parses the structured data on every page and reports what type each block declares and where it is malformed. Deciding what to do with a FAQPage block is much easier when you know how many pages carry one.
Site auditWhy this is harder than it looks
The Google feature is gone
FAQ rich results were retired on 7 May 2026 and the documentation followed on 15 June 2026. Any tool, this one included, that promises an expanded FAQ in Google search results is describing something that no longer happens.
Other consumers are undocumented
Valid FAQPage markup is still read by other search engines, site search, assistants and internal tooling, and none of them publish a requirements list the way Google did. Correct against schema.org is the only standard left to hold output to.
The answer has to be on the page
Marking up an answer a visitor cannot see was always a policy problem, and it is still simply wrong when nothing renders it. The markup describes the page, so a builder that lets you type answers the page does not contain is helping you publish something untrue.
An FAQ block is often the wrong format
A page padded with invented questions to carry markup reads worse than the same information written as prose under real headings. Losing the rich result removed the only reason many of those blocks existed.