FAQ Schema in 2026: Is It Still Worth Adding to Service Pages?

FAQ schema no longer earns a rich result: Google stopped showing FAQ rich results for every site on May 7, 2026. Keep the questions on your service pages for buyers, and treat the markup as optional.

If a proposal on your desk has a line item for FAQ schema on 40 service pages, ask what it buys. It’s a fair question.

Until this year the pitch was easy to follow, which was to add the markup, win the expandable questions under your search listing, collect the extra clicks, and let the traffic report do the rest of the selling. That result is gone.

Google had already cut FAQ rich results back to well-known government and health sites in 2023, and in May 2026 it switched them off for everyone, so nobody gets the dropdown now.

So the markup isn’t the issue. It’s still valid code. The issue is whether it’s worth a line item, a plugin setting or a developer’s afternoon, and the FAQ on the page is a separate matter from the markup around it. We’ll take the two apart.

What Google Changed With FAQ Schema, and When

FAQ schema is FAQPage structured data, a block of code that labels the questions and answers on a page, and its one job in Google Search was to make those pairs eligible for an expandable result under your listing. Here’s how that job ended.

FAQ Rich Results, Date by Date

Dates matter here. The sources are Google’s 2023 Search Central post, its documentation changelog and Search Engine Journal’s report of the notice that carried the June and August dates.

The 2023 post already told you what to do. Google wrote that you could drop the markup, that there was “no need to proactively remove it,” and that unused structured data “does not cause problems for Search, but also has no visible effects in Google Search.” Three years on, that’s the whole situation. Nothing new.

The markup type itself survived. Schema.org still defines FAQPage as a page presenting frequently asked questions. What died was the reward. Any click-through lift you read about in an older article belongs to a result that no longer exists.

Does FAQ Schema Help You Show Up in AI Answers?

This is the pitch that replaced the old one. Mark up your questions and the AI engines will quote you. Check it against what’s documented.

Google’s page on AI features and your website says there are no additional requirements to appear in AI Overviews or AI Mode, and no other special optimizations are necessary. It adds that you don’t need new machine-readable files or markup, and that there’s no special schema.org structured data to add. The page has to be indexed and eligible to show in Search with a snippet. That’s the entry ticket. Nothing about FAQ code.

What about ChatGPT, Claude and Perplexity? None of them has published a rule saying FAQ markup changes what it cites, so this page doesn’t claim one. If a vendor tells you otherwise, ask for the source.

The words on the page are what every system reads. Markup is a label on those words. A weak answer with a label is still a weak answer. Our post on LLM optimization covers how tech companies get into ChatGPT, Claude, Gemini and Perplexity answers.

Keep, Remove or Skip FAQ Schema: A Decision Rule

Four situations, four calls.

• The markup is already on your service pages and matches the questions on the screen, so leave it, because Google says there’s no need to remove it and pulling it out costs developer time and returns nothing.
• The markup is there, but the questions it describes have been reworded, hidden or deleted. Fix it or delete it this week. Google’s structured data guidelines say don’t mark up content that isn’t visible, and that your markup must be a true representation of the page.
• Nothing’s there yet. Don’t commission it. If your SEO plugin adds FAQPage when you publish an FAQ block, fine, because that costs nothing.
• A quote bills FAQ markup as its own line. Ask what result it buys. In Google Search in 2026, the honest answer is none.

Notice what’s missing from that list. No rollout. There’s no case for building one. Google’s guidelines have always said it doesn’t promise that markup will appear in results, even when the markup is correct, and for FAQ that promise is now zero by design.

What a Service Page FAQ Is Really For

Here’s the part the markup pitch always buried. A service page FAQ is a sales tool. It’s where the objections go that would otherwise come up on call two.

Think about what an MSP buyer asks before signing. What happens to our current tools when we switch? How’s onboarding billed? What does the response-time commitment cover after hours? Who actually answers when a server goes down on a Sunday? Find those answers on the page and the buyer walks into the first call already past the basics, with the real conversation ahead.

Pull the questions from your own sales calls and support tickets, not from a keyword tool. Answer in the first sentence, plainly, then add the detail. Five to eight is plenty. Every question should be one a buyer has actually asked.

Sales runs on process, and so does this: one owner, one list, one review a quarter. None of it needs markup. A buyer doesn’t see JSON-LD. A buyer sees whether you answered.

A Ten-Minute Check on Your Own Pages

You don’t need an audit to settle this. Ten minutes. Pick your three best service pages and run through it.

1. Open the page and read the FAQ the way a buyer would. Cut any question nobody has asked.
2. View the page source and search for FAQPage. If it’s there, compare each question and answer with what’s on screen, word for word.
3. Fix or delete every mismatch. Markup that describes text the page no longer shows is the one problem on this list.
4. Rewrite any answer that opens with a warm-up so the first sentence answers the question.
5. Write down the objections from your last five sales calls that the page still doesn’t answer, then add them.

If the search for FAQPage comes back empty, you’ve lost nothing. If a plugin put the markup there, leave it, and spend the time you saved on the answers. Our SEO audit services test each key page against the question a buyer is really asking, and the guide to schema markup for MSP websites has the wider structured data walkthrough.

A label on a drawer isn’t what’s in the drawer. The answers are the asset, and the markup is optional. Fix the foundation first. If you want a second opinion on what’s worth doing on your service pages, book a growth strategy call.