Every fact an AI system holds about your company was extracted from somewhere — and extraction from prose is lossy. Structured data (JSON-LD in your pages’ markup) is the one channel where you state facts in a form built for machines: this organization, founded then, located there, offering these services, verified by these profiles. It is the cheapest high-leverage move in AEO, and most agency websites — including, until recently, ours — ship none of it.
Priority order matters, because schema sprawl helps nobody. Here is the sequence we implement, and now run on this site.
The core four: identity schema
Organization is the anchor — name, legal name, founding date, address, contact, and critically sameAs links to your LinkedIn, GitHub, and directory profiles, which let machines join your entity across the web. WebSite ties the domain to the org. Person markup for real, verifiable people — founders and named experts — links E-E-A-T to humans. FAQPage on your genuine questions-and-answers, because assistants lift well-marked Q&A almost verbatim. Ship these four before anything else.
“Prose can be misread. JSON-LD is you telling the machine, in its own language, exactly what is true.”
The commercial layer
Service schema on each service page states what you sell and where, in machine terms. Product or SoftwareApplication for things you make. Article with real authors and ISO dates on posts — undated content reads as stale to freshness-weighted retrieval. BreadcrumbList exposes your site’s hierarchy so engines understand which page is canonical for which topic. Together they turn "a website about software" into a legible catalog.
The mistakes that backfire
Marking up what is not true: schema-izing invented reviews or fictional team members is worse than nothing — you are feeding falsifiable claims to systems built to cross-check, and search engines issue manual actions for it. Schema contradicting the visible page. Orphan markup nothing corroborates. The rule: structured data amplifies verifiable truth; it cannot manufacture it. If a fact would not survive a diligence check, do not put it in JSON-LD.
Implementation is a day of work on most sites — ours took one. Validate with Google’s Rich Results test, keep it in sync with reality, and let the entity-resolution machinery do its quiet work. The final piece in this series compresses everything into a 20-point checklist.
Emperor Brains Engineering
Emperor Brains LLP
