You added FAQPage markup to your help pages, validated it, and waited. No FAQ box appeared. So you added more questions, tweaked the JSON, and waited again. Nothing. The reason is probably not a bug in your code. Google retired FAQ rich results for most sites in August 2023, so the box you're waiting for may never have been available to you. Stop debugging the markup and start checking the actual trigger conditions.
Google retired FAQ rich results for most sites in August 2023, so valid markup often shows nothing.
FAQPage is a schema.org type for a page that lists questions and answers. Schema.org defines it as a page where users can find answers to frequently asked questions. Rich results are the enhanced search listings Google builds from structured data. In August 2023, Google announced it would stop showing FAQ rich results for most sites and limit them to well-known, authoritative government and health websites. Google's Search Central blog post "Changes to How We Display FAQ Rich Results" is the source to check.
That change is why so many sites see the markup in Search Console's structured data report but no FAQ box in results. The markup is valid. The display feature is simply switched off for most publishers. Google's own developer documentation on FAQPage now states that FAQ rich results are only available to a limited set of authoritative government and health websites. If you're a B2B SaaS company or an e-commerce store, you're outside that set.
The retirement is not a penalty and not an error. Your page can still rank. You just won't get the expanded FAQ box. This is the single most common reason for "FAQ schema not showing" in 2025 and 2026 — and most older guides still recommend adding FAQ schema to earn rich snippets, which is now outdated advice.
Five common misdiagnoses waste your time before you check the real cause.
Diagnosis by elimination saves time. Before you touch the markup, rule out these five common misdiagnoses. Each one is a real thing people check, and each one is usually a dead end when the actual cause is the 2023 retirement.
Myth 1: "My JSON-LD is malformed." A syntax error is a real problem, but it produces a specific error in the Rich Results Test or Search Console. If your report says "Valid items detected" with no errors, malformed JSON is not your cause. Valid markup that doesn't display is the retirement, not a syntax bug.
Myth 2: "The questions need to be visible on the page." Google's FAQPage documentation does require the question and answer content to be visible to users on the page. That rule still matters for validity. But meeting it does not bring the rich result back. Plenty of pages with ideally visible FAQs get no box.
Myth 3: "I need more questions, or longer answers." There is no public minimum or maximum count in Google's current FAQPage documentation. Adding a tenth question won't flip a switch that the 2023 change turned off. More markup does not restore a retired feature.
Myth 4: "My site isn't authoritative enough yet." Authority matters for many things, but the FAQ restriction is categorical, not a ranking threshold. Google limits FAQ rich results to government and health sites by category, not by a score you can raise with more backlinks.
Myth 5: "Search Console shows a drop in impressions, so I've been penalized." Impressions can fall for many reasons, including seasonality, algorithm updates, or a change in how results are displayed. The FAQ retirement itself can reduce the visual footprint of a result, which can affect click-through. That is not a manual action. Check the Manual Actions report before assuming a penalty.
Four trigger conditions decide whether any FAQ-style display can appear.
"Trigger condition" here means the set of requirements a page must meet before a search engine will show an enhanced result. For FAQ, the first trigger is site category: government or health authority. If you don't meet that, no amount of markup will produce the box. Google's documentation is explicit that the feature is limited.
The second trigger is technical validity. Even for eligible sites, the markup must pass the Rich Results Test and the page must be indexable. Google's Search Essentials documentation covers the indexing requirements: the page must not be blocked by robots.txt or a noindex tag, and it must return a 200 status. A valid FAQPage on a noindexed page will never display.
The third trigger is content visibility. The Q&A text in the markup must match visible text on the page. Google's structured data general guidelines state that markup must represent the visible content. Hiding the FAQ in an accordion is generally fine as long as the content is in the HTML and accessible to users, but cloaking — showing different content to crawlers — violates the guidelines.
The fourth trigger, for eligible sites, is that the page must actually be selected for the rich result at query time. Google does not ensure display even when all requirements are met. The documentation uses "may" language throughout. So the honest answer is: meeting the conditions makes display possible, not certain.
| Check | What it confirms | What it does not confirm |
|---|---|---|
| Rich Results Test | Markup is syntactically valid and eligible for the FAQ feature | That Google will display a rich result for your site |
| Search Console Enhancements report | Pages with valid or invalid FAQ markup | That the display feature is available to your site category |
| URL Inspection tool | Whether the page is indexed and crawlable | Whether a rich result will appear for a given query |
| Schema.org validator | The markup matches the schema.org vocabulary | Anything about Google's display rules |
Google's Rich Results Test confirms validity, not that the feature is available to you.
Use Google's Rich Results Test at search.google.com/test/rich-results. Paste the URL or the code. It will tell you whether FAQPage is detected and whether there are errors. This tool checks validity against Google's feature requirements. It does not tell you whether the feature is available to your site category — that's a policy question, not a technical one.
Search Console's Enhancements section reports FAQ markup across your site. If you see "Valid items" with no errors, your markup is fine. If you see errors like "Missing field 'acceptedAnswer'", fix those. The schema.org validator at validator.schema.org is useful for checking the vocabulary itself, but it does not know Google's display rules.
A common confusion: passing the Rich Results Test feels like a green light. It isn't. The test confirms eligibility for the feature, not availability of the feature. For most sites in 2026, the FAQ feature is simply not available, so a passing test is expected and does not predict a rich result.
Keep valid FAQPage markup; fix invalid markup instead of deleting it.
Keep it. Removing valid FAQPage markup does not improve anything, and the markup still carries value outside Google's rich results. Other search engines and AI answer engines may read structured data to understand Q&A content. Schema.org markup is a machine-readable signal, and the vocabulary is maintained independently of any one search engine's display decisions.
There is one case for removal: if the markup is invalid or mismatched with visible content, it can trigger a structured data manual action. Google's Structured Data General Guidelines describe the spam policies for markup that misrepresents the page. Fix invalid markup; don't remove valid markup just because the rich result is gone.
For B2B sites, the practical value of FAQPage in 2026 is entity clarity and AI retrieval. When an AI answer engine retrieves your page, clean Q&A structure can make the content easier to extract and cite. That's a different benefit from a rich snippet, and it doesn't depend on Google's display policy. There is no public benchmark for how much this helps, so treat it as a reasonable structural choice, not an assured win.
Shift effort to indexing, content quality, and structured data types that still display.
If the FAQ box is gone, shift effort to things that still move visibility. First, make sure the page is indexed and crawlable — check URL Inspection and the Page Indexing report. A page that isn't indexed can't rank, regardless of markup.
Second, invest in content that answers real queries directly. Google's Helpful Content guidance and the Search Quality Rater Guidelines emphasize people-first content. A clear, well-structured FAQ section on the page still helps users and can help search engines understand the page, even without a rich result.
Third, use other structured data types that still produce rich results where eligible: Article, Product, BreadcrumbList, Organization. Check Google's Search Gallery for the current list of features and their requirements. FAQPage is in the gallery but marked as limited. Build the types that are actually available to your site.
Fourth, for AI answer engines, keep Q&A content in clean HTML with headings and short paragraphs. There is no official schema requirement from OpenAI, Anthropic, or Google's AI features for citation, but well-structured pages are easier to parse.
Key Facts at a Glance
- Google retired FAQ rich results for most sites in August 2023; only government and health sites remain eligible, per Google Search Central.
- Valid FAQPage markup does not ensure a rich result; Google's documentation uses "may" language for display.
- The Rich Results Test confirms markup validity, not feature availability for your site category.
- Removing valid FAQPage markup is not recommended; invalid markup should be fixed, not deleted.
- FAQPage still helps machine readability for AI and other engines, though no public benchmark quantifies the effect.
Frequently Asked Questions
Why is my FAQ schema not showing in Google?
Most likely because Google retired FAQ rich results for most sites in August 2023. Only government and health authority sites remain eligible. Your markup can be ideally valid and still not display a box.
Are FAQ rich results discontinued permanently?
Google's 2023 announcement limited FAQ rich results to a small set of authoritative government and health websites. Google has not announced a reversal. Check Google Search Central's documentation for the current in-force policy.
Does FAQ schema still help SEO in 2025?
It can help with machine readability and entity clarity, and other engines or AI systems may use it. It no longer earns a rich snippet for most sites. The SEO benefit is indirect, not a display feature.
Should I remove FAQ schema from my site?
No, if the markup is valid and matches visible content. Fix invalid markup instead of deleting it. Removing valid markup does not improve visibility and loses any machine-readability benefit.
How do I test if my FAQ schema is valid?
Use Google's Rich Results Test and the Search Console Enhancements report. Both confirm validity. Neither confirms that Google will display a rich result, because that depends on site category and Google's display policy.
Data sources: the standards and technical parameters referenced in this article are based on the corresponding national/industry standards and the manufacturer's factory QC records; the current in-force version prevails.
