FAQ, HowTo, Speakable: The Schema Google Retired

Two camps showed up the week Google pulled FAQ rich results. One says rip the markup out of every page today. The other says leave it, the AI engines still read it. Both are guessing, and the guess costs you either a sprint of dev time or nothing at all.

Here is the distinction neither camp draws. A rich result is a rendering decision. Schema is a parsing input. Google deciding to stop drawing your FAQ accordion into the SERP does not make your JSON-LD unreadable — it makes it unrewarded by one feature on one engine.

Below is what Google's changelog actually says, what to do with each of the three retired schema types, and the part that stings: if you bolted FAQ blocks onto pages to farm SERP real estate rather than answer a real question, that content was junk before the change. Now it is junk with no payout.

Did Google actually kill FAQ schema, or just the rich result?

Just the rich result. Google's Search Central changelog entry dated May 8, 2026 says it added a deprecation notice to the FAQ rich result documentation because “this feature will no longer appear in Google Search starting May 7, 2026.” A second entry on June 15, 2026 records that Google removed the FAQPage documentation page outright.

That is the entire announcement. No statement that FAQPage markup is invalid. No penalty. No crawling change. The old documentation URL now redirects to the changelog, schema.org still defines FAQPage, and your JSON-LD still validates.

The feature was already dead for almost everyone. On August 8, 2023 Google announced that “going forward, FAQ (from FAQPage structured data) rich results will only be shown for well-known, authoritative government and health websites.” Unless you run a state health department, you have not had an FAQ rich result in nearly three years. May 2026 just finished the job.

Should you remove FAQPage markup from your site?

No. Google answered this itself in the 2023 announcement of the same kind of change, in one sentence: “While you can drop this structured data from your site, there's no need to proactively remove it.” Nothing since has changed that.

Run it like an operator instead of a purist. Stripping valid markup out of a 60-page site is a template change, a QA pass, and a re-crawl wait. The upside is a marginally smaller HTML payload. The downside is a real chance a dev breaks a shared component and takes your LocalBusiness or Product markup with it.

Verdict: leave the markup, rewrite the answers. Removing schema is the only row on that table with a downside and no upside. If your markup breaks every time someone touches a template, that is a technical SEO problem, not a schema-strategy problem.

Do AI engines still read schema Google stopped rendering?

Nobody outside those companies can prove it either way, and any agency that tells you otherwise is selling. What is documented: Google's AI-features guidance says there are no additional technical requirements to appear in AI Overviews or AI Mode beyond being indexed and eligible to show with a snippet — and it lists “making sure your structured data matches the visible text on the page” as a best practice, not a requirement.

Read that carefully, because it sets the ceiling on what schema can do. Structured data is a machine-readable mirror of your page. It clarifies. It does not conjure. If the answer is not in the visible text, no amount of JSON-LD puts it into an AI answer.

So the honest position is boring and cheap: keep FAQPage markup because it costs nothing and every parser that is not Google can still use it. Do not build a GEO program on it. The thing that gets you cited is the answer text, which is why the rewrite beats the markup every time. The structured data that still carries real weight is covered in our breakdown of which schema types actually matter for GEO.

What happened to HowTo and speakable schema?

HowTo is fully gone; speakable is alive but tiny. Google's August 8, 2023 post said HowTo rich results “will only be shown for desktop users, and not for users on mobile devices,” and the September 14, 2023 changelog then removed the HowTo structured data documentation entirely, stating the rich result “is no longer shown in search results, on both desktop and mobile devices.”

Speakable is the survivor almost nobody can use. Its documentation is still live (last updated December 10, 2025), still labeled beta, and it is limited to news content in English for users in the U.S. with Google Home devices. If you are not a US news publisher, speakable has never done a thing for you, and still does not.

Where should an FAQ live — inline, on the service page, or on a /faq page?

Three placements, three different jobs, and mixing them up is how you cannibalize your own money page. Objection FAQs (price, contract length, timeline) go inline on the page that handles the objection, because they convert. Query FAQs go on the page that already targets that query, because they rank. A standalone /faq page exists only for cross-cutting operational questions — billing, onboarding, support hours.

The failure mode is expensive and everywhere. A company writes an FAQ page answering “how much does dental SEO cost,” while the service page that should own that buyer term sits two clicks away. Now two URLs compete for one query and Google picks the weaker one. The fix is not more content. It is moving the answer onto the page that owns the term and leaving “do you offer month-to-month billing” on /faq.

One test settles most placement arguments: would a buyer read this answer and get closer to a decision, or just get a fact? Decisions belong next to the buy button. Facts belong wherever the query lives.

Why does “as mentioned above” make an FAQ answer invisible to AI?

Because extraction happens at the passage level, and inside a passage there is no “above.” An answer engine lifts one self-contained chunk — Pew Research Center found the median AI summary in its March 2025 study was 67 words long — so if your answer opens with “as mentioned above” or “see the pricing section,” the chunk it lifts is a pointer to nothing.

This is not a schema fix. It is a writing fix. Every FAQ answer has to survive being torn out of the page and read alone: name the subject, give the number, close the loop in 30 to 100 words. No pronouns pointing at paragraphs the machine never saw.

Question-shaped queries are exactly where this pays off. Ahrefs analyzed 146 million SERPs and found question queries trigger an AI Overview 57.9% of the time versus 20.5% of keywords overall, and Pew found 60% of searches beginning with question words like who, what, when or why produced an AI summary (March 2025 data). Your FAQ block aims straight at the query class most likely to be answered by a machine — so write it the way machines read, using the inverted-pyramid pattern.

Which Search Console report tells you what you actually lost?

The Performance report — and if you truly had an FAQ rich result, it will show there, because Google said so in 2023: “for both of these items, you may also notice this change in the Search Console reporting for your website.” The enhancement report for a retired feature simply stops existing, which tells you nothing.

Do this, in order. Set Performance to compare the 28 days before May 7, 2026 against the 28 days after. Filter to the pages carrying FAQPage markup. Then read impressions and CTR — not average position. A retired rich result changes how your listing is drawn, so CTR moves first and rankings usually do not move at all.

If CTR is flat, you never had the rich result. Unless you are a government or health site, that is the likely answer, and you just avoided a pointless refactor. If clicks did fall, the cause is somewhere else — a core update, a competitor, a redirect — and ripping out schema would have hidden it.

One thing that report will not give you: how much traffic came from AI Overviews. Google folds AI-feature clicks into the ordinary Web search type and does not break them out. Anyone quoting you an AI Overview traffic number from Search Console is inventing it. The realistic AI measurement plan lives in our answer engine optimization guide.

What should you rewrite instead of ripping out?

Start with every FAQ block you built to occupy SERP space rather than answer a question. That content had exactly one job, the job is gone, and it is now dead weight on a page you want indexed for something else. Five moves, in this order.

• Cut questions nobody asks. If it is not in People Also Ask, autocomplete, or your sales calls, it is filler.
• Rewrite every answer to be self-contained — subject, number, 30 to 100 words, no “as mentioned above.”
• Move buyer-intent answers (cost, contract length, timeline) onto the money page that targets the term.
• Keep the FAQPage JSON-LD, and make sure it matches the visible text — that is Google's stated best practice for AI features.
• Audit the schema that still earns rich results: Product, Review, LocalBusiness. Google updated its Product structured data guidance in July 2026.

That is an afternoon per page, not a re-platform. And it survives the next deprecation, because it is not betting on a rendering decision.

The whole episode is a useful filter. If your FAQ section holds up when it is read one answer at a time, out of order, by a machine, it was always doing real work and the markup was never the point. If it does not, no schema was ever going to save it. Want to know which of your pages are carrying dead FAQ blocks and broken markup? That is a technical SEO job. Get my free audit.