entity-seo

$npx mdskill add kostja94/marketing-skills/entity-seo

Optimize content for entity recognition and Knowledge Graph visibility.

  • Helps users make their brand and content recognizable as distinct entities.
  • Relies on Google's Knowledge Graph and entity-based search algorithms.
  • Analyzes content to align with entity signals and relationships.
  • Provides actionable recommendations for entity-first content optimization.

SKILL.md

.github/skills/entity-seoView on GitHub ↗
---
name: entity-seo
description: When the user wants to optimize for entity recognition, Knowledge Graph, or entity-based SEO. Also use when the user mentions "entity SEO," "entity optimization," "Knowledge Graph," "Knowledge Panel," "entity signals," "brand entity," "entity linking," "entity relationships," or "entity-first content." For structured data, use schema-markup.
metadata:
  version: 1.0.1
---

# SEO: Entity SEO

Guides entity-based SEO—making your brand, product, and authors recognizable as distinct entities in search engines' knowledge systems. Google moved from keyword-matching to meaning-based understanding (Hummingbird, RankBrain, BERT, MUM); entity understanding is central to how search processes queries. Content structured around entities can receive ~3.2× more visibility in AI-powered search. References: [Semrush](https://www.semrush.com/blog/entity-based-seo-strategy/), [Search Engine Land](https://searchengineland.com/guide/entity-first-content-optimization).

**When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output.

## Scope

- **Entity definition**: Singular, unique, well-defined things (person, place, organization, product, event)
- **Entity vs keyword**: Entities = underlying concepts; keywords = text strings
- **Knowledge Graph**: Google's entity database; powers disambiguation and related concepts
- **Implementation**: Schema (Organization, Person); entity signals in content; consistency across platforms

## What Is an Entity?

An **entity** is a thing or concept that is singular, unique, well-defined, and distinguishable—e.g. person, place, organization, product, event. Entities have:

| Attribute | Meaning |
|----------|---------|
| **Unique identity** | "Apple Inc." ≠ "apple (fruit)" despite same word |
| **Attributes** | Founding date, location, industry |
| **Relationships** | Connections to other entities (e.g. Apple Inc. → Steve Jobs, iPhone) |

**Entity SEO** = optimizing so search engines can identify, categorize, and connect your brand/product/author within the knowledge graph. Keywords are ambiguous; entities maintain consistent meaning across contexts.

## Why Entity SEO Matters

- **Search evolution**: Google uses entities to understand intent, not just match phrases
- **Knowledge Graph**: Billions of entities and relationships; disambiguation, related concepts
- **AI search**: Entity-optimized content ~3.2× more visible in AI results
- **E-E-A-T**: Entity signals support Experience, Expertise, Authoritativeness, Trust. See **eeat-signals**
- **GEO**: AI Overviews, Copilot, Perplexity cite entities; clear identity improves citation. See **generative-engine-optimization**

## Entity Signals (Content Best Practices)

| Practice | Purpose |
|----------|---------|
| **Clear brand/product name** | Consistent naming; avoid confusion with similar entities |
| **Author identity** | Person schema; author bio; link to author page |
| **Organization identity** | Organization schema site-wide; logo, sameAs |
| **Citable paragraphs** | Each block understandable on its own; supports AI extraction |
| **Consistency** | Same name, description, logo across website, social, directories |

## Schema for Entity SEO

### Organization

- **Placement**: **Minimum**—homepage; **Optimal**—root layout / global component (layout.tsx, _document, global header) so it appears on every page. Do **not** confine to About page; About uses AboutPage schema. See **schema-markup** for full placement table.
- **Required**: `@id`, `name`, `url`; add `logo`, `sameAs` (social, Wikidata)
- **Optional**: `description`, `address`, `contactPoint`; use most specific type (LocalBusiness, SoftwareApplication, etc.) when applicable

**@id**: Use stable URL (e.g. `https://example.com/#organization`) for entity linking across pages. Link Organization ↔ WebSite on homepage for sitelinks searchbox.

### Person

- **Use**: Author pages; Article author; team members
- **Properties**: `name`, `url`; `affiliation` (Organization); `sameAs` (LinkedIn, Twitter)
- **@id**: Enables entity linking; e.g. `https://example.com/author/jane/#person`

See **schema-markup** for full VideoObject, Article, Product, etc.; Organization and Person are core for entity SEO.

## Knowledge Panel & Knowledge Card

| Feature | Description | Obtainability |
|---------|-------------|---------------|
| **Knowledge Panel** | Entity info (brand, person, place) in SERP | WikiData, partnerships; most sites cannot directly obtain |
| **Knowledge Card** | Top-of-SERP semantic answer | Same as Knowledge Panel |

**Actions** (limited control):
- **Claim**: Google Business Profile; suggest updates when available
- **Consistency**: Same brand name, description, logo across all platforms
- **Entity Home**: Authoritative About page as primary reference
- **WikiData / Wikipedia**: Can support Knowledge Panel generation

See **serp-features** for Knowledge Panel in SERP context; **multi-domain-brand-seo** for Hub-Spoke entity consistency.

## Entity & Multi-Domain / Brand

When using multiple domains (Hub-Spoke):
- **Consistency**: Same brand name, description, logo across Hub and Spoke
- **Entity Home**: Authoritative About page on Hub as primary reference
- **Schema**: Organization with subOrganization for related entities
- **Entity confusion**: Avoid legacy brands, sub-brands, directories diluting brand perception

See **multi-domain-brand-seo** for full strategy.

## GEO & AI Citation

Entity signals strengthen GEO citation:
- **Direct-answer format** + **entity signals** = clearer AI extraction
- **Citable paragraphs** with clear brand/product/author identity
- **Distribution**: Website, YouTube, forums, Reddit—consistent entity identity across platforms

See **generative-engine-optimization** for full GEO strategy.

## Output Format

- **Entity audit** (brand, product, author identity gaps)
- **Schema** (Organization, Person; @id placement)
- **Consistency** checklist (name, logo, description across touchpoints)
- **Knowledge Panel** (claim if eligible; suggest updates)

## Related Skills

- **schema-markup**: Organization, Person; @id for entity linking
- **eeat-signals**: E-E-A-T; author bio; Person schema
- **generative-engine-optimization**: GEO; entity signals for AI citation
- **serp-features**: Knowledge Panel, Knowledge Card; SERP context
- **multi-domain-brand-seo**: Entity & Knowledge Panel; Hub-Spoke consistency
- **about-page-generator**: Entity Home; authoritative brand reference

More from kostja94/marketing-skills

SkillDescription
404-page-generatorWhen the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
about-page-generatorWhen the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
affiliate-marketingWhen the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
affiliate-page-generatorWhen the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
ai-traffic-trackingWhen the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
alternatives-page-generatorWhen the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
api-page-generatorWhen the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
app-adsWhen the user wants to run app install ads, user acquisition (UA), or promote mobile apps. Also use when the user mentions "app ads," "app install ads," "UA," "user acquisition," "Google App Campaigns," "Apple Search Ads," "ASA," "UAC," "App Store ads," "Play Store ads," "CPI," or "app promotion." For store listings, use distribution-channels.
article-contentWhen the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.
backlink-analysisWhen the user wants to analyze backlinks, audit link profile, or identify link issues. Also use when the user mentions "backlink analysis," "backlink audit," "referring domains," "toxic links," "link profile," or "disavow file." For acquisition, use link-building.