entity-seo
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.
Best use case
entity-seo is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using entity-seo should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/entity-seo/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How entity-seo Compares
| Feature / Agent | entity-seo | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
SKILL.md Source
# 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
Related Skills
website-structure
When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy." For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
seo-audit
When the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
research-sources
When the user wants to find information sources for content ideation, competitor monitoring, or industry tracking. Also use when the user mentions "research sources," "information sources," "content ideation," "industry monitoring," "competitor monitoring," "market intelligence," "content research," or "topic research." For keywords, use keyword-research.
product-launch
When the user wants to plan a product launch, execute launch channels, or create a launch checklist. Also use when the user mentions "product launch," "launch strategy," "product announcement," "launch channels," or "market launch." For GTM motion and positioning, use gtm-strategy. For cold start and first users, use cold-start-strategy. For Product Hunt day-of, use product-hunt-launch.
pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
indie-hacker-strategy
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
gtm-strategy
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
growth-funnel
When the user wants to plan growth using the AARRR framework, diagnose growth bottlenecks, or map actions across the customer lifecycle. Also use when the user mentions "growth funnel," "AARRR," "pirate metrics," "acquisition activation retention," "customer lifecycle metrics," or "growth framework." For retention tactics, use retention-strategy.
conversion-optimization
When the user wants to improve conversion rates, run A/B tests, optimize funnels, or reduce friction. Also use when the user mentions "CRO," "conversion rate optimization," "A/B test," "split test," "funnel optimization," "checkout optimization," "form optimization," or "conversion funnel." For pricing psychology, use pricing-strategy.
cold-start-strategy
When the user wants to plan cold start, get first users, or launch a new product with zero traction. Also use when the user mentions "cold start," "cold start problem," "first users," "seed users," "finding users," "finding early users," "Fiverr Upwork," "comment outreach," "Twitter search users," "product launch strategy," "0 to 1 growth," "early-stage acquisition," "launch channels," "get first customers," "Product Hunt launch," "AppSumo," "LTD," "indie hacker," "bootstrapping," or "solo founder." For directory listing copy and submissions, use directory-submission. For Product Hunt day-of execution, use product-hunt-launch. For GTM motion design, use gtm-strategy.