FAQ Schema Generator
The FAQ accordion is gone from Google Search — the schema itself still has real, narrower value. Here is what actually happened and what to do now.
Pages with Q&A content — shows expandable answers directly in Google Search results.
Minimum 1 question + answer required. The content must be visible on the page — Google rejects FAQ schema if questions are not displayed to users.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": []
}
</script>- At least one question and answer
How to use the FAQ Schema Markup Generator
- Add your first question — enter the full question text exactly as it appears on your page. Google compares schema content against what users actually see.
- Enter the answer for that question. You can use basic HTML in answers: <p>, <ul>, <li>, <a>, <b>, <strong>, <i>, <em> are all supported.
- Click "Add question" to add more Q&A pairs. Put the most important questions first — they carry the most weight for topical relevance even without an on-page accordion in the SERP.
- Copy the generated JSON-LD block from the output panel.
- Paste it inside the <head> of your HTML — or anywhere in <body>. Both placements work for Google.
- Verify that every question and answer in the schema is also visibly present on the page — undisclosed or hidden content still risks a manual action, accordion or not.
- Test with the Google Rich Results Test to confirm the JSON-LD is technically valid. Note: as of May 2026, the test no longer scores FAQPage for a dedicated rich result — it will validate the markup without offering FAQ-specific eligibility, and Search Console's old Enhancements → FAQ report is gone too.
What changed on May 7, 2026 — and what still works
Google retired the FAQ rich result on May 7, 2026. The expandable Q&A accordion that used to appear beneath a search snippet no longer shows up — for anyone, on any query. This is not a ranking drop or a site-specific issue: Google announced the deprecation directly in its Search Central changelog on May 8, then removed the FAQPage documentation entirely on June 17, confirming the feature is gone for good rather than paused.
You can verify this yourself in under a minute. Run any page through the Rich Results Test — it will validate your JSON-LD as technically correct, but it no longer lists FAQPage among the rich results it checks for. And in Search Console, the Enhancements → FAQ report that used to track accordion coverage has been removed from the sidebar entirely — not hidden, not merged, just gone.
What still works
- The schema.org type is still valid. FAQPage remains part of the schema.org vocabulary — adding it does not break anything, trigger a penalty, or waste effort. Google has explicitly said unused structured data does not cause problems.
- Semantic understanding. Structured data still gives Google's crawler an unambiguous, machine-readable read of your Q&A content, separate from whatever visual rich result it may or may not generate.
- AI Overviews and AI Mode. Google's own May 2026 guidance on optimizing for generative AI features says structured data continues to help its systems understand and potentially cite page content — this was never exclusive to the now-retired accordion.
- Your actual FAQ content, not the markup. A genuinely useful, well-written Q&A section on the page still helps with long-tail queries, featured snippets and user trust — that value was always driven by the visible text, not the JSON-LD wrapped around it.
The honest recommendation: if the only reason you were adding FAQPage schema was the accordion, that specific payoff is gone and re-platforming effort just for this markup is no longer justified. If you already have a real FAQ section, keep the schema — it costs nothing, stays valid, and may still feed AI-driven search features. What follows below explains what the schema still does, and — where the old documentation made claims that no longer hold — says so plainly rather than pretending May 2026 did not happen.
How the FAQ Schema Markup Generator works
FAQ schema markup is a JSON-LD script block that describes a list of questions and answers to search engines in a machine-readable format. The generator lets you add Q&A pairs dynamically — enter a question, enter its answer, repeat as needed. The JSON-LD output updates live, and you copy the final block directly into your HTML. No server, no account, no data leaves your browser.
Once the markup is on your page, Google reads it during the next crawl and can use it to better understand your Q&A content in machine-readable form. Until May 2026 this also decided whether a page qualified for the FAQ Rich Results accordion; Google has since retired that specific display, so the practical benefit today is semantic clarity for crawlers and AI features rather than a visual change in the SERP.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What is JSON-LD structured data?",
"acceptedAnswer": {
"@type": "Answer",
"text": "JSON-LD is a script block placed in your page's head that tells search engines what your page contains in a machine-readable format."
}
},
{
"@type": "Question",
"name": "Does structured data improve SEO rankings?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Structured data is not a direct ranking factor, but it enables Rich Results that increase click-through rates — an indirect SEO benefit."
}
}
]
}
</script>What FAQ Schema does — and no longer does — in Google Search
Before May 2026, FAQPage was one of the most visually impactful schema types in Search — a standard snippet could expand into a multi-row accordion, several times taller than a plain blue link. That specific mechanism is gone. What is left is a mix of effects that were never about the accordion in the first place, plus a couple of claims that were always weaker than the marketing around them suggested.
Retired — do not expect these anymore
- Expandable Q&A accordion — removed sitewide, for every query, as of May 7, 2026. This was the headline feature and it is simply not shown anymore, regardless of how well-formed your schema is.
- Larger SERP footprint from the accordion — with no accordion, there is no extra vertical space to claim. A page with FAQPage schema now looks identical in the SERP to one without it.
- Sitelink extension from FAQ content — this was an occasional side effect of the accordion feature and appears to have gone with it; Google has not documented a replacement mechanism.
Uncertain — not officially confirmed either way
- Voice search answers — Google Assistant is being absorbed into Gemini, and there is no current Google documentation confirming FAQPage schema still feeds voice responses. Treat this as unverified rather than assume it still works.
Still real — but was never about the schema markup itself
- Featured snippet competition — driven by your visible, well-written Q&A text ranking for the question query, not by the JSON-LD wrapper around it. This was always true and remains true with or without the accordion.
- AI Overviews and AI-mode citation — Google's current generative-search guidance says structured data continues to help its systems parse and potentially cite content. This is the closest thing to a live successor to the old rich-result benefit.
- Crawler-level semantic clarity — a machine-readable Q&A structure is still a cleaner signal than expecting Google to infer the same thing from unstructured HTML.
FAQPage vs QAPage — which type applies to your content
Schema.org defines two separate types for Q&A content: FAQPage and QAPage. They look similar but are intended for fundamentally different page structures. Using the wrong type will not break your schema, but it signals incorrect content classification to Google.
| Property | FAQPage | QAPage |
|---|---|---|
| Who writes answers | The site owner — one authoritative answer per question | The community — multiple answers, voted or scored |
| Accepted answers per question | Exactly one | One or more, with ranking |
| Typical use case | Official company FAQ, product FAQ, help center | Forums, Stack Overflow-style platforms, Reddit |
| Google rich result support | None — the accordion was retired May 2026; only crawler-level understanding remains | None — never had a dedicated rich result format |
| Schema.org type to use | FAQPage + Question + Answer | QAPage + Question + Answer (with upvoteCount) |
| Risk of misuse | Manual action if content is spammy or not visible on page | Less commonly misused |
Use FAQPage for virtually all standard website FAQ pages, product Q&A sections, and help articles. Use QAPage only if your page genuinely hosts community-generated answers with voting or scoring — and even then, the Rich Result benefit is limited compared to FAQPage.
Where a visible FAQ section still helps — and where the schema still makes sense
Worth separating two decisions that used to be bundled: whether to write a Q&A section on the page (still a good idea, unrelated to the accordion), and whether to also add FAQPage schema on top of it (still harmless and possibly still useful, just no longer a growth lever on its own).
Pages where FAQ Schema is the right choice
- Dedicated FAQ pages — a page whose entire purpose is answering common questions. This is the textbook use case: every question in the schema is visible on the page, the content is written by the site owner, and the answers are authoritative.
- Service and product pages with a Q&A section — a short FAQ section (3–6 questions) on a service landing page still captures long-tail query traffic through the visible text itself; adding the schema on top costs nothing extra.
- Long-form articles with a "Frequently Asked Questions" block — pairing FAQPage schema with Article schema on the same page is still valid markup and gives Google two distinct, clearly labeled content blocks to parse from the same URL.
- Help center and support documentation — individual help articles answering a specific user question are ideal candidates, especially if they already rank for question-format queries.
- Local business pages answering location-specific questions — "Do you offer delivery to X?", "What are your hours during holidays?" — FAQ schema on these pages can appear in local search results.
When FAQ Schema becomes a risk
- Adding FAQPage to every page on the site — Google explicitly limits FAQ rich results to a small number of results per query and has deprioritized sitewide FAQPage use since 2023. Blanket implementation across hundreds of pages rarely adds value and signals low-quality schema use.
- Questions not visible on the page — Google verifies that each question and answer in the schema appears visibly in the page content. If the schema contains questions that users cannot actually see, Google will reject the markup. This is one of the most common reasons for FAQPage validation failures.
- Promotional or marketing content framed as Q&A — questions like "Why is our product the best?" with promotional answers violate Google's guidelines. FAQ schema is for genuine informational Q&A, not marketing copy.
- Duplicate FAQ content across many pages — if the same set of questions is deployed on dozens of pages via a footer or sidebar widget, Google may ignore the schema entirely as low-quality.
- Sites with a history of spammy structured data — if a site has received a manual action related to structured data abuse, adding FAQPage schema may be scrutinized more heavily.
Technical deep dive: visible content, character limits, and placement
The visible content rule is still the most important technical constraint for FAQPage schema, and it did not go away with the accordion. Every Question and Answer in your JSON-LD must correspond to content that a user can actually read on the page — this is a general structured-data integrity requirement under Google's spam policies, not something specific to the retired rich result. Hidden content (display:none, visibility:hidden, behind a tab that requires JavaScript) does not count. If the FAQ is in a collapsed accordion on the page itself, that is fine as long as the HTML content is present in the DOM even when visually collapsed.
Answer length — with the accordion gone, there is no more SERP truncation limit to write around. Write complete, useful answers regardless of length: Google uses the full text for relevance matching and, per its own generative-search guidance, for parsing content into AI Overviews. Short, vague answers that omit key details still compete worse for featured snippets and AI citations than thorough, specific ones.
JSON-LD placement — FAQPage schema can be placed either in the <head> or anywhere in the <body>. Both are fully supported by Google. For React and other SPA frameworks, the schema must be in the server-rendered HTML — adding it via useEffect after page load means Google may not see it during the first crawl. Use react-helmet-async for React with SSR, or next/head in Next.js Pages Router, or a Server Component in Next.js App Router.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "What schema types does this tool support?",
"acceptedAnswer": {
"@type": "Answer",
"text": "<p>This tool supports six schema types:</p><ul><li><b>Product</b> — for e-commerce product pages</li><li><b>Article</b> — for blog posts and news</li><li><b>FAQPage</b> — for Q&A sections</li><li><b>Organization</b> — for company pages</li><li><b>LocalBusiness</b> — for physical locations</li><li><b>BreadcrumbList</b> — for navigation paths</li></ul>"
}
},
{
"@type": "Question",
"name": "Is this tool free to use?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes — the tool is completely free. No account, no signup, no usage limits. All JSON-LD generation happens in your browser."
}
}
]
}
</script>