Module 05 · Lesson 4 of 4
Structured Data for Entities
Structured data is a vocabulary (schema.org is the common one) for stating facts about a page and its entities in a machine-readable format. Used truthfully, it removes ambiguity: it says which entity this site represents, which URLs belong to it, who wrote this page. Used as a charm, it wastes an afternoon.
What it does, honestly
- Disambiguation: an Organization block with your canonical name, URL and sameAs profile links states "this site is that entity".
- Relationships: Person markup on author pages ties articles to people; publisher blocks tie pages to the organisation.
- Classic search features: eligible rich results (reviews for products, event listings, course listings where genuinely applicable) depend on matching markup.
- Maintenance of meaning: one authoritative JSON block is easier to keep accurate than prose scattered across footers.
What it does not do
Three myths to kill on sight. It does not cause AI citations: Google states its AI features require no special schema, and no platform documents any markup that produces citations. It does not substitute for corroboration: declaring "award-winning" in JSON persuades nobody, because markup is still self-description. And it does not override your visible content: markup that contradicts the page is worse than no markup. Structured data states what is already true, cleanly. That is the whole job.
The honest minimum
| Site type | Truthful minimum | Only if factually true |
|---|---|---|
| Business site | Organization with name, url, logo, sameAs | address, contactPoint, founder |
| Publication | Organization + Person on author pages | alumniOf, award (verifiable ones) |
| Personal site | Person with name, url, sameAs | jobTitle, worksFor |
| This course site | Organization, WebSite, WebPage, Course | instructor, if a real named instructor exists |
Validation is free: Google's Rich Results Test and Search Console's reports flag syntax errors and eligibility. Validate when you add markup and re-validate after any site template change, which is when silent breakage happens.
- State @id once ("https://example.com/#org") and reference it from pages instead of restating the entity.
- name: the canonical trading name from your lesson 5.1 record, exactly as written there.
- sameAs: your real profiles only. Three genuine URLs beat ten including dead accounts.
- description: the one-sentence identity from the canonical record, not this quarter's campaign line.
- Re-check every six months: dead profile links in sameAs are the most common rot.
- Check whether your site already carries Organization or Person markup (view source, search "application/ld+json").
- If it exists, verify every field against your canonical record and delete anything stale or untrue.
- If it does not, add the honest minimum for your site type and validate it.
- Add a six-month calendar note to re-validate, tied to your entity-consistency re-check from lesson 5.1.
Does adding Organization schema make an AI system cite you?
What belongs in sameAs?
When is markup worse than nothing?
Sources used in this lesson
Google Search Central: structured data
Google Search Central: AI features and your website