Beyond Basic Schema
Session 3.1 · ~5 min read
In Entity Authority 1.0, you deployed basic structured data. Organization schema. Person schema. Maybe a WebSite type. Google validated it. You got a green checkmark. And then nothing happened.
That is because basic schema tells search engines one thing: "I exist." It does not tell them what you do, what you know, who you work with, or why you matter. Layer 1 schema is a business card. Layer 2 schema is a conversation.
Schema as Entity Language
Schema.org contains over 800 types and 1,400 properties. Most implementations use fewer than 10. The gap between what is available and what is deployed represents an enormous missed opportunity for entity recognition.
Think of structured data as a vocabulary for describing your entity to machines. In Layer 1, you learned to say your name. In Layer 2, you learn to express your relationships, your expertise, your body of work, and your organizational connections.
Basic schema declares existence. Advanced schema declares meaning. The difference between the two is the difference between being a node in the knowledge graph and being a node with meaningful edges.
The Schema Vocabulary You Are Not Using
Here is a comparison of what most entities implement versus what is available for entity recognition.
| Category | Layer 1 (Basic) | Layer 2 (Recognition) |
|---|---|---|
| Identity | name, url, logo | sameAs, identifier, alternateName |
| Expertise | (none) | knowsAbout, hasOccupation, hasCredential |
| Relationships | (none) | affiliation, memberOf, worksFor, founder |
| Content | Article with headline, date | Article with author, about, mentions, isPartOf |
| Achievements | (none) | award, alumniOf, honorificPrefix |
| Output | (none) | Course, Event, Product with provider/organizer |
Every property in the right column is a signal. Not a ranking factor in the traditional sense, but a machine-readable declaration that feeds entity understanding. As AI search systems grow, these explicit declarations become increasingly valuable.
How Search Engines Read Advanced Schema
When Google encounters your structured data, it does not just validate syntax. It reads the semantic content and incorporates it into its entity understanding. A Person schema with knowsAbout: ["entity SEO", "knowledge graphs", "structured data"] is an explicit topical declaration. A Person schema with worksFor pointing to an Organization schema creates a relationship edge.
This diagram shows a single entity with multiple relationship types expressed through schema. Each arrow is a machine-readable edge. Together they form a mini knowledge graph on your own website, one that search engines can directly consume.
The Recognition Signal Stack
Advanced schema works best when layered with other recognition signals. Structured data alone does not create recognition. But structured data combined with consistent cross-platform identity, topical content, and external mentions creates a signal stack that machines can process with high confidence.
The schema you deploy in this module serves as the machine-readable layer underneath all your other recognition work. Your content hubs declare topical depth. Your schema makes that depth explicitly readable. Your external mentions validate your claims. Your schema connects those claims to formal entity declarations.
What This Module Covers
Over the next 8 sessions, you will move through the full spectrum of recognition-level structured data:
- Person and Organization advanced properties that declare expertise and affiliations.
- Article and CreativeWork schema that connects your content to your entity and your topics.
- The knowsAbout property for explicit expertise declarations.
- Relationship schema between entities on your properties.
- Event, Course, and Product schema as supporting entity signals.
- JSON-LD architecture that connects schema across your entire site.
- Validation and monitoring to ensure your schema stays accurate.
Each session builds on the previous one. By the end of this module, your structured data will not just say "I exist." It will say "I am connected to these topics, I created this body of work, I am affiliated with these organizations, and these are my areas of expertise."
Further Reading
- Full Schema.org Type Hierarchy (Schema.org)
- Structured Data Documentation (Google Search Central)
- Guide to the Schema.org Vocabulary (Schema App)
- Organization Schema Markup: Complete Guide to Knowledge Graph and Entity SEO (Stackmatix)
Assignment
- Audit your current structured data using Google's Rich Results Test on your 5 most important pages.
- List every schema type and property currently implemented across your site.
- Compare your implementation against the full Schema.org vocabulary for your entity type (Person or Organization).
- Identify 10 unused properties that could strengthen your entity profile. For each, note what entity signal it would create.