FAQ markup is no longer the shortcut many marketers treated it as.
That does not mean question-driven content stopped mattering. It means the cheap version stopped paying. For years, teams bolted a giant FAQ block onto the bottom of a page to farm the accordion rich result, whether or not anyone needed those answers there. Google closed that loophole. What replaces it is not less answering. It is answering better, in the places a decision actually happens.
What changed
Google deprecated FAQ rich results for most sites, keeping the visual widget for a narrow set of trusted government and health sources. The blue-link accordion that used to expand under a result is gone for the average marketing site. That closes off a pattern that was frequently abused: FAQ blocks built to chase a visual feature rather than to help a reader, often stuffed with questions no customer ever asked.
The important part is what did not change. AI Overviews and AI assistants still retrieve and quote passages that cleanly answer a question. So the incentive shifted from "earn a widget" to "be the quotable answer", and the second one rewards genuine, specific, well-placed content instead of markup volume.
What to replace old FAQs with
- Answer blocks inside service pages. Put the question near the relevant section, not in a detached dump at the bottom. A buyer reading about scope should find the "how long does it take" answer right there, phrased so a model can lift it.
- Comparison pages. Use side-by-side framing where buyers genuinely weigh a tradeoff, such as hire versus train or build versus buy. These earn citations because they resolve a real decision.
- Proof-backed explainer posts. A short article that answers one question with a concrete example and a real source outperforms a thin FAQ line for AI retrieval, because it gives the model context and evidence, not just an assertion.
- Support and help content. Real operational questions (setup, billing, troubleshooting) still deserve dedicated pages. Those pages age well and quietly earn long-tail AI answers.
The replacement is not less answering. It is better integrated answers, living inside the pages that already carry business weight.
Should you delete the schema?
Usually not. FAQPage schema no longer earns the visual rich result for most sites, but it still helps machines parse a clean question-and-answer structure, and it causes no harm when it describes real content that is visible on the page. The only case for removing it is the one Google was targeting: invisible, markup-only FAQ stuffing with no on-page counterpart.
My rule is simple. If the questions and answers are genuinely on the page and useful to a reader, keep the schema and improve the surrounding content. If the FAQ existed only as hidden markup to game a feature, delete it and write something a person would actually read. The schema is a description of good content, never a substitute for it.
Where FAQs still help
FAQs still help when they are:
- close to the buyer decision;
- specific to the offer;
- supported by proof or process detail;
- written for understanding instead of markup games.
A well-placed FAQ next to a pricing section, answering the three objections a buyer actually raises, is worth more than it ever was. A detached wall of twenty generic questions at the page footer is worth nothing and may dilute the page.
If your site still depends on old FAQ-page SEO habits, replace them with stronger answer architecture inside the pages that already matter to the business. That is the same answer-first structure I build into client service pages, and it is what keeps a page useful to a human and quotable by AI search at the same time.