Should an ordinary publisher still use FAQ schema?
Use FAQ markup only for genuine visible questions and answers, not as a traffic shortcut. Google generally limits FAQ rich results to authoritative health and government sites.
Written for independent publishers deciding whether an FAQ block and FAQPage JSON-LD deserve space in their article templates.
Key facts
- Google says FAQ rich results are generally shown for well-known authoritative government and health websites.
- FAQPage markup must describe visible questions with complete visible answers.
- An FAQ section can still earn value through clarity, internal links, and direct answer structure.
A useful rule: make each important claim understandable and verifiable without requiring the reader to reconstruct your meaning from the rest of the page.
Is FAQPage markup still eligible for most sites?
Usually not for a visible Google FAQ rich result. Google reduced FAQ rich-result availability and states that it is generally shown for well-known, authoritative government and health sites. An ordinary software, commerce, or editorial publisher should therefore stop treating FAQ schema as a search-result expansion tactic. The vocabulary still exists, and valid markup can be understood by other consumers, but expected Google presentation should be close to zero outside the stated categories. Make the implementation decision based on maintenance cost, other consumers, and reader usefulness rather than an outdated screenshot of expanded results.
- Remove FAQ rich-result projections from ordinary publisher forecasts.
- Keep visible FAQs when they answer real follow-up questions.
- Do not mass-add markup to every article merely because a plugin offers it.
When is a visible FAQ section still useful?
A compact FAQ works when readers repeatedly ask distinct follow-up questions that do not fit naturally into the main flow. Each answer should be complete on the page, concise enough to scan, and linked to deeper guidance when necessary. Avoid repeating the article's headings as questions simply to create a block. Search and answer systems can extract clear prose without FAQPage markup, so the editorial structure matters more than the schema label. Put the main answer near the top, reserve FAQs for edge cases, and delete stale questions during scheduled reviews.
- Choose questions from support logs, search queries, or user research.
- Answer each question without requiring an accordion click to understand the claim.
- Keep primary instructions in the article body rather than hiding them in FAQs.
What does compliant FAQ markup require?
If you retain FAQPage JSON-LD, every marked question and accepted answer must be visible to users on the page. Accordions are acceptable when users can expand them, but the answer cannot exist only in metadata. Do not mark user-submitted discussion where multiple answers compete; that is a different content model. Avoid advertising disguised as an answer, profanity, illegal content, or claims that contradict the page. Generate markup from the same question records rendered in HTML so edits cannot leave invisible or outdated answers in the structured object.
- Create HTML and JSON-LD from one FAQ array.
- Mark only publisher-authored question-and-answer pairs.
- Remove markup when the visible FAQ is removed.
Sources: 2
Could the markup still help AI answer systems?
There is no reliable evidence that adding FAQPage markup alone improves citation in AI answers. Major search guidance emphasizes accessible, indexed, helpful content and says no special AI markup is required for Google AI features. Clear question headings and self-contained answers may improve extractability because they reduce ambiguity, but that benefit comes from the visible writing. If another named consumer documents support for FAQPage, test it directly. Do not present speculative AI visibility as a reason to maintain markup that has no verified consumer or produces mismatched content.
- Prioritize crawlable visible answers over speculative schema benefits.
- Name the consumer and measurement before adding maintenance work.
- Track citations by query and passage, not markup presence alone.
Sources: 2
What should replace an FAQ schema-first strategy?
Build pages around one real decision, answer it early, and use question-shaped subheadings for the remaining evidence and implementation details. Link important terms to canonical guides, cite primary sources close to changing claims, and maintain visible update dates. This structure serves readers, classic search, and answer systems without depending on a scarce rich result. If an FAQ is still the best interface, keep it and measure engagement. If it is merely repeated content beneath an already complete article, remove it. Your success metric should be solved user tasks and qualified search visits, not the number of schema objects emitted.
- Use the main question as the page's editorial spine.
- Place sources beside consequential claims.
- Measure task completion and qualified entrances.
Put it to work
Find the highest-impact fix on your site.
Compare every FAQ entity with its visible question and answer before deciding whether the markup should remain.
Audit FAQ markupSources
- 1.Google Search Central: Changes to FAQ and HowTo rich resultsChecked 2026-07-26
- 2.Google Search Central: General structured data guidelinesChecked 2026-07-26