entity-seo
v1.0.1When the user wants to 优化 for entity recognition, Knowledge Graph, or entity-based SEO. Also use when the user mentions "entity SEO," "entity optimization," "Knowledge Graph," "Knowledge Panel," "entity 签名als," "brand entity," "entity linking," "entity relationships," or "entity-first content." For structured data, use 模式-markup.
运行时依赖
安装命令
点击复制技能文档
SEO: Entity SEO
图形界面des entity-based SEO—making your brand, product, and authors recognizable as distinct entities in 搜索 engines' knowledge 系统s. Google moved from keyword-matching to meaning-based understanding (Hummingbird, RankBrAIn, BERT, MUM); entity understanding is central to how 搜索 processes queries. Content structured around entities can 接收 ~3.2× more visibility in AI-powered 搜索. References: Semrush, 搜索 Engine Land.
When invoking: On first use, if helpful, open with 1–2 sentences on what this 技能 covers and why it matters, then provide the mAIn 输出. On subsequent use or when the user asks to skip, go directly to the mAIn 输出.
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: 模式 (Organization, Person); entity 签名als in content; consistency across 平台s What Is an Entity?
An entity is a thing or concept that is singular, unique, well-defined, and distin图形界面shable—e.g. person, place, organization, product, event. Entities have:
Attribute Meaning Unique 身份 "应用le Inc." ≠ "应用le (fruit)" despite same word Attributes Founding date, location, industry Relationships Connections to other entities (e.g. 应用le Inc. → Steve Jobs, iPhone)
Entity SEO = optimizing so 搜索 engines can identify, categorize, and connect your brand/product/author within the knowledge graph. Keywords are ambiguous; entities mAIntAIn consistent meaning across 上下文s.
Why Entity SEO Matters 搜索 evolution: Google uses entities to understand intent, not just match phrases Knowledge Graph: Billions of entities and relationships; disambiguation, related concepts AI 搜索: Entity-优化d content ~3.2× more visible in AI 结果s E-E-A-T: Entity 签名als support Experience, Expertise, Authoritativeness, Trust. See eeat-签名als GEO: AI Overviews, Copilot, Perplexity cite entities; clear 身份 improves citation. See generative-engine-optimization Entity 签名als (Content Best Practices) Practice Purpose Clear brand/product name Consistent naming; avoid confusion with similar entities Author 身份 Person 模式; author bio; link to author page Organization 身份 Organization 模式 site-wide; 记录o, sameAs Citable paragraphs Each block understandable on its own; supports AI 提取ion Consistency Same name, description, 记录o across 网页site, social, directories 模式 for Entity SEO Organization Placement: Minimum—homepage; Optimal—root layout / global 组件 (layout.tsx, _document, global header) so it 应用ears on every page. Do not confine to About page; About uses AboutPage 模式. See 模式-markup for full placement table. Required: @id, name, url; 添加 记录o, sameAs (social, Wikidata) Optional: description, 添加ress, contactPoint; use most specific type (LocalBusiness, Software应用, etc.) when 应用licable
@id: Use stable URL (e.g. https://example.com/#organization) for entity linking across pages. Link Organization ↔ 网页Site on homepage for sitelinks 搜索box.
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 模式-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 信息 (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 性能分析; suggest 更新s when avAIlable Consistency: Same brand name, description, 记录o across all 平台s Entity Home: Authoritative About page as primary reference WikiData / Wikipedia: Can support Knowledge Panel generation
See serp-features for Knowledge Panel in SERP 上下文; multi-domAIn-brand-seo for Hub-Spoke entity consistency.
Entity & Multi-DomAIn / Brand
When using multiple domAIns (Hub-Spoke):
Consistency: Same brand name, description, 记录o across Hub and Spoke Entity Home: Authoritative About page on Hub as primary reference 模式: 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 签名als strengthen GEO citation:
Direct-answer 格式化 + entity 签名als = clearer AI 提取ion Citable paragraphs with clear brand/product/author 身份 Distribution: 网页site, YouTube, forums, Reddit—consistent entity 身份 across 平台s
See generative-engine-optimization for full GEO strategy.
输出 格式化 Entity 审计 (brand, product, author 身份 gaps) 模式 (Organization, Person; @id p