When the user wants to optimize brand search for a company with multiple domains (e.g. parent company.com vs product.ai). Ensure the parent/company domain ranks first for brand queries. Also use when the user mentions "brand search," "multi-domain SEO," "company domain first," "parent vs product domain," "hub-spoke domain," "brand SERP control," or "differentiate company and product domains." For domain structure, use domain-architecture.
日本語の概要は準備中です。原文の説明を表示しています。
実行スコア 未検証
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
When a company has multiple domains (e.g., company.com and product.ai), ensure the company/main site ranks first for brand queries. Product sites focus on product keywords and do not compete for brand position. See domain-architecture for structure decisions; rebranding-strategy for domain change and migration.
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.
| Scenario | Description |
|---|---|
| Multiple domains | Company main site (company.com), product site (product.ai / product.io) |
| Brand query competition | Product site or third-party (Crunchbase, LinkedIn, reviews) may outrank main site for brand |
| Entity confusion | Legacy brands, sub-brands, directories dilute brand perception |
| Goal | Brand queries → company.com first; product.ai → product keywords only |
| Role | Domain | Responsibility |
|---|---|---|
| Hub | company.com | Brand #1; About, Research, ecosystem, product matrix |
| Spoke | product.ai | Product keywords, features, pricing; visible "by [Company]" and link back to company.com |
| Dimension | Hub (company.com) | Spoke (product.ai) |
|---|---|---|
| Audience | Investors, partners, media, developers | Product users, prospects |
| Keywords | Brand name, company name, industry | Product features, use cases |
| Content | Mission, About, Research, Events, product matrix | Features, Use Cases, Pricing, Sign up |
| Conversion | Contact, Waitlist, Early Access | Sign up, Try free, Pricing |
| Item | Recommendation |
|---|---|
| Title | Company full name + positioning, e.g. [Company] — [Slogan] | AI Research & Products |
| Meta Description | Company name, core business, partners; 150–160 chars |
| H1 | Company name or main slogan |
| URL | Canonicalize www vs non-www (301) |
| Item | Recommendation |
|---|---|
| About | Company intro, founders, founding date, positioning; link to product sites |
| Products | Product matrix; each product links to its site |
| Research / News | Papers, events, partnerships; increase brand mentions |
| FAQ | "What is [Company]?" "What is [Product]?"; FAQ schema |
| Item | Recommendation |
|---|---|
| Title | Product name + product description, e.g. [Product] — [Core function] or [Product keyword] | [Product]; avoid brand-only |
| About | "A product of Company" |
| Footer | "© [Company]" or "A [Company] Product" + link to company.com |
| Schema | SoftwareApplication with author or publisher pointing to Company |
Use Organization schema with subOrganization to define product relationships:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "[Company Name]",
"url": "https://www.company.com",
"description": "[Company description]",
"sameAs": ["https://linkedin.com/company/...", "https://github.com/..."],
"subOrganization": [
{
"@type": "SoftwareApplication",
"name": "[Product Name]",
"url": "https://product.ai",
"applicationCategory": "[Category]"
}
]
}
See entity-seo for full entity optimization. Key for multi-domain:
まだレビューはありません。使ってみた感想をお寄せください。
ログインなしで書き込めます。使ってみた感想、質問、動かなかった環境などを気軽にどうぞ。
まだコメントはありません。最初のコメントを書いてみませんか。
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.
日本語の概要は準備中です。原文の説明を表示しています。