Entity SEO
Entity SEO optimizes how search engines understand your brand, products, people, and concepts as distinct entities with defined relationships.
Learning Focus
After this lesson you can define entities, optimize for knowledge graphs, and maintain entity consistency across platforms.
This lesson covers the seven entity SEO areas (leaves 8.2.1–8.2.7): entity definition, knowledge graph optimization, entity relationship mapping, brand entity consistency, attribute and fact consistency, structured entity signals, and sameAs and profile alignment.
Why This Matters
- Search engines increasingly understand content through entities and their relationships, not just keywords.
- A strong entity presence can improve brand visibility in knowledge panels, AI answers, and semantic search.
- Entity signals compound over time as more sources reference your consistent entity.
Entity Definition
Define the entities your brand should be associated with.
Entity types:
| Type | Examples |
|---|---|
| Organization | Your company, subsidiaries, parent company |
| Person | Founders, executives, authors, subject matter experts |
| Product | Products, features, services |
| Concept | Industry terms, methodologies, frameworks |
| Place | Office locations, service areas |
| Event | Conferences, webinars, product launches |
Entity definition workflow:
- List all entities relevant to your brand.
- For each entity, define: name, description, type, identifier (URL, sameAs), relationships to other entities.
- Document the canonical source for each entity (e.g., your about page for the organization).
Knowledge Graph Optimization
Core Concept
The Google Knowledge Graph is Google's database of entities and their relationships.
Knowledge graph optimization factors:
| Factor | Action |
|---|---|
| Organization schema | Implement Organization schema with all relevant properties |
| Wikipedia presence | Wikipedia articles are a strong knowledge graph signal |
| Wikidata presence | Wikidata entries provide structured entity data |
| Authoritative linking | Links from authoritative sites to your entity pages |
| SameAs consistency | Consistent sameAs references across all entity mentions |
| Social profile completeness | Complete, linked social profiles |
| Regular content publishing | Fresh content about your entity topics |
warning
Knowledge panel eligibility:
- Knowledge panels are algorithmically generated.
- There is no guaranteed method to get or change a knowledge panel.
- Completing your entity signals increases the likelihood of accurate panel generation.
Entity Relationship Mapping
Map the relationships between your entities.
Relationship types:
| Relationship | Example | Schema Property |
|---|---|---|
| Organization → Person | Company employs CEO | founder, employee |
| Organization → Product | Company produces product | makesProduct |
| Organization → Place | Company has office | location |
| Product → Feature | Product has feature | — |
| Person → Organization | Person works for organization | worksFor |
| Organization → Parent | Subsidiary of parent company | parentOrganization, subOrganization |
Entity relationship map example:
ExampleCorp (Organization)
├── email-marketing-platform (Product)
│ ├── email-segmentation (Feature)
│ └── automation-workflows (Feature)
├── 500-startups (Funding Entity)
├── Jane-Smith (Employee): CEO
├── austin-office (Place)
└── email-marketing-association (Membership)
Brand Entity Consistency
Maintain consistent entity representation across your site and external platforms.
Consistency requirements:
| Signal | Consistency Standard |
|---|---|
| Organization name | Same name everywhere (no "ExampleCorp" on site, "Example Corp" on Wikipedia) |
| Logo | Same logo across site, GBP, social profiles |
| URL | Preferred domain used consistently |
| Description | Consistent value proposition across platforms |
| SameAs | Same set of social profiles referenced everywhere |
| Address | NAP consistency (for local entities) |
Consistency audit: Quarterly, review your entity signals across your site, Wikipedia, Wikidata, social profiles, GBP, and review sites.
Attribute and Fact Consistency
Ensure factual claims about your entity are consistent across all sources.
Fact consistency areas:
| Fact | Check |
|---|---|
| Founding date | Same year everywhere |
| Company size | Consistent employee count range |
| Revenue | Consistent revenue data |
| Product names | Same product names across all pages |
| Features | Consistent feature names and descriptions |
| Pricing | Consistent pricing across all pages |
Structured Entity Signals
Use structured data to reinforce entity information.
Entity-related schema types:
| Schema Type | Purpose |
|---|---|
| Organization | Brand entity definition |
| Person | Author, staff, expert entities |
| Product | Product entities |
| LocalBusiness | Location entities |
| WebSite | Site entity |
| BreadcrumbList | Content hierarchy relationships |
| SameAs | Entity identity links |
Entity schema implementation:
Organization Schema Example
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "ExampleCorp",
"url": "https://example.com",
"logo": "https://example.com/logo.png",
"sameAs": [
"https://www.linkedin.com/company/examplecorp",
"https://twitter.com/examplecorp",
"https://www.facebook.com/examplecorp"
],
"foundingDate": "2015",
"numberOfEmployees": "200"
}
SameAs and Profile Alignment
SameAs properties link your entity to authoritative external profiles.
SameAs best practices:
| Platform | URL Pattern |
|---|---|
https://www.linkedin.com/company/examplecorp | |
| Twitter/X | https://twitter.com/examplecorp |
https://www.facebook.com/examplecorp | |
| YouTube | https://www.youtube.com/@examplecorp |
| Wikipedia | https://en.wikipedia.org/wiki/ExampleCorp |
| GitHub | https://github.com/examplecorp |
https://www.instagram.com/examplecorp |
Profile alignment workflow:
- Claim your brand name on all major platforms.
- Ensure profile names are consistent.
- Link profiles to each other where possible.
- Include sameAs in your Organization schema.
- Verify profiles are public and up to date.
Workflow
- Define all relevant entities: organization, persons, products, places, events, and concepts. Document the canonical source URL for each entity.
- Implement entity schema: Organization schema on the homepage about/about page with sameAs, foundingDate, logo. Person schema on author pages with worksFor, jobTitle.
- Claim and unify profiles across Wikipedia, Wikidata, social platforms, knowledge bases. Ensure consistent entity name, logo, URL, and description across all platforms.
- Map entity relationships: document how entities relate (Organization → Product, Person → Organization, Organization → Place). Encode relationships in schema where properties exist.
- Audit entity consistency quarterly: check for name variations, outdated information, missing sameAs links, and attribute discrepancies across external sources.
Common Mistakes
- Assuming knowledge panels can be directly edited: Knowledge panels are algorithmically generated and you cannot request or edit them directly. You can only suggest changes through the knowledge panel feedback feature. Completing entity signals increases the chance of accuracy.
warning
- Using different brand names across platforms: "ExampleCorp" on your website but "Example Corp" on Wikipedia creates entity fragmentation. Use the same exact name everywhere.
- Neglecting sameAs links: Without sameAs in your Organization schema linking to Wikipedia, Wikidata, and social profiles, Google has fewer signals to connect your entity across platforms.
- Creating entity pages with no backlinks or references: An entity page that no other authoritative source acknowledges carries little weight. Earn Wikipedia mentions, press coverage, and links from authoritative directories.
- Forgetting to update entity data: Founding dates, employee counts, office locations, and product names that are outdated across multiple sources create inconsistency. Audit and update entity data quarterly.
Checklist
- Define all entity types (organization, persons, products, places, events)
- Document canonical source URLs for each entity
- Implement Organization schema with sameAs, logo, foundingDate on homepage/about page
- Implement Person schema on author pages with worksFor, jobTitle
- Claim and unify profiles on Wikipedia, Wikidata, LinkedIn, Twitter/X, Crunchbase
- Ensure consistent entity name, logo, URL, and description across all platforms
- Map entity relationships (Organization → Product, Person → Organization)
- Audit entity consistency across all platforms quarterly