Token导航 LogoToken导航TokenDH.com
研究检索需要联网github未标认证来源可访问许可证需确认审计通过

entity-seoentity SEO 搜索

Agent Skill

entity-seo 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

10,454

周安装

440

GitHub Stars

409

下载量

3,661
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:entity-seo(entity SEO 搜索)
来源仓库:https://github.com/kostja94/marketing-skills
仓库路径:skills/entity-seo
安装命令:
npx skills add https://github.com/kostja94/marketing-skills --skill entity-seo
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/kostja94/marketing-skills --skill entity-seo

简介

Entity SEO 搜索技能用于查找、检索和筛选相关信息。

  • 适合根据关键词或任务场景快速定位候选结果。entity-seo 属于研究检索类 Skill,可作为该场景下的辅助能力补充。
  • 可结合来源仓库和原始 README 继续核验具体用法。
  • 安装前建议确认权限范围和维护状态,避免触发不必要的网络请求。
  • 注意区分本地环境与生产环境的差异,防止误操作。

SKILL.md

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, 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.

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:

AttributeMeaning
Unique identity"Apple Inc." ≠ "apple (fruit)" despite same word
AttributesFounding date, location, industry
RelationshipsConnections 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)

PracticePurpose
Clear brand/product nameConsistent naming; avoid confusion with similar entities
Author identityPerson schema; author bio; link to author page
Organization identityOrganization schema site-wide; logo, sameAs
Citable paragraphsEach block understandable on its own; supports AI extraction
ConsistencySame 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

FeatureDescriptionObtainability
Knowledge PanelEntity info (brand, person, place) in SERPWikiData, partnerships; most sites cannot directly obtain
Knowledge CardTop-of-SERP semantic answerSame 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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

36.14%
按下载量换算1,323

Claude

27.13%
按下载量换算993

Cursor

17.36%
按下载量换算636

Gemini CLI

9.92%
按下载量换算363

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills