Does FAQ Schema Still Work? Google Dropped FAQ Rich Results in May 2026. What to Keep, What to Remove, and a Script to Check Your Pages
Google stopped showing FAQ rich results on May 7, 2026, and has since removed the documentation and the Search Console report. FAQPage markup is still valid, but it no longer earns anything in Google. We checked 22 ranking pages and the top guides for "faq schema" to see who has caught up.
FAQ schema no longer earns a rich result in Google: Google stopped showing FAQ rich results for every site on May 7, 2026, after limiting them to government and health sites in 2023.
Google removed its FAQ structured data documentation in June 2026, and its deprecation notice said the Search Console report and the Rich Results Test's FAQ support would go the same month.
Google says there is no special schema.org markup needed to appear in AI Overviews or AI Mode, and that structured data should match the visible text on the page.
In our Nov. 18, 2026 check, 5 of 22 pages ranking for FAQ searches in the US, UK and Australia still carried FAQPage markup, and 2 of the 4 top guides we could read for "faq schema" did not mention that the rich result is gone.
Our view: keep FAQPage markup that matches a real, visible FAQ, remove markup with hidden or templated questions, and put the effort into question headings with direct answers.
FAQ schema no longer does anything visible in Google Search. Google stopped showing FAQ rich results, the expandable questions under a search result, on May 7, 2026, according to its documentation changelog, and removed the FAQ structured data documentation in June. The FAQPage markup itself is still valid Schema.org code, so it won't hurt a page, but adding it no longer earns a feature in Google.
That matters because "faq schema" still gets 720 searches a month in the US (DataForSEO, Nov. 18, 2026), and much of the advice that ranks for it was written before May. Below: what changed, what the markup still does, what we would keep or remove, and a script that checks any list of pages for it.
Does FAQ schema still work in 2026?
Not for Google's search results. Google wound the feature down in two steps:
August 2023: FAQ rich results limited to "well-known, authoritative" government and health websites. Everyone else lost them.
May 7, 2026: FAQ rich results no longer shown for any site. Google added a deprecation notice to its docs on May 8.
June 2026: Google removed the FAQ structured data documentation, because "the FAQ rich result feature is no longer shown in Google Search results." The deprecation notice said the FAQ search appearance, the rich result report in Search Console and FAQ support in the Rich Results Test would go in June 2026, and FAQ support in the Search Console API in August 2026.
So if you see FAQ questions under a result today, that is not markup at work. The old documentation page now redirects to the changelog entry.
Does FAQ schema help with AI Overviews, AI Mode or ChatGPT?
Google says no special markup is needed. Its AI features guide says "there's also no special schema.org structured data that you need to add" to appear in AI Overviews or AI Mode, and lists making sure your structured data "matches the visible text on the page" among its best practices.
We haven't found a statement from OpenAI, Perplexity or Microsoft that FAQPage markup affects whether a page is cited, and we haven't tested it. What a reader and any AI answer quoting the page both see is the visible text, so that is where the effort pays: a question as a heading and a direct answer in the next sentence. Our guides to getting cited by ChatGPT and ranking in AI Overviews cover that in detail.
Who still uses FAQ schema? We checked 22 pages
On Nov. 18, 2026 we pulled the Google results for "faq schema" (US) and the top five results for four FAQ searches: "passport renewal faq" and "mortgage faq" in the US, "flu vaccine faq" in the UK and "visa faq" in Australia, through DataForSEO. We skipped videos, forum threads, a PDF and a login page, and four pages that refused our request or served a bot challenge (HTTP 402, 403 and 404, and one Cloudflare challenge page). That left 22 pages, which we ran through the script below.
5 of 22 carried FAQPage markup: two SEO tool and agency pages about FAQ schema, a passport renewal guide, a South African marketing blog (in microdata) and a UK government flu vaccine factsheet with 11 questions.
In all four JSON-LD cases, every marked-up question also appeared in the visible text. That matches what Google's AI guide asks for.
17 of 22 had none, including both NHS pages, the CDC page and Australian government pages, the kind of sites that were still eligible until May.
Of the four top-ranking guides for "faq schema" whose text we could read, two say FAQ rich results stopped in May 2026. The other two, which still rank on page one, don't mention it. A fifth (WordLift) served our request a bot challenge instead of the page.
It's a small sample from one day, picked by search results rather than at random, so read it as a snapshot, not a census.
Should you remove FAQ schema from your site?
Our view, by case:
Real FAQ on the page, markup matches it: leave it. It costs nothing, it's still valid Schema.org, and other systems that read structured data may use it. Just don't expect anything from Google for it.
Questions in the markup that aren't on the page (hidden, templated across thousands of pages, or left over from an old design): remove them. Google's AI guide asks for structured data that matches visible text, and markup that doesn't is the kind of thing that ages badly.
Plugin adding FAQ markup to every post automatically: turn that off. A block of questions added only for a rich result that no longer exists helps nobody.
Planning to add FAQ schema for traffic: spend the time on the questions themselves instead. Write the question as a heading, answer it in the first one or two sentences, and keep the answer current.
How to add FAQ schema correctly, if you keep it
The markup is a FAQPage with one Question per item, each with an acceptedAnswer. In JSON-LD it looks like this:
faq-schema.json
{ "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [{ "@type": "Question", "name": "Does FAQ schema still work?", "acceptedAnswer": { "@type": "Answer", "text": "Not for Google rich results. Google stopped showing them on May 7, 2026." } }]}
Put it in a <script type="application/ld+json"> tag on the page that shows those questions, with the same wording as the visible text. The Rich Results Test no longer checks FAQ markup, so validate it with the Schema Markup Validator instead, which checks the code against the Schema.org vocabulary. If a single question gets answers from users (a forum thread), the type is QAPage, not FAQPage.
A script to check your pages for FAQ schema
This Node.js script (version 18 or later, no packages) takes a list of URLs and reports, for each one, whether it has FAQPage markup in JSON-LD or microdata, how many questions it marks up, and which of those questions it can't find in the page's visible text. It reads pages the way a crawler would, without running JavaScript, so markup that only appears after scripts run won't show up.
check-faq-schema.mjs
// check-faq-schema.mjs: for each URL, find FAQPage structured data (JSON-LD or// microdata), count its questions, and check each question appears in the// page's visible text. Node.js 18+, no packages. Usage:// node check-faq-schema.mjs https://example.com/faq https://example.com/pricingconst urls = process.argv.slice(2);const UA = 'Mozilla/5.0 (compatible; faq-schema-check/1.0)';const clean = s => s.replace(/<[^>]*>/g, ' ').replace(/ | /g, ' ') .replace(/&/g, '&').replace(/�?39;|’|’/g, "'").replace(/"/g, '"') .replace(/\s+/g, ' ').trim().toLowerCase();function faqNodes(data, out = []) { if (Array.isArray(data)) data.forEach(d => faqNodes(d, out)); else if (data && typeof data === 'object') { const t = [].concat(data['@type'] || []); if (t.includes('FAQPage')) out.push(data); Object.values(data).forEach(v => faqNodes(v, out)); } return out;}for (const url of urls) { let html; try { const res = await fetch(url, { headers: { 'user-agent': UA }, redirect: 'follow' }); html = await res.text(); if (!res.ok) { console.log(`${url}\n HTTP ${res.status}\n`); continue; } } catch (e) { console.log(`${url}\n fetch failed: ${e.message}\n`); continue; } const visible = clean(html.replace(/<script[\s\S]*?<\/script>|<style[\s\S]*?<\/style>/gi, ' ')); const questions = []; let badJson = 0; for (const m of html.matchAll(/<script[^>]*application\/ld\+json[^>]*>([\s\S]*?)<\/script>/gi)) { try { for (const faq of faqNodes(JSON.parse(m[1]))) { for (const q of [].concat(faq.mainEntity || [])) if (q && q.name) questions.push(String(q.name)); } } catch { badJson++; } } const microdata = /itemtype=["']https?:\/\/schema\.org\/FAQPage["']/i.test(html); console.log(url); if (!questions.length && !microdata) { console.log(` no FAQPage markup${badJson ? ` (${badJson} JSON-LD block(s) failed to parse)` : ''}\n`); continue; } if (microdata) console.log(' FAQPage in microdata (questions not counted)'); if (questions.length) { const missing = questions.filter(q => !visible.includes(clean(q).slice(0, 60))); console.log(` FAQPage JSON-LD: ${questions.length} question(s), ${missing.length} not found in visible text`); missing.slice(0, 3).forEach(q => console.log(` missing: ${q}`)); } console.log('');}
Save it, then run node check-faq-schema.mjs followed by the pages you want to check. A line that says "not found in visible text" is the one to fix or remove.
How we tested it: before the live run, we served three test pages from a local server: one with FAQPage inside an @graph holding a visible question and a hidden one, one with microdata only, and one with broken JSON-LD, plus a missing page. It found both questions and flagged the hidden one, spotted the microdata, reported the broken block and printed the 404. Then we ran it on the 22 pages above.
What we don't know yet
Google hasn't said whether it still reads FAQPage markup for anything else, such as understanding a page, and we found no statement from OpenAI, Perplexity or Microsoft on whether their AI answers use it. Schema.org still lists the type, so the markup won't break. If any of them says it uses FAQ markup, we'll update this guide.
Kiran runs Kihan Marketing, a web design, SEO and ads agency, and manages dozens of websites across real estate, home services and healthcare. He writes about SEO, AI search and paid ads news, and what it means for the people who run websites.