Yes, but for a different reason than before. Google narrowed which sites qualify for the visual FAQ rich-result treatment in search in 2023, but FAQPage schema remains a clean, low-cost way to help both search engines and AI assistants parse question-and-answer content accurately.
What changed in 2023
Prior to August 2023, almost any page with valid FAQPage schema could earn the expanded FAQ rich result in Google Search — the collapsible Q&A dropdown that took up extra visual space in results. Google restricted this significantly, limiting the rich-result treatment mostly to "well-known, authoritative government and health websites." Most commercial and content sites lost the visual snippet even with perfectly valid markup.
This led some SEO commentary to conclude FAQ schema was now "dead" — a reasonable reaction if the schema's only value was the search-result visual treatment. But that's not the only thing it does.
Why it still matters
1. AI assistants read structured data, not just render it. Search rich results are a visual/UI decision Google makes independently of whether the underlying data is useful. AI systems parsing your page to generate an answer benefit from FAQPage markup regardless of whether Google chooses to display a rich snippet — the markup makes question/answer pairs unambiguous to extract, rather than requiring the model to infer where a question ends and its answer begins from unstructured prose.
2. It's free correctness, not a growth hack. Since the rich-result restriction removed the main incentive to over-use FAQ schema for SEO gaming purposes, what's left is close to its honest use case: marking up content that's genuinely structured as Q&A. There's little downside to implementing it correctly.
3. It complements, not replaces, other structured data. FAQPage works alongside Article, HowTo, and BreadcrumbList schema — each marking up a different aspect of the same page. Skipping FAQ schema doesn't make your other structured data more effective; they're independent signals.
When to use it (and when not to)
Use FAQ schema when:
- You have a genuine FAQ section with real questions and complete answers, visible on the page
- The content answers the kind of direct questions a user might type into a search box or ask an AI assistant
Don't use FAQ schema when:
- You're manufacturing shallow Q&A pairs purely to add schema (e.g., splitting one paragraph into three trivial "questions")
- The content isn't actually visible on the page — schema must match visible content
- You've already marked up the same content as a different schema type on the same page
How to implement it correctly
- Write real questions users actually ask — check your support tickets, sales calls, or "People Also Ask" boxes in Google for inspiration.
- Write complete, standalone answers — someone should understand the answer without needing the surrounding page context.
- Generate the JSON-LD with our FAQ Schema Generator — paste in your Q&A pairs and get validated markup with a live preview.
- Place the
<script type="application/ld+json">block on the same page the FAQ content actually appears on, and keep both in sync when you edit one. - Validate with Google's Rich Results Test to confirm it parses without errors — a technically valid file is still worth having even if it doesn't earn the visual snippet.
The bottom line
FAQ schema's role shifted from "an SEO snippet growth tactic" to "a content-clarity signal for machines," AI systems included. If your page has real FAQ content, marking it up remains worth the ten minutes it takes — just don't expect it to reliably win back the search-result visual treatment it used to.