What FAQ Schema Does and Does Not Do

FAQ schema is structured data that labels a list of questions and answers on a page. It does not give you expandable FAQ results in Google any more: as of May 7, 2026, Google no longer shows them for any site, as its documentation changelog records. Google has not presented it as a ranking factor, and it does not guarantee an AI tool will cite you. What it still does is describe your FAQ content to machines in a standard format.

Last checked against Google's changelog on October 7, 2026.

What happened to FAQ rich results

FAQ rich results were the expandable question-and-answer dropdowns that appeared under some search listings. Google cut them back and then ended them.

The FAQPage type itself still exists in the Schema.org vocabulary. What ended is the Google search feature that used to display it.

What FAQ schema does not do

It does not give you a bigger search result

This was the main reason people added it, and it is gone. Adding the markup today will not produce dropdowns in Google.

It does not improve your rankings

Google has not presented FAQ markup as a ranking factor, and nothing about the May 2026 change adds one.

It does not guarantee AI citations

No AI tool provider has confirmed that FAQPage markup gets you cited. Google's own guide to its generative AI search features says structured data is not required for them and that no special schema.org markup is needed. It also treats optimizing for AI search as SEO, which is why our explainer on SEO, AEO and GEO keeps the three terms side by side. Whether an answer engine uses your content depends on things no one outside can fully see.

It does not fix weak content

Markup describes what is on the page. If the answers are thin or padded, the markup just describes thin or padded answers.

Do not mark up questions that are not on the page

Marking up questions that are not on the page, or stuffing a page with FAQs to look relevant, can create quality problems and goes against Google's structured data guidelines, which require markup to reflect the visible page.

What FAQ schema still does

It describes your content in a standard format

The markup says this page contains these questions and these answers. Some commentators say Google still reads FAQ markup to understand pages even though it no longer shows the result. We found no statement to that effect in Google's changelog or its AI guide, so treat it as unconfirmed. Other search engines and tools that parse structured data may use it in their own ways, but you should not count on it.

Google has not asked you to remove it

Google's changelog entries announce the end of the rich result. They do not tell site owners to take existing FAQ markup out. If your markup is accurate and matches the visible page, leaving it in place costs nothing.

Should you keep it, add it, or remove it?

In our scan of 97 large sites, only 2 of the 67 home pages we could read (3%) carried FAQPage markup. That is a floor, not a usage rate, because FAQ markup usually sits on inner pages we did not scan. Big brands are not putting it on the home page by default, and you do not need to either.

Keep it if the page has a real FAQ section and the markup matches it. It costs nothing to leave.

Add it only if you want a machine-readable description of a real FAQ section and you are willing to keep it in step with the page. Do not add it hoping for rich results. Our how-to guide on adding FAQPage schema has a copy-paste template.

Remove it if the questions are not really on the page, if the FAQ is not the point of the page, or if you added markup everywhere only for rich results and now have to maintain it.

Check whether a page has FAQ markup

1. Open the page and view its source (right-click and choose View Page Source, or press Ctrl+U on Windows or Cmd+Option+U on Mac).
2. Search the source for FAQPage. Most sites use JSON-LD, which looks like this (shortened):

<script type="application/ld+json">
{"@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [ ... ]}
</script>

Older setups use microdata, where you will see itemtype="https://schema.org/FAQPage" on the page elements. 3. If you find nothing but the page leans on JavaScript, the markup may be added after the page loads. Open your browser's developer tools, look at the Elements panel (the rendered page) and search there. 4. To check that the markup is valid, paste the URL or code into the Schema Markup Validator. It checks the markup against the Schema.org vocabulary. It does not tell you whether Google would show anything, because Google no longer shows FAQ results.

What a clean removal looks like

1. Find where the markup comes from. SEO plugins and CMS themes often add FAQPage markup automatically from a block or a setting. If you delete the code by hand and leave the setting on, it comes back.
2. Remove the markup, not the FAQ. Delete the JSON-LD block or the microdata attributes, or switch off the plugin option. Leave the visible questions and answers on the page.
3. Do not edit halfway. If you change the visible FAQ text, change or remove the markup in the same edit, so the two never disagree.
4. Check again. Clear any page cache, reload, and search the page source for FAQPage. It should be gone while the FAQ section is still on the page.
5. Update your reporting. Take FAQ rich result tracking out of dashboards and exports.

What to do instead

The reason to write an FAQ is unchanged: people ask these questions, and a clear answer helps them. Put your time into the content.

• Answer the real questions your customers ask, in plain words.
• Start each answer with the direct response, then add detail. Our guide to writing answers AI tools can quote shows how.
• Keep every answer true and current.

Check your own pages

The free GEO checker can tell you whether a page carries FAQ markup. Treat that as an extra signal, not as a Google requirement.

Sources

• Google Search Central, Latest documentation updates: entries for May 8, 2026 (FAQ deprecation notice) and June 15, 2026 (FAQ documentation removed).
• Google Search Central, Optimizing your website for generative AI features, section "What you don't need to do."
• Google Search Central blog, HowTo and FAQ changes (August 2023).
• Schema.org, FAQPage.

Related posts

• Free tool: GEO checker
• The basics: Structured Data for Beginners: What to Add First
• Add it properly: How to add FAQPage schema, with copy-paste JSON-LD
• Write for answers: How to write answers AI tools can quote
• The wider picture: SEO, AEO and GEO: what is the difference
• The data: AI-readiness scan of 97 large sites