FAQ schema,
validator-checked,
copy-pasteable.
Type your questions and answers into the fields, get clean schema.org FAQPage JSON-LD back — run through our bundled validator first, so you find the missing properties before a crawler does. Google stopped showing FAQ rich results in May 2026; this markup is now for the engines that read your answers rather than the ones that decorate your listing.
Need a different type? The full schema generator also covers Article, BlogPosting, HowTo, Product, Organization, BreadcrumbList, and WebSite.
Google stopped showing it. Machines didn’t stop reading it.
Google restricted FAQ rich results to authoritative government and health sites in August 2023, then retired the appearance entirely on May 7, 2026. If you added FAQ schema for the expandable questions under your listing, that reason is gone.
The markup itself is untouched. FAQPage is still a valid schema.org type, Google still parses it, and leaving it in place causes no harm. What it buys you now is different: a question with a labelled answer is the smallest self-contained unit an answer engine can lift, and ChatGPT, Perplexity, Gemini, and AI Overviews all answer by extracting passages rather than ranking pages.
Four rules that keep FAQ schema valid
The Q&A must be visible on the page
Structured data describes content a visitor can see. Marking up answers that aren't in the page body is a violation — and AI engines cross-check the markup against the text they retrieved, so hidden answers get discarded anyway.
One FAQPage block per page
Put every pair in a single mainEntity array rather than emitting several FAQPage blobs. If your SEO plugin already outputs FAQ schema, don't add a second copy — check the page source first.
You wrote the answer, not your users
FAQPage means one official answer per question, authored by the site. Forum threads and community answers are QAPage, which is a different type with suggestedAnswer entries.
Answers that stand alone
Two to four plain sentences, no "as mentioned above," no promotional padding. The answer is quoted out of context or not at all, so it has to make sense with the page stripped away.
On WordPress, make it a field instead.
The free AuditAE WordPress plugin adds an FAQ editor to the post editor: type question-and-answer pairs as fields on any post or page and they publish as FAQPage JSON-LD — no shortcodes, no theme edits, nothing pasted into post content. It also gives you a filtered list of the posts still missing FAQ schema, and it defers to Yoast, Rank Math, All in One SEO, SEOPress, and The SEO Framework when one of them is already emitting it, so you never ship two competing blobs.
FAQ schema, answered
What is FAQ schema?+
FAQ schema (schema.org FAQPage) is JSON-LD structured data that labels the question-and-answer pairs on a page so machines can read them without parsing your HTML. Each entry is a Question with an acceptedAnswer, and the whole set sits in a mainEntity array. It tells a crawler "this text is the question, this text is the answer" explicitly, instead of leaving it to be inferred from your heading structure.
Is FAQ schema still worth adding in 2026?+
Yes, but for a different reason than it used to be. Google retired FAQ rich results — the expandable questions under a search listing — on May 7, 2026, so FAQ schema will not change how your listing looks in Google anymore. What it still does is make your answers machine-readable for the systems that now consume structured data: ChatGPT, Perplexity, Gemini, and Google's AI Overviews all extract passage-level answers, and a labelled Q&A pair is the cleanest possible unit for that. FAQPage is still a valid schema.org type and Google has confirmed leaving the markup in place causes no problems.
How do I add FAQ schema to my website?+
Generate the JSON-LD, wrap it in a <script type="application/ld+json"> tag, and place it anywhere in the page's HTML — head or body both work. On WordPress, the free AuditAE plugin adds an FAQ editor to the post editor so you enter Q&A pairs as fields and it emits the FAQPage JSON-LD for you, with a list view of the posts still missing it. If you hand-code it, remember the schema must describe questions and answers that are actually visible on that page.
Do the questions and answers have to appear on the page?+
Yes. Structured data has to describe visible content — marking up answers a visitor cannot see is a structured-data violation, and it also defeats the point for AI engines, which cross-check the markup against the page text they retrieved. Write the FAQ section on the page first, then generate schema from that same copy.
What's the difference between FAQPage and QAPage schema?+
FAQPage is for questions you wrote and answered yourself — one official answer per question, authored by the site. QAPage is for pages where users ask and multiple people answer, like a forum thread or a community Q&A, and it supports several suggestedAnswer entries plus vote counts. Using FAQPage on user-generated discussion is the most common mix-up. If your visitors can post answers, it's QAPage.
How many questions should FAQ schema include?+
There's no hard limit, but keep it to the questions people genuinely ask about that page's topic — usually four to eight. Each answer should stand on its own in two to four sentences, because that is the unit an AI engine lifts when it quotes you. Long, hedged answers get summarized (and the attribution goes to whoever was clearer); padding the list with keyword variants of the same question adds nothing a machine can use.
Is this FAQ schema generator free?+
Yes — free, no signup, no limit on how many you generate. Every blob is checked against a bundled schema.org validator before you copy it, so you see missing required properties before Google or an AI crawler does. AuditAE makes money on AI-citation audits; the generator exists because it is the fix we most often end up recommending.
Schema makes you readable. It doesn’t prove you get cited.
Shipping FAQPage markup is the input. The output worth measuring is whether ChatGPT, Perplexity, Gemini, and AI Overviews actually name your brand — and whether they link you or someone else — for the questions your buyers ask. AuditAE runs those prompts across all four engines and shows you the gap.