FAQPage Schema

TL;DR — FAQPage schemaFAQPage schema (schema.org/FAQPage) is structured data for a page's frequently-asked-questions content. It used to make pages eligible for an expandable FAQ rich result in Google Search, but Google fully removed that rich result on May 7, 2026 — the markup itself stays valid schema.org vocabulary, Google says it still reads it for understanding, and Bing has announced no equivalent removal. is code you add to a page with a frequently-asked-questions section — it labels each question and its answer for search engines. It used to make Google show an expandable list of your questions right in the search results (the “FAQ rich result”). Google took that feature away for everyone on May 7, 2026. The markup itself is still fine to keep — Google’s policy is that it doesn’t cause any problems and Google says it still reads it — but it no longer earns you that extra spot in search.

What FAQPage schema is

If a page has a “Frequently asked questions” section, a human can tell the questions from the answers just by reading. A search engine sees plain text. FAQPage schema spells it out in code, using the shared schema.org vocabulary: “this is the page’s FAQ,” “this is a question,” “this is its answer.”

It’s almost always written as JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. — a small block of code that sits in the page without changing how the page looks.

Why people added it — and what changed

For years, valid FAQPage markup could earn a FAQ rich result: Google would show your questions as an expandable list directly under your search listing, taking up more space on the page. That’s why FAQ schema got so popular.

Here’s the part that matters most in 2026: that rich result is gone. Google phased it out in stages —

• August 2023 — Google limited the FAQ rich result to well-known government and health websites. Most sites stopped seeing it.
• May 7, 2026 — Google removed it entirely, for everyone, including those government and health sites.

So today, Google does not list FAQPage among its current supported rich-result types. Valid Schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. markup and Google rich-result eligibility are separate questions. Evidence for this claim Google's current search gallery and FAQ documentation determine whether FAQ markup has a supported Google rich-result treatment. Scope: Google Search feature status; valid Schema.org markup can exist without a corresponding Google rich result. Confidence: high · Verified: 2026-07-14 Google: Structured data search gallery

Should you remove your FAQ schema?

Probably not — but it’s worth checking a few things, not just taking “Google said it’s fine” at face value. Google’s standing rule is that structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. it no longer displays doesn’t cause any problems and there’s no penalty for leaving it in place, and Google says it still reads structured data generally to help understand pages. Treat that as Google’s stated policy rather than something re-confirmed specifically for FAQPage in this pass.

Before you decide, check:

• Is the markup still true? If your FAQ content changed and the schema didn’t keep up, fix or remove it — stale markup that misrepresents the page is the wrong call regardless of any rich result.
• Does anything besides Google still use it? Non-Google systems may still read FAQPage markup even though Google’s rich result is gone — a reason to keep it, not a reason to remove it.
• Is the upkeep worth it? If keeping the markup in sync with the page is real ongoing work and you’re confident nothing meaningful reads it in your case, removing it is a legitimate call too.
• What else could that time do? Effort spent maintaining unused FAQ markup might be better spent elsewhere — a business tradeoff, not a penalty-avoidance one.

What you shouldn’t do is add FAQ schema now expecting the old rich result. That reward doesn’t exist anymore.

Two quick things that trip people up

• Google isn’t the whole web. Bing hasn’t announced any equivalent restriction or removal of its own — but that’s an absence of an announcement, not direct confirmation that Bing is currently displaying FAQ rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. for you. Treat it as “no known Google-style removal,” not a guarantee.
• FAQPage is not the same as QAPage. FAQPage is for your questions and answers (one authoritative answer each). QAPage is for community Q&A where users post multiple competing answers (think forum threads) — and QAPage is still supported by Google. Don’t mix them up.

Want the exact dates, the JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. structure, the FAQPage-vs-QAPage breakdown, the “does it help AI searchAI search uses large language models and retrieval-augmented generation (RAG) to synthesize an answer from multiple sources rather than returning a ranked list of links. Examples include Google AI Overviews, ChatGPT Search, and Perplexity.” data, and clear keep-or-remove guidance? Switch to the Advanced tab.

TL;DR — schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor./FAQPage markup (mainEntity → Question → acceptedAnswer → Answer.text) once made a page eligible for Google’s expandable FAQ rich result. Google restricted it to authoritative government and health sites on August 8, 2023, then fully removed it for everyone — including those gov/health sites — on May 7, 2026. Google’s own FAQ tooling wound down on a staggered schedule: the FAQ search-appearance filter, rich result report, and Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test support stopped in June 2026; Search Console APIA set of REST APIs that let you programmatically read and manage Google Search Console data for properties you've verified — Performance data, URL index status, sitemaps, and properties — authorized with OAuth 2.0. support is scheduled to drop in August 2026 and hadn’t happened as of this update. Critically, the FAQPage type is not deprecated — it’s still valid markup, Google says it keeps parsing it for page understanding, and there’s no penalty for leaving it in. Bing has announced no equivalent restriction or removal — that’s an absence of an announcement, not independent confirmation Bing is actively displaying FAQ rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. today. FAQPage ≠ QAPage (community Q&A, still supported, with a March 24, 2026 supported- properties update). The “FAQ schema boosts AI citationsAn AI citation is the visible source link an AI answer engine shows next to its generated text — the clickable reference that credits the web page it used. A citation's presence is a separate thing from whether the cited page actually supports the statement, and from being retrieved (read behind the scenes) or merely mentioned (named without a link); citation is driven more by brand mentions and being retrievable than by traditional ranking.” claim is unproven — the one dataset I could verify foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. a statistically insignificant change, not a meaningful effect either way. My call: leave existing markup, don’t chase the dead rich result, judge new FAQ content on its own merits.

The central question: is FAQ schema still worth doing?

This is the question almost everyone lands on this topic asking in 2026, so I’ll answer it up front and then justify it:

• The FAQ rich result is gone — fully removed from Google Search on May 7, 2026, for every site.
• The FAQPage schema type is not deprecated. It’s still valid schema.org vocabulary, Google says it still parses it to understand your page, and there’s no penalty and no need to remove it.
• So don’t panic-delete existing markup, and don’t add new FAQ schema expecting the old SERP enhancement — that reward no longer exists. Evaluate FAQ content on its on-page/UX value, not on a schema-ROI case that’s now moot in Google.

Everything below is the detail behind that.

TIP Separate valid FAQPage markup from a retired Google feature

The vocabulary can remain valid while the display feature is gone. Check the current feature status before treating a clean schema validation as evidence of rich-result eligibility.

Paste the live page or JSON-LD into my eligibility checker to see the detected type and its current Google feature status. Rich-Result Eligibility Checker Free

1. Confirm the checker detects FAQPage and that the visible questions and answers match the markup.
2. Read the feature status and verification date separately from schema.org validity.
3. Keep accurate markup if it still serves your systems, but remove the retired Google display from forecasts and reporting expectations.

Tap to enlarge

The full timeline — how FAQ rich results were phased out

The single thing most competing articles get loose on is the dates. Here’s the precise version. Google didn’t remove FAQ rich results in one move — there were three distinct stages:

August 2023 — restricted to government and health sites

Google’s Changes to HowTo and FAQ rich results blog post (August 8, 2023) drew the line: going forward, FAQ rich results from FAQPage structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. would only be shown for well-known, authoritative government and health websites, and for all other sites the rich result would no longer be shown regularly. (This was reported contemporaneously by Search Engine Journal, which quoted the post directly.) The reason, per Google’s framing and industry summaries of it, was abuse: sites bolting on artificial FAQ sections purely to grab more SERP real estate, with questions that didn’t match intent and “answers” that existed only to occupy pixels.

This is where a lot of stale content — and, until recently, even this site’s own structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. hub — got stuck: describing the 2023 gov/health state as if it’s still the current state. It isn’t.

May 7, 2026 — fully removed for everyone

On May 7, 2026, Google removed the FAQ rich result entirely. The gov/health carve-out from 2023 went away with it — nobody sees a FAQ rich result in Google now. Google added a deprecation notice to the FAQPage documentation, and coverage from Search Engine Land and Search Engine Journal captured the notice verbatim. Google’s own documentation changelog also logged a separate, later entry — dated June 15, 2026 — describing removal of the dedicated FAQ rich-result documentation itself, a distinct step from the May 7 display change. The general FAQPage structured-data reference page (linked in Official Docs below) still exists as of this writing, so read this as Google retiring a standalone FAQ guide, not every FAQ-related doc page disappearing.

June–August 2026 — Google retires its own FAQ tooling

Removing the SERP featureSERP features are any element on a search results page beyond the classic ten blue links — featured snippets, People Also Ask, knowledge panels, sitelinks, image and video packs, AI Overviews, and structured-data-driven rich results. Google documents that losing rich-result eligibility doesn't affect ranking; their SEO relevance is CTR (they redistribute clicks). Some are unlocked by markup; most are purely algorithmic. is one thing; Google also wound down the reporting and testing infrastructure around it on a staggered schedule, which is what the deprecation notice spelled out. Per Google’s notice:

“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. To allow time for adjusting your API calls, support for the FAQ rich result in the Search ConsoleGoogle's free tool for monitoring crawling, indexing, and search performance. API will be removed in August 2026.”

So the Rich Results Test and Search Console’s FAQ report/filter stopped covering FAQ in June 2026. The Search Console API is scheduled to drop FAQ support in August 2026 — as of this update that change hadn’t taken effect yet. If a script of yours already returns nothing for the FAQ search-appearance type in Search Console’s UI, that’s the June change; expect the API call itself to stop returning FAQ data once August 2026 arrives.

What Google says now — the markup is not deprecated

This is the distinction the whole topic hinges on, and it’s where the lower-quality coverage goes wrong: “Google stopped displaying it” is not the same as “the markup is now wrong / harmful / against guidelines.”

Google’s own deprecation-notice wording is about the feature — the rich result — not the vocabulary. The FAQPage, Question, and Answer types remain valid schema.org markup. Google has been consistent that it keeps reading structured data to understand pages even when it no longer produces a visible result, and that its standing policy is: structured data that isn’t being used doesn’t need to be proactively removed and doesn’t cause problems for Search. (I’d point at a primary Search Central line for that exact sentence, but the cleanest version of it in my research was captured secondhand — treat it as the well-established Google policy it is rather than a fresh verbatim quote.)

There’s a broader rep signal here too. When people saw the FAQ removal alongside a run of other structured-data type retirements, John Mueller pushed back on the “schema is dying” framing, saying Google is not killing schema — the supported set gets trimmed of old or redundant types while the ones that meaningfully help Search are kept, more haircut than funeral (reported by Search Engine Roundtable). One caveat I want to be straight about: that comment appears to be about the broader wave of structured-data retirements, not FAQPage specifically, so I’m treating it as general context on Google’s posture toward schema — not as FAQ-specific commentary.

Bottom line from Google’s side: no penalty, no need to remove, still parsed for understanding — just no rich result.

FAQPage structure and example JSON-LD

The markup itself hasn’t changed; it’s worth knowing regardless, because it’s still valid schema.org vocabulary and Bing has announced no equivalent removal. This is a statement about schema.org validity, not a claim about current Google rich-result eligibility — that feature is gone. The minimum valid structure is:

FAQPage → mainEntity (an array of Question items) → each Question has a name (the question text) and an acceptedAnswer (an Answer whose text holds the answer, which may include some basic HTML like links).

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Do I need to remove FAQPage schema now that the rich result is gone?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. The rich result is gone, but the FAQPage markup is still valid, causes no problems, and Google still reads it. There's no penalty for leaving it in place."
      }
    },
    {
      "@type": "Question",
      "name": "Has Bing made the same change to FAQ rich results as Google?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. Bing has not announced any equivalent restriction or removal — this is a Google-specific change."
      }
    }
  ]
}

A few property notes: mainEntity is inherited from CreativeWork and holds the array of questions; Question (schema.org/Question) also documents answerCount and suggestedAnswer, but for FAQ you want a single acceptedAnswer per question; the answer body lives in Answer.text. That single-authoritative-answer shape is exactly what distinguishes FAQPage from QAPage. Evidence for this claim FAQPage uses Question entities and acceptedAnswer Answer entities to represent publisher-authored questions and answers. Scope: Schema.org vocabulary; QAPage models a different community-answer use case. Confidence: high · Verified: 2026-07-14 Schema.org: FAQPage

FAQPage vs. QAPage — don’t confuse them

This is the freshest, most useful distinction to get right, because a lot of coverage smears “FAQ schema” and “Q&A schema” together, and they are different types with different eligibility:

If your page is genuinely a community Q&A with multiple user-submitted answers, that’s QAPage — a separate, still-supported type — not FAQPage. Reaching for QAPage on a page you control and answer yourself is just as wrong as reaching for FAQPage on a forum thread. This distinction is why FAQPage sits in the Social & Community schema group alongside QAPage and DiscussionForumPosting: they’re the “who’s doing the talking” family of types, and only some of them lost their rich result.

QAPage isn’t just theoretically still around, either: Google’s own documentation changelog recorded an update to QAPage’s supported properties on March 24, 2026 — a sign the type is actively maintained, not a stale leftover. That’s a different claim than “QAPage will show a rich result for your specific query” — confirm current eligibility for your own pages with the Rich Results Test rather than assuming blanket support.

Does FAQ schema still help with AI search or AI Overviews?

Here’s a claim I see everywhere with zero evidence behind it: “FAQ schema boosts your AI Overview / LLMA large language model (LLM) is a deep-learning model trained on massive text corpora to predict the next token and generate human-like text. LLMs use the transformer architecture and power AI search features like Google's AI Overviews (Gemini) and Bing Copilot (GPT-4). citations, so it’s worth doing for that reason alone.” Be skeptical.

There’s no confirmed Google linkage between FAQ structured data and AI Overview inclusion. Google says no special Schema.org markup is required for AI OverviewsAI Overviews are the AI-generated summary box Google shows above or within its regular search results, written by Gemini models from pages retrieved out of Google's normal Search index. It's a Search feature, not a separate platform or index. or AI Mode. Evidence for this claim Google says there is no special Schema.org markup required to appear in AI Overviews or AI Mode. Scope: Google Search AI-features guidance; FAQPage markup should not be presented as a confirmed AI-citation lever. Confidence: high · Verified: 2026-07-14 Google: AI features and your website The best data point I found doesn’t support an AI-citation lift either: an Ahrefs test reported by Search Engine Journal measured ChatGPT citations across roughly 1,885 pages before and after adding schema markup (pooling multiple schema types together, not testing FAQPage specifically) and found only a +2.2% change — small enough that the researchers themselves called it “too small to tell apart from random variation.” I’d treat that as a null result, not evidence of a lift or a penalty, and it isn’t an FAQPage-specific test. Either way, it’s enough to knock down the confident “FAQ schema is an AI-citation lever” assertion — the data doesn’t support it.

The distinction that actually holds up: well-structured Q&A content — clear questions, direct answers, scannable format — genuinely helps LLMs extract and reuse your material, and it helps human readers too. That value comes from the content and its structure on the page, and LLMs can read it whether or not it’s wrapped in FAQPage JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal.. The FAQPage markup itself has no demonstrated AI-citation lift. Write good FAQ content; don’t do it for the schema.

Does Bing still use FAQ schema?

This is a Google-specific change, not an industry-wide one. Bing has not announced any restriction or removal of FAQ rich results, and industry reporting in 2026 says Bing (and the engines on its index, like DuckDuckGo and Brave Search) continues to process FAQPage markup — though I haven’t independently reconfirmed that against a Bing-owned primary source in this pass, so treat it as industry-reported rather than Bing-official. Bing doesn’t publish a standalone FAQ rich-result spec page — it supports the shared schema.org vocabulary through its general structured-data documentation — so the accurate framing is “no deprecation announced by Bing,” not “Bing currently shows FAQ rich results for every query,” which isn’t something this pass independently verified.

Fabrice Canel, Principal Product Manager at Microsoft Bing, has separately confirmed — in the broader structured-data context — that schema markupSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. helps Microsoft’s LLMs and Copilot understand content (via Search Engine Land), which is already cited on this site’s structured data hub. That’s general, not FAQ-specific, but it’s a fair reason not to assume FAQ markup is “dead everywhere” just because Google stopped displaying it.

What FAQPage schema is still good for

Strip away the rich result and there’s still a real, if smaller, case for FAQ content (note: content, not necessarily the markup):

• On-page UX. A clean FAQ section lets users scan for the objection or detail that’s blocking them, which matters most right before a conversion.
• Internal linkingLinks between pages on the same site.. Answer.text accepts basic HTML, so answers can link out to your deeper pages — a legitimate way to route authority and readers.
• Content organization for humans and machines. Structured Q&A is easy for people to read and easy for engines and LLMs to parse — even without a Google rich-result reward, and potentially in Bing too, where no equivalent removal has been announced.

So: keep your existing FAQPage markup (it’s harmless and Google says it still reads it), keep writing genuinely useful FAQ content where it serves readers, and just stop treating the Google FAQ rich result as a reason to do either — because it’s gone.

For where FAQPage sits in the wider picture, see the broader Structured DataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. and Schema Markup hubs this article nests under, and the QAPage schemaQAPage schema (schema.org/QAPage) is structured data for a page built around a single question with community-submitted answers — like a forum's solved thread or a Stack Overflow page — so Google can show it as a Q&A rich result. It's distinct from FAQPage (which is site-owner-authored) and, unlike FAQPage, remains an active, supported rich result as of mid-2026. sibling for the community-Q&A side of this family.

AI summary

A condensed take on the Advanced version:

• What it is: schema.org/FAQPage markup (usually JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal.) that labels a page’s FAQ content — mainEntity → Question (with name) → acceptedAnswer → Answer.text.
• The core answer: the FAQ rich result is gone, but the FAQPage type is not deprecated — still valid, Google says it still parses it for understanding, no penalty and no need to remove it.
• Exact timeline (three stages): Aug 8, 2023 restricted to authoritative gov/health sites → May 7, 2026 fully removed for everyone (gov/health included) → June 2026 FAQ search-appearance filter, rich result report, and Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test support dropped → August 2026 Search Console APIA set of REST APIs that let you programmatically read and manage Google Search Console data for properties you've verified — Performance data, URL index status, sitemaps, and properties — authorized with OAuth 2.0. support scheduled to drop (not yet in effect).
• Google’s stance: the deprecation notice is about the feature, not the vocabulary; Mueller says Google is “not killing schema” (that comment reads as general, not FAQ-specific).
• Bing: no equivalent restriction or removal announced — that’s an absence of an announcement, not confirmed current display. Google-specific change, not industry-wide.
• FAQPage ≠ QAPage: FAQPage = page-owner content, one accepted answer, rich result removed; QAPage = community Q&A, multiple answers, still supported. Different types, different use cases.
• AI-citation myth: unproven — an Ahrefs test (via SEJ) pooling schema typesSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. across ~1,885 pages foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. only a +2.2% ChatGPT-citation change after adding schema, small enough that the researchers called it indistinguishable from random variation (not an FAQPage-specific test). The value is in well-structured Q&A content, which LLMsA large language model (LLM) is a deep-learning model trained on massive text corpora to predict the next token and generate human-like text. LLMs use the transformer architecture and power AI search features like Google's AI Overviews (Gemini) and Bing Copilot (GPT-4). read with or without the markup — not the markup itself.
• Still good for: on-page UX, internal linkingAn internal link is a hyperlink from one page on a website to another page on the same website. Internal links help search engines discover your pages and pass ranking signals (PageRank and anchor-text context) between them. (answers accept basic HTML), and content organization — plus a chance at Bing rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show., since no equivalent removal is announced there.
• My advice: leave existing markup in place, don’t chase the dead Google rich result, judge new FAQ content on its on-page merits.

Official documentation

Primary-source documentation and the change record.

Google

• FAQPage (FAQ) structured data — the FAQPage reference, now carrying the deprecation notice for the FAQ rich result.
• Changes to HowTo and FAQ rich results (Aug 8, 2023) — the original restriction to government and health sites.
• Structured data general guidelines — the standing policy that unused/no-longer-displayed structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. doesn’t need to be removed and causes no problems.
• Rich Results Test — still validates FAQPage as valid markup, but no longer reports FAQ rich-result eligibility (that support was dropped June 2026).

schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor.

• FAQPage — a WebPage presenting one or more frequently-asked questions; hierarchy Thing > CreativeWork > WebPage > FAQPage.
• Question — the Question type with acceptedAnswer, answerCount, and suggestedAnswer.
• QAPage — the different type for community Q&A pages, so you can see the contrast.

Bing / Microsoft

• Marking up your site with structured data — Bing’s general structured-data support (schema.org, JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal.). No FAQ-specific removal announced.

Quotes from the source

On-the-record statements, with deep links where the source page exposes the text.

Google — the deprecation notice

• “FAQ rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. are no longer appearing in Google Search. We will be dropping the FAQ search appearance, rich result report, and support in the Rich resultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. test in June 2026. To allow time for adjusting your API calls, support for the FAQ rich result in the Search Console APIA set of REST APIs that let you programmatically read and manage Google Search Console data for properties you've verified — Performance data, URL index status, sitemaps, and properties — authorized with OAuth 2.0. will be removed in August 2026.” — Google Search Central, FAQPage documentation deprecation notice. Jump to coverage

Google — the August 2023 restriction

• “Going forward, FAQ (from FAQPage structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding.) rich results will only be shown for well-known, authoritative government and health websites. For all other sites, this rich result will no longer be shown regularly.” — Google Search Central Blog, Changes to HowTo and FAQ rich results (Aug 8, 2023), as quoted by Search Engine Journal. Read the coverage

John Mueller, Google (general structured-data context, not FAQ-specific)

• Google is “not killing schema” — Google trims old or redundant markup types while keeping the ones that meaningfully help Search understand and display content. Read the coverage

FAQPage schema cheat sheet

The one-line answer

FAQ rich result = gone in Google (May 7, 2026). FAQ markup = still valid, Google says it still reads it, no penalty, no need to remove. Bing: no equivalent change announced.

The removal timeline

Minimum valid structure

FAQPage → mainEntity[] → Question { name, acceptedAnswer: Answer { text } }

FAQPage vs. QAPage

Fast facts

• The FAQPage type is not deprecated — only the rich result was removed.
• Google’s policy: unused structured dataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. causes no problems; no need to remove it.
• Bing: no equivalent change announced.
• AI-citation lift: unproven — an Ahrefs test (via SEJ) foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. only a +2.2% ChatGPT-citation change after adding schema (pooled across schema typesSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor., ~1,885 pages, not FAQPage-specific) — too small to separate from random variation.
• Don’t add FAQ schema expecting the old Google rich result — it’s gone for good.

Should I keep, remove, or add FAQPage schema?

Work down the questions:

FAQPage schema myths and mistakes to avoid

Myth: “FAQPage schemaFAQPage schema (schema.org/FAQPage) is structured data for a page's frequently-asked-questions content. It used to make pages eligible for an expandable FAQ rich result in Google Search, but Google fully removed that rich result on May 7, 2026 — the markup itself stays valid schema.org vocabulary, Google says it still reads it for understanding, and Bing has announced no equivalent removal. still gives everyone a rich result.” It doesn’t — the FAQ rich result was fully removed on May 7, 2026 for every site, including the government and health sites that briefly kept it after August 2023. Nobody gets a FAQ rich result in Google now.

Myth: “Google restricted FAQ to gov/health sites, and that’s still the current state.” That was the interim August 2023 state. The May 7, 2026 removal took it away even from those sites. A lot of older content — and this site’s own hub, before it was tightened — is stuck describing the 2023 situation as if it’s current.

Myth: “The FAQPage type is deprecated / against guidelines now — rip it out.” The rich result is gone; the schema type is not deprecated. It’s still valid schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor. markup, Google says it still parses it for understanding, Bing has announced no equivalent removal, and there’s no penalty for leaving it. Removing it isn’t required — it’s just busywork.

Myth: “FAQPage and QAPage are the same thing.” They’re distinct types with different eligibility. QAPage (community Q&A, multiple user-submitted answers) is a separate, still-supported Google rich result. Don’t use FAQPage for a forum thread, or QAPage for your own help-page FAQ.

Myth: “FAQ schema is a proven AI OverviewAI Overviews are the AI-generated summary box Google shows above or within its regular search results, written by Gemini models from pages retrieved out of Google's normal Search index. It's a Search feature, not a separate platform or index. / ChatGPT citation booster.” There’s no confirmed Google linkage, and an Ahrefs test (via SEJ) that pooled schema types across ~1,885 pages foundA 302 (\"Found\") is a temporary redirect: it forwards users to a new URL while telling search engines the original URL should stay in the index. It's a weak canonicalization signal, not the zero-equity dead end of SEO folklore. only a +2.2% ChatGPT-citation change after adding schema — small enough that the researchers called it indistinguishable from random variation, and it wasn’t an FAQPage-specific test. The value is in well-structured Q&A content — which LLMsA large language model (LLM) is a deep-learning model trained on massive text corpora to predict the next token and generate human-like text. LLMs use the transformer architecture and power AI search features like Google's AI Overviews (Gemini) and Bing Copilot (GPT-4). read regardless of markup — not in the FAQPage JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. itself.

Myth: “Since Google dropped it, no search engine cares about FAQ schema.” This is a Google-specific change. Bing (and DuckDuckGo/Brave on the Bing indexStoring a crawled page in the search index so it can appear in results. Crawled is not the same as indexed — Google selects what to keep, and indexing isn't guaranteed.) have announced no equivalent removal — treat it as an industry-wide death and you’re wrong.

Mistake: adding FAQPage schema to chase the old Google rich result. That reward no longer exists for anyone. If you’re adding FAQ content, do it for readers, for Bing, or for content clarity — not for a Google SERP enhancement that’s been removed.

Mistake: still querying the FAQ search-appearance type in the Search Console APIA set of REST APIs that let you programmatically read and manage Google Search Console data for properties you've verified — Performance data, URL index status, sitemaps, and properties — authorized with OAuth 2.0.. Support is scheduled to drop in August 2026 (the Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test and rich result report support already dropped in June 2026). If a monitoring script already returns nothing for FAQ in the report/filter, that’s the June change; expect the API call itself to stop returning FAQ data once August 2026 arrives — update your script ahead of that.

FAQPage in practice — right, wrong, and mis-typed

A valid FAQPage block (still fine to keep)

Page-owner Q&A, one authoritative answer per question, answers can carry basic HTML:

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "When did Google remove FAQ rich results?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Google restricted them to government and health sites on August 8, 2023, then removed them entirely for everyone on May 7, 2026."
      }
    },
    {
      "@type": "Question",
      "name": "Should I delete my FAQPage schema?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "No. It is still valid markup, Google says it still reads it, Bing has announced no equivalent removal, and there is no penalty for leaving it in place."
      }
    }
  ]
}

This validates and is harmless. It just won’t earn a Google rich result — that’s the only thing that changed.

The wrong type: this should be QAPage, not FAQPage

A forum thread where users post multiple competing answers is community Q&A — QAPage, not FAQPage. Marking it up as FAQPage misrepresents it (and FAQPage has no rich result to gain anyway):

{
  "@context": "https://schema.org",
  "@type": "QAPage",
  "mainEntity": {
    "@type": "Question",
    "name": "How do I fix a slow LCP on a WordPress site?",
    "answerCount": 3,
    "acceptedAnswer": {
      "@type": "Answer",
      "text": "The top-voted community answer..."
    },
    "suggestedAnswer": [
      { "@type": "Answer", "text": "Another user's answer..." }
    ]
  }
}

Note the differences: QAPage, an answerCount, and suggestedAnswer alongside the acceptedAnswer — the shape of community Q&A. QAPage is still a supported Google rich result; FAQPage isn’t. Pick the type that matches who actually wrote the answers.

The “why is my script empty?” case

If a Search Console APIA set of REST APIs that let you programmatically read and manage Google Search Console data for properties you've verified — Performance data, URL index status, sitemaps, and properties — authorized with OAuth 2.0. call or a Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test check for FAQ rich-result eligibility suddenly returns nothing, it’s not a bug in your markup:

• Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test / FAQ rich result report / FAQ search-appearance filter — support dropped June 2026.
• Search ConsoleA free Google service that reports how a site performs in Google Search and surfaces problems with how Google crawls, indexes, and serves it. It's first-party data straight from Google — but you don't need it to appear in results. API FAQ support — scheduled to drop August 2026 (not yet in effect as of this update).

The markup can still be perfectly valid; Google just no longer reports on a rich result it no longer shows. Update the script’s expectations rather than “fixing” the schema.

Tools for checking FAQPage markup

• Schema Markup Validator — paste the JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. or page HTML to confirm that the still-valid FAQPage vocabulary is well formed, each Question has a name, and each acceptedAnswer has text.
• schema.org Validator — use the vocabulary’s own validator as a second check when the question is whether the markup is valid schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor., not whether it can earn a Google feature.
• Bing Webmaster ToolsMicrosoft's free portal for monitoring and improving how a site appears in Bing search — the peer to Google Search Console, plus IndexNow instant indexing, richer backlink data, and keyword volumes. Because Bing's index also feeds Microsoft Copilot, it doubles as a window into AI-search visibility. Markup Validator — use Bing’s validator when Bing is the reason you are retaining or adding the markup. Google’s Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test no longer supports the removed FAQ rich result, so it is not the right pass/fail tool for FAQPage eligibility in 2026.

Test yourself: FAQPage Schema

Five quick questions on FAQPage schemaFAQPage schema (schema.org/FAQPage) is structured data for a page's frequently-asked-questions content. It used to make pages eligible for an expandable FAQ rich result in Google Search, but Google fully removed that rich result on May 7, 2026 — the markup itself stays valid schema.org vocabulary, Google says it still reads it for understanding, and Bing has announced no equivalent removal., the removal timeline, and how it differs from QAPage. Pick an answer for each, then check.

Resources worth your time

My writing on this topic

I haven’t published a standalone FAQPage schemaFAQPage schema (schema.org/FAQPage) is structured data for a page's frequently-asked-questions content. It used to make pages eligible for an expandable FAQ rich result in Google Search, but Google fully removed that rich result on May 7, 2026 — the markup itself stays valid schema.org vocabulary, Google says it still reads it for understanding, and Bing has announced no equivalent removal. guide of my own — this is genuinely fresh ground rather than a rewrite — so rather than point you at something that doesn’t exist, I’ll send you to the primary sources and the related structured-data work on this site. For the broader vocabulary and where FAQPage fits (including the full list of rich-result types Google has removed), see the Structured DataStructured data is a standardized way of labeling page content (using the schema.org vocabulary in JSON-LD, Microdata, or RDFa) so search engines can understand its meaning. It's not a direct ranking factor — its value is rich results and entity understanding. hub this article nests under; for the AI angle, Schema Markup for AISchema markup (structured data) is machine-readable code — usually JSON-LD — that labels what your content means using the schema.org vocabulary. For AI search it's infrastructure for entity disambiguation, not a direct citation lever: controlled studies found no meaningful uplift in AI citations from adding it..

From around the industry

• FAQPage (FAQ) structured data (Google Search Central) — the reference, now carrying the deprecation notice.
• Changes to HowTo and FAQ rich results (Google Search Central Blog, Aug 8, 2023) — the original restriction to government and health sites.
• Google to no longer support FAQ rich results (Search Engine Land) — the breaking-news piece with the deprecation-notice wording.
• Google Drops FAQ Rich Results From Search (Search Engine Journal) — independent corroboration of the notice, dates, and “markup stays valid” framing.
• SERP FAQ Removal & New Data Challenge Schema’s AI Search Value (Search Engine Journal) — the Ahrefs ChatGPT-citation test (~1,885 pages, +2.2% change, called statistically insignificant).
• The rise and fall of FAQ schema – and what it means for SEO today (Search Engine Land, Jenn Mathews) — the historical arc from the 2023 restriction onward.
• Google Is Not Killing Schema (Search Engine Roundtable) — Mueller’s pushback on the “schema is dying” framing (general, not FAQ-specific).
• FAQ Pages for SEO (+ Examples & Best Practices) (Ahrefs) — practical FAQ-content guidance beyond the markup.

FAQPage Schema

FAQPage schema (schema.org/FAQPage) is structured data for a page's frequently-asked-questions content. It used to make pages eligible for an expandable FAQ rich result in Google Search, but Google fully removed that rich result on May 7, 2026 — the markup itself stays valid schema.org vocabulary, Google says it still reads it for understanding, and Bing has announced no equivalent removal.

Related: Structured Data, QAPage Schema

FAQPage Schema

FAQPage schema is the schema.orgSchema markup is code that uses the schema.org vocabulary to label what your content means so search engines can understand it and show rich results. It's most often written in JSON-LD, and it's not a direct ranking factor./FAQPage vocabulary you add to a page — usually as JSON-LDJSON-LD (JavaScript Object Notation for Linked Data) is a script-based structured data format, typically paired with the schema.org vocabulary to describe page content for search engines and AI systems. Google recommends it over Microdata and RDFa because it's the easiest format to implement and maintain at scale — but all three work, and structured data isn't a ranking signal. — to mark up its frequently-asked-questions content. The structure is a mainEntity array of Question items, each with a name (the question text) and an acceptedAnswer (an Answer object whose text holds the answer).

Historically, valid FAQPage markup made a page eligible for an expandable FAQ rich result in Google Search. Google restricted that rich result to well-known, authoritative government and health sites on August 8, 2023, then fully removed it for everyone — including those gov/health sites — on May 7, 2026. Google’s own FAQ tooling wound down after that: the FAQ search-appearance filter, rich result report, and Rich ResultsRich results (formerly 'rich snippets') are enhanced search listings — stars, images, prices, breadcrumbs, video thumbnails, and more — that Google and Bing build from structured data. They're a display feature, not a ranking factor, and eligibility never guarantees they'll show. Test support stopped in June 2026, and Search Console APIA set of REST APIs that let you programmatically read and manage Google Search Console data for properties you've verified — Performance data, URL index status, sitemaps, and properties — authorized with OAuth 2.0. support is scheduled to drop in August 2026 (not yet in effect as of this update).

The key thing to keep straight: the rich result is gone, but the FAQPage type is not deprecated. It remains valid schema.org markup, Google says it still parses it to understand pages, and Bing has announced no equivalent restriction or removal — an absence of an announcement, not confirmed current display. FAQPage is also distinct from QAPage, which marks up community Q&A with multiple user-submitted answers and remains an actively maintained, still-supported Google type (its supported properties were updated March 24, 2026).

Related: Structured Data, QAPage Schema

Changelog