Request a consultation
Home/Writing/Advanced schema markup
Advanced Structured Data

Advanced schema markup.

Most sites have schema that technically validates and accomplishes almost nothing — a handful of disconnected blocks a plugin generated. Advanced schema is different: a single, nested graph of entities that reference each other, link out to known knowledge bases, and give search engines and AI a real model of who you are. This is the part I get hired for.

Why basic schema plateaus

Validating isn't the same as working.

A plugin will happily emit an Organization block, an Article block, and a Breadcrumb block — each in its own script, each an island. Nothing tells the search engine that the article's author is a person who works for that organization, or that the organization is the same entity referenced on LinkedIn and Wikidata. The data passes validation, but it's a pile of facts, not a map. Advanced schema is about the relationships between entities — and that's exactly what AI systems use to reason about you.

The @graph pattern

One block, connected entities.

Instead of scattering separate scripts, you place every entity in a single @graph array and give each one a stable @id. Then entities reference each other by that id — the WebPage isPartOf the WebSite, the Article's author points to the Person, the Person worksFor the Organization. Clean, deduplicated, and unambiguous.

Get advanced schema built
  • Stable @id for every entitySo references resolve instead of duplicating data across blocks.
  • Cross-references between entitiesauthor, worksFor, publisher, isPartOf — the relationships that build the map.
  • One maintainable source of truthA single graph beats a dozen plugin snippets fighting each other.
Entity linking & disambiguation

Tell Google which "you" you are.

Names are ambiguous; entities aren't. The sameAs property connects your Person and Organization to authoritative references — Wikipedia, Wikidata, LinkedIn, your other profiles — so search engines collapse all of them into one confident entity. That's how you earn knowledge-panel treatment and how AI systems stop confusing you with someone who shares your name.

How this powers AI citations →
  • sameAs to knowledge basesWikipedia and Wikidata are the references the graph trusts most.
  • knowsAbout for expertiseDefines your topical authority in machine-readable terms.
  • Consistency across profilesThe same name, URL, and facts everywhere you appear.

Outgrown plugin schema? Let's build the real thing.

Custom JSON-LD, a connected @graph, entity linking, and site-wide templates — validated end to end. If you want structured data that actually does something, this is the work.