
Multi Domain Brand Seo
- 753 installs
- 787 repo stars
- Updated June 9, 2026
- kostja94/marketing-skills
multi-domain-brand-seo is a marketing skill that optimizes brand search rankings across multiple company domains for developers and growth engineers who need the main company site to rank first for branded queries.
About
multi-domain-brand-seo is a version 1.0.1 marketing skill from kostja94/marketing-skills for companies operating more than one domain—such as company.com alongside product.ai. The skill ensures the parent or company domain ranks first for brand queries while product sites support rather than cannibalize branded SERP positions. It activates on phrases like brand search, multi-domain SEO, parent vs product domain, hub-spoke domain, brand SERP control, and differentiate company and product domains. Developers and growth engineers reach for multi-domain-brand-seo when launching or restructuring domain portfolios and need actionable SEO guidance instead of generic single-domain checklists. For broader domain topology planning, the readme points to the related domain-architecture skill.
- Guarantees the parent/company domain ranks #1 for brand queries
- Prevents product sites and third-party directories from stealing brand SERP position
- References domain-architecture and rebranding-strategy skills for complete domain strategy
- Provides clear parent vs product domain keyword ownership rules
- Opens with 1-2 explanatory sentences on first use, then delivers direct output
Multi Domain Brand Seo by the numbers
- 753 all-time installs (skills.sh)
- +6 installs in the week ending Jul 25, 2026 (Skillselion tracking)
- Ranked #617 of 1,879 Marketing & SEO skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Jul 31, 2026 (Skillselion catalog sync)
npx skills add https://github.com/kostja94/marketing-skills --skill multi-domain-brand-seoAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 753 |
|---|---|
| repo stars | ★ 787 |
| Security audit | 3 / 3 scanners passed |
| Last updated | June 9, 2026 |
| Repository | kostja94/marketing-skills ↗ |
How do you rank the company domain first for brand searches?
Ensure their main company domain ranks first for brand searches when they operate multiple domains such as company.com and product.ai.
Who is it for?
Growth engineers and developers at companies with separate corporate and product domains who must control branded Google results.
Skip if: Single-domain products or teams seeking paid-ad or native-ad campaign playbooks instead of organic brand SERP strategy.
When should I use this skill?
The user mentions brand search, multi-domain SEO, parent vs product domain, hub-spoke domains, or brand SERP control.
What you get
Brand search strategy, hub-spoke domain guidance, and SERP differentiation plans for multi-domain companies.
- Brand SERP strategy
- Multi-domain SEO recommendations
By the numbers
- Published as version 1.0.1 of the multi-domain-brand-seo skill
Files
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] \ |
| 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] \ |
| 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
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 transition
Related skills
How it compares
Use multi-domain-brand-seo for branded SERP priority across domain portfolios; pair with domain-architecture for structural domain planning.
FAQ
What problem does multi-domain-brand-seo solve?
multi-domain-brand-seo helps companies with multiple domains ensure the main company site ranks first for brand queries while product domains support discovery without displacing the corporate brand in search results.
When should multi-domain-brand-seo be invoked?
multi-domain-brand-seo activates when users mention brand search, multi-domain SEO, parent vs product domain conflicts, hub-spoke structures, or brand SERP control across separate corporate and product URLs.
Is Multi Domain Brand Seo safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.