FAQ Schema in 2026: Is It Still Worth Adding?

The markup lost its rich result. The visible FAQ kept doing the thing everyone credited the markup with.

Mostly no, and there is one narrow case where it still might be. That is the honest answer, and it is worth more than another 2,000 words telling you to install a plugin.

FAQ schema is one type inside the wider practice our schema markup post covers. That post owns structured data end to end — the formats, which types Google still supports, how to validate. This page covers the FAQPage type only, after the thing it existed for stopped existing.

Everything dated below was read on 28 September 2026. We are naming the pages and the dates because most of what ranks for this query was written before May and has not been touched since.

What FAQ schema is, and what it used to do

FAQ schema is a block of JSON-LD on a page that lists its questions and their answers in a machine-readable form, using schema.org's FAQPage, Question and Answer types. The page shows the FAQ to people; the markup describes the same FAQ to machines.

From 2019 it bought you something visible. Google would expand your result in the search listing into a stack of clickable questions, so a single blue link occupied several lines of the page instead of one.

That was the whole appeal, and it explains the decade of plugins, generators and "add FAQ schema to every page" advice. It was never about ranking — it was about taking up more room.

The markup itself is unremarkable. Stripped of the script wrapper it goes in, one question looks like this:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Does FAQ schema still produce a rich result?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "No. Google switched the FAQ rich result off on 7 May 2026."
    }
  }]
}

Nothing is wrong with it. It is valid schema.org and it parses. It simply has nothing left to trigger in Google Search.

What changed, and when

Google announced it in its own documentation changelog rather than a blog post, which is part of why so many people missed it. Two entries, five weeks apart.

The first, dated 8 May 2026 and titled "Deprecating the FAQ rich result feature", reads: "Added a deprecation notice to the FAQ rich result documentation. This feature will no longer appear in Google Search starting May 7, 2026."

The second, dated 15 June 2026 and titled "Removing documentation for the FAQ rich result feature", reads: "Removed documentation for the FAQ rich result feature. The FAQ rich result feature is no longer shown in Google Search results, as announced in the changelog entry in May 2026." Both are on Google's Search documentation updates page.

Removed means removed. The old FAQPage documentation URL now resolves to that changelog page instead of a guide — we followed it on 28 September 2026. And Google's structured data markup gallery (last updated 15 June 2026) lists 31 features without FAQ among them.

Reporting it on 8 May 2026, Barry Schwartz in Search Engine Land quoted Google's note: "FAQ rich results are no longer appearing in Google Search. We will be dropping the FAQ search appearance, rich result report, and support in the Rich results test in June 2026." Support in the Search Console API ended in August 2026. Matt G. Southern in Search Engine Journal, 10 May 2026, reports the same dates.

This was the second cut, not the first. On 8 August 2023 Google narrowed FAQ rich results to "well-known, authoritative government and health websites" — also reported by Schwartz. We cite his report rather than Google's August 2023 post because Google's post body would not load for us this run, and we do not quote what we have not read.

So if you are looking at a 2024 tutorial promising extra SERP real estate, it is describing something that existed when it was written. It does not now. Our SERP features guide tracks what a result can actually look like today.

Does the FAQPage markup on your pages need to come off?

No, and taking it off will not help you either. On current evidence removing FAQPage markup does nothing in Google Search — it neither recovers anything nor costs anything, because there is no feature left for it to feed.

The relevant Google line predates the deprecation. Announcing the 2023 narrowing, Google said that "structured data that's not being used does not cause problems for Search" — quoted in Search Engine Land's 8 August 2023 report. Unsupported markup is ignored, not punished.

That is not a blanket amnesty, and this is where a lot of "schema can't hurt you" advice overreaches. Google's general structured data guidelines (last updated 10 July 2026) say "Don't mark up content that is not visible to readers of the page", and warn that violating a quality guideline can "possibly cause it to be marked as spam". The same page notes that a structured data manual action means "a page loses eligibility for appearance as a rich result; it doesn't affect how the page ranks in Google web search".

Read those two things together and the position is clear.

• Valid FAQPage markup that mirrors a real, visible FAQ: harmless. Leave it or remove it; nothing observable changes in Google.
• FAQPage markup describing questions that are not on the page: a guidelines problem that was always a guidelines problem. Fix it by deleting the markup or publishing the content.
• FAQPage markup wrapped around marketing copy dressed as questions: same category. It earned nothing before May 2026 and it is a liability with your readers now.
• A giant FAQ block bolted onto every page purely for the rich result: the markup is the smaller problem. The bolted-on content is the one to revisit.

One thing not to do: swap FAQPage for QAPage to chase a surviving rich result. Google's Q&A structured data documentation (last updated 8 September 2026) says "users must be able to submit answers to the question", and lists "an FAQ page written by the site itself with no way for users to submit alternative answers" among the cases it must not be used for. That substitution is a guidelines violation, not a workaround.

The narrow case for keeping it

Here is the honest version of the argument you will see made confidently elsewhere: structured Q&A may still be read by things that are not Google Search, and keeping a valid block costs you nothing. That is a reasonable bet. It is not a proven benefit, and anyone telling you it is has data none of us have seen.

What can actually be checked:

• The vocabulary is alive. schema.org's FAQPage type (version 30.1, dated 16 September 2026) is not deprecated or archived. Google retiring a feature does not retire a schema.org type.
• It is still widely deployed. That same schema.org page reports FAQPage usage at 1M–10M domains, from monthly aggregations of Google's web index dated August 2026. Whatever parses the web is parsing a lot of it.
• Google itself points elsewhere for it. Google's introduction to structured data (last updated 10 December 2025) says there are schema.org attributes and objects "that aren't required by Google Search; they may be useful for other search engines, services, tools, and platforms".

So: a plausible reason to leave existing markup in place. Not a reason to add it to 300 pages this quarter, and not a reason to buy a tool. If the markup is already there and it is accurate, leaving it alone is the cheapest correct decision available.

What it is definitely not is an AI requirement. Google's AI features documentation (last updated 10 December 2025) is explicit: to be shown as a supporting link in AI Overviews or AI Mode a page must be indexed and eligible to appear with a snippet, and "there are no additional technical requirements". It adds that "there's also no special schema.org structured data that you need to add". Our AI Overviews post goes further into that surface.

What actually earns the placements: the visible FAQ

This is the part that matters, and it was true throughout. The questions and answers people can read are what win People Also Ask slots and get quoted in AI answers. The markup was never the mechanism — it only controlled a display format that Google has now withdrawn.

Google says as much about the closest documented equivalent. Asked how to mark a page up for a featured snippet, its featured snippets documentation (last updated 10 December 2025) answers: "You can't. Google systems determine whether a page would make a good featured snippet for a user's search request, and if so, elevates it." There is no markup for it, and never was. Our featured snippets guide covers the formatting that does correlate with winning them.

People Also Ask has no Google documentation at all, so treat what follows as observation rather than a spec — but the pattern is consistent. Pages that surface in PAA tend to answer the question in a short, self-contained block near a heading that matches it. That is a writing property, not a schema property.

The same shape travels to assistants. A 40-to-60-word answer that stands on its own, directly under the question it answers, is quotable by anything reading the page — which is the working principle behind our AI search guide.

Our own policy on this site

How we choose the five questions, in practice:

1. Pull them from the live SERP. Open the People Also Ask box for the primary query and expand two, which loads more. Those are the follow-ups Google associates with the query today.
2. Pull them from Search Console. Filter the Performance report to the page, open the Queries tab, and look for question-shaped queries with impressions and no clicks. Google thinks the page is about that; the searcher disagrees.
3. Answer in the first two sentences. One question per details block, the answer complete before any qualification. If it needs the paragraph above it to make sense, it cannot be lifted.
4. Cap it. Five real questions beat fifteen padded ones. When a sixth question genuinely deserves an answer, it usually deserves its own H2 in the body instead.
5. Re-read it as a stranger. If an answer reads as a sales line, cut it. A FAQ full of marketing copy is the problem the guidelines were written about.

Re-briefing an existing library around that standard — real questions, liftable answers, markup as an afterthought — is where our SEO services engagements usually begin. Expect three to six months before organic results are meaningful; this is a compounding change, not a switch.

The rules that still apply if you do use it

If you keep FAQPage markup or add it for non-Google reasons, the old discipline still holds. It is a description of the page, not an extra channel for content.

And keep the validation expectation realistic. The Rich Results Test dropped FAQ support in June 2026, so a clean result there says nothing about FAQPage either way — it simply has no opinion any more.

Where to go from here

Do nothing to the markup. Genuinely — if your FAQPage blocks are accurate, this deprecation is not a task, and the hour you were going to spend stripping them is better spent elsewhere.

Spend it on the FAQs themselves. Open your five highest-value pages, read the visible questions out loud, and ask whether any of them is a question a customer has ever asked. Rewrite the ones that are not.

Then stop treating structured data as a growth lever. It is a description layer: useful, worth getting right, and never the thing that earned the placement.