FAQ Schema in 2026: Is It Still Worth Adding?

FAQ schema (FAQPage structured data) no longer produces FAQ rich results in Google. Google limited them to authoritative government and health sites in August 2023, then its documentation stated they would no longer appear in Google Search from 7 May 2026. Existing markup won't hurt you, but adding it just for Google rich results is no longer worth the effort.

That's a big change for a feature that, a few years ago, many SEO checklists treated as essential. This post explains what changed and when, what still makes sense to do with FAQ schema in 2026, and how FAQ content fits into AI-powered search. For a general introduction to structured data, see our structured data guide.

If you still want to generate valid FAQPage JSON-LD, for another platform or for internal consistency, our free schema generator builds it from a simple question and answer form, alongside LocalBusiness, Organisation, Article, Breadcrumb and Product markup.

AI Automation for Healthcare Clinics, Explained Step by Step · 2:57 Subscribe

A short history of FAQ rich results

FAQ rich results showed expandable questions and answers directly under a search result. They took up a lot of space, which made them popular with site owners. That popularity is part of why Google cut them back.

According to Search Engine Roundtable's report on the May 2026 notice, Google also said it would drop the FAQ search appearance and rich result report from Search Console, and Rich Results Test support, in June 2026, with Search Console API support removed in August 2026.

So for most businesses, FAQ rich results effectively ended in 2023. The 2026 change completed the removal, including for the government and health sites that had kept them.

What happened to HowTo schema?

HowTo rich results, which showed numbered steps in search results, went first. Google's August 2023 post restricted them to desktop, and its September 2023 update said they were no longer shown on desktop and the result type was deprecated. Google also removed HowTo reporting from Search Console.

If you're still adding HowTo markup to guides, it no longer produces a rich result in Google. Spend the time on making the steps themselves clear instead.

Should you remove existing FAQ schema?

You don't have to. Google's 2023 post said structured data that isn't used doesn't cause problems for Search and has no visible effect. When the 2026 change was reported, Google's John Mueller commented that there was "no need to change anything, but if you did it for search, you can remove the markup if you want."

Reasons you might remove it anyway:

• Maintenance. Markup that duplicates on-page text has to be kept in sync. If answers change and the schema doesn't, you have conflicting versions of the same information.
• Page weight and clutter. Large FAQ blocks on every page add code nobody uses.
• Plugin cleanup. Many sites added FAQ schema through SEO or page builder plugins. Removing unused blocks can simplify things.

Reasons you might keep it:

• It's accurate and up to date. If the markup matches visible content and costs nothing to maintain, there's no harm in leaving it.
• Other consumers may read it. Structured data is a public vocabulary, and search engines and tools other than Google can parse it. Whether they use FAQPage for anything visible is up to them and changes over time, so don't rely on it.

What you shouldn't do is keep adding FAQ blocks to every page purely in the hope of rich results. That benefit has gone.

Is FAQ schema still worth adding in 2026?

For most small business sites, adding new FAQ schema is a low priority. Here's a quick way to decide:

The schema types that still produce visible features or help Google understand your business are a better use of time. For a local business, that usually means local business schema and accurate organisation details.

FAQ schema and AI search

Many people now ask whether FAQ schema helps with AI Overviews, AI Mode, ChatGPT search or similar tools. For Google, the answer is documented.

Google's page on AI features and your website says: "There are no additional requirements to appear in AI Overviews or AI Mode, nor other special optimizations necessary." It adds: "There's also no special schema.org structured data that you need to add." Among the general best practices, it lists "making sure your structured data matches the visible text on the page."

In other words, FAQ schema isn't a key to AI Overviews. What helps is the content itself:

• Real questions people ask, phrased the way they ask them.
• Direct answers in the first sentence or two, followed by detail.
• Answers visible on the page, not hidden in markup only.
• Accurate, current information, especially prices, rules and dates.
• Pages that can be crawled and indexed. AI features draw on pages in Google's index.

Other AI search tools have their own crawlers and their own ways of choosing sources. Our guide to getting content into AI Overviews goes into more detail, and the free AI crawler checker shows whether your robots.txt allows the main AI bots.

Are FAQ sections on pages still useful?

Yes, when they answer genuine questions. A well-written FAQ section can:

• deal with objections before someone calls ("Do you charge a call-out fee?")
• cover follow-up questions that don't fit the main flow of the page
• match how people phrase searches, including longer questions
• give AI and search systems a clear, quotable answer

What doesn't work is a generic FAQ block repeated across dozens of pages, or questions nobody asks written to squeeze in keywords. Those add length without helping anyone.

Writing a good FAQ section

1. Collect real questions. Look at enquiry emails, sales calls, live chat logs, reviews and the People Also Ask box for your main topics.
2. Answer the question in the first sentence. "Yes, we cover all LS postcodes" before any explanation.
3. Keep each answer self-contained. Someone might read only that answer.
4. Be specific. Prices, timeframes, areas covered, what's included.
5. Keep answers short. Around 40 to 80 words is plenty for most questions. Link to a full page for anything longer.
6. Review them regularly. Out-of-date answers do more harm than missing ones.

If you do add FAQPage markup

If you decide to keep or add FAQPage JSON-LD, for consistency or for other platforms, follow the basics that applied when Google supported it:

• Mark up only questions and answers that are visible on the page.
• Use it for FAQs written by you, not user-submitted questions with multiple answers (that's what QAPage was for).
• Don't use it for advertising.
• Keep the markup and the visible text identical.

A minimal example:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do you charge a call-out fee?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. We quote a fixed price before starting any work, and there's no charge for the visit itself."
      }
    }
  ]
}
</script>

Check it's valid with our schema markup validator. Note that, according to Google's announcement as reported, the Rich Results Test no longer reports on FAQ markup, so a general schema validator is the better check.

What to do now

1. Audit existing FAQ markup. Find which pages carry FAQPage schema and whether it matches the visible text.
2. Decide keep or remove based on maintenance, not fear. Neither choice hurts rankings.
3. Stop adding FAQ blocks for rich results. Add FAQ sections only where real customers have real questions.
4. Prioritise schema that still matters: Organization, LocalBusiness, Product, Article and Breadcrumb where they fit.
5. Improve the answers themselves, for readers and for AI search.

If your team is maintaining structured data by hand across many pages, it's worth building checks into your publishing workflow. Make It Flow helps healthcare clinics and other businesses design those workflows, with people approving anything that needs judgement. Get in touch if you'd like to talk it through.

FAQ

Does Google still show FAQ rich results?

No. Google's documentation stated that FAQ rich results would no longer appear in Google Search from 7 May 2026, and the FAQ documentation was removed in June 2026. Before that, since August 2023, they had only been shown for well-known, authoritative government and health websites.

Should I remove FAQ schema from my website?

You don't need to. Google has said unused structured data doesn't cause problems, and John Mueller said there's no need to change anything, though you can remove it if you added it only for search. Remove it if it's hard to keep in sync with your content; otherwise it's fine to leave.

Is HowTo schema still supported by Google?

No. Google restricted HowTo rich results to desktop in August 2023, then stopped showing them on desktop in September 2023 and described the result type as deprecated. HowTo markup no longer produces a rich result in Google Search, so clear, well-structured steps on the page matter more than the markup.

Does FAQ schema help with AI Overviews?

Google says there's no special schema.org structured data needed to appear in AI Overviews or AI Mode, and no special optimisation beyond normal SEO best practice. Clear, visible questions and direct answers on the page are what matter. If you use structured data, Google says it should match the visible text.

When did Google limit FAQ rich results?

Google announced on 8 August 2023 that FAQ rich results would only be shown for well-known, authoritative government and health websites, and would no longer be shown regularly for other sites. HowTo rich results were cut back in the same announcement. The remaining FAQ rich results were then removed entirely in May 2026.

Are FAQ sections still good for SEO?

Yes, when they answer real questions. A good FAQ section handles objections, covers follow-up questions and gives clear, quotable answers that help readers and search systems. It's the content that helps, not the markup. Avoid generic FAQ blocks repeated across many pages or questions written only to include keywords.