Multi domain brand SEO skill

When the user wants to optimize brand search for a company with multiple domains (e.g.

by kostja94·MIT license·★ 1,006 Stars on the repo·GitHub ↗

Use now

Files of Multi domain brand SEO

kostja94/main1 file shown
SKILL.md
Show the full text119 lines

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.

Typical Scenarios

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

Hub-Spoke Model

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

Differentiation

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

Avoid Cannibalization

  • Hub does not target Spoke product keywords (e.g., "virtual staging," "AI design tool")
  • Spoke does not target Hub brand keywords (Title avoids brand-only; add product description)
  • Internal links: Hub → Spoke (Products); Spoke → Hub (About, Footer)

Optimization Checklist

Hub (company.com) On-Page
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)
Hub Content & Structure
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
Spoke (product.ai) Differentiation
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
Schema (Hub)

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]"
    }
  ]
}

Entity & Knowledge Panel

See entity-seo for full entity optimization. Key for multi-domain:

  • Consistency: Same brand name, description, logo across Hub and Spoke
  • Entity Home: Authoritative About page on Hub as primary reference
  • Knowledge Panel: Claim via Google; suggest updates when available

Output Format

  • Hub vs Spoke mapping (domains, roles)
  • On-page checklist (Hub and Spoke)
  • Schema (Organization with subOrganization)
  • Internal linking plan
  • Cannibalization check
  • domain-architecture: Hub-Spoke structure; when to use multiple domains
  • schema-markup: Organization, SoftwareApplication; subOrganization
  • serp-features: Knowledge Panel, Sitelinks; brand SERP
  • entity-seo: Entity & Knowledge Panel; Organization schema; consistency
  • rebranding-strategy: Domain change; 301 redirects during transition
1---
2name: multi-domain-brand-seo
3description: 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.
4metadata:
5 version: 1.0.1
6---
7 
8# SEO: Multi-Domain Brand Search
9 
10When 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.
11 
12**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.
13 
14## Typical Scenarios
15 
16| Scenario | Description |
17|----------|-------------|
18| **Multiple domains** | Company main site (company.com), product site (product.ai / product.io) |
19| **Brand query competition** | Product site or third-party (Crunchbase, LinkedIn, reviews) may outrank main site for brand |
20| **Entity confusion** | Legacy brands, sub-brands, directories dilute brand perception |
21| **Goal** | Brand queries → company.com first; product.ai → product keywords only |
22 
23## Hub-Spoke Model
24 
25| Role | Domain | Responsibility |
26|------|--------|----------------|
27| **Hub** | company.com | Brand #1; About, Research, ecosystem, product matrix |
28| **Spoke** | product.ai | Product keywords, features, pricing; visible "by [Company]" and link back to company.com |
29 
30## Differentiation
31 
32| Dimension | Hub (company.com) | Spoke (product.ai) |
33|-----------|--------------------|---------------------|
34| **Audience** | Investors, partners, media, developers | Product users, prospects |
35| **Keywords** | Brand name, company name, industry | Product features, use cases |
36| **Content** | Mission, About, Research, Events, product matrix | Features, Use Cases, Pricing, Sign up |
37| **Conversion** | Contact, Waitlist, Early Access | Sign up, Try free, Pricing |
38 
39## Avoid Cannibalization
40 
41- Hub does not target Spoke product keywords (e.g., "virtual staging," "AI design tool")
42- Spoke does not target Hub brand keywords (Title avoids brand-only; add product description)
43- Internal links: Hub → Spoke (Products); Spoke → Hub (About, Footer)
44 
45## Optimization Checklist
46 
47### Hub (company.com) On-Page
48 
49| Item | Recommendation |
50|------|----------------|
51| **Title** | Company full name + positioning, e.g. `[Company] — [Slogan] \| AI Research & Products` |
52| **Meta Description** | Company name, core business, partners; 150–160 chars |
53| **H1** | Company name or main slogan |
54| **URL** | Canonicalize www vs non-www (301) |
55 
56### Hub Content & Structure
57 
58| Item | Recommendation |
59|------|----------------|
60| **About** | Company intro, founders, founding date, positioning; link to product sites |
61| **Products** | Product matrix; each product links to its site |
62| **Research / News** | Papers, events, partnerships; increase brand mentions |
63| **FAQ** | "What is [Company]?" "What is [Product]?"; FAQ schema |
64 
65### Spoke (product.ai) Differentiation
66 
67| Item | Recommendation |
68|------|----------------|
69| **Title** | Product name + product description, e.g. `[Product] — [Core function]` or `[Product keyword] \| [Product]`; avoid brand-only |
70| **About** | "A product of [Company](https://company.com)" |
71| **Footer** | "© [Company]" or "A [Company] Product" + link to company.com |
72| **Schema** | SoftwareApplication with `author` or `publisher` pointing to Company |
73 
74### Schema (Hub)
75 
76Use Organization schema with `subOrganization` to define product relationships:
77 
78```json
79{
80 "@context": "https://schema.org",
81 "@type": "Organization",
82 "name": "[Company Name]",
83 "url": "https://www.company.com",
84 "description": "[Company description]",
85 "sameAs": ["https://linkedin.com/company/...", "https://github.com/..."],
86 "subOrganization": [
87 {
88 "@type": "SoftwareApplication",
89 "name": "[Product Name]",
90 "url": "https://product.ai",
91 "applicationCategory": "[Category]"
92 }
93 ]
94}
95```
96 
97## Entity & Knowledge Panel
98 
99See **entity-seo** for full entity optimization. Key for multi-domain:
100- **Consistency**: Same brand name, description, logo across Hub and Spoke
101- **Entity Home**: Authoritative About page on Hub as primary reference
102- **Knowledge Panel**: Claim via Google; suggest updates when available
103 
104## Output Format
105 
106- **Hub vs Spoke** mapping (domains, roles)
107- **On-page checklist** (Hub and Spoke)
108- **Schema** (Organization with subOrganization)
109- **Internal linking** plan
110- **Cannibalization** check
111 
112## Related Skills
113 
114- **domain-architecture**: Hub-Spoke structure; when to use multiple domains
115- **schema-markup**: Organization, SoftwareApplication; subOrganization
116- **serp-features**: Knowledge Panel, Sitelinks; brand SERP
117- **entity-seo**: Entity & Knowledge Panel; Organization schema; consistency
118- **rebranding-strategy**: Domain change; 301 redirects during transition
119 

Discussion

Alternatives

Agentic Browsing ReadinessAudit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).Marketing · MITBacklink Profile AnalysisBacklink profile analysis: referring domains, anchor text distribution, toxic link detection, competitor gap analysis. Works with free APIs (Moz, Bing Webmaster, Common Crawl) and DataForSEO extension. Use when user says backlinks, link profile, referring domains, anchor text, toxic links, link gap, link building, disavow, or backlink audit.Marketing · MIT/setup-cmsConnect a CMS to notfair SEO tools. Guides users through configuring WordPress, Strapi, Contentful, or Ghost — tests the connection, and writes credentials to .env.local. Once set up, seo-analysis automatically cross- references CMS content against Google Search Console data. Use whenever the user says "connect my CMS", "set up WordPress", "configure Strapi", "add Contentful", "connect Ghost", or "CMS setup". Also trigger if the user asks why no CMS data appears in a seo-analysis report. · MITBacklink checkBacklink profile for any domain — referring domains, authority, anchors, new/lost links, and a side-by-side vs a competitor. Use when asked "check my backlinks", "backlink profile of X", "who links to them", or "link gap vs competitor".Marketing · MIT