FAQ Schema in 2026: What Changed, What to Do

Administrator in Search Engine Optimization Oct 20 / 1 week ago

Many older guides still tell you to add FAQ schema to every page to win an FAQ rich result in Google. In 2026 that advice is a mistake. Google stopped showing the FAQ rich result in early May 2026 and removed its documentation in June 2026. This guide explains what changed, what the FAQPage type still is and is not for, and what to do with the markup you already have. The examples are fictional and come from Denver, Berlin, Dublin and Seoul.

What happened to FAQ rich results in Google Search?

Google stopped showing FAQ rich results in Search starting in early May 2026, and it added a deprecation notice to the documentation that month. In June 2026 it removed the FAQ rich result documentation because the feature no longer appears. The old documentation page now sends visitors to the Search Central updates page.

The decline started years earlier, in September 2023, when Google updated its FAQ documentation to say the feature is only shown for well-known, authoritative government and health websites. In the same update it removed the How-to documentation, because that rich result was no longer shown in search results. For a typical business site, the FAQ feature was already gone by then, and the May 2026 change ended it for everyone. Each entry is listed in the Google Search Central documentation updates. Google keeps trimming other types too. In November 2025 it said it was phasing out the practice problem and dataset types from Search results, as part of its effort to simplify the results page.

What is FAQ schema, and is it still valid markup?

FAQ schema means the FAQPage type from schema.org. Schema.org still defines FAQPage as a type of WebPage that presents one or more frequently asked questions. The markup is still valid vocabulary. What changed is that Google no longer lists FAQ among the structured data features it supports in Search.

A type can stay valid on schema.org even after Google stops using it for a visual feature. You can read the current definition on the schema.org FAQPage page. Google's own list names types such as Article, Breadcrumb, Organization, Product, Q and A, Discussion forum, Review snippet, Video and Event, but FAQ and How-to are not on it. If you are new to the format, our JSON-LD schema markup guide explains how the code is written, so this post skips that part. The short version is that valid code is not the same as useful code in Google Search.

Is adding FAQ schema to every page still worth it?

No. Adding new markup to every page to win an FAQ rich result is a mistake, because Google no longer shows that result. The markup costs time to write, test and keep in sync with the page. If the only goal was the rich result, that time is better spent elsewhere.

Our take: do not add new FAQ markup expecting a Google rich result, because there is no such result left to win. Take a fictional dental clinic in Denver, Colorado. Years ago its agency added a block of five questions, with markup, to every service page. The clinic is not a well-known health authority, so those blocks stopped earning anything in Search long before May 2026. Yet the team still pays a developer to update them each time a price or policy changes. Do patients read those answers? If they do, the visible section stays, and if the same three answers repeat on every page, they go. Our medical practice SEO guide covers the wider picture for clinics like this one.

Does Google still support any question and answer markup?

Yes. Google's list of supported features still includes Q and A pages and Discussion forum markup. A Q and A page is one question followed by its answers, where users can submit answers. Discussion forum markup covers user posts followed by a threaded or non-threaded discussion. Neither one is a replacement for a site-written FAQ.

Google also keeps an Education Q and A feature that helps students discover flashcards. In March 2026 it added more supported properties for Discussion Forum and QA Page markup, to clarify how comment threads are structured. A fictional SaaS company in Berlin runs a community forum where customers ask setup questions and other customers reply. Each thread focuses on one question that anyone can answer, so it fits QAPage. The same company's pricing FAQ, written by its own staff, does not.

Can you swap FAQPage for QAPage markup?

No. Google says not to use QAPage markup for FAQ pages or for pages with several questions. QAPage is for a page focused on a single question where users can submit answers. An FAQ page written by the site itself, with no way for users to add answers, is listed as an invalid use.

One tempting shortcut after the change is to relabel the old FAQPage block as QAPage and hope for a new result in Search. Google's QAPage guide rules it out in plain words, and it also lists other invalid uses, such as a how-to guide, a blog post or an essay that answers a question. Relabeling is the same mistake in new clothes, and it leaves you with markup that does not describe the page. If you already did this, our structured data debugging guide shows how to find and clean up the affected pages.

Which structured data types are still worth your time in 2026?

Spend effort on types that still appear in Google's list of supported features and match your pages. For many business sites that means Product, Review snippet, Breadcrumb, Article and Organization. Each one has its own rules, and Google does not guarantee that any of them will show, so pick the ones that fit your content.

The table below shows where common types stand today.

The status column is based on the Google Search Central documentation and its changelog. For the types still listed, start with product schema for ecommerce, then read about review snippets and star ratings and breadcrumbs and BreadcrumbList. Publishers should also see our article schema guide, and every brand can use our organization schema guide. Test any new Product or Breadcrumb block in the Rich Results Test before it ships. In our view, one correct Product block on a real product page is worth more than a dozen question blocks that nobody reads.

Do AI Overviews need FAQ markup?

No. Google's guide to generative AI features says structured data is not required for generative AI search, and there is no special schema.org markup you need to add. It still calls structured data a good idea for overall SEO, because it helps pages become eligible for rich results.

The same guide lists things you can skip for Google Search, such as chunking content into tiny pieces, creating special AI text files, or rewriting pages just for AI systems. To show up in AI Overviews or AI Mode at all, a page must be indexed and eligible to show in Search with a snippet. Read the full Google guide to optimizing for generative AI features before you pay for any AEO service. Our guide to ranking in AI search covers the wider strategy, and our Generative AI report guide shows how to measure it in Search Console. We make no claim that FAQ markup changes how often AI features cite a page, because Google does not say so.

Should you keep or remove the FAQ markup you already have?

Our take: keep a valid FAQPage block if it matches visible questions and answers and costs nothing to maintain, since other tools may still read schema.org types. Remove it when the questions are hidden, stale or auto-generated. Either way, stop counting on it for a Google rich result.

The changelog does not say what to do with leftover FAQ code, but it does hold a useful precedent. When Google dropped its video carousel test in April 2024, it wrote that you can leave that markup on your site so search engines and other systems can better understand the page. Google did not repeat that note for FAQ, so treat it as a hint, not a promise. A fictional shop in Dublin found an old plugin that printed eight questions into the markup but showed only three on the page. That mismatch is the part to fix first, whatever you decide about the rest.

How do you audit the FAQ sections on your site?

Start with a list of every page that carries the FAQPage type or a visible FAQ block. Check that each marked-up question appears on the page, that answers are current, and that the questions help readers. Then decide page by page whether to keep, rewrite or remove the block.

The Berlin SaaS team ran this checklist across its help center in one afternoon.

• Every marked-up question and answer is visible on the page.
• The answers match current prices, policies and product details.
• No block is copied word for word across many pages.
• Each question is one a real customer has asked.
• Thin auto-generated blocks are turned off at the source.
• New markup work goes to types Google still lists.

Our take: delete thin auto-generated FAQ blocks rather than polish them, because a block that adds nothing a reader needs is clutter with or without markup. Our content refresh and pruning guide shows how to decide what stays and what goes.

What do Google's general structured data rules still require?

The general guidelines still apply to every type you keep. Markup must be a true picture of the visible main content. Do not mark up content that readers cannot see, or content that is irrelevant or misleading. Do not block the pages from Googlebot, and remember that Google does not guarantee a rich result.

Violations can lead to a manual action. Google says a structured data manual action means the page loses eligibility for rich results, but it does not change how the page ranks in web search. You can check for one in the Manual Actions report in Search Console, and our manual actions recovery guide explains the fix and the review request. The Rich Results Test and URL Inspection catch many technical errors, while quality problems such as misleading content are harder for a tool to spot. Our Search Console guide covers the reports if they are new to you.

Are visible FAQ sections still good for readers?

Yes, when the questions are ones your readers ask. A clear FAQ section answers doubts fast, and it does that with or without a rich result. Google's AI guide asks for content organized in sections with clear headings for people, and a good FAQ fits that pattern.

Our advice: write the questions your support inbox gets, answer them in plain words, and stop. The fictional Dublin shop cut its product page FAQ down to the questions about delivery, returns and sizing that customers send by email. If you want to compete for answer boxes, our featured snippets and People Also Ask guide covers those features on their own terms. Our zero-click search guide explains why a clear answer on your page still matters. Our take: trust comes from the content itself, as our E-E-A-T and helpful content guide explains.

How should a business in Seoul plan its FAQ content?

A business in Seoul, South Korea should apply the same Google rules: no new FAQPage blocks aimed at a rich result, and visible answers only where they help. Our take: Google is not the only engine that matters there, so plan separate work for Naver and for Korean language content.

A fictional skincare brand in Seoul, South Korea sells to shoppers at home and in the US. Its Korean pages get their own question list, built from what Korean customers ask rather than translated word for word. The team reads our Naver SEO guide for Korea before deciding what else that engine needs. This post makes no claim about how Naver handles FAQPage, because none of our sources cover it.

Across Denver, Berlin, Dublin and Seoul, the lesson holds. The FAQ rich result is gone, and chasing it with new markup is the mistake to avoid. Keep the questions that help people, keep any markup honest, and put fresh schema work where Google still uses it.

Frequently asked questions about faq schema

Do FAQ rich results still show for government or health sites?

The September 2023 update limited the feature to well-known, authoritative government and health websites. The May 2026 changelog entry then said the FAQ rich result would no longer appear in Google Search, and the June 2026 entry removed the documentation because the feature is no longer shown. Neither later entry lists an exception for those sites. Plan as if the feature is gone for everyone, including public agencies and large hospitals.

Will leftover FAQPage code hurt my site?

The changelog entries that retired the feature do not mention any penalty for leftover markup, and they do not tell you to remove it. The general guidelines still apply, though, so markup must match visible content and must not mislead. Our take: the risk sits in mismatched or hidden questions, not in the type itself. Fix any mismatch first, then decide calmly whether the rest is worth keeping.

Which other rich results has Google retired?

Several. Google removed the How-to documentation in September 2023 because that result was no longer shown. In September 2025 it removed the docs for course info, estimated salary, learning video, special announcement and vehicle listing. The practice problem docs went in January 2026, and dataset markup now serves only Dataset Search. The sitelinks search box docs were removed in November 2024. The pattern is clear, so check the changelog before you invest in any type.

Can a support forum use QAPage instead?

Yes, if each page focuses on one question and users can submit answers. Google lists a forum page and a product support page with user answers as valid uses. The page needs one Question nested under mainEntity, with at least one answer, either accepted or suggested. Pages on the forum that are not questions are not eligible for the markup. In short, use it only where your community writes the answers.

Where can I see how my pages do in AI features?

Google points site owners to the Generative AI performance report in Search Console. It shows how people find your content through generative AI features in Google Search and Discover. Google also warns that no third-party tool has access to its internal ranking or AI systems. Use outside tools if they help your workflow, but weigh their advice against the official guidance. Pair the report with your normal Performance report to see the full picture.

Why does this post still have an FAQ section?

Because these are questions readers still ask after the main guide. There is a small irony here, because the FAQ rich result is gone, yet a visible FAQ still helps readers who scan for one answer. You are reading one right now. Write the section for people, keep each answer short and true, and skip the markup if its only purpose was the rich result. Questions copied from a keyword tool, with no real reader behind them, add little.

Should I write a separate page for every question variation?

No. Google's AI guide warns that creating content for every possible variation of a query, mainly to manipulate rankings or AI responses, violates its scaled content abuse policy. It also calls this an ineffective long-term plan, since a high number of pages does not make a site better. Group related questions on the page that answers them best, and let each page earn its place.

Should a CMS plugin keep adding FAQ blocks automatically?

Our take: switch off any setting that adds questions and markup to every post by default. Auto-generated blocks tend to repeat the same lines across many pages, which helps nobody. If your plugin builds the block from questions you write on purpose, it is fine to keep the visible section. Then check that the markup, if any, matches the page word for word. A quick review each quarter keeps the answers current.