A plain-text version of this site for AI assistants is at https://contengi.com/llms.txt, with the full product documentation in one file at https://contengi.com/llms-full.txt. Every page is also available as markdown by adding .md to its URL.

··8 min read

FAQ schema in 2026: what it still does after Google dropped FAQ rich results

FAQ rich results are gone from Google, so here's what FAQ schema is still good for and where to spend the time instead.

A plain-text version of this site for AI assistants is at https://contengi.com/llms.txt, with the full product documentation in one file at https://contengi.com/llms-full.txt. Every page is also available as markdown by adding .md to its URL.

TL;DR

  • FAQ schema is FAQPage structured data, a block of JSON-LD that labels the questions and answers on a page so machines can read them as pairs.
  • Google stopped showing FAQ rich results on 7 May 2026, removed the feature's documentation in June, and dropped its Search Console API support in August, so the markup no longer changes how you look in Google.
  • Leaving accurate markup in place does no harm, and FAQPage is still a valid Schema.org type that sits on millions of domains.
  • For AI answers, the visible FAQ section does the heavy lifting: clear questions with short answers are easy for AI systems like Copilot to lift, with or without the markup.
  • Keep the markup where it matches the page, remove it where it doesn't, stop paying for FAQ schema plugins, and spend the time on better questions.

For years FAQ schema was the cheapest trick in SEO. You pasted a block of JSON-LD under your FAQ, Google folded your answers open right in the results, and your listing grew tall enough to push a competitor below the fold. Then the trick stopped working, in two stages, and a lot of advice online still sells it.

The markup still has a job, a smaller one. We ship FAQPage on every post on contengi.com, so below you'll find what changed in 2026, what FAQ schema does for AI search now, how we handle it, and what to keep, fix, or delete on your own site.

What is FAQ schema?

FAQ schema is structured data that marks up a list of questions and answers on a page using the FAQPage type from Schema.org, a WebPage presenting one or more frequently asked questions. Each question becomes a Question with an acceptedAnswer, usually written as JSON-LD in a script tag in the page's HTML.

A trimmed version looks like this:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Is FAQ schema still relevant in 2026?",
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "Not for Google rich results, which stopped in May 2026."
    }
  }]
}

It's far from a niche format. FAQPage shows up on between one and 10 million domains, based on Google's web index in August 2026, which is a lot of sites still carrying a label for a feature that has gone.

Does FAQ schema still work in 2026?

Not for Google's search results. FAQ rich results stopped appearing in Google Search on 7 May 2026, after three years of Google pulling the feature back.

DateWhat changed
August 2023FAQ rich results limited to well-known, authoritative government and health websites
7 May 2026FAQ rich results no longer appear in Google Search, for anyone
8 May 2026Deprecation notice added to the FAQ rich result documentation
June 2026FAQ search appearance filter, rich result report, and Rich Results Test support dropped; the documentation itself removed on 15 June
August 2026Support for the FAQ rich result in the Search Console API removed

Google didn't publish a blog post or a reason for the removal. The markup also won't cause problems if you leave it in place, and FAQPage is still a valid Schema.org type.

So every "add FAQ schema to win more space in the results" guide written before May 2026 is now selling a menu for a restaurant that closed. Check the date on anything you're following.

Does FAQ schema help with AI search?

Google has no special markup for its AI features, FAQ or otherwise. To appear in AI Overviews or AI Mode a page has to be indexed and eligible for a snippet, and there are no additional technical requirements. Structured data sits on the same list as every other SEO basic, with one rule attached: make sure your structured data matches the visible text on the page.

What does help is the thing the markup describes. Clear headings, tables, and FAQ sections make content easier for AI systems to reference accurately across Copilot and Bing's AI summaries. And Google's AI features fire off related searches around the original question, so a page that answers the side questions cleanly gets more chances to be pulled in.

My take after running FAQs on every post we publish: the visible question and its two-sentence answer do the work, and the JSON-LD is a tidy label on top. If your CMS builds the label for free, keep it. If you're paying someone to hand-write it, stop.

How we handle FAQ schema on contengi.com

Every blog post on this site ends with a "Frequently asked questions" section, and the site turns that section into FAQPage markup automatically. Our posts live in Contengi's content library and CMS and render on a Next.js site, where a small function finds the FAQ heading, reads each question and the answer under it, and writes the JSON-LD from that. The markup can't drift away from the text a reader sees, and the answers sit open in the server HTML, with nothing tucked behind a click.

The questions themselves come from Search Console. This week our post on AI content tools for B2B SaaS teams showed up at position two for "best ai content workflow tools for b2b saas marketing teams" with no clicks, so that question got its own answer in the FAQ. The live page now carries eight questions in its FAQPage markup, three of them added this week from Search Console queries.

That's the whole system. Nobody on our side writes schema by hand, and nobody chases a rich result that no longer exists. The refreshes run from Claude through Contengi's connector, which is how we run the blog from inside Claude, and the FAQ markup follows the text on its own.

Should you keep, add, or remove FAQ schema?

Keep it where it's accurate, and stop spending money or hours on it. This table covers the situations we see on small business sites.

Your situationWhat to do
Markup on pages with a visible FAQ that matches itKeep it, no action needed
Markup on pages where the FAQ was hidden or deletedRemove the markup or put the FAQ back on the page
A plugin adds FAQ markup to every page, FAQ or notSwitch it off on pages without real questions
A new page with questions buyers really askWrite the visible FAQ first, add markup if your CMS does it for free
Paying for an FAQ schema generator or pluginCancel it, the rich result it sold is gone
A dashboard built on the FAQ rich result reportRebuild it on clicks, impressions, and AI citations

How to write an FAQ section that still earns its place

  1. Pull questions from your own data. Filter Search Console queries for "what", "how", "which", and question marks, and add the questions from sales calls and support emails.
  2. Use the searcher's wording in the heading. If people type "is faq schema still relevant", that's your H3, word for word or close.
  3. Answer in the first sentence. Two or three sentences in total, specific enough to stand on its own if an AI answer quotes only that block.
  4. Keep answers open on the page. Render them in the HTML a crawler receives, because the markup and the text on the page has to say the same thing.
  5. Write one FAQ per page. The same five questions pasted across 40 pages are duplicate content, and no engine needs 40 copies of one answer.
  6. Measure what replaced the rich result. Track AI citations with the free Google and Bing AI reports, and see who gets named for your questions with an LLM brand tracking tool.

The FAQ is also the cheapest place to start if you're working on getting named by ChatGPT, next to claiming your business on ChatGPT. If you'd like the questions pulled from Search Console, answered in your voice, and published straight to your site, join the beta.

Frequently asked questions

Is FAQ schema still relevant in 2026?

Not for Google rich results, which stopped appearing on 7 May 2026. FAQPage is still a valid Schema.org type and accurate markup does no harm, so keep it where your CMS adds it for free and put your effort into the visible questions and answers.

When did Google stop showing FAQ rich results?

On 7 May 2026. Google had already limited them to government and health sites in August 2023, then dropped the rich result report and Rich Results Test support in June 2026 and the Search Console API support in August 2026.

Does FAQ schema help with AI Overviews or ChatGPT?

There's no special markup for AI answers, and AI Overviews and AI Mode have no technical requirements beyond normal Google Search. Clear FAQ sections help AI systems reference your content accurately, so the visible questions and answers count far more than the JSON-LD.

Should I remove FAQ schema from my site?

Only where it no longer matches the page, for example when the FAQ was deleted or hidden. Accurate markup doesn't cause problems in Google Search, so there's no reason to strip it out across the site.

How many questions should an FAQ section have?

Five to eight is plenty for a blog post. Answer the questions people search and ask on calls, and stop when you run out of real ones, because filler questions dilute the good answers.

Content like this, in your own voice

The workflows behind this blog run inside Contengi. A strategist sets up your knowledge base, and the agents write to your rules.