Chapter 18 — Key Takeaways
A one-page reference. If you remember nothing else: structured data buys eligibility, not outcomes, and it works only when it tells the truth.
The one idea
Structured data is a caption written for machines — you state, in a standardized vocabulary, the facts a human would otherwise infer from your page. It does two jobs: (1) makes meaning explicit (durable, invisible), and (2) makes the page eligible for rich results (visible, but Google decides — never guaranteed). It is not a ranking factor.
The two jobs (keep them separate)
| Job | What it does | Visible? | How durable |
|---|---|---|---|
| 1 — Meaning | Helps Google understand the page + connect it to entities (Ch 4) | Rarely | Durable — no feature can be revoked |
| 2 — Eligibility | Qualifies the page for a rich result (stars, breadcrumb, etc.) | Yes, when shown | Fragile — Google gives and takes features |
Vocabulary + format
- Schema.org = the shared vocabulary (types like
LocalBusiness,Product; properties likeprice). - JSON-LD = the syntax Google recommends — a self-contained code block, separate from visible HTML.
- Older syntaxes (Microdata, RDFa) still work; use JSON-LD for anything new.
Rich results — the honest status table
| Type | Schema | Status |
|---|---|---|
| Breadcrumb | BreadcrumbList |
Live — the clean, low-risk first win |
| Product (stars/price) | Product + Offer + AggregateRating |
Live; e-commerce core (Ch 31) |
| Recipe / Event / Video | Recipe / Event / VideoObject |
Live where genuinely applicable |
| Review stars | Review/AggregateRating on a supported type |
Not for self-serving business reviews (since 2019) |
| FAQ | FAQPage |
Rolled back 2023 — only authoritative gov/health sites |
| HowTo | HowTo |
Removed 2023 — no rich result for anyone |
Rules of thumb
- Eligibility, not outcomes. Marking up qualifies you; Google decides what to show, per query, and can stop.
- Mark up only what's true and visible. Invisible or invented markup risks a "Spammy structured markup" manual action. A markup-versus-page mismatch is mechanically checkable.
- Use the most specific accurate type (
HVACBusiness>LocalBusiness); more markup is not better markup. - Schema ≠ the local pack.
LocalBusinessaids entity/NAP; the Google Business Profile drives the map pack (Ch 25). - Some markup has no rich result at all (e.g.,
Service) — you add it for meaning, and nothing "appears." - Test → monitor. Rich Results Test (eligibility) → Schema Markup Validator (validity) → Search Console Enhancements (working at scale, over time).
The mental reframe
- The most valuable markup is often the least visible (Organization, LocalBusiness,
sameAs→ entity understanding). Beginners over-invest in the visible; strategists value the durable. - Never build a strategy on one SERP feature — the 2023 FAQ/HowTo rollback proved features are Google's to withdraw.
- Faking markup is self-defeating, not just against the rules — it's easy to detect and the "win" is temporary.
What you can do today
Run the free Rich Results Test on your homepage and one key page. Note what markup you already emit, whether the type is as specific as it could be, and whether you're eligible for any rich result. Write a two-column list: "markup to add" and, honestly, "what I expect it to do (eligibility, not outcome)."
Where this goes next
→ Chapter 19 confronts the prior problem: helping Google see your content at all when a site is built on JavaScript — because meaning is worthless if the machine never reached the words.