multi-domain-brand-seo
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.
Best use case
multi-domain-brand-seo is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using multi-domain-brand-seo should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/multi-domain-brand-seo/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How multi-domain-brand-seo Compares
| Feature / Agent | multi-domain-brand-seo | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Marketing
Discover AI agents for marketing workflows, from SEO and content production to campaign research, outreach, and analytics.
Best AI Agents for Marketing
A curated list of the best AI agents and skills for marketing teams focused on SEO, content systems, outreach, and campaign execution.
SKILL.md Source
# SEO: Multi-Domain Brand Search
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](https://company.com)" |
| **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:
```json
{
"@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
## Related Skills
- **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 transitionRelated Skills
domain-selection
When the user wants to choose an SEO-friendly domain for a new site—brand vs keyword domain, TLD selection, or domain best practices. Also use when the user mentions "domain choice," "pick domain," "SEO-friendly domain," "brand domain," "EMD," "PMD," "exact match domain," "partial match domain," "TLD," ".ai domain," ".com vs .io," "domain length," "domain history," or "defensive domain registration." For migration, use rebranding-strategy.
domain-architecture
When the user wants to decide domain structure for multiple products or brands—subfolder vs subdomain vs independent domain. Also use when the user mentions "subfolder vs subdomain," "subdirectory vs subdomain," "multiple products domain," "multiple websites," "brand architecture," "branded house," "house of brands," "where to host product," "domain structure," or "hub-spoke domain." For brand SERP, use multi-domain-brand-seo.
rebranding-strategy
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection.
brand-monitoring
When the user wants to monitor brand mentions, detect trademark infringement, or set up brand monitoring. Also use when the user mentions "brand monitoring," "brand watch," "trademark watch," "brand mentions," "impersonation detection," "counterfeit detection," or "brand abuse monitoring." For enforcement, use brand-protection.
brand-visual-generator
When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics). Also use when the user mentions "brand style guide," "visual identity," "design system," "typography," "color palette," "brand guidelines," "AI brand aesthetics," "brand colors," "font choices," "spacing system," "design tokens," "motion," "distinctive design," "frontend aesthetics," "PowerPoint theme," "Google Slides brand," or "slide master colors." For brand story, positioning, and voice, use branding.
branding
When the user wants to define, audit, or apply brand strategy—purpose, values, positioning, storytelling, voice, narrative (not only visuals). Also use when the user mentions "brand strategy," "brand story," "brand storytelling," "brand voice," "brand identity," "brand guidelines," "brand purpose," "brand values," "origin story," "brand narrative," "brand personality," "brand archetype," "slide deck branding," "PPT brand colors," or "document style guide." For typography, colors, design tokens, and frontend visuals, use brand-visual-generator.
brand-protection
When the user faces brand impersonation, fake websites, phishing sites, or trademark infringement. Also use when the user mentions "fake site," "impersonation," "phishing site," "trademark infringement," "domain squatting," or "brand abuse." For monitoring, use brand-monitoring.
website-structure
When the user wants to plan website structure, decide which pages to build, or prioritize pages for a new or existing site. Also use when the user mentions "website structure," "site structure," "which pages do I need," "page planning," "sitemap planning," "Must Have pages," "website architecture," or "site hierarchy." For a specific page template (e.g. homepage), use homepage-generator or landing-page-generator as appropriate. Not for organic SEO roadmap alone; use seo-strategy.
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
seo-audit
When the user wants to run an SEO audit, technical SEO audit, or site health check. Also use when the user mentions "SEO audit," "technical audit," "site audit," "crawl audit," "indexing audit," "SEO health," or "fix SEO issues." For prioritization and organic strategy, use seo-strategy. For GSC data analysis, use google-search-console.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
research-sources
When the user wants to find information sources for content ideation, competitor monitoring, or industry tracking. Also use when the user mentions "research sources," "information sources," "content ideation," "industry monitoring," "competitor monitoring," "market intelligence," "content research," or "topic research." For keywords, use keyword-research.