A few years ago we had a client who, after reading that FAQ rich results had been deprecated, decided to rip every ounce of structured data off the site. "Why bother?" they said. "It doesn't even show anymore."
That reasoning feels rational right up until the moment you realize where that markup went. It didn't vanish. Most of it went into the inputs AI engines use to decide what you are and what to quote you for.
Here's what structured data actually does in the AI era, and why removing it is exactly backwards.
It's an identity card, not a badge
When FAQ schema lost its blue expandable snippets, people assumed schema's job was to produce visible flourishes. It wasn't. The deeper job — the one that never showed on a SERP — is telling the machine, unambiguously, who this business is and what each page claims.
Organization and LocalBusiness schema say "this is the entity, here's its name, its location, its type." Service schema says "this page delivers this offering." Even if none of that ever renders as a rich result, the engine reads it. AI systems especially reward it, because extracting a coherent answer from structured claims is far easier than parsing prose.
What to actually mark up
Skip the clever experimental types. Nail the foundational ones:
- Organization + LocalBusiness: your entity, everywhere it applies. This is the base layer for AI visibility.
- Service: one per offering, clearly named and described, consistent with the visible text.
- FAQPage: yes, still worth it. The loss of the rich result didn't kill the value — a structured Q&A is exactly the shape an AI answer wants to pull from.
- BreadcrumbList: helps engines understand site structure and your place in it.
- Industry types: MedicalBusiness, Restaurant, TravelAgency, whatever fits. Match each page to its most specific type.
A single JSON-LD block per page is usually enough. You don't need a plugin generating twelve competing types.
The rule that keeps markup honest
Every claim in the schema must match visible content. The moment schema says one thing and the page says another, you've introduced a contradiction — and contradictions are the fastest way to lose an entity's trust. We sweep for these: schema should be a precise mirror of what a human visitor sees.
Why this is doubling down, not diversifying
Structured data used to be one small layer in a big technical checklist. In the AI era it's load-bearing. The engines that synthesize answers lean on machine-readable claims to attribute and quote, and the brands that leave the markup out are asking the AI to parse unmarked prose and guess. Guessing favors whoever's simplest to parse.
So keep the FAQ schema, even if nothing blue expands. Add identity schema to every page. Keep it in sync with the copy. The visible internet may have stopped decorating rich results, but the invisible layer is doing more work than ever.
If you want a structured-data audit that looks at it through the AI visibility lens — not just validation warnings — book a free website teardown and we'll tell you whether your markup is helping you get quoted, or quietly making you invisible.