Entity Seo
Structure your brand, product, and authors as recognizable entities so Google and AI search can cite you—not just match keywords.
Overview
entity-seo is an agent skill most often used in Launch (also Grow content) that guides entity recognition, Knowledge Graph signals, and entity-first content strategy.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill entity-seoWhat is this skill?
- Entity-based SEO aligned with Hummingbird, RankBrain, BERT, and MUM-style meaning retrieval
- Separates entities (concepts) from keywords (strings) for clearer topical architecture
- Knowledge Graph and Knowledge Panel orientation for brands, products, and people
- Entity linking and relationship guidance for stronger disambiguation
- Points to schema-markup skill when structured data is the next step
- References claim entity-structured content can see ~3.2× more visibility in AI-powered search (cited third-party sources
Adoption & trust: 949 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your site ranks on strings but search and AI systems do not consistently recognize your brand, product, or authors as distinct entities.
Who is it for?
Solo founders publishing marketing sites or content hubs who want Knowledge Graph-oriented SEO beyond keyword lists.
Skip if: Users who only need JSON-LD implementation without entity strategy—use schema-markup instead.
When should I use this skill?
User wants entity SEO, Knowledge Graph, Knowledge Panel, entity signals, brand entity, entity linking, or entity-first content.
What do I get? / Deliverables
You get an entity-first SEO plan—definitions, relationships, and content structure—ready to pair with schema-markup for structured data.
- Entity-first SEO recommendations
- Entity relationship and linking guidance
- Handoff notes for structured data via schema-markup
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Entity SEO targets discoverability and Knowledge Graph signals at go-live and beyond, so Launch → SEO is the canonical placement. The skill covers entity definitions, Knowledge Graph, and entity-first content—not paid distribution or app-store metadata.
Where it fits
Map brand, product, and founder entities before publishing core marketing URLs.
Shape copy so AI search can disambiguate your product from generic category terms.
Plan a content cluster that reinforces entity relationships between tools and use cases.
Audit whether a waitlist page introduces a clear brand entity before paid traffic arrives.
How it compares
Entity and Knowledge Graph strategy skill—not a structured-data code generator.
Common Questions / FAQ
Who is entity-seo for?
Indie marketers and builders optimizing SaaS, content, or ecommerce properties for brand and product entity visibility.
When should I use entity-seo?
At Launch when planning site architecture and copy for SEO; during Grow when expanding content that should reinforce entity relationships.
Is entity-seo safe to install?
It is editorial SEO guidance with no shell access—review the Security Audits panel on this page like any third-party skill.
Workflow Chain
Then invoke: schema markup
SKILL.md
READMESKILL.md - Entity Seo
# 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