Search for FAQPage schema 2026 and you will find two opposite pieces of advice.
One says FAQ schema is dead because Google no longer shows FAQ rich results.
The other says you should keep adding it because AI systems need structured answers.
Neither is precise enough.
Google no longer shows the FAQ rich-result feature in Search. That is confirmed. But FAQPage still exists as a Schema.org type, and removing a Google rich result does not make the vocabulary itself invalid. Google for Developers
What has not been established is that FAQPage markup gives you a special advantage in AI Overviews, AI Mode, ChatGPT or other generative systems. Google explicitly says there is no special schema markup required for its generative AI search features. Google for Developers
So the practical answer is:
Keep writing useful FAQs. Use FAQPage markup where it accurately describes the page and is easy to maintain. Do not treat it as a shortcut to AI visibility.
That distinction matters.
Table of Contents
- What happened to FAQ rich results?
- Did Google remove FAQPage schema?
- Rich results and machine comprehension are different things
- Does FAQPage schema help AI search?
- Why FAQ content itself still matters
- How to write FAQ answers that stand alone
- Does FAQ schema help People Also Ask?
- When should you still add FAQPage markup?
- When is it not worth the effort?
- How to validate FAQPage markup
- Frequently Asked Questions
What happened to FAQ rich results?
FAQPage markup once had a very obvious Google benefit.
Google introduced support for FAQ structured data in 2019. Correctly marked-up pages could become eligible for an expanded search result displaying questions and answers directly underneath the normal listing. Google for Developers
Then Google changed course.
August 2023
Google announced that FAQ rich results would only be shown regularly for well-known, authoritative government and health websites.
For ordinary commercial websites, appearances became much less common.
Importantly, Google said at the time that website owners could remove unused FAQ structured data but did not need to proactively delete it. Unused markup would not cause problems for Search. Google for Developers
May 2026
The position changed again.
Google announced that the FAQ rich-result feature would stop appearing in Google Search from 7 May 2026. Google for Developers
June 2026
Google then removed the FAQ rich-result documentation because the feature was no longer displayed in Search. Google for Developers
So if somebody tells you that adding FAQPage schema today will give an ordinary UK SME an expanded Google FAQ listing, that advice is out of date.
Did Google remove FAQPage schema?
No.
This is where the wording matters.
Google removed its FAQ rich-result feature.
Schema.org did not remove the FAQPage type.
As of 2026, Schema.org still defines FAQPage as a WebPage containing one or more frequently asked questions. Schema.org
Those are separate systems.
Schema.org provides a vocabulary for describing things on the web.
Google decides which pieces of that vocabulary it uses for specific Search features.
Google’s own structured-data documentation makes this distinction clear: Schema.org includes many types and properties beyond the structured-data features Google Search supports. Google for Developers
So:
FAQPage is not dead as a Schema.org type.
But:
FAQPage no longer powers a dedicated Google FAQ rich result.
That is the useful distinction.
For the broader priority list, see our guide to which schema types actually matter for AI search
Rich results and machine comprehension are different things
A rich result is a search interface feature.
Structured data is machine-readable metadata describing page content.
Those things overlap, but they are not identical.
For example, Organization schema can help identify information about a company. Breadcrumb markup can describe the hierarchy of a page. Article markup can describe authorship and publication information.
FAQPage does something similar conceptually.
It can explicitly label:
This is a question.
This is the accepted answer.
That is cleaner semantically than a machine having to infer the relationship from arbitrary HTML alone.
But that does not automatically mean every search engine or AI assistant uses that information.
Schema only helps a system if the system chooses to consume and use it.
That leads to the more important question.
Does FAQPage schema help AI search?
There is currently no good basis for saying:
Add FAQPage schema and AI systems will cite or recommend you more often.
Google is particularly explicit on this point.
Its current guidance says structured data is not required for its generative AI search features, and there is no special Schema.org markup you need to add for AI Overviews or AI Mode. Google actually warns site owners against overfocusing on structured data as an AI optimisation tactic. Google for Developers
That does not make structured data useless.
Google still recommends ensuring that structured data accurately matches the visible text on the page as part of normal SEO practice. Google for Developers
The sensible position is therefore:
FAQPage markup can accurately describe FAQ content, but there is no published evidence that the markup itself gives that content a special AI visibility boost.
That is very different from saying FAQ content has no value.
Why FAQ content itself still matters
This is where some businesses drew the wrong conclusion.
Google removing an FAQ search feature did not make customer questions less useful.
A good FAQ section can still do several jobs at once.
It can answer a commercial objection before somebody contacts sales.
It can explain terminology that would otherwise interrupt the main service copy.
It can address qualification questions around pricing, geography, implementation, accreditation or process.
It can also give search systems clear textual information to work with.
Google’s current AI guidance specifically advises website owners to make important information available in textual form. It does not require a special AI schema layer around that text. Google for Developers
That is the distinction worth keeping.
Visible FAQ content can be useful.
FAQPage markup is optional metadata around it.
For the wider approach to structuring answers around real buyer questions, see our guide to Answer Engine Optimisation.
How to write FAQ answers that stand alone
If you are adding FAQs for buyers rather than simply filling space at the bottom of a page, write each answer so it still makes sense when separated from the surrounding copy.
A weak answer looks like this:
Yes, we do.
That answer depends entirely on the question appearing beside it.
A stronger answer would be:
Yes. We provide planned and reactive commercial maintenance services across London and the South East.
The second version preserves context.
That matters for users scanning the page, traditional search snippets and any system extracting a passage without the rest of the section.
A practical FAQ should usually have one clear question, give the direct answer early, include enough context to make sense independently and avoid adding claims that the main page cannot support.
There is no published Google rule saying an FAQ answer must contain a particular number of words.
Write enough to answer the question properly.
Not enough to hit an arbitrary SEO length.
Does FAQ schema help People Also Ask?
There is no documented People Also Ask schema.
Google describes People Also Ask as a related questions group. When somebody expands one of those questions, Google can display a featured snippet. Google for Developers
Google’s current supported structured-data gallery does not list FAQPage as a method for controlling People Also Ask appearances. Google for Developers
So do not tell a client:
Add FAQ schema and you will appear in People Also Ask.
There is no basis for that guarantee.
What does make sense is writing genuinely useful, self-contained answers to questions searchers are asking.
That can create useful content for normal search independently of whether FAQPage markup is present.
For more on that search feature:
Why featured snippets still matter in 2026
When should you still add FAQPage markup?
For most SMEs, I would treat it as conditional rather than essential.
If your site already uses an SEO plugin that correctly generates FAQPage JSON-LD from genuine visible FAQs, leaving that markup in place is reasonable.
If you have another system, search engine or downstream tool that consumes Schema.org data, keeping correctly implemented markup may also make sense.
And if your technical approach is to describe page entities consistently using Schema.org, an FAQPage type can still be a valid semantic description of genuine FAQ content.
The test is simple:
Does this markup accurately describe content that actually exists on this page?
If yes, there is nothing inherently wrong with using it.
Just be clear about why.
When is it not worth the effort?
If a developer needs several hours to create a bespoke FAQPage implementation solely because somebody promised an AI ranking boost, I would put that work lower down the list.
For many SMEs, that time would be better spent fixing more fundamental problems such as vague service pages, inconsistent company details, poor internal linking, missing evidence, technically inaccessible content or weak buyer-focused answers.
The same applies if your plugin already creates multiple competing schema graphs and another FAQ implementation would only add duplication.
FAQ markup should describe a useful content structure.
It should not become the project.
How to validate FAQPage markup
There is another 2026 change to be aware of.
Because Google no longer supports the FAQ rich-result feature, FAQPage is no longer something you should treat as a current Google rich-result implementation project.
For the underlying Schema.org vocabulary, use the Schema.org Validator to inspect whether the markup is syntactically valid and how its entities are being interpreted.
Schema.org continues to define FAQPage, including the relationship between the page and its FAQ content. Schema.org
The bigger validation check, however, is simpler:
Does the structured data agree with the visible page?
Do not mark up questions or answers users cannot actually find in the content.
And do not use structured data to make claims that the page itself does not support.
Frequently Asked Questions About FAQPage Schema in 2026
Did Google remove FAQ rich results?
Yes.
Google first significantly reduced FAQ rich-result visibility in August 2023. It then stopped showing the feature in Google Search from 7 May 2026 and removed the documentation the following month.
Google: FAQ rich result changes That does not mean Schema.org removed the FAQPage type.
It still exists.
Does FAQPage schema help People Also Ask?
There is no documented People Also Ask schema.
Google describes People Also Ask as a related questions experience that can display featured snippets when a question is expanded.
FAQPage markup does not guarantee inclusion.
Google: Search visual elementsHow many FAQs should I put on a page?
Google does not publish an ideal FAQ count.
Use the number required to answer genuine questions relevant to that page. Three useful questions are better than fifteen repetitive ones written to manufacture keywords.
Keep the page focused on its main commercial or informational purpose.
Can I mark up existing FAQ content?
Yes, if the markup accurately describes genuine FAQ content on the page.
The structured data should reflect what the user can actually access rather than adding questions and answers that exist only inside the markup.
Does FAQPage schema improve AI visibility?
There is no published evidence that adding FAQPage schema creates a special AI visibility advantage.
For Google specifically, the company says no special Schema.org markup is required for AI Overviews or AI Mode.
Google: AI search optimisation guidanceShould I remove FAQPage schema from my website?
Not simply because Google removed the FAQ rich result.
If the markup is accurate, generated cleanly and costs nothing to maintain, there is little reason to panic and delete it.
But it should now be treated as lower priority for most SMEs than schema types with clearer current uses.
See which schema types actually matter for AI search for the wider priority list.
FAQPage schema is now a supporting detail, not the strategy
Google removing FAQ rich results changed the commercial value of FAQPage markup.
It did not make customer questions irrelevant.
That distinction is the whole answer.
In 2026:
Write the FAQ because the question matters.
Make the answer clear enough to stand alone.
Keep the content visible and accurate.
Add FAQPage markup if it genuinely describes the page and fits your technical setup.
But do not add it because somebody promised an AI citation, a People Also Ask placement or the return of Google’s old FAQ rich result.
Those claims go further than the evidence.
For most SMEs, useful answer content is the asset.
The schema is the label attached to it.
Get your free AI visibility audit
For broader AEO guidance:
https://lobodigital.co.uk/services/geo-aeo/answer-engine-optimisation/
For the schema priority guide:
https://lobodigital.co.uk/schema-types-that-matter-ai-search/
For related traditional search visibility: /
Google’s 2023 announcement documents the initial restriction of FAQ rich results. Google Search Central: Changes to FAQ and HowTo rich results
Google’s 2026 documentation changelog confirms that FAQ rich results stopped appearing from 7 May 2026 and that the documentation was later removed. Google Search Central: 2026 documentation updates
Schema.org still maintains FAQPage as a valid vocabulary type. Schema.org: FAQPage
Google’s current AI guidance says no special structured data is required for AI Overviews or AI Mode. Google Search Central: Generative AI optimisation guidance
