Every published page on this site carries FAQPage schema, and Google has shown a FAQ rich result for none of them. Search Console’s own appearance report is the source, and it lists two appearance types across ninety days.
That isn’t a markup fault. It’s what happens now, and it’s worth knowing before anybody spends another sprint adding the same schema.
The markup still earns something. It stopped earning the thing most people add it for.
What the Appearance Report Shows
Search Console reports which special result types a site appeared in. Ours returns two rows for the last ninety days.
| Appearance type | Impressions |
|---|---|
| Translated result | 15 |
| Product snippets | 7 |
| FAQ rich result | None recorded |
270 published pages carry valid FAQPage markup and the report has no FAQ row at all. Not a low number. No row.
Why the Row Is Missing
It’s missing because Google no longer shows FAQ rich results for anyone. The feature was narrowed to well-known government and health sites in 2023, and in May 2026 Google stopped displaying it in Search altogether.
The reporting went with it. In June 2026 Google retired the FAQ rich result report, the FAQ search appearance filter and FAQ support in the Rich Results Test.
The markup itself isn’t invalid, and it still parses. That’s why teams keep shipping schema that no longer buys the result they wanted.
The retirement landed before most audits caught up
Plenty of SEO checklists still list FAQ schema under ways to win more space in the results page. That advice describes a version of Google Search that no longer exists.
What the Markup Still Does
Three things survive, and only one of them was ever about Google’s display layer.
- Machine-readable structure. A question paired with its answer is easy for a retrieval system to lift.
- Plainer answers. Writing a real FAQ block commits you to short, direct answers.
- A readable data graph. The entity relationships around it stay legible, which is the same argument set out in entity SEO.
The first is the one that matters commercially now. Our own work on how AI crawlers pick sources covers what these systems read on a page, and clean question-and-answer pairs sit near the top of that list.
What This Changes About Adding It
You should still add it, and you should stop expecting a visual return from it.
Add it where the questions are real
A block of five invented questions nobody asks is padding with markup wrapped around it. Pull the questions from support tickets, sales calls or the question-form queries in your own Search Console.
Stop treating it as a SERP tactic
If a proposal justifies FAQ schema by the space it wins in results, the justification is out of date. The honest case for it today is machine readability, and that case is strong enough on its own.
Judge it by citation, not by appearance
The measurable question is whether AI answers quote the passage, not whether Google draws an accordion. That distinction is set out in AI citation ranking factors.
How to Check Your Own Site in Two Minutes
You can run the same check we did in Search Console, and the answer is now the same for every site.
- The Search Appearance filter. Open Performance and add it to list every special result type your site still earns.
- The FAQ row. It’s gone, because Google dropped FAQ from that filter in June 2026.
- The Schema Markup Validator. It still confirms the markup parses, which is a different claim from being displayed.
Every site will find what we found. That’s the expected outcome rather than a sign something is broken.
What This Does Not Prove
One property, one ninety-day window. On its own that would only settle what this site earns, but Google’s retirement of the feature makes the result general.
It doesn’t cover other engines. Google’s documentation doesn’t ask anyone to remove the markup, and other search and answer engines may still read it.
It also measures the wrong half of the argument on purpose. Search Console reports what Google displayed, and says nothing about whether an AI answer quoted the passage, which is the return the markup is now defended on.
What would settle that half
Tracking whether your answers appear inside AI responses, which is a different instrument entirely and reads the answer rather than the results page.
Frequently Asked Questions
Does FAQ schema still work in 2026
It works as machine-readable structure, and it no longer produces FAQ rich results for any site. Google stopped showing the feature in May 2026, after restricting it to government and health sources in 2023.
Should I remove FAQPage markup
No. It costs nothing to keep, it stays readable to retrieval systems, and removing it gives back the one benefit that still applies.
Why does my markup validate but show nothing
It happens because validity and display are different questions. A validator checks that the markup parses correctly, and Google has stopped displaying the FAQ type at all.
Do AI answer engines read FAQ schema
They read the page, and structured question-and-answer pairs are among the easiest passages to lift. Treat the markup as help for that rather than as a route to a search feature.
What replaced FAQ rich results
Nothing that you can add markup for. The space went to AI overviews and other generated summaries, which draw on the page rather than on a declared block.
Check the Appearance Report Before the Next Sprint
Two minutes in Search Console settles what a quarter of schema work is buying. The markup still deserves a place on the page, not on the list of things that win results-page real estate.