Upgrowly
← Blog

FAQ Schema in 2026: Is It Still Worth Adding to Your Site?

By Neha

FAQ schema is code that labels the questions and answers on a page, and in 2026 it no longer changes how you look in Google. Google stopped showing FAQ rich results, the expandable questions under a listing, from 7 May 2026. The markup is harmless and still valid, so keep it if you have it, but do not add it expecting more clicks.

That is a bigger change than most SEO advice has caught up with. For three years the line was "FAQ dropdowns now only appear for government and health sites". Today they do not appear for anyone, and Google has removed the documentation page that described them. This guide sets out what Google has actually said, checked on 15 November 2026, what the markup still does, and when a small business should bother with it.

Short answer: FAQ schema no longer earns any visible result in Google Search; Google ended FAQ rich results on 7 May 2026. Valid markup does no harm, and Google says unused structured data causes no problems, so there is no need to rip it out. For AI search, Google says no special schema is needed, and the AI crawler documentation we read does not mention FAQ markup. The visible FAQ section on your page is what still matters.

What is FAQ schema?

FAQ schema is a block of structured data, using the schema.org type FAQPage, that tells machines "this page lists these questions, and here is the answer to each".

Structured data is hidden code, usually in a format called JSON-LD, that labels facts on a page so search engines do not have to guess. Our guide to what schema markup is explains the idea from scratch. Schema.org defines FAQPage simply as a web page "presenting one or more 'Frequently asked questions'".

Here is what it looks like for a dental clinic in Pune with two questions on its page:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you accept UPI payments?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes. You can pay by UPI, card or cash at the reception."
      }
    },
    {
      "@type": "Question",
      "name": "Is the clinic open on Sundays?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We are open on Sundays from 10 am to 2 pm, by appointment only."
      }
    }
  ]
}

The code sits inside a <script type="application/ld+json"> tag. Visitors never see it; they see the normal FAQ section on the page, which must say the same thing.

What did Google change, and when?

Google limited FAQ rich results in August 2023 and ended them for everyone on 7 May 2026.

The timeline, from Google's own pages:

DateWhat Google saidSource
8 August 2023FAQ rich results "will only be shown for well-known, authoritative government and health websites"Search Central blog
8 May 2026Deprecation notice added; the feature "will no longer appear in Google Search starting May 7, 2026"Search documentation updates
From 7 May 2026"FAQ rich results are no longer appearing in Google Search", so FAQ impressions drop in Search Console's performance reportSearch Console data anomalies page
June 2026Documentation for the FAQ rich result removed, because the feature "is no longer shown in Google Search results"Search documentation updates

The old address of Google's FAQPage guide now redirects to that updates page. So any article, plugin screen or tool that still promises "FAQ dropdowns under your listing" is out of date.

If you saw FAQ impressions in Google Search Console fall to nothing in May 2026, this is the reason. It was not a penalty and it was not anything you did.

Is FAQ schema still valid, and does it hurt to keep it?

It is still valid schema.org code, and keeping it does not hurt; Google said in 2023 that unused structured data causes no problems.

When Google first cut back FAQ rich results, its announcement said site owners could drop the markup but there was "no need to proactively remove it", and that "Structured data that's not being used does not cause problems for Search, but also has no visible effects in Google Search." We found no newer Google statement replacing that advice, and it fits the 2026 change too.

So for an existing site:

  1. Leave working FAQ markup where it is, as long as it matches the visible questions on the page.
  2. Remove it if it is wrong: questions that are no longer on the page, old prices, or the same FAQ block pasted onto every page of the site. Google's general guidelines say "Don't mark up content that is not visible to readers of the page", and that rule did not go away.
  3. Do not pay anyone to add it as a Google ranking or click-through fix. There is nothing visible left for it to unlock in Google.

The schema detector shows which structured data a live page carries and whether it can be read, which is a quick way to find old FAQ blocks your developer or plugin added years ago.

Does FAQ schema help with ChatGPT, Gemini or AI Overviews?

Nobody has documented that it does. Google says AI features need no special schema, and the AI crawler documentation we checked does not mention FAQ markup.

This is where online advice gets loose, so here is the line between what is written down and what is guessed.

ClaimStatusWhere it comes from
Google needs special schema for AI Overviews or AI ModeDocumented as false. Google says "there's no special schema.org markup you need to add"Google's AI optimisation guide
Structured data in general is still worth having for GoogleDocumented. The same guide says to keep using it because "it helps with being eligible for rich results"Same guide
ChatGPT, Claude or Perplexity read FAQ markupNot documented. Their crawler pages describe access and robots.txt, not structured dataOpenAI, Perplexity
FAQ markup makes AI assistants quote youObserved or guessed by some marketers; no primary sourceNone

That does not prove FAQ markup is ignored. It means nobody who runs these systems has said they use it, so no one can honestly promise a benefit. Our guide to ranking in AI Overviews covers what Google does say helps.

What clearly matters is the visible text: a question in a heading and a complete answer in the first sentence below it. Any search engine or AI tool that can read your page sees that text, with or without code.

So is FAQ schema worth adding in 2026?

For most small businesses, only as a five-minute extra on a page that already has a real FAQ section; never as a priority.

Your situationWhat to do
You have FAQ markup that matches the pageKeep it. Nothing to fix.
Your FAQ markup lists questions no longer on the pageRemove or update it.
You have a real FAQ section and no markupOptional. Add it if it takes minutes; skip it if your developer charges for it.
You have no FAQ section at allWrite the section first. That is the part customers and search engines read.
An agency is selling "FAQ schema for rich results"Ask what visible result they expect. Since May 2026 the honest answer is none in Google.

For freelancers and agencies, this is also a reporting point. If a client's report showed FAQ rich result impressions before May 2026, explain the drop before they ask, using Google's own wording above. Our guide to explaining SEO results to clients covers how to word changes like this.

The better use of an hour, for a coaching centre in Kota or a CA practice in Lucknow, is the content itself: the questions parents or clients actually ask on the phone, answered plainly on the page they would land on.

How to write an FAQ section that still earns its place

Answer the questions customers really ask, one complete answer each, in words they use; the code is optional.

  1. Collect real questions. Look at WhatsApp enquiries, calls, emails and Google reviews from the last three months. "Do you have parking?", "Is there an EMI option?", "Do you visit on Sundays?"
  2. Put the answer first. Start with yes, no, a price range or a time, then explain in one or two sentences.
  3. One page, its own questions. A service page for root canal treatment gets root canal questions, not the clinic's general FAQ copied again.
  4. Keep facts current. Old prices and hours in an FAQ are worse than no FAQ, especially when an AI assistant repeats them.
  5. Add markup only if it matches. If you add FAQ schema, the FAQ schema generator turns your questions into clean FAQPage code, flags missing answers and repeated questions, and reminds you that the code must match the page.
  6. Check it before publishing. Paste the code into the schema validator to catch broken JSON, a misspelt type or a missing @context.

Our guide to writing content for AI Overviews goes deeper on answer-first writing.

What should you add instead of FAQ schema?

Spend the effort on structured data Google still documents, and on the basics AI tools need to read your site.

  • LocalBusiness markup for a shop, clinic or office, so your name, address, phone and hours are labelled clearly. Our guide to local business schema markup walks through it.
  • Breadcrumb, Product, Article or Event markup, where the page genuinely is one of those things.
  • Crawler access. Structured data is useless if bots cannot read the page. The AI readiness checker scores your site out of 100 for how easily AI tools can read it, covering crawler access, llms.txt, your sitemap and structured data, and our guide to showing up in ChatGPT and AI search explains the rest.

The readiness checker still notes whether a page has FAQPage markup, as a small item. Treat that as tidiness, not a ranking lever.

Frequently asked questions

Does Google still show FAQ rich results?

No. Google says FAQ rich results stopped appearing in Google Search from 7 May 2026, for all sites. Before that, from August 2023, they were shown only for well-known government and health websites.

Should I remove FAQ schema from my website?

There is no need if it is correct. Google has said unused structured data does not cause problems for Search. Remove or fix it only if it no longer matches the visible questions on the page.

Is FAQ schema a ranking factor?

Google has never said FAQ markup is a ranking factor, and the rich result it supported has now gone. The visible FAQ content can still help a page answer more searches, because it is ordinary text on the page.

Does ChatGPT use FAQ schema?

OpenAI has not said so. Its crawler documentation covers which bots read your site and how robots.txt applies, not structured data. Write clear questions and answers in the visible page, which any assistant that reads your site will see.

What is the difference between FAQPage and QAPage?

FAQPage is for questions you answer yourself, such as a clinic's FAQ. QAPage is for a page built around one question and its answers, often posted by users, such as a forum thread. Schema.org lists them as separate types, so pick the one that matches who wrote the answers.