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.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
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.
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
日本語の概要は準備中です。原文の説明を表示しています。
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
日本語の概要は準備中です。原文の説明を表示しています。