Case Study 18.1 — The Day the FAQ Snippet Vanished: Google's 2023 Rich-Result Rollback

Type: Real, public, Tier-1 event analysis. The core facts — that Google announced, in 2023, a sharp reduction of FAQ and HowTo rich results — come from Google's own public Search Central announcements and documentation. No traffic statistic is invented; where an illustrative figure appears it is labeled, and the lesson rests on the documented change, not on any specific number.

Background: the golden age of the FAQ snippet

For several years, two structured-data types were the most-recommended, most-added markup in the entire SEO world: FAQPage and HowTo. After Google introduced their rich results (FAQ rich results arrived in 2019), the appeal was irresistible and, for a while, entirely real. You marked up a list of questions and answers, or the steps of a task, and Google rewarded you with a big, expandable block right in the search results — extra vertical space, extra visibility, your text sitting under your listing where competitors' plain blue links couldn't reach.

An enormous cottage industry grew around this. "Add FAQ schema to every page" became boilerplate advice in tutorials, plugins, and agency proposals. Sites bolted FAQ sections onto pages specifically to earn the rich result, sometimes whether or not the questions were genuinely useful. For a business, the pitch was simple and true: here is a free way to make your listing bigger. The tactic worked because Google was choosing to display it. And that last clause — because Google was choosing to display it — is the whole case.

The issue: a feature is not a promise

On August 8, 2023, Google announced a change to how it would show FAQ and HowTo rich results, and it was not a small one:

  • FAQ rich results would from then on appear only for "well-known, authoritative government and health websites." For every other site — businesses, blogs, stores, publishers — the expandable FAQ block would simply stop appearing.
  • HowTo rich results would be limited to desktop devices only, disappearing from mobile.

A little over a month later, Google went further: HowTo rich results were deprecated entirely — removed across all devices — and Google retired the corresponding HowTo report in Search Console. Google framed the change as part of an effort toward "a cleaner and more consistent" search experience.

Read what did and did not happen carefully, because the distinction is the lesson.

FIGURE C18.1 — "What the 2023 rollback did and didn't change"        [after Google Search Central, 2023]
  WHAT CHANGED                              WHAT DID NOT CHANGE
  Google stopped DISPLAYING the FAQ rich    The FAQPage / HowTo VOCABULARY still exists in
    result for ordinary sites (kept it for    Schema.org; the markup is still valid.
    authoritative gov/health only).         Google can still READ the markup to understand
  Google stopped displaying HowTo rich        a page's Q&A or steps (job one: meaning).
    results for everyone (deprecated).       Nobody's markup became "wrong" overnight — it
  Search Console's HowTo report was removed.   just stopped producing a visible SERP feature.

Notice that no one's markup broke. The JSON-LD that sites had added was still valid, still readable, still describing true content. What changed was entirely on Google's side: its willingness to display the feature. The publishers who had treated the FAQ rich result as a durable asset discovered it was a loan — extended at Google's discretion, and called back at Google's discretion.

What it shows

This event is the cleanest real-world proof of three claims the chapter makes.

  1. Structured data buys eligibility, not outcomes — and eligibility itself is revocable. The chapter's central caution was demonstrated at scale: sites that had done everything "right" (valid markup, real questions) lost the visible payoff anyway, because Google, not the publisher, decides what to show, and can change that decision unilaterally.
  2. SERP features are Google's to give and take. Any strategy whose value depended on a specific SERP feature was exposed as fragile. This is why the book refuses, everywhere, to build a plan on one feature — and why traffic diversification (Chapter 36) and durable fundamentals matter more than any single snippet.
  3. The durable value of markup is meaning, not display. After the rollback, the only remaining reason to add FAQPage markup for an ordinary site is job one — helping Google understand the page's Q&A content. That value survived the announcement precisely because it never depended on a display feature. The publishers who had understood markup as "meaning first, feature second" lost the least.

There is also an honest question of why Google did it, and the likely answers are instructive. Google does not publish a single reason, but two documented dynamics point the way. First, the feature was being abused and diluted — pages stuffing marginal or irrelevant FAQs purely to grab real estate, which degrades the results page. Second, FAQ rich results contributed to the zero-click dynamic: when the answer is fully displayed in the SERP, the user may never click through, which hurts the very publishers the feature was meant to help (and complicates Google's own ecosystem). A feature that is gamed and that suppresses clicks is a feature Google has every incentive to curtail. The lesson for the practitioner: the more a SERP feature is exploited, the more likely Google is to take it away.

📄 Read the Report

text FIGURE C18.2 — "A content site's FAQ-dependent listings, before and after" [constructed teaching example] THE PAGE A how-to publisher with hundreds of pages carrying FAQ + HowTo markup for the rich blocks. BEFORE (early '23) Many listings showed expandable FAQ blocks and HowTo step previews — large, prominent. AFTER (late '23) The same listings render as plain results. Markup unchanged and still valid; the visible enhancement is simply gone. The Search Console HowTo report has disappeared. WHAT IT SHOWS A visible asset the site did not own evaporated on Google's schedule, not the site's. WHAT IT DOESN'T It does NOT mean the site was penalized or its rankings fell — the *positions* may be unchanged; only the listing's appearance changed. (Illustrative; no specific figure.) THE LESSON Never treat a SERP feature as a possession. Own the fundamentals; borrow the features.

Outcome

The practical aftermath was uneven and, tellingly, undramatic in ranking terms. Sites did not generally get penalized — their positions were not the issue — but listings that had relied on the FAQ/HowTo blocks for visual prominence became plain again, and whatever click advantage the bigger listing conferred was lost. Much of the accumulated "add FAQ schema everywhere" advice became instantly obsolete, and the plugins and workflows built around it had to be reframed. Google left the markup valid and readable, so no cleanup was strictly required; sensible teams removed FAQ sections that had existed only to feed the snippet (and added nothing for users) while keeping genuinely useful Q&A content.

The teams that weathered it best were the ones who had never over-invested: who added FAQ markup as a minor, meaning-first touch rather than a load-bearing tactic, and who had built their visibility on content quality, architecture, and authority that no announcement could revoke.

The lesson

Date your SEO knowledge, and never build on a borrowed feature. This case is the reason the chapter insists you check the date on any structured-data advice and confirm a feature against Google's current documentation before investing in it. A tactic that was correct, ubiquitous, and effective in 2022 was largely dead by late 2023 — not because anyone did anything wrong, but because the feature it relied on was always Google's to withdraw. The durable lesson underneath is the book's spine: structured data's lasting value is telling Google the truth about your page so it understands it. The visible rewards come and go; the understanding compounds.

Discussion questions

  1. No one's markup "broke" in the 2023 rollback, yet many sites lost a visible asset. Explain, using the chapter's "eligibility, not outcomes" idea, why that outcome was predictable — and what it implies about how you should describe rich results to a client.
  2. Google likely curtailed FAQ results partly because they were abused and partly because of zero-click dynamics. For each reason, describe a different way a responsible practitioner's behavior should change going forward.
  3. After the rollback, is there any reason left for an ordinary business to add FAQPage markup? Argue yes and no, then state which you find more persuasive and why.
  4. The chapter says "the more a SERP feature is exploited, the more likely Google is to take it away." Name another SERP feature (from this or earlier chapters) and predict whether it is at similar risk. What signals would tell you?
  5. A stakeholder asks you to "add all the schema types we can, to grab as much SERP real estate as possible." Using this case, write the two or three sentences you would say in reply.