FAQ Rich Results Deprecated: What to Do With Schema

FAQ and HowTo Rich Results Are Gone: What to Do With Your Schema Now

On 8 May 2026 Google added a deprecation notice to its FAQ structured data documentation: the feature “will no longer appear in Google Search starting May 7, 2026”. On 15 June 2026 it finished the job, removing the documentation because “The FAQ rich result feature is no longer shown in Google Search results”. HowTo went the same way earlier, announced in August 2023.

Most teams overcorrect in one of two directions. Either a ticket goes in to strip every FAQPage block out of the CMS - a week of engineering spent removing something that is not broken. Or nothing happens, and the audit tool keeps flagging "missing FAQPage markup" on the monthly report.

This is the calm version: what changed and when, what is still true, and the decision for each of three situations. Adviora.ai's Technical SEO Governance module scores schema against the current Google feature list rather than a remembered one - the only way an audit survives a deprecation.

Why Schema Housekeeping Matters in 2026

Structured data ages badly in silence. A type that stops producing a rich result looks identical in your codebase to one that still works: nothing errors, nothing warns, the validator still passes. A deprecation therefore corrupts your reporting rather than your site - the feature leaves the SERP, but the rule checking for its absence keeps failing. Adviora.ai keeps schema checks as a versioned rule set inside AGBS, so a retired feature changes the score instead of persisting as a finding.

What Changed, and Exactly When

Three dates matter, and much secondhand commentary has them muddled.

• August 2023 - Google announced the removal of HowTo rich results, completing on desktop that September. Rich Results Test support was withdrawn afterwards.
• 8 May 2026 - a deprecation notice was added to the FAQ documentation: “This feature will no longer appear in Google Search starting May 7, 2026.” The notice postdates the effective date by a day.
• 15 June 2026 - the changelog records “Removed documentation for the FAQ rich result feature”, reason given: “The FAQ rich result feature is no longer shown in Google Search results.”

The under-registered consequence of that third date: the FAQPage rich-results page on developers.google.com is gone, so any link to it from your wiki, CMS help text or agency deck is now dead. There was no announcement blog post either - the Search Central changelog is the primary record, which is a fair argument for monitoring it.

What Is Still True: Valid Vocabulary, Retired Feature

Schema.org and Google's rich results programme are different things. Schema.org publishes a shared vocabulary; Google chooses which parts to render, and changes that choice whenever it wants. Hold three lines apart and every decision below is obvious.

• Still valid: FAQPage markup describing questions and answers genuinely visible on the page.
• No longer true: that this markup makes a Google rich result appear.
• Unknown and unpromised: whether any non-Google consumer - another engine, an LLM retrieval pipeline - derives value from it. Nobody has published a guarantee either way, so do not build a business case on it.

Situation One: FAQPage Markup Is Already Live

Leave it. Removing valid markup is a code change, a QA cycle, a deployment and a regression risk, spent to reach a state no better than the one you are in, and there is no penalty for publishing structured data whose rich result was retired. HowTo is the precedent: most publishers left it and nothing followed.

1. Confirm the markup still matches content visible on the page - that rule predates the deprecation and still bites.
2. Remove FAQPage from every rich-results forecast, deck and business case.
3. Re-label it in documentation as "retained vocabulary, non-Google", and batch any genuine removal into a template change you were already making.

Situation Two: You Were About to Add FAQPage Markup

Cancel the ticket and reallocate the capacity. The business case was the rich result, and it is gone. Continuing because "it might help with AI" is the unfalsifiable reasoning that fills roadmaps with unevaluable work. Keep the content half - a well-built FAQ still works for answer engines and humans, because it front-loads a direct answer in plain text.

• Keep: question-shaped headings matching how people phrase the query.
• Keep: a complete, self-contained answer in the first two sentences.
• Keep: answers as readable HTML text, not script-injected or hidden in an accordion that never populates the DOM.
• Drop: the JSON-LD rollout as a standalone deliverable with its own success metric.

Situation Three: Your Audit Tool Still Flags It as Missing

This is where the change actually costs money, because it manufactures work every cycle. Any tool built before May 2026 keeps listing "FAQPage markup missing" on every page with a question on it. Each is now a false positive. Fix the rule, not the site.

1. Find every scoring rule, template and checklist referencing FAQPage or HowTo as a rich-results opportunity, agency deliverables included.
2. Change the rule from "missing = deficiency" to "not applicable - feature retired May 2026", and record the date.
3. Ask your vendor, in writing, when their rule set was last reconciled against the Search Central changelog. The answer tells you how far to trust the rest of the report.

What Not to Do - Starting With QA Page

The substitution trap is being recommended in public right now: FAQ is gone, but Q&A Pages remain in the gallery, so re-mark the FAQ as QAPage and keep the feature. It does not work. Google's QA Page documentation, updated 24 March 2026, states the rule directly:

“Users must be able to submit answers to the question. Don't use QA Page markup for content that has only one answer for a given question with no way for users to add alternative answers.”

A site-authored FAQ fails that test by definition: you wrote the question, you wrote the single authoritative answer, and no visitor can add a competing one. QAP age exists for forum threads and support communities where user answers accumulate, and needs main Entity as a Question with answer Count, name and either accepted Answer or suggested Answer.

• Do not run a bulk removal project - inert markup is not harmful markup.
• Do not delete the FAQ content with the schema; answer-shaped text is your most reusable asset across search and AI surfaces, as our guide to being cited by AI search sets out.
• Do not attribute a mid-2026 traffic movement to this change without evidence - the FAQ rich result expanded your own listing, it was never an additional one.

The Structured Data Types That Still Produce Rich Results

The counterweight to a deprecation is a current inventory. Google's search gallery still documents more than thirty features; these are live and worth auditing against your templates.

• Breadcrumb - the page's position in the site hierarchy: cheap, sitewide, frequently missing. Organization - logo, legal name, address and contact information: your brand's entity anchor, under-attended almost everywhere.
• Article, Product, Review snippet, Event, Recipe, Video, Course, Job Posting, Local Business - the commercially significant types.
• Q&A Pages and Discussion forum - for genuine community content only, under the eligibility rule above.

Google notes that “The actual appearance in search results might be different”, so preview with the Rich Results Test. Check your vocabulary version too: the current stable Schema.org release is 30.0, published 19 March 2026, adding a Credential class for has Credential and an Error class with error Code. Adviora.ai's Technical SEO Governance module reports schema coverage by template, so the gap shows in one view.

Best Practices

1. Read the Search Central updates changelog monthly. This deprecation was recorded there and nowhere better.
2. Record when each schema rule was last reconciled against the gallery; treat anything older than a quarter as unverified.
3. Score schema on two axes - is the markup valid, and does the target feature still exist. Never collapse them into one result.
4. Require that structured data always matches visible page content. This rule survives every deprecation.
5. Add a visible last-updated date to any page documenting a platform change.

The Future of Structured Data in Search

The direction of travel is legible from the last three years. Google keeps retiring features whose markup was easy to add and whose SERP value was diffuse, while keeping the types that describe distinct real-world entities - products, organisations, events, jobs, local businesses. Structured data is drifting from decorating a listing towards stating what a thing is, a more durable job as generative surfaces grow. Build your strategy around entities you can defend, not features you hope will render.