FAQPage Schema in 2026: No Rich Results, What It Still Does
FAQPage schema no longer earns Google rich results (removed May 2026). What the markup still does, when to add it and how to write answers that stand alone.
Kazi Khalid Hasan Tamim · BugViso Team
16 min read
FAQPage schema is JSON-LD that marks up question-and-answer pairs on a page.
Google limited FAQ rich results to well-known government and health sites in August 2023. It stopped showing them entirely on May 7, 2026, so FAQPage no longer earns an accordion in Google Search.
It stays valid schema.org for any parser that reads it. This guide covers the spec, how to generate it and when it is still worth adding.
1. What Happened to FAQ Rich Results (and What FAQ Schema Still Does)
Google's Search Central changelog records the sequence. In August 2023 FAQ rich results were limited to well-known government and health websites.
On May 8, 2026 Google added a notice that the feature "will no longer appear in Google Search starting May 7, 2026".
On June 15, 2026 it removed the documentation, saying the feature "is no longer shown in Google Search results." Existing markup causes no errors, and you do not have to remove it.
| Date | What changed for FAQ rich results |
|---|---|
| August 2023 | Limited to well-known government and health sites |
| May 7, 2026 | Stopped appearing in Google Search (notice added May 8) |
| June 15, 2026 | Google removed the FAQ structured data documentation |
What FAQPage schema still does is narrower than older guides claim:
- It states Q&A pairs explicitly. A parser reads question and answer text without inferring it from headings and paragraphs.
- It may help other consumers. Bing and AI engines can read JSON-LD, but none has published how much weight it gets, and we have no measurement showing a citation lift. Treat any such benefit as unproven.
- It documents your own content. The visible FAQ, not the markup, is what readers and AI engines actually quote.
The practical rule: write a good visible FAQ first, with questions people really search and answers that open with the direct answer. Add the markup if it costs you nothing to keep in sync.
For a broader view, see what schema markup is and how to add it, and schema markup for AI search for what is known about AI engines. For complementary advice on writing extractable answers, read content extractability for AI search engines.
2. FAQPage Schema: A Valid JSON-LD Example
The following JSON-LD is valid FAQPage markup with several Q&A pairs. Copy the structure; there is also a ready-made FAQ block in the JSON-LD template library:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"@id": "https://example.com/pricing/#faq",
"mainEntity": [
{
"@type": "Question",
"name": "What is the difference between standard technical SEO and Generative Engine Optimization (GEO)?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Traditional technical SEO focuses on optimizing web infrastructure for search engine crawlers like Googlebot to index HTML and rank blue links. Generative Engine Optimization (GEO) focuses on structuring content into high-extractability semantic entities, direct answer blocks, and valid JSON-LD schema so that generative AI engines (ChatGPT, Perplexity, Claude, Google AI Overviews) can easily retrieve and cite your brand as an authoritative source."
}
},
{
"@type": "Question",
"name": "How does FAQPage schema impact Google search results after the 2023 update?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Google limited FAQ rich results to government and health sites in August 2023 and stopped showing them entirely on May 7, 2026. The markup is still valid schema.org, but it no longer earns a rich result in Google Search."
}
},
{
"@type": "Question",
"name": "Can I include hyperlinks inside the acceptedAnswer text property?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Google supports basic HTML formatting tags within the acceptedAnswer text property, including anchor links (<a href='https://example.com/target'>link text</a>), bold text (<b>text</b>), italics (<i>text</i>), and paragraph breaks (<p>text</p>). Script tags, iframes, and style elements are strictly forbidden."
}
},
{
"@type": "Question",
"name": "Does FAQPage schema require every question to be visibly displayed on the page?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Google Webmaster Guidelines strictly dictate that 100% of the questions and answers declared in your JSON-LD markup must be visibly rendered in the user-facing HTML. Marking up hidden content, collapsed accordions that never load text, or deceptive FAQs will trigger a manual action for spammy structured data."
}
}
]
}
</script>3. Dynamic Next.js 15 & React Implementation
In modern enterprise applications, FAQ sections are frequently rendered using interactive UI accordions (e.g., Radix UI, Tailwind CSS, or Headless UI).
The Next.js 15 React component below dynamically synchronizes the visible client-side accordion component with the server-rendered JSON-LD script block, keeping the markup and the visible text in sync:
// components/faq/InteractiveFAQ.tsx
'use client';
import React, { useState } from 'react';
import { ChevronDown } from 'lucide-react';
export interface FAQItem {
question: string;
answerHtml: string;
plainTextAnswer: string;
}
interface InteractiveFAQProps {
items: FAQItem[];
canonicalUrl: string;
}
export function InteractiveFAQ({ items, canonicalUrl }: InteractiveFAQProps) {
const [openIndex, setOpenIndex] = useState<number | null>(null);
// Generate valid FAQPage JSON-LD payload
const jsonLd = {
'@context': 'https://schema.org',
'@type': 'FAQPage',
'@id': `${canonicalUrl}/#faq`,
mainEntity: items.map((item) => ({
'@type': 'Question',
name: item.question,
acceptedAnswer: {
'@type': 'Answer',
text: item.plainTextAnswer
}
}))
};
const toggleAccordion = (index: number) => {
setOpenIndex(openIndex === index ? null : index);
};
return (
<section className="faq-container my-12 max-w-4xl mx-auto px-4">
{/* Isolated Server/Client Synced JSON-LD Script */}
<script
type="application/ld+json"
dangerouslySetInnerHTML={{ __html: JSON.stringify(jsonLd) }}
/>
<h2 className="text-2xl font-bold text-slate-900 mb-6 tracking-tight">
Frequently Asked Technical Questions
</h2>
<div className="space-y-4">
{items.map((item, idx) => {
const isOpen = openIndex === idx;
return (
<div
key={idx}
className="border border-slate-200 rounded-xl overflow-hidden bg-white shadow-xs"
>
<button
type="button"
onClick={() => toggleAccordion(idx)}
className="w-full flex items-center justify-between p-5 text-left font-bold text-slate-900 hover:bg-slate-50 transition-colors"
aria-expanded={isOpen}
>
<span>{item.question}</span>
<ChevronDown
className={`w-5 h-5 text-slate-500 transition-transform duration-200 ${
isOpen ? 'rotate-180' : ''
}`}
/>
</button>
{isOpen && (
<div
className="p-5 pt-0 text-slate-700 text-sm leading-relaxed border-t border-slate-100"
dangerouslySetInnerHTML={{ __html: item.answerHtml }}
/>
)}
</div>
);
})}
</div>
</section>
);
}4. The 4 Rules of High-Extractability FAQ Content for AI Citations
Answer engines have not published how they use FAQ markup, so these standards aim at making the visible answers easy to quote:
- Inverted Pyramid Answers — State the direct answer in the first 40 words
- Exact Entity Pinning — Use RFCs, metrics, and domain-specific terms
- Natural Anchor Links — Embed deep-link references inside answer text
- Strict Neutral Voice — Avoid marketing hyperbole and promotional buzz
1. The 40-Word Definitive Answer Opening
Concise, factual openings are easiest to quote. Structure the first sentence of every acceptedAnswer.text to deliver a standalone, grammatically complete answer before expanding into nuances or steps:
- ❌ Weak / Conversational: "When considering whether to update your robots.txt file, there are many factors to weigh..."
- ✅ Optimized / Factual: "To block AI training scrapers while allowing search bots, configure
User-agent: GPTBotwithDisallow: /while settingUser-agent: OAI-SearchBottoAllow: /in your robots.txt root file."
2. Precise Entity Pinning
Avoid generic terminology. Include exact HTTP status codes (e.g., 301, 308, 404), specific Core Web Vitals acronyms (LCP, INP, CLS), and exact RFC specifications (RFC 9309).
Specific terms make an answer unambiguous to readers and to any parser.
3. Deep Source Hyperlinking
Include real Markdown or HTML anchor links inside the answer text pointing to primary source documentation. Links to primary sources let readers verify the claim.
For forum and support pages, where users submit the answers, see QAPage versus FAQPage schema.
5. Python Automation: FAQ Schema Extractability & Syntax Validator
This Python script parses a target URL and extracts all FAQPage entities. It checks for valid JSON, verifies that every question appears in the visible text, and reports how long each opening sentence is:
# scripts/audit_faq_extractability.py
import sys
import json
import httpx
from bs4 import BeautifulSoup
def audit_faq_page(url: str):
print(f"[*] Auditing FAQPage Schema & Extractability on: {url}")
headers = {"User-Agent": "BugVisoGEOValidator/1.0 (+https://bugviso.com)"}
try:
res = httpx.get(url, headers=headers, timeout=12.0, follow_redirects=True)
except Exception as e:
print(f"[X] Request failed: {e}")
return False
soup = BeautifulSoup(res.text, "html.parser")
page_text = soup.get_text()
scripts = soup.find_all("script", type="application/ld+json")
if not scripts:
print("[X] Critical Error: Zero JSON-LD script blocks detected.")
return False
faq_found = False
for script in scripts:
if not script.string:
continue
try:
data = json.loads(script.string)
except json.JSONDecodeError as exc:
print(f"[X] JSON Syntax Error: {exc}")
continue
nodes = data.get("@graph", [data]) if isinstance(data, dict) else data
for node in nodes:
if node.get("@type") == "FAQPage":
faq_found = True
questions = node.get("mainEntity", [])
print(f"[✓] Detected FAQPage entity containing {len(questions)} Q&A pairs.")
print("=" * 65)
for idx, q in enumerate(questions, start=1):
q_text = q.get("name", "").strip()
ans_node = q.get("acceptedAnswer", {})
a_text = ans_node.get("text", "").strip()
print(f"Question #{idx}: {q_text}")
# Verify Question is present in visible text
if q_text not in page_text:
print(" [!] Deceptive Warning: Question text not found in visible DOM!")
else:
print(" [✓] Verified: Question visible on page.")
# Calculate Word Count and First Sentence Length
words = len(a_text.split())
first_sentence = a_text.split(".")[0] if "." in a_text else a_text
first_sentence_words = len(first_sentence.split())
print(f" - Answer length: {words} words")
print(f" - Opening sentence: {first_sentence_words} words")
if first_sentence_words <= 45:
print(" [✓] Optimal Answer-First structure for AI snippet extraction.")
else:
print(" [!] Sub-optimal: Opening sentence exceeds 45 words; condense for higher GEO score.")
print("-" * 65)
if not faq_found:
print("[X] No FAQPage schema found on page.")
return False
return True
if __name__ == "__main__":
target = sys.argv[1] if len(sys.argv) > 1 else "https://example.com/faq"
audit_faq_page(target)6. How BugViso Audits FAQ Schema & AI Search Citations Automatically
Auditing FAQ markup across hundreds of landing pages needs automation. BugViso's structured data check and AI Search Readiness engine inspect FAQ content across every URL in a signed-in crawl.
- JSON-LD Extraction — Reads every ld+json block on each crawled page
- Property Validation — Checks FAQPage
mainEntity - Extractability Check — AI Search Readiness engine looks at answer-first structure
- Fix List — Ranked findings with AI-written fixes in the PDF
When you initiate an audit with BugViso:
- Structured data validation: The crawler parses every JSON-LD block on the page, validating required
mainEntityandQuestionfields and flagging malformed JSON-LD. - Extractability scoring: The AI Search Readiness engine checks whether question-style headings, lists and summary blocks are present and includes them in its 0 to 100 GEO citability score.
- Fix list: Findings appear in the ranked fix list, with AI-written fixes in the PDF.
BugViso does not compare the text in your schema with the visible page, so use the Python script above for that check. You sign in to run a scan; the checks are listed on the technical SEO audit page.
7. Common Implementation Traps & Edge Cases
Avoid these frequent mistakes when deploying FAQ structured data:
1. Using FAQPage for User-Submitted Forums (Use QAPage Instead)
A common schema violation is applying FAQPage to community forums, comment sections, or Q&A discussion boards where multiple users submit different answers.
FAQPage: Reserved exclusively for content authored by the website where there is a single, definitive answer per question.QAPage: Must be used when users submit alternate answers that can be voted on or accepted by community members.
Using FAQPage on user-generated content goes against Google's structured data guidelines. Use QAPage there.
2. Embedding Raw Interactive Scripts or CSS in Answer Text
While Google supports basic HTML formatting tags (such as <b>, <i>, <a>, and <p>), embedding <script>, <iframe>, <form>, or <style> elements inside the acceptedAnswer.text property is strictly forbidden. The parser will fail, and the entire FAQPage block will be discarded as unparsable.
8. Frequently Asked Questions
Does FAQ schema still show rich results in Google?
No. Google limited FAQ rich results to well-known government and health sites in August 2023 and stopped showing them entirely on May 7, 2026. Valid FAQPage markup causes no errors, but it will not produce an accordion in Google Search.
Why should I implement FAQ schema if my site does not get visual accordions?
Mostly for tidiness, not traffic. The schema states the pairs explicitly, and other parsers may read it, but no AI engine has published that it prefers FAQ markup and we have no data showing higher citation rates. If keeping it in sync is cheap, keep it; if not, put the effort into the visible answers.
How many questions should I include in an FAQPage schema block?
There is no required number. Include the questions people genuinely ask about the page's topic, and skip thin filler questions. Every marked-up question must also be visible on the page.
Can I markup the same FAQ across multiple pages on my website?
Avoid it. Repeating identical FAQ blocks across many URLs adds duplicate content and little value. Write the questions that fit each page.
Can FAQPage schema be combined with Product or Article schema in a single @graph?
Yes. Using an integrated @graph array is the recommended enterprise architecture. You can nest Product, BreadcrumbList, and FAQPage together on a single URL, linking them cleanly via unique @id URI identifiers.
9. Conclusion
FAQPage schema no longer earns a Google rich result, so the effort belongs in the visible FAQ: real questions, answer-first responses and accurate facts.
Keep any markup in sync with that text. An automated BugViso scan validates the JSON-LD on every page of your domain.
Written by
Kazi Khalid Hasan Tamim · BugViso Team
Kazi writes BugViso’s guides on website audits, Core Web Vitals, technical SEO, accessibility and AI search. The data in them comes from audits BugViso runs in a real Chromium browser, including our 219-site study of website health.
Summarise with AI
Open this guide in your assistant.
Follow BugViso
New guides and audit data as we publish them.
AI visibility tracker
Is your brand in AI answers?
See how often AI assistants mention you, cite your site and rank you against your competitors.
- ChatGPT
- Gemini
- Perplexity
- Claude
- AI Overviews
See where your site stands
Run a free BugViso audit for SEO, speed, accessibility and AI search readiness — with fixes you can ship today.