FAQ Schema Generator

What FAQPage markup does now that the rich result is gone

FAQPage is a schema.org type, expressed as JSON-LD, that marks a block of questions and answers on a page as machine-readable Q&A. It no longer produces a rich result in Google. Google deprecated FAQ rich results on 7 May 2026 — announced only as a note added to the top of the FAQ structured data documentation, with no blog post — and the expandable question rows stopped appearing in search from that date. Search Console reporting and Rich Results Test support for the type ended in June 2026, and the Search Console API stops serving FAQ data in August 2026.

What did not change: FAQPage is still a valid schema.org type, Google states it still uses the markup to understand what a page covers, and carrying it costs you nothing and risks nothing. Bing, other search engines, and the retrieval crawlers behind AI answer engines all still parse it, and a Q&A block expressed as data is far easier for a retrieval system to lift cleanly than the same content buried in prose. This generator emits the same structure it always did — a mainEntity array of Question nodes, each wrapping an acceptedAnswer — because the schema is unchanged; only Google's rendering of it went away.

When it is still worth adding

Add FAQPage markup when a page genuinely has a visible Q&A section and you want that Q&A available as structured data to every consumer other than Google's rich result renderer: Bing, an LLM crawler, your own site search, or internal tooling that reads your pages. Treat it as data modelling, not as a ranking or SERP-real-estate tactic. In practice nothing about a normal commercial site's Google appearance changes when you add it — and nothing changed when the feature died either, because Google had already restricted FAQ rich results to well-known authoritative government and health sites back in August 2023, so most sites had not seen one for nearly three years before the deprecation.

Don't strip existing FAQPage markup off your pages in response to the deprecation: Google's own guidance is that it can stay, and removing it only costs you the non-Google consumers that still read it. Do keep following the guideline that the marked-up questions and answers must be visible to a visitor on the page — that requirement was never about the rich result, and mismatched markup is still a structured-data spam signal.

Example

A SaaS pricing page with "Can I cancel anytime?" answered "Yes, cancel from your account settings with no penalty; you keep access until the billing period ends." and "Do you offer a free trial?" answered "Every plan includes a 14-day free trial, no credit card required." generates a mainEntity array with two Question nodes. Paste the resulting <script type="application/ld+json"> tag into the page's <head>, or right before </body>. Google's Rich Results Test dropped FAQPage in June 2026, so validate the output with the Schema.org validator at validator.schema.org instead — it checks the types and property names without reporting on a search feature that no longer exists.