FAQ Schema and AI Search: What It Does and Does Not Do in 2026

Short answer: FAQ schema no longer earns you anything visual in Google Search — that ended on May 7, 2026. It still has a narrow, real job: describing question-and-answer content that already exists on the page so machines can parse it unambiguously. It does not create authority, it does not guarantee AI citations, and it cannot rescue thin content. This is what to keep, what to delete, and what order to work in.

What Actually Changed in 2026

Google's change was narrow and well documented, and it is worth stating precisely so nobody over-corrects:

• As of May 7, 2026, FAQ rich results no longer appear in Google Search for the overwhelming majority of sites.
• The Rich Results Test dropped FAQPage validation in June 2026, and Search Console's FAQ report was retired.
• API support for the FAQ rich-result type was removed later in the year.

What did not change: FAQPage remains a valid Schema.org type, Google still parses structured data to understand pages, and other consumers of markup — Bing, assistants, and internal search tools — continue to read it. The visual reward disappeared. The descriptive function did not.

The Distinction That Fixes Most Confusion

Almost every bad decision here comes from conflating two different things:

• Visible FAQ content — the questions and answers a human reads on the page. This is the asset. It answers real queries, satisfies intent, and is the thing an AI system can quote.
• FAQPage markup — a machine-readable description of that content. This is a label. Labels help a parser identify what it is looking at; they do not improve what is inside.

Markup without visible content was always a policy violation and is now also pointless. Visible content without markup still works. If you only have budget for one, buy the content.

Accurate Expectations for AI Citations

There is no published mechanism by which FAQPage markup causes a citation in ChatGPT, Perplexity, Google AI Mode or AI Overviews. What is observable is that these systems reliably lift short, self-contained passages that directly answer a stated question. FAQ formatting produces exactly that shape of passage — which is why well-written FAQ sections get quoted, with or without the schema attached.

So the honest framing is: the format helps, the markup describes the format, and neither substitutes for being a credible source. Anyone promising citations as a deliverable of adding schema is selling a correlation as a lever. If you want to see where you actually stand across AI surfaces, measure it directly rather than inferring it from markup — our AEO services and GEO services both start from measurement, not markup.

The Audit Checklist

Run this against every page carrying FAQPage markup:

1. Is every marked-up question and answer visible on the page? If not, remove the markup or publish the content.
2. Does the answer stand alone? Read it out of context. If it needs the paragraph above it to make sense, rewrite it.
3. Is the answer 40 to 60 words? Long enough to be complete, short enough to be lifted intact.
4. Is the question phrased the way a customer would ask it? Not the way your product team names things.
5. Is the FAQ block genuinely useful, or was it added for the old rich result? Delete the latter — including the markup.
6. Does the markup validate? Use the Schema.org validator; the Rich Results Test no longer covers this type.
7. Are duplicate FAQ blocks repeated sitewide? Boilerplate repeated across 200 pages is a quality signal in the wrong direction.
8. Do author, dates and organisation entities on the page reflect reality? These carry far more weight than the FAQ type ever did.

Priority Order

If you are deciding what to work on this quarter, this is the sequence that produces compounding results rather than tidy-looking code:

1. Crawlability and indexability. Nothing downstream matters if crawlers, including AI crawlers, cannot fetch the page.
2. Answer quality on the pages that already rank. Rewrite existing FAQ answers to be self-contained and specific.
3. Entity clarity. Accurate Organization details, real authors, honest dates.
4. Local specificity. For a Vancouver business, service area, pricing ranges and real local examples do more than any markup type. That is the substance behind our Vancouver SEO work.
5. Markup, last. Describe what is already true.

What to Do This Week

Do not run a sitewide FAQPage purge — it is not a penalty risk and removal is not urgent. Instead, pull the list of pages carrying the markup, apply the eight-point checklist above, and split them into keep, rewrite, and delete. Most sites find that a small number of genuinely useful FAQ sections are worth strengthening, and a long tail of copy-pasted blocks should simply come off the site entirely. The markup decision follows automatically from that content decision — which is the right way round.