THE SHORT ANSWER
Keep FAQ schema when it accurately describes useful questions and answers that readers can access, and your team can maintain it. Fix mismatched or hidden answers before adding more markup. Google has retired FAQ rich results, and its AI search features do not require special schema. A valid FAQPage is not a promise of an AI citation.
Separate FAQ schema from Google’s search display
Google’s documentation update log records that FAQ rich results stopped appearing on May 7, 2026. Google removed the feature’s documentation on June 15. Do not budget for FAQ markup on the assumption that it will restore expandable FAQ results in Google Search.
Schema.org still defines FAQPage as a page presenting frequently asked questions. That vocabulary and Google’s display feature are separate things. Meanwhile, Google’s generative AI optimization guidance says structured data is not required for generative AI search. These sources establish a format and a platform rule; they do not establish a citation uplift across assistants.
Choose follow-up questions that change a decision
A September 26, 2026 SEO discussion about FAQ blocks asks whether copying questions from People Also Ask still helps. A July 15 discussion about forced FAQs questions adding them everywhere for citations. These are evidence of uncertainty, not proof of ranking effects.
Use search suggestions as research leads, then check whether each question belongs on this page. Prefer an unresolved condition, objection or next step over a heading rewritten as a question. Our framework for researching buyer questions helps distinguish observed needs from editorial assumptions.
- Relevance: would this answer help the page’s intended reader act?
- Evidence: can an owner verify the answer and its exceptions?
- Maintenance: will someone update it when the product or policy changes?
Publish the answer and markup from one record
Store each approved question and complete answer together. Use that record to render the visible FAQ and generate FAQPage mainEntity entries. Each entry uses Question for its type, name for the question, and acceptedAnswer containing an Answer with text. Keep the wording and qualifications consistent in both outputs.
Google’s structured-data policies require markup to reflect visible, relevant content. An answer only inside JSON-LD fails that check. Keep article authorship, dates and image information in the article schema as well; adding an FAQ does not replace the description of the article itself.
Check the rendered FAQ in every language
Validate the generated markup with the Schema.org validator, then compare it with the actual page. A syntax check cannot decide whether an answer is true, complete or useful. Inspect the server response and the document after language switching when the site changes text in the browser.
Use ordinary question headings and readable answers, or test an accordion against W3C’s accordion interaction pattern. Readers must be able to reach the answer, including with a keyboard. Our multilingual publishing guide explains why a translated browser view and a separate language URL need different checks.
- Match every question and complete answer, including limits and exceptions.
- Translate the FAQ heading, questions, answers and any links readers use.
- Check that inLanguage and schema text describe the document being served.
- Inspect all schema blocks for stale or conflicting copies from templates and plugins.
- Retest after an edit, language switch and navigation back to the page.
Decide what to keep, repair or remove
Keep accurate markup when it has a clear maintenance owner and a useful purpose in your publishing system. Repair it when the visible answer, language or product conditions have changed. Remove obsolete FAQ markup when its corresponding questions have been removed; keep any useful visible answers while you fix their data.
If you test whether a change affects AI visibility, save a baseline and record exactly what changed. Rewriting answers and adding schema together cannot isolate the effect of markup. Use our guide to interpreting AI visibility evidence to keep sampled citations separate from visits and inquiries. Citevia’s technical SEO service can help review implementation; the first deliverable is consistent, usable content.
FAQ schema: practical questions
Should I remove all existing FAQ markup?
No blanket removal is necessary just because Google retired its FAQ display. Review whether the markup still describes real, accessible answers and whether you can maintain it. Remove obsolete or misleading entries. Do not promise an AI benefit merely because the remaining markup is valid.
Can answers sit inside a collapsed accordion?
Yes, readers can use an accordion to reveal answers. Make its controls understandable and keyboard accessible, and ensure the complete answer appears when opened. An answer stored only in structured data is different: the reader has no way to reveal it. Simple visible headings are also a useful option.
Can I add extra keywords or answers only in JSON-LD?
Do not add claims or answers that readers cannot find on the page. Write useful, supported answers for readers first, then describe that content in the markup. Keep product restrictions and exceptions in both places instead of turning a qualified answer into a broader promotional claim.
Is there a required number of FAQ questions?
Schema.org defines FAQPage around one or more frequently asked questions. That definition does not establish an ideal number for AI citations. Include enough questions to resolve relevant follow-up needs, and stop when additional answers would repeat the page or add filler.
What if two plugins publish different FAQ answers?
Inspect the delivered page to identify which template or plugin creates each block. Choose one maintained source for each question-and-answer set, remove conflicting output, and retest the rendered page. Validate article and breadcrumb data too, so fixing FAQ duplication does not remove other accurate descriptions.