skills/seo/entity-seo/SKILL.md
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.
npx skillsauth add kostja94/marketing-skills entity-seoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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, Search Engine Land.
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.
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.
| 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 |
@id, name, url; add logo, sameAs (social, Wikidata)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.
name, url; affiliation (Organization); sameAs (LinkedIn, Twitter)https://example.com/author/jane/#personSee schema-markup for full VideoObject, Article, Product, etc.; Organization and Person are core for entity SEO.
| 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):
See serp-features for Knowledge Panel in SERP context; multi-domain-brand-seo for Hub-Spoke entity consistency.
When using multiple domains (Hub-Spoke):
See multi-domain-brand-seo for full strategy.
Entity signals strengthen GEO citation:
See generative-engine-optimization for full GEO strategy.
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
testing
When the user wants to add or optimize Open Graph metadata for social sharing. Also use when the user mentions "Open Graph," "og:tags," "og:title," "og:image," "og:description," "Facebook preview," "LinkedIn preview," or "social share preview." For X (Twitter) link previews, use twitter-cards. For SERP title/description, use title-tag and meta-description.
tools
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
development
When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border shipping," "international delivery," or "order tracking." For legal overview, use legal-page-generator.