FAQPage schema in 2026: why it still matters for AI search even though Google dropped rich results

Your Rank Math dashboard flags a schema warning. Or Search Console shows a “FAQ” report that used to fill in every week and now sits empty. You ask your developer, or your agency, or Google itself, and the answer you get back is some version of: “Google killed FAQ schema.”

That’s not quite what happened. And the difference matters, because it changes what you should actually do with the FAQPage schema already sitting on your site.

In May 2026, Google confirmed it’s dropping the FAQ rich result, the little expandable question-and-answer box that used to show up directly in search results. If you’ve been following how generative engine optimization has reshaped what “ranking” even means this year, this is one more piece of that shift, not a separate story. So is FAQPage schema dead? Should you strip it out of your site before it “breaks” something? This article walks through exactly what changed, what didn’t, and what the honest (not the hyped) answer is on whether FAQ schema still does anything for AI search.

Key takeaways

• Google removed the FAQ rich result display from search results. It did not remove FAQPage as a valid schema type.
• The removal happened in stages: a documentation notice in May 2026, Search Console changes in June 2026, and API support removal in August 2026.
• Leaving FAQPage schema on your site doesn’t cause Search Console errors or hurt your rankings. Google has said as much directly.
• Whether FAQ schema helps you get cited in AI Overviews, AI Mode, ChatGPT, or Perplexity is genuinely unconfirmed. The evidence is mixed.
• What seems to matter more: visible, well-structured Q&A content on the page itself, not just the markup behind it.
• Other crawlers, including Bing’s and various AI retrieval systems, still read FAQPage markup even with Google’s rich result gone.
• The practical move is simple: keep FAQ schema if it matches real content on the page, don’t panic-remove it, and don’t bolt it on just to chase a feature that no longer exists.

What actually happened on May 7, 2026

On May 7, 2026, Google added a deprecation notice to the top of its FAQ structured data developer documentation. No blog post. No announcement email. Just a notice sitting at the top of the page, stating plainly that “FAQ rich results are no longer appearing in Google Search.”

The notice laid out a timeline for what comes next. Support in the Rich Results Test would be dropped in June 2026, along with the FAQ search appearance filter and rich result report inside Search Console. Then, in August 2026, Google would pull FAQ rich result data from the Search Console API entirely, giving site owners a few months’ notice to adjust any tooling that pulled that data automatically.

If this feels like whiplash, it helps to zoom out. This wasn’t a sudden reversal. It was the last step in a pullback that had been running for nearly three years. Back in August 2023, Google first restricted FAQ rich results to “well-known, authoritative government and health websites,” the same announcement that also curtailed HowTo rich results. For most commercial sites, the FAQ rich result had effectively already stopped appearing years before anyone made it official.

Then came the March 2026 core update, which further thinned out what little FAQ rich result visibility remained. By April 2026, the feature was generating almost no impressions for almost anyone still using it. The May notice didn’t cause the decline. It documented one that had already happened.

So here’s the timeline in full: August 2023 restriction, March 2026 core update, May 2026 documentation notice, June 2026 Search Console changes, August 2026 API removal. Five steps, three years, one conclusion Google never actually announced with fanfare.

It’s worth pausing on what actually disappears from the search results page here. The FAQ rich result was the expandable box under a listing, the one where a question sat in bold and tapping it opened the answer right there, before a searcher ever clicked through to a site. For a local service business, that meant extra vertical space on the results page and a shot at answering a question before a competitor’s listing did. That’s the piece going away, not the underlying data.

There’s also a practical wrinkle buried in the August 2026 API change. Some agencies and in-house teams built reporting dashboards that pulled FAQ rich result impressions straight from the Search Console API on a schedule. Once that data support is removed, those automated reports will need to be retired or repointed, not because anything on the client’s site broke, but because the API stops returning a field that no longer has anything behind it. If that’s part of your reporting stack, this is the actual deadline to plan around, not June, and not the May notice itself.

What FAQ rich results actually were, for anyone who never quite understood them

If you’re fuzzy on what feature just went away, you’re not behind. FAQ rich results were a specific display format Google Search could show for pages that had FAQPage schema markup and matched content on the page. A business would list a few common questions and answers, mark them up with structured data (a layer of code search engines can read, separate from what a visitor sees), and Google would sometimes pull those question-and-answer pairs into an expandable box right under the listing in search results.

Not every page with FAQ schema got the rich result. Google decided case by case, based on relevance and how well the content matched real user questions. When it worked, it gave a listing more room on the page and a chance to answer something before a click ever happened. When it didn’t, the schema still sat quietly on the page doing nothing visible, which is closer to where things stand for everyone now.

A common example: a plumbing company’s page might mark up “What areas do you serve?” and “Do you offer emergency service?” When Google chose to surface that pair as a rich result, it could appear directly under the listing, sometimes pushing a competitor’s plain listing further down the visible page. That was the entire mechanism. Nothing more mysterious than an optional visual treatment Google applied selectively.

The distinction most coverage is getting wrong: rich result versus schema type

Here’s the part that gets flattened in a lot of the “FAQ schema is dead” reporting. Two separate things are being talked about as if they’re one thing.

The first is the FAQ rich result: the visual box in search results. That’s the feature Google is removing, on the timeline covered above. The second is FAQPage: the underlying Schema.org structured data type itself, a standard maintained independently of Google, used across the web by search engines, AI systems, and other tools that read structured data. FAQPage as a schema type has not been deprecated, restricted, or flagged as an error. It’s still a valid, supported vocabulary for marking up question-and-answer content.

Google has been explicit about this distinction, even if the framing hasn’t traveled as far as the original headline. Unused or non-rich-result-eligible structured data does not cause problems for Search. Leaving FAQPage schema in place on your site, even without the rich result attached to it anymore, does not generate Search Console errors and does not affect your rankings. The schema layer keeps functioning exactly as it always did. What changed is only whether Google chooses to visually surface it in the results page.

Think of it in layers. There’s the content a visitor reads on the page. There’s the JSON-LD code in the page’s source, a block that says, in effect, “here is a question, and here is its answer,” structured so a machine can parse it without guessing. And there’s whatever a search engine chooses to do with that code, which might be nothing at all. Google’s rich result was only ever the third layer. The first two layers, the visible content and the JSON-LD describing it, are untouched by any of this.

Put simply: the display feature is gone. The schema type remains valid.

Why this is getting reported as “FAQ schema is dead” when that’s not quite right

Search marketing coverage tends to compress “Google removed a rich result” into “Google killed the schema,” and it’s easy to see why. The two concepts sound like the same thing to anyone who isn’t neck-deep in structured data terminology, and headlines reward the more dramatic version. Independent outlets covering the announcement, including Search Engine Journal’s reporting on the timeline, were generally careful to note the rich-result-versus-schema-type distinction. That nuance rarely survives the trip from the original article to the Slack message a client sends their agency asking if they need to rip everything out.

Some of that compression happens in aggregator posts and social threads that summarize the summary, stripping out the one sentence that would have prevented the confusion. By the time a small business owner hears about it secondhand, from a web person or a Facebook group or an SEO tool’s automated alert, “Google is removing the FAQ rich result feature in stages” has become “get rid of your FAQ schema before it hurts you.” Neither Google’s documentation nor the outlets reporting on it actually said that.

The panic here is overblown. Nobody’s site broke in May 2026. Nobody’s rankings dropped because of this notice. What actually happened is narrower and less dramatic than the phrase “FAQ schema is dead” suggests, and the confusion is understandable given how the story got told, but understandable isn’t the same as accurate.

Does FAQ schema still help with AI search in 2026?

This is the question that actually matters to most people reading this, and it deserves a straight answer instead of a sales pitch: nobody knows for certain, and anyone telling you otherwise with total confidence is overselling it.

Here’s what’s actually on the table. Microsoft has said publicly that schema markup helps its systems understand page content for Copilot, which is a real, if somewhat general, signal in favor of structured data mattering to at least one AI platform. On the other side, an independent study from Search/Atlas in December 2024 looked at schema markup coverage against AI citation rates and found no meaningful correlation between the two. Two credible sources, pointing in different directions, on a question that’s still genuinely unsettled.

Google itself has not confirmed that FAQPage schema improves your odds of being cited in AI Overviews or AI Mode. Not a soft maybe, not a hedge, an actual absence of confirmation. If you’ve read a blog post claiming Google said FAQ schema boosts AI citation, that claim isn’t coming from Google.

So what’s the honest takeaway? The more defensible claim, the one better supported across what evidence does exist, is that visible, well-structured Q&A content on the page itself is doing the real work for AI citation, not the schema markup sitting behind it. Large language models and retrieval systems are reading your actual page content: the question in your heading, the answer in the paragraph underneath it, written the way a person would actually ask and answer it. FAQPage schema is one way of reinforcing that structure for machines, a low-cost, low-risk layer on top of content that already needs to be good regardless. It’s supporting evidence, not the mechanism itself.

If you want a sense of where your own business actually stands on this, a simple check of whether you’re showing up in ChatGPT and Google AI Overviews at all tells you more than any schema audit will. A business with no visible AI citation footprint has a content problem to solve first, and schema markup won’t fix that on its own.

This is also the point where a lot of agency pitches overpromise. If someone tells you adding FAQ schema will get your business cited in AI Overviews, treat that the same way you’d treat a guarantee of a first-page Google ranking: with real skepticism. The honest version of this pitch sounds less exciting and more accurate. Structured data is a supporting layer, not a lever you pull to make an AI platform notice you.

Fix the content first. The markup is a detail, not the strategy.

How to implement FAQPage schema correctly in 2026

If you’re keeping FAQ schema, or adding it for the first time, the implementation basics haven’t changed even though the rich result has gone away.

FAQPage schema is written in JSON-LD, a block of code placed in a page’s source that describes content in a structured, machine-readable format. A properly formed FAQ block names the schema type, lists a set of questions, and pairs each one with its corresponding answer text.

The rule that matters most here, and the one businesses got tripped up on back in 2023, is straightforward: the schema has to match what’s actually visible on the page. Every question and answer in your JSON-LD needs a real, readable counterpart that a visitor sees without clicking anything extra. Marking up content that doesn’t appear on the page, or stuffing extra keyword-heavy questions into the schema that never show up visually, is the exact abuse pattern that got FAQ rich results restricted to government and health sites back in August 2023 in the first place. That door isn’t reopening.

A few practical rules keep implementation clean: use real questions customers actually ask, not keyword-stuffed variations invented for search engines. Keep answers genuinely useful on their own, not vague teasers designed to force a click. And match the schema content word for word, or close to it, with the visible page content. If your on-page FAQ text says one thing and your JSON-LD says something else, you’ve created a mismatch that serves no one, human or machine.

Here’s a concrete version of the mismatch to avoid: a landscaping company adds five FAQ questions to its schema, including “What is the best landscaping company in Florida?” with an answer naming itself, but that question never appears anywhere on the visible page. That’s the pattern that drew scrutiny in the first place, marking up promotional claims dressed as questions rather than real answers to real things customers ask. Compare that to “Do you offer irrigation repair?” appearing as visible text on the page with a genuine answer, then mirrored in the JSON-LD. One is structured data supporting real content. The other is keyword stuffing wearing a schema costume.

Rank Math-specific implementation using the Schema Generator shortcode

If you’re running WordPress with Rank Math Pro and a page builder like WPBakery rather than Gutenberg, the block-based schema options built into Rank Math’s default editor flow won’t apply directly to you. The Schema Generator shortcode is the practical path, and it works cleanly inside WPBakery without fighting the builder.

Start in Rank Math’s Schema Generator tool, found under the plugin’s Schema menu in the WordPress dashboard. Build your FAQ schema there: add each question and its matching answer, one pair at a time, exactly as they’ll appear on the visible page. Rank Math generates a shortcode tied to that specific schema block once you save it.

Drop that shortcode into a WPBakery text element on the page where the visible FAQ content lives; a Raw HTML element or a standard Text Block module both work. The shortcode renders the JSON-LD in the page’s output without you needing to hand-edit any code, and because it’s tied to a shortcode rather than a Gutenberg block, it survives inside WPBakery’s row-and-column structure without breaking the builder’s layout.

One detail worth double-checking: the shortcode needs to sit on the same page as the visible FAQ text it describes, not on a template file or a global element loaded sitewide. Rank Math’s own FAQ schema guide walks through the Schema Generator interface in more visual detail, including where the tool option lives inside the plugin menu, which is worth a look if this is your first time building a schema block through Rank Math specifically.

A common snag: pasting the shortcode into a WPBakery Text Block sometimes triggers the visual editor to auto-format quotation marks into curly quotes, which can occasionally interfere with how the shortcode parses. If your schema isn’t rendering after you save, check the raw text mode of that element first before assuming the Schema Generator tool itself failed. Nine times out of ten, it’s a formatting quirk in the builder, not a problem with Rank Math’s output.

If you’re not sure whether your current setup is actually working the way you think it is, running your site through a quick audit is a lower-effort first step than manually checking every page’s source code by hand. That’s exactly the kind of gap a free scan can surface before you spend time rebuilding something that was already fine.

How to validate your FAQPage schema implementation

Once the shortcode is live, confirm it actually generated valid JSON-LD before moving on. Two tools matter here, and which one you use depends on when you’re reading this.

Through June 2026, Google’s Rich Results Test still supports FAQ schema validation specifically, even though the rich result itself no longer appears in search. Paste in your page URL, and the tool will confirm whether your FAQPage markup parses correctly, flagging any structural errors in the JSON-LD.

After June 2026, when that support is removed, switch to the Schema Markup Validator instead. It checks the same underlying JSON-LD structure without the FAQ-specific rich result framing that’s being retired. Either tool catches the basics: malformed JSON, mismatched question-and-answer pairs, or schema that references content the tool can’t find on the page.

Common errors both tools will catch include a missing closing brace in the JSON-LD block, a question listed without a matching answer, or an answer that references text that was later edited or removed from the visible page. Any of these will show up as a flagged error rather than a silent failure, which is the point of validating in the first place.

What to actually do with your existing FAQ schema right now

Here’s the decision framework, stripped down to three actual choices.

Keep it if your FAQ schema matches real, visible content on the page. There’s no downside. It doesn’t generate Search Console errors, it doesn’t hurt your rankings, and it remains readable by Bing, various AI crawlers, and retrieval systems that have nothing to do with Google’s rich result decision at all.

Don’t panic-remove it. Ripping out schema that’s working fine because of a headline about “dead” FAQ schema is the wrong reaction to what actually happened. Removing valid structured data doesn’t help you and adds unnecessary work for no benefit.

A quick gut check for the “keep or remove” decision: open the live page and compare it side by side with your JSON-LD. If every question in the schema has a visible, matching answer on the page, you’re fine as is. If you find questions in the schema that don’t appear anywhere visible, or answers that were rewritten on the page without updating the schema to match, that’s the specific thing worth fixing, not the schema type as a whole.

Don’t add it purely to chase a rich result that no longer exists. If you’re building new FAQ content from scratch, build it because the questions and answers genuinely help visitors and give AI systems something clear to read, not because a rich result used to reward that effort. The rich result is gone. The reasons to write good, structured Q&A content for actual readers aren’t.

Not sure if your FAQ schema is doing anything? Talk to Innovative Flare

Reading through Google’s documentation, checking Search Console, and running your own JSON-LD validation takes time most business owners don’t have to spare. If you’d rather have someone who does this daily take a direct look at your site’s structured data, your FAQ content, and where you actually stand for AI search visibility, that’s exactly what our team handles. We’ll tell you plainly what’s working, what isn’t, and what’s worth fixing, without inflating the schema layer into more than it is.

If you want the deeper version of this conversation, including how your current setup compares against what actually moves the needle for search engine optimization in 2026, schedule a call with Innovative Flare and we’ll walk through it together.

FAQ schema in 2026: common questions