FAQ Rich Results Are Gone: Keep or Remove Schema?

FAQ rich results are gone. Your useful answers are not.

Google stopped showing FAQ rich results in Search on May 7, 2026. On June 15, Google removed the feature documentation because the result was no longer shown.

The retired feature was the expandable list of questions that could appear under a Google result. It was a Search presentation. It was not the text on your page, and it was not the entire Schema.org vocabulary.

Date	What Google changed	What it means for your site
August 2023	Google limited FAQ rich results mainly to authoritative government and health sites	Most commercial sites had already lost the expanded result
May 7, 2026	FAQ rich results stopped appearing in Google Search	No site should plan on winning that accordion
June 15, 2026	Google removed the FAQ rich-result documentation	FAQ is no longer in Google’s supported structured-data feature gallery

Schema.org still defines FAQPage as a type of web page that presents one or more frequently asked questions. A valid vocabulary type can exist without a current Google rich result.

That is why “Google removed FAQ schema” is the wrong summary. Google retired its FAQ rich result. Your next decision depends on whether the visible answers help people and whether the markup has a real consumer.

Make four decisions, not one.

An FAQ section can look like one feature on the page. Behind it are four separate things.

Layer	What it is	The decision now
Visible answer	The words a person reads	Keep it only when it is useful, specific and true
`FAQPage` markup	Machine-readable Schema.org code	Keep it only for a named consumer and a maintained answer
Google FAQ rich result	The expandable Search treatment	Retired; do not plan or report against it
Reporting and testing	Old FAQ-specific Search Console and test support	Remove stale filters, dashboards and API dependencies

This distinction prevents two expensive mistakes.

The first is paying someone to add new FAQPage code because an audit says the site is “missing schema.” The second is deleting useful buying information because the Google accordion is gone.

Google’s structured-data introduction says its own documentation is definitive for Google Search behavior. Schema.org contains a larger vocabulary that other services may use. Vocabulary validity and Google feature eligibility are not the same test.

The tools are different too. Google’s Rich Results Test checks markup for current Google-supported appearances. The Schema Markup Validator checks whether the vocabulary is formed correctly. A block can pass generic vocabulary validation without making the page eligible for a Google rich result.

Use the broader structured-data decision guide when the question is whether another visible page fact deserves markup, which consumer it serves and who will keep it current.

If a technical audit treats all four layers as one score, use the technical SEO decision guide before approving the work.

Do not add FAQPage markup for the old Google accordion.

If the only reason for adding FAQPage is to get the old expandable result, stop. That result is gone.

Even when Google supported FAQ rich results, valid markup never guaranteed that a page would receive one. Google’s current general structured-data guidelines still make that clear for the rich-result types it supports today.

Do not turn the change into a ranking story. Google said during the earlier 2023 restriction that unused FAQ structured data had no visible effect in Search. The 2026 retirement removes the remaining FAQ presentation and its supporting documentation. It does not create evidence that deleting the code will improve rankings.

The sensible choices are smaller:

Do not commission new FAQPage implementation for Google.
Remove “FAQ rich result” from proposals, forecasts and success reports.
Check whether a shared template still emits the code.
Leave accurate existing markup alone until you know whether another system uses it.
Fix or remove markup that no longer matches the visible page.

That last point matters. “No emergency” does not mean “never maintain it.” Google’s guidelines require structured data to represent visible content accurately. Stale code that describes questions no one can see is a quality problem, even when the retired FAQ appearance is no longer available.

Keep a question when it helps someone act.

A useful question removes uncertainty before a call, consultation, appointment, demo or order. It earns its place even without special markup.

Keep the question when all four statements are true:

A real buyer asks it before taking the next step.
The answer is specific to this service, product, policy or page.
Someone owns the answer and can keep it current.
The page does not already explain the same point more clearly.

Put the answer where the uncertainty appears. A financing condition may belong beside pricing. A service-area limit may belong near the call button. A return condition may belong on the product or policy page. Do not hide every important fact in an accordion at the bottom.

Remove or rewrite a question when it repeats a keyword, restates the heading, gives a vague sales answer or exists because a plugin requested five FAQs. Five weak questions do not make a page complete.

The planned-pages guide applies the same principle at a larger scale: publish a page or section because it owns a useful decision, not because a tool asks for more content.

The commercial outcome is clarity. A better answer can help someone continue, but it does not prove that the answer caused the call or sale. Measure the action separately.

Keep existing markup only for a named consumer.

Accurate existing FAQPage code does not need an emergency cleanup. It does need a reason to remain.

Use a consumer-and-cost check:

Current situation	Smallest defensible action
The visible answer helps readers, but no named system needs the markup	Keep the answer; stop adding or maintaining FAQPage code
A documented system consumes the markup	Keep it temporarily; name the owner and test the rendered output
The markup no longer matches the visible answer	Fix or remove it
A plugin emits FAQPage across many templates for Google alone	Remove the generator or disable the output centrally
No one can identify who created it or what uses it	Hold the release, inspect representative pages and document the dependency

“AI might use it” is not a named consumer. Name the platform, find its current documentation and define how you will test the claim. If you cannot do that, treat the benefit as unverified.

When a plugin, theme or component creates the markup, change that source instead of deleting JSON-LD page by page. Test several representative URLs first. A service page, policy page, product page and article can share code while carrying very different content.

Record who owns the visible answer as well as the markup. The code can be technically correct on release day and become false when an operating policy changes next month.

QAPage is not the replacement for a normal FAQ.

Do not switch every FAQ block to QAPage because Google’s current structured-data gallery still lists Q&A.

Google’s QAPage guidance describes one question followed by its answers. For the ordinary Q&A feature, users must be able to submit alternative answers.

Suitable examples include a forum thread focused on one question or a support page where users contribute answers. Google’s invalid examples include a company-written FAQ, a blog post that answers a question and a page with several different questions.

Page pattern	Use QAPage?	Why
One forum question with user-submitted answers	Evaluate it	It can match the current QAPage model
Company service page with six publisher-written FAQs	No	It contains several questions and no user answer submission
Blog article answering one question	No	A question-shaped title does not make it a Q&A community page
Product page with customer questions mixed together	Not by default	The page structure and submission model must match Google’s rules

Changing the label without changing the page does not solve anything. It can turn accurate FAQ markup into inaccurate QAPage markup.

FAQ schema is not an AI-visibility shortcut.

Google’s current generative AI Search guide says structured data is not required for generative AI search and that there is no special Schema.org markup to add.

That does not mean structured data has no job. Google still recommends page-appropriate markup as part of ordinary SEO when it supports a current Search feature. It means FAQPage is not a special switch for AI Overviews or AI Mode.

Claims about other AI systems need their own evidence. Some agencies and software vendors say FAQPage makes ChatGPT, Perplexity or other systems more likely to cite a page. The current public evidence does not establish that effect.

A 2026 third-party observational analysis from GetIntel compared pages already cited by AI systems. Its result changed after duplicate domains were controlled, and the authors concluded that current observational studies had not shown that FAQ schema earns citations. That is a useful limit, not proof of no effect everywhere.

Separate two possible changes:

writing a clearer visible answer; and
adding FAQPage code around it.

If both change together, you cannot tell which one mattered. If your goal is AI-search measurement, use a frozen question set and dated observations as described in the AI-search measurement guide. The how AI search works guide explains why eligibility, retrieval and a final answer are different stages.

Use structured data for the page’s real job.

Start with the page, not a schema checklist.

Google’s current structured-data feature gallery lists the appearances it supports. Choose the guide that matches the visible main purpose of the page. Then provide fewer complete and accurate properties instead of adding every type a tool recognizes.

An ecommerce product page is a clear example. Current Product structured-data guidance covers product snippets and merchant listings. Depending on the page and program requirements, price, availability, shipping or return information may support a live shopping appearance. That is a stronger reason for implementation than adding FAQPage because the product page has an accordion.

Other pages may accurately describe an organization, local business, article or breadcrumb path. Accuracy still does not guarantee a special result. Follow the current guide for the specific feature, keep the marked information visible and test the rendered page.

Use Google’s Rich Results Test for current Google-supported types. Use the Schema Markup Validator when you need to check generic vocabulary. After deployment, use URL Inspection to compare the live and indexed page. A successful test proves a narrow technical condition; it does not guarantee ranking, display or a buyer action.

The useful questions change across five industries.

The decision rule is the same. The questions, owners and review requirements change.

Industry	A useful decision question	Commercial next step	Review boundary
Home Services	Do you serve this address, offer emergency coverage or provide the stated financing option?	Qualified call or booked work	Operations must confirm the actual area, hours and terms
Legal	What happens in the consultation, which jurisdiction applies and what documents should the person bring?	Appropriate consultation request	An attorney must review jurisdiction, deadlines and advertising language
Healthcare	Is a referral required, is this insurance accepted and when should someone seek urgent care instead?	Appropriate appointment request	Clinical and privacy review are required
B2B SaaS	Which integrations, permissions, security review and contract terms affect evaluation?	Demo, trial or qualified pipeline action	Product, security and commercial owners must confirm the answer
eCommerce	What are the shipping, return, sizing and compatibility conditions for this product?	Order or support resolution	Catalog and operations owners must keep product and policy facts aligned

Do not copy one industry’s questions into another. A legal deadline is not a generic marketing fact. A medical urgency answer is not conversion copy. A software security answer must match the product. A contractor’s service-area promise must match dispatch reality.

The page should help the right person take an appropriate next step. It should not use a question format to make a regulated or operational claim easier to publish without review.

Record one decision before changing a template.

Use one short record for every page type or shared component. This is the FAQ decision card: Reader, Consumer, Cost, Risk.

Field	Record
URL or template	The exact page, component or content type affected
Reader	The real uncertainty the visible answer removes
Content owner	The person who can confirm and update the answer
Consumer	The named system that needs the markup, or “none verified”
Cost	The generator, maintenance work and pages affected
Risk	What can become false, misleading or broken
Decision	Keep content, edit content, keep markup temporarily, remove generator, evaluate QAPage or use another supported type
Proof	Rendered HTML, appropriate validator, representative URLs and URL Inspection
Rollback	The specific condition that would reverse the change

Before release, capture the current rendered output and the template that creates it. Test a small, representative page set. After release, verify the live page, the indexed view when available and any dashboard or API job that depended on the retired FAQ appearance.

Do not use “traffic changed” as the only rollback trigger. A site release, seasonality, demand and many other changes can move traffic at the same time. Name the failure you are testing: missing visible content, broken current markup, a consumer that stopped receiving data or a template that changed the wrong pages.

Mindflow’s methodology uses the same evidence rule: identify the first constraint, make the smallest justified change and measure the layer that changed.

If you need help finding that constraint, review Mindflow’s Organic SEO service or request the Free Visibility Check. If you already know which template is affected, contact Mindflow with one example URL, the visible question block and the reason the markup was added.

Keep the useful answers. Stop chasing the old FAQ result.