Your FAQ markup is valid, the Rich Results Test passes, and still no FAQ box appears in Google. Here's the short answer: for most sites, FAQ rich results were retired in 2023, so the box isn't a bug you can fix. A definition first: FAQ schema is structured data (usually JSON-LD) that labels question-and-answer pairs on a page so search engines can read them as a list, not as ordinary paragraphs.
Google's own documentation now says FAQ rich results are limited to well-known, authoritative government and health sites. If you run a normal business site, the absence is expected behaviour, not a technical fault. The useful work is deciding whether to keep the markup and how to earn visibility through other means.
The crawl-to-citation path explains why valid markup still shows nothing
Follow the path a page takes. A crawler fetches the URL. The indexer stores and parses the content. The retrieval system picks candidate passages. Then the answer engine or search feature decides whether to show a citation or a rich result.
FAQPage markup sits at the parsing stage. It helps a machine spot question-answer pairs. It doesn't force a display decision later. Google's rich results documentation separates “eligible” from “shown”: eligibility means the page meets the technical rules, while showing depends on the feature still existing and the query context.
For FAQ rich results, the feature itself was narrowed in 2023. Google's Search Central blog announced that FAQ rich results would only appear for “well-known, authoritative government and health websites.” That change happened at the display layer, not the parsing layer. Your markup can still be valid while the box never appears.
Five common beliefs are not the reason your FAQ box is missing
Most diagnosis time gets wasted on causes that don't apply. Here are five things people blame, and why each one is usually wrong.
- “My JSON-LD has a syntax error.” If the Rich Results Test reports no errors, syntax isn't the blocker. A valid page can still show nothing because the feature was retired.
- “Google hasn't recrawled the page yet.” Recrawling affects whether Google sees the markup, not whether the FAQ feature exists. Waiting won't bring back a retired feature.
- “I put the schema in the wrong place.” FAQPage can be embedded or standalone; Google's documentation accepts both. Placement matters for parsing, but not for a feature that's no longer offered to most sites.
- “My FAQ answers are too long.” Length can affect display, but the primary gate is site type. A short, clean answer on a commercial site still gets no box.
- “I need more FAQ items.” Adding questions doesn't change eligibility. The number of items isn't the trigger.
Put simply, these are hygiene issues. They're worth fixing, but none of them explains a missing feature that Google no longer shows to most publishers.
FAQ visibility needs two layers to pass, and most sites fail the first
The actual trigger has two layers. The first is feature availability: Google's FAQ rich result is limited to government and health authority sites, per Google's Search Central announcement in August 2023. The second is page-level eligibility: the markup must be valid, the content must be visible on the page, and the page must be indexable.
If you're not a government or health authority site, the first layer fails no matter how clean your schema is. That's the condition most people miss. The table below separates the layers so you can see where your site stands.
| Layer | What it controls | Typical check | If it fails |
|---|---|---|---|
| Feature availability | Whether Google still offers FAQ rich results for your site type | Google Search Central FAQ documentation and 2023 announcement | No FAQ box, regardless of markup quality |
| Markup validity | Whether Google can parse your FAQPage data | Rich Results Test and Schema Markup Validator | Fix errors before expecting any feature |
| Content visibility | Whether the Q&A text is visible to users on the page | Manual page check; Google requires visible content | Hidden FAQ text may be ignored |
| Indexability | Whether the page can appear in search at all | URL Inspection in Search Console | No rich result possible on a non-indexed page |
| Query context | Whether the search intent matches a FAQ display | Compare queries in Search Console Performance | Even eligible pages may not show for every query |
The table is a diagnostic order, not a promise. Even when every row passes, Google decides what to display per query. There's no public formula for that decision.
A missing page and a missing FAQ box are different problems
A missing page means the URL isn't indexed, so nothing can appear. A missing FAQ box means the page is indexed but the feature isn't displayed. Mixing them up sends you down the wrong fix.
Start with URL Inspection in Google Search Console. If the page is “URL is on Google,” the page is indexed and the FAQ box issue is a display-layer question. If it says “URL is not on Google,” fix indexing first: check robots.txt, noindex tags, and canonical signals.
Next, run the Rich Results Test on the live URL. This tells you whether Google can parse the FAQPage markup. It doesn't tell you whether the FAQ box will show. The tool reports eligibility, not display. Keep that distinction clear.
Then check the page itself. Google's structured data guidelines require the marked-up content to be visible to users. If your FAQ is hidden behind a tab that never renders, or collapsed in a way that hides the text from the rendered page, the markup may not match what users see.
A 2023-aligned drop in FAQ impressions is the retirement, not a penalty
If you saw FAQ impressions fall after 2023, the likely cause is the feature retirement, not a penalty. Search Console counts impressions when a result is shown. When Google stopped showing FAQ rich results for most sites, those impressions disappeared.
Check the Performance report with the “Search appearance” filter set to “FAQ rich results.” A drop that lines up with the 2023 change is expected. A drop that doesn't line up may point to a separate indexing or content issue.
Don't read the drop as a ranking loss. The page can still rank in normal results. What changed is the extra visual element, not the underlying position.
Keep FAQPage schema if it's accurate, drop it if it's not
There's no single answer, and Google doesn't penalise either choice. The decision depends on what you want the markup to do.
Keep it if you want consistent machine-readable Q&A structure for AI answer engines and internal tooling. FAQPage is a schema.org type, and schema.org vocabulary is read by many systems beyond Google's rich results. Keeping the markup costs little and can help other parsers.
Remove it if the markup is inaccurate, duplicates content awkwardly, or creates maintenance work with no clear owner. Inaccurate structured data is worse than none. Google's guidelines ask for markup that reflects the visible page.
A middle path works for many teams: keep the visible FAQ section and the FAQPage markup, but stop treating the SERP box as the success metric. Measure whether the page gets cited in AI answers or clicked from normal results instead.
Direct, visible answers earn visibility that markup alone can't
Shift effort from the retired box to the parts of the pipeline you can influence. The crawl-to-citation path rewards clear structure, visible answers, and pages that load and render reliably.
Write direct answers in the first sentence of each section. AI answer engines and featured snippets both pull from passages that answer a question without preamble. Keep question headings close to the wording people search for.
Make sure the page renders without JavaScript for the core text, or that server-side rendering delivers the Q&A content. Google's rendering documentation explains that content must be available after rendering; if your FAQ only appears after a script runs, test how it renders.
Track citations manually. Search your key questions in the AI tools your buyers use and note whether your page is quoted. That's a more useful signal now than an FAQ impression count.
Key Facts at a Glance
- FAQ rich results were retired for most sites in 2023; the absence is expected, not a bug.
- Google limits FAQ rich results to well-known government and health sites.
- Diagnose in order: indexability, markup validity, content visibility, then query context.
- A missing page and a missing FAQ box are different problems with different fixes.
- Keeping FAQPage schema is optional; accuracy matters more than presence.
- Direct, visible answers support AI citations even when the FAQ box is gone.
Why is my FAQ schema not showing in Google?
Most likely because Google retired FAQ rich results for most sites in 2023. The feature is now limited to well-known government and health sites. Valid markup does not override that limit.
Are FAQ rich results discontinued?
They are not fully discontinued, but they are restricted. Google's 2023 announcement limited them to well-known, authoritative government and health websites. For other sites, the display no longer appears.
Should I remove FAQPage schema from my site?
Keep it if the markup is accurate and you want machine-readable Q&A for other parsers. Remove it if it is inaccurate or unmaintained. Google does not penalise either choice.
Does FAQ schema still help SEO in 2026?
It can help machines parse your Q&A, but it no longer earns a FAQ box for most sites. Treat it as a structure aid, not a SERP feature. Visible, direct answers matter more for citations.
How do I test if my FAQ schema is valid?
Use the Rich Results Test on the live URL and the Schema Markup Validator for the raw JSON-LD. Both check parsing, not display. Pair them with URL Inspection to confirm the page is indexed.
