You added FAQ schema exactly the way every guide says to. It passes the Rich Results Test with a clean green checkmark. Google Search Console shows it as a valid item, no errors, no warnings. And yet, week after week, your search listing shows a plain blue link and a meta description — no expandable questions, no extra real estate, nothing.
If your first instinct was to re-check the JSON-LD syntax again, you're looking in the wrong place. In most cases in 2026, the markup was never the problem. What changed is how selective Google has become about actually displaying FAQ rich results at all — and that's a different fix than a syntax error.
Valid FAQ schema doesn't guarantee a rich result. Google restricted FAQ rich results in 2023 to a small set of authoritative sites for most queries, and even outside that restriction it can withhold the snippet for content quality, duplication, or visibility reasons unrelated to markup syntax. Passing validation confirms the schema is readable — it doesn't confirm Google has chosen to display it.
What's actually going on?
There are two entirely separate systems at work, and conflating them is why so much FAQ schema troubleshooting goes in circles.
- Validation checks syntax, not display. Tools like the Rich Results Test and Search Console's structured data report confirm your JSON-LD is well-formed and has the required fields — they say nothing about whether Google will render it in search.
- Google narrowed FAQ eligibility in 2023. Google significantly reduced how often the FAQ rich result appears, limiting it in most cases to a small set of well-known, authoritative government and health websites, regardless of how correctly other sites implement the markup.
- Quality and policy filters sit on top of eligibility. Even within eligible categories, Google can suppress a rich result if it judges the content thin, duplicated across pages, manipulative, or misaligned with what's visibly on the page.
- Display can change without any change on your end. Because eligibility is partly algorithmic and partly policy-driven, a rich result can disappear or reappear with no edits to your code at all.
In short: "not showing up" is very rarely a broken tag. It's almost always a mismatch between what your markup claims and what Google is currently willing to surface for a page like yours.
Why this matters
Chasing the wrong cause wastes time and can lead to changes that make things worse:
- You can "fix" schema that was never broken. Rewriting already-valid JSON-LD repeatedly doesn't change an eligibility restriction, so the rich result still won't appear no matter how many times the markup is edited.
- Hiding FAQ content to "clean up" the page can backfire. Some site owners visually hide FAQ text they think looks cluttered, but Google requires the marked-up content to be visible to users, so hiding it can get the schema disregarded entirely.
- Duplicating the same FAQ block sitewide draws scrutiny. Copy-pasting one generic FAQ across hundreds of pages reads as a scaled, low-value pattern rather than genuine per-page content.
- Knowing the real cause saves the content investment. Well-written FAQ content still helps users, still can inform AI-generated answers and overviews, and is worth keeping even without the rich snippet.
Step-by-step: diagnosing the real cause
- Confirm the markup is actually valid. Run the page through the Rich Results Test and Search Console's structured data report to rule out a genuine syntax or required-field error first.
- Check whether your site fits the current eligible category. Since 2023, FAQ rich results have largely been limited to well-known, authoritative sites in specific categories — confirm whether your site type is currently one of them.
- Verify the FAQ content is visible on the page itself. Every question and answer in the schema must appear as readable content to a visitor, not just inside the JSON-LD block.
- Check for duplication across your site. Search for the exact same FAQ questions repeated across many pages, which can read as a scaled or templated pattern rather than page-specific content.
- Review Search Console for manual actions or warnings. A structured data-related manual action or a spam policy warning will explain a suppression that a validator alone can't reveal.
- Preview how the listing currently renders. Use a SERP simulator to see exactly what the title, description, and any active rich elements look like today, so you have a clear baseline to compare against after changes.
- Give it time after any genuine fix. If an actual issue was corrected, allow for a recrawl and re-evaluation cycle before concluding the fix didn't work.
Common mistakes that suppress FAQ rich results
1. Assuming validation equals eligibility
A green checkmark on the Rich Results Test only means the schema is readable — it's not a promise that Google will choose to display it, especially post-2023 for non-authoritative sites.
2. Hiding the FAQ content visually
Collapsing or hiding questions and answers purely for design reasons, without them being genuinely accessible to a visitor, conflicts with the requirement that marked-up content be visible on the page.
3. Reusing one generic FAQ block across the whole site
The same five questions pasted onto hundreds of product or location pages looks like a scaled content pattern rather than answers specific to each page, and can be disregarded.
4. Marking up content that isn't really a Q&A
Wrapping arbitrary headings and paragraphs in FAQ schema, when they aren't phrased as a genuine question with a direct answer, misrepresents the page's content to search engines.
5. Ignoring Search Console's actual signals
Repeatedly editing the schema without checking Search Console for related warnings or manual actions means a real, stated reason for suppression can go unnoticed indefinitely.
Real-world examples
How this plays out across different kinds of sites:
The pattern across all four: the outcome tracks Google's eligibility rules and content quality signals far more closely than it tracks whether the JSON-LD is technically correct.
Possible causes compared
Where to look first, roughly in order of how often each one is the actual cause.
| Cause | How common | How to confirm | Fixable by you? |
|---|---|---|---|
| 2023 eligibility restriction | Very common | Site isn't in Google's small set of supported categories | No |
| Content hidden from users | Common | View page with JS disabled or check rendered HTML | Yes |
| Duplicated FAQ across pages | Common | Site search for repeated question text | Yes |
| Genuine markup error | Less common | Rich Results Test flags a specific field or syntax issue | Yes |
See exactly how your listing renders — free
The Rebrixe SERP Simulator shows your title, meta description, and URL exactly as they're likely to appear on both desktop and mobile search results, so you can confirm what's actually live before assuming a rich result issue is a schema problem.