If your site still carries FAQPage markup, May 7, 2026 was the date Google's treatment of it ended. The practical question is what to do with the markup you already have. Should you strip it out, leave it in place, or replace it with something else? The answer depends on the page, and it depends on which claims about "schema for AI answers" actually have evidence behind them. This article sets out the dated sequence, then sorts the cases, then looks at what is proven and unproven for AI-generated answers. It closes with how to read your own data.
One note on sourcing. The dates below come from Google's Search Central documentation changelog. Wording and scope of individual entries can be revised, so treat the changelog and the structured data documentation as the authority and check them before you act.
- The timeline: from restriction to retirement
- What the markup is, and what it was never
- Keep, remove or replace: a case-by-case table
- What is proven and what is not for AI answers
- Visible Q&A blocks without template headings
- Which Q&A types Google still supports
- What happened on the network pages
- A practical plan for existing markup
- What not to conclude
- FAQ
- The short version
The timeline: from restriction to retirement
The change did not arrive in one step. It played out over almost three years, and the order matters because it explains why many sites saw nothing happen on the day itself.
August 2023: the restriction. Google announced that FAQ rich results would be shown only for well-known, authoritative government and health websites. For nearly every other site, the expandable question-and-answer snippet under a search listing stopped appearing. The markup remained valid and Search Console kept reporting on it. What disappeared for most publishers was the visible reward. If you added FAQPage markup after that date purely to win extra space on the results page, the feature was already unavailable to you.
May 7, 2026: the end. The FAQ rich result as a Search feature was brought to an end. From this point there is no search appearance that FAQPage markup unlocks for any site, including the government and health sites that had kept it. The restriction in 2023 narrowed the audience. The 2026 change closed the feature.
June 2026 and August 2026: removals. The changelog records further removals in these two months. These are the follow-through steps that usually come after a feature is retired: documentation, reports and tooling that referred to it are taken down in stages. Read each entry for its exact scope rather than relying on a summary, including this one. The practical point is that the surrounding support for FAQ rich results was withdrawn in steps, so something you used to check in June may look different by now.
Two things follow from this sequence. First, the effect on traffic is easy to over-attribute. For most sites the visible snippet was already gone in 2023, so a drop after May 2026 needs a different explanation, and it is worth checking before you blame the markup. Second, "no longer produces a rich result" is not the same as "now harmful". Google has not said that FAQPage markup becomes an error or a penalty. It is simply no longer rewarded.
What the markup is, and what it was never
FAQPage is a schema.org type that describes a page containing a list of questions with a single, authoritative answer to each, written by the site itself. It is not meant for pages where users submit competing answers, and it is not meant for a single question. Google's guidance has long required that the marked-up content be visible on the page. Markup that describes text a visitor cannot see has always been against the structured data guidelines.
That visibility rule is the key to the rest of this article. The questions and answers are the content. The JSON-LD was only a machine-readable description of that content. When the description stops earning anything, the content can stay, and often should.
Keep, remove or replace: a case-by-case table
The table below sorts common situations. It is a decision aid based on the documented status of the feature, not a rule that Google has published for each case.
| Case | Recommendation | Reason |
|---|---|---|
| Page has a visible FAQ section written for readers, with FAQPage markup | Keep the content. Markup is optional; remove it if you want a lean template. | The content still serves visitors. The markup no longer produces a rich result. Leaving valid, accurate markup in place is low risk. |
| Page has FAQPage markup but the questions are not visible (hidden, injected only in JSON-LD) | Remove the markup, or make the content visible. | Markup describing content users cannot see has never matched the guidelines. There is no benefit left to justify the risk. |
| Template adds the same generic FAQ block to hundreds of pages | Remove the template block, or replace it with page-specific questions. | Repeated filler adds length without helping readers. Without a rich result as an incentive, there is little reason to keep it. |
| Support or help article where users post questions and others answer | Replace with QAPage or discussion forum markup where it fits. | These types describe user-generated Q&A, which is a different structure from an authored FAQ. See the section below. |
| Single question with one or more answers on a page, such as a community thread | Use QAPage if it genuinely fits. | FAQPage is for a list of authored answers, not one open question. |
| Product or service page with a short list of buyer questions | Keep visible Q&A. Drop or keep the markup, your choice. | The questions help the reader decide. Markup is not needed for them to do that. |
| Step-by-step instructions disguised as FAQs | Rewrite as normal headed sections. | The content is a procedure, not a set of independent questions. |
| Government or health site that kept the rich result until May 2026 | Plan for the end of the feature. Keep the visible content. | The exception was removed along with the feature. |
| Plugin or theme that auto-generates FAQPage on every post | Review the setting and the output. | Auto-generated markup often describes content that is thin, duplicated or not visible. |
The pattern is consistent. The reader-facing content survives almost every case. The markup is what you can decide freely about. Where there is a real reason to remove it (hidden content, duplicated templates, heavy maintenance cost), do so. Where it is accurate and harmless, there is no urgency.
What is proven and what is not for AI answers
The most common reason people give for keeping FAQPage after May 2026 is that "AI systems read it". That claim deserves a close look, because the available evidence is thin and some of it points the other way.
What Google says
Google's documentation on AI features in Search, which covers AI Overviews and AI Mode, says in substance that no special optimization is required to appear in these features. The same documentation says that the usual SEO fundamentals apply, and that structured data should match the visible content of the page. Read the current text of that page for the exact wording and quote it from the source, since the document is updated from time to time. The point to take away is the absence: the document does not list FAQ markup, or any specific schema type, as a requirement or a lever for being cited in AI features.
That is not the same as saying schema is useless. Structured data can help systems understand a page. But Google has not claimed that FAQPage in particular raises your chance of being included in an AI answer.
What Microsoft said
Microsoft's position is somewhat different. At SMX Munich in 2025, a Bing representative said that schema markup helps Microsoft's language models understand web content, in the context of Copilot. This is a statement from a search engine about its own system. It deserves to be taken seriously, and it also has clear limits. It says that markup can help machines interpret a page. It does not say that FAQPage specifically increases citation, and it gives no measurement of an effect. "Helps understanding" is a weaker claim than "increases visibility", and the two are often blurred in secondhand reports.
What the independent test found
Ahrefs published a test covering 1,885 pages that added schema markup, matched against control pages that did not, to see whether the markup was associated with citation in AI answers. Its reported finding was that there was no meaningful citation lift. In plain terms, pages that added the markup were not cited more often than comparable pages without it. As with any single study, it has limits: it reflects the pages, queries and AI systems included at the time, and a null result in one sample is not proof that an effect can never exist. It is, however, the only dataset cited here that tries to measure the question, and it does not support the idea that FAQ markup gets you cited.
Putting the three together
- Google's documentation does not list schema as a requirement for AI features.
- Microsoft says markup can help its models understand content, without quantifying anything.
- The one large independent test cited here found no citation lift.
The fair summary is that the claim "FAQPage markup improves AI citations" is not proven. The claim "FAQPage markup harms AI citations" is not proven either. The evidence available supports a modest position: the markup is a description of content, and the content is what AI systems and readers actually use. If you keep the markup, keep it for accuracy and for machine-readability in general, and not because you expect a ranking or citation boost.
Visible Q&A blocks without template headings
A useful consequence of all this is that the best FAQ content never depended on the markup. A visible set of questions and answers can be useful to readers and can be easy for any system to extract. Here is how to write them so they hold up without a rich result.
Write the question the way a person would ask it. Use plain wording from real queries, support tickets, sales calls or search suggestions, rather than invented questions that exist only to carry a keyword.
Answer in the first sentence. Put the direct answer first, then add one or two sentences of context or a caveat. A reader who stops after the first sentence should still have the answer.
Place each Q&A where it belongs in the article. A question about pricing sits next to the pricing discussion. A question about eligibility sits next to the eligibility rules. This is usually better than collecting every question at the bottom.
Avoid the "Frequently Asked Questions" template heading as a reflex. A generic heading above a generic block is the clearest sign of a template. If the questions are real and specific, you can introduce them with a heading that describes the topic, such as "Common problems with renewals" or "What to check before you switch plans". The questions themselves can be subheadings. Search systems and readers both do better with descriptive headings than with a repeated label.
Keep answers specific to the page. If an answer could be pasted onto a hundred other pages without changes, it does not belong on this one.
Do not pad. If a page has two real questions, show two. A block of eight questions where six are filler adds length and removes trust.
Whether you wrap such a block in FAQPage markup is secondary. Done well, the block works as a plain HTML section. If you do want to mark it up, the visible text must match the markup exactly. The FAQ Schema Builder can generate valid JSON-LD from your visible questions and answers, so the two stay aligned, and you can paste the result into your template or tag manager.
Which Q&A types Google still supports
FAQPage is not the only Q&A-related type, and the end of the FAQ rich result did not remove the others. The type that matters most here is QAPage.
QAPage describes a page built around a single question, with one or more answers submitted by users. Think of a community question-and-answer page, where there is one question as the main subject and an accepted or top-rated answer is visible. This is structurally different from an FAQ, where the site itself writes a list of questions and gives one answer to each.
Google's structured data documentation continues to describe QAPage as a supported type for this kind of page. Check the current documentation for the properties it requires and recommends, such as the question, the answer count and the answers, and for any changes to how the result may appear. Two cautions apply:
- Do not use QAPage for a page where the site writes both question and answer as a list. That is the FAQ pattern, and QAPage does not fit it.
- Do not use QAPage on a page with several unrelated questions. The type expects one question as the main entity of the page.
For forums and threaded discussions, Google also documents separate markup for discussion forum content. Whether it fits depends on whether the page is a conversation between users. Again, the official documentation is the place to confirm current status and requirements.
If you are unsure which type matches your pages, the types of structured data overview compares the common options and what each one describes. For building the markup once you have chosen, the schema markup generator covers several types in one place.
What happened on the network pages
The brief for this piece asked for first-party figures: how many pages across our network carried FAQPage markup, and how their Search Console impressions changed after May 7. Those figures were not available when this article was prepared, and we will not estimate them or describe an analysis we cannot document. No number is given here, and nothing in this article should be read as a result from our own sites.
What we can offer instead is a method you can apply to your own property. It is more useful than somebody else's total anyway, because the effect on any one site depends on its templates, its audience and its other changes.
1. Identify which pages carry the markup. Crawl the site and extract the JSON-LD, or use your CMS or plugin settings to list pages with FAQPage. Record the page URLs and a count. If the markup is injected by a script or tag manager, crawl with rendering enabled.
2. Separate the cohorts. Make one group of pages that carried FAQPage and one of comparable pages that did not. Comparable means similar type, age and traffic level. Without a comparison group, any change in the first group could be a sitewide shift.
3. Pick windows that make sense. Compare a period before May 7, 2026 with a period after, of equal length and covering the same days of the week. Remember that the rich result was already limited in August 2023, so for most sites the visible feature was gone long before May 2026, and the markup's effect on impressions should have been small or absent already.
4. Look at the right measures. In Search Console, compare impressions and clicks for each cohort, and look at the pages' queries too. Impressions can move for reasons unrelated to markup: seasonality, a core update, a change in how results are laid out, or a change in how impressions are counted.
5. Check for confounders. Did you change templates, internal linking or titles in the same period? Did Google ship a ranking update? Was there a tracking or consent change? Write these down before drawing any conclusion.
6. Treat small samples with care. If only a few dozen pages carried the markup, a change in a handful of queries can look like a trend.
If you find that the cohort with FAQPage and the cohort without it moved in parallel, that supports leaving the markup decision to cost and accuracy. If the FAQ cohort fell while the control did not, look at whether the content or the template changed before you blame the markup itself.
A practical plan for existing markup
Here is a sequence that keeps the effort proportionate.
- Inventory. List pages with FAQPage and note whether the questions are visible, specific and still accurate.
- Fix or remove the clear problems. Hidden content, duplicated site-wide blocks and outdated answers are the first things to resolve. Remove the markup, and often the block too, where the content has no value to a reader.
- Decide on the rest. For good visible Q&A with accurate markup, you can keep the markup or remove it. Keeping it costs little if it is generated from the visible text. Removing it reduces the maintenance load. Neither choice is likely to be decisive.
- Move user-submitted Q&A to the right type. If you run a community or help forum, see whether QAPage or discussion forum markup describes the pages better.
- Update templates and plugins. Switch off automatic FAQ generation that cannot guarantee visible, page-specific content.
- Watch the official sources. Re-check the changelog and the structured data documentation periodically, because the June and August 2026 removals show that supporting material can change after the main announcement.
- Validate whatever you keep. Use a schema validator to confirm the syntax is correct and that the visible text and the markup match.
What not to conclude
A few conclusions are tempting and unsupported.
- "Removing FAQPage will improve rankings." There is no evidence for that. The markup was never a ranking factor that Google documented.
- "Keeping FAQPage will get us into AI answers." The documentation and the one large test cited here do not support it.
- "Schema no longer matters." Structured data for other types still has documented uses, and Microsoft has said markup helps its models understand pages. The change affects one type, not the whole practice.
- "FAQ content is dead." Visible Q&A that answers real questions remains useful to readers, which is the reason it was worth writing before any rich result existed.
FAQ
Did Google remove FAQ rich results completely?
Google restricted them in August 2023 to well-known government and health sites, and the feature ended on May 7, 2026, according to the Search Central changelog. Further removals followed in June and August 2026. Check the changelog for the exact scope of each entry.
Is FAQPage markup now an error?
Google has not described it as an error or a penalty. It no longer produces a rich result. Markup that is accurate and matches the visible content is not made harmful by that change, but markup that describes hidden or misleading content was always against the guidelines.
Does FAQ schema help with AI Overviews or AI Mode?
Google's documentation on AI features does not list schema, or FAQ markup in particular, as a requirement or a special optimization. An independent Ahrefs test of 1,885 pages reported no meaningful citation lift from schema. Microsoft said at SMX Munich in 2025 that markup helps its models understand content, but gave no measured effect on citations.
Should I delete the FAQ section from my pages?
Not as a reflex. If the questions are real, visible and specific to the page, they help readers. Delete generic template blocks and anything outdated. The markup is a separate decision from the content.
When should I use QAPage instead of FAQPage?
Use QAPage for a page centered on one question with answers submitted by users, such as a community thread. Use FAQPage only where the site itself writes a list of questions with one answer each, and recognize that the second case no longer earns a rich result. Confirm the current requirements in Google's structured data documentation.
How can I build the markup if I keep it?
Write the visible questions and answers first, then generate matching JSON-LD with the FAQ Schema Builder. For other types, the schema markup generator and the types of structured data page cover the options.
Where can I check what Google currently says?
Use Google Search Central: the documentation changelog for dated entries, the structured data documentation for supported types and their properties, and the page on AI features in Search for its current guidance on AI Overviews and AI Mode.
The short version
FAQPage lost its search feature in two stages, the second on May 7, 2026, and follow-up removals came in June and August. The markup is not required for AI answers, and the evidence that it helps is weak: Google lists no such requirement, Microsoft speaks only of understanding, and a 1,885-page test found no meaningful citation lift. Keep visible, useful Q&A where it serves readers. Treat the markup as optional, accurate description. Use QAPage or discussion forum markup for genuine user-submitted Q&A. Then confirm every detail against the official sources, because those pages, not summaries, define what is supported.