FAQ schema deprecated? Google ended the rich result, not the markup

Is FAQ schema deprecated? For Google's rich results, yes: the FAQ rich result stopped appearing in Google Search on May 7, 2026, and Google has since deleted the documentation for it. The FAQPage type itself is not deprecated, though. It is still a live schema.org type, and tools such as the seogeoaeo.ai FAQ Schema Builder still produce it, now with a note about the Google change.

That split between "the search feature is gone" and "the markup is still valid" is where most of the confusion sits, so here is the timeline and what it means for a site that already ships FAQ markup.

The timeline

The 2023 change is in Google's Search Central blog post on HowTo and FAQ rich results. The two 2026 entries are in the Search Central documentation updates log. If you try the old FAQPage documentation URL today, it redirects to that log.

For most sites the 2023 step was the real cutoff. If you were not a government or health publisher, the expandable questions under your result had already stopped showing regularly. The 2026 steps closed the door for everyone else and removed the reference docs.

What "deprecated" does not mean

It does not mean your FAQ markup is now an error. In the 2023 post, Google wrote that structured data it does not use causes no problems for Search and simply has no visible effect, and that there was no need to remove FAQ markup proactively. Nothing in the 2026 entries says otherwise.

It also does not mean the type is gone from the vocabulary. Schema.org still defines FAQPage as a web page that presents one or more frequently asked questions, with each Question pointing to an accepted Answer. Validators still parse it.

It is not a ranking signal story either. Google said the 2023 change should not be considered a ranking change.

So should you keep it

Keep it if the page has real questions and answers that readers can see, and if the markup is accurate. It costs nothing to leave in place and it still describes the page to systems that read structured data.

Drop it, or skip adding it, if it exists only to chase the old rich result, if the questions are not visible on the page, or if it duplicates content from other pages. Google's general guidelines say not to mark up content readers cannot see, and that has not changed.

Do not add it expecting AI Overviews to pick you up. Google's page on AI features says there are no extra requirements for AI Overviews or AI Mode and no special schema.org markup to add.

If you still want the markup

The cleanest way is to generate it from the exact questions on the page. The seogeoaeo.ai FAQ Schema Builder takes one question and answer per line, returns FAQPage JSON-LD with a preview against validator rules, and costs 3 credits a run. It fetches nothing, and its output carries a plain note that Google no longer shows the rich result.

If you would rather not spend credits on a short list, writing the block by hand and checking it on validator.schema.org works fine.

The short version for the timeline crowd: the feature died, the vocabulary did not. Treat FAQPage as accurate page description, not as a search trick, and seogeoaeo.ai is a sensible place to build it.