If you do SEO work in 2026, you probably felt the whiplash: FAQ rich results stopped appearing on May 7, 2026. If your strategy depended on those expanding dropdowns, your click-through rate just lost a crutch.

Here’s the operator-friendly framing: FAQ rich results going away doesn’t mean “structured data is dead.” It means Google is cleaning up a SERP feature while the answer layer (AI Overviews / AI Mode) keeps growing. Your job shifts from “SERP decoration” to “be the safest cited source.”

What changed (and what didn’t)

  • Changed: FAQ rich results stopped appearing in Google Search on May 7, 2026 (and related reporting/testing support is being removed on a timeline).
  • Didn’t change: Google’s guidance for AI features is still the same SEO fundamentals — no special “AI markup” required.
  • Didn’t change: structured data still matters as a clarity layer — but only when it matches visible content.

The mistake to avoid: replacing one hack with another

When a visibility tactic dies, teams scramble for the next trick: “AI schema,” hidden FAQ blocks, synthetic Q&A, token-count folklore. That’s not durable. Google’s own AI features documentation is explicit: there are no additional requirements (and no special schema.org structured data) to appear in AI Overviews or AI Mode.

What to build instead: proof modules (for real building decisions)

If you’re a remodeler, builder, GC, designer, or showroom, your most valuable pages aren’t “what is X?” explainers. They’re decision pages: scope, sequencing, pricing guardrails, lead times, and tradeoffs. AI can summarize generic advice. It struggles with operator-grade constraints and proof.

  • Truth set: service area, minimums, what’s included/excluded, timeline ranges, and what happens next (visible, not buried).
  • Proof module: a small case-study slice with numbers + constraints (what changed, what didn’t, and the exact context).
  • Decision checklist: the “we will not do X” guardrails that prevent bad-fit inquiries and bad AI summaries.
  • Intake path: a single, stable next step (book / apply / request a bid review) with clear confirmation states.

A simple template: the Answer Packet

For each high-intent query you care about (“How much does X cost?”, “How long does Y take?”, “Do I need a permit?”), build one page that follows this structure:

  • 1) The answer in one paragraph (no throat-clearing).
  • 2) The constraints (what must be true for the answer to apply).
  • 3) The evidence (a real example, a table, a photo, a checklist).
  • 4) The next action (a single CTA with what happens after you click).

Technical hygiene still wins (because it reduces ambiguity)

  • Keep canonical URLs stable and internally linked from relevant service pages.
  • Keep structured data accurate: Article/BlogPosting + BreadcrumbList, and make sure it matches the visible title/description/date/image.
  • Keep content accessible: crawlable, text-first, fast enough, and not hidden behind scripts or paywalls.

Datum’s take

FAQ rich results disappearing is a reminder: durable visibility comes from useful assets, not markup tricks. In the building industry, the winners will publish proof modules that encode constraints and tradeoffs — then connect those pages to a conversion-ready intake flow.

Sources Read