Multi Domain Brand Seo

by kostja948dd89c57395eNo license1K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 2 days ago

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.

Instructions onlyMarketing & Sales
AI-generated overview

Guides multi-domain brand SEO so a company's main domain outranks product domains for brand queries.

What it does
This skill provides instructions for optimizing brand search when a company operates several domains, such as a parent company site and a product site. It defines a hub-and-spoke model, differentiation rules, cannibalization checks, on-page checklists, Organization schema with subOrganization, internal linking plans, and an output format covering hub-versus-spoke mapping. It produces a structured SEO plan rather than files or code.
When to use it
Use it when a company has multiple domains and wants its main or company domain to rank first for brand queries. It also fits situations involving brand SERP control, entity confusion, or competition between a parent domain and product domains for brand terms.
Requirements
No scripts or special tooling; it is an instructions-only document. It references related skills such as domain-architecture, schema-markup, serp-features, entity-seo, and rebranding-strategy, and assumes the agent can work with SEO concepts and schema markup.

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

ScenarioDescription
Multiple domainsCompany main site (company.com), product site (product.ai / product.io)
Brand query competitionProduct site or third-party (Crunchbase, LinkedIn, reviews) may outrank main site for brand
Entity confusionLegacy brands, sub-brands, directories dilute brand perception
GoalBrand queries → company.com first; product.ai → product keywords only

Hub-Spoke Model

RoleDomainResponsibility
Hubcompany.comBrand #1; About, Research, ecosystem, product matrix
Spokeproduct.aiProduct keywords, features, pricing; visible "by [Company]" and link back to company.com

Differentiation

DimensionHub (company.com)Spoke (product.ai)
AudienceInvestors, partners, media, developersProduct users, prospects
KeywordsBrand name, company name, industryProduct features, use cases
ContentMission, About, Research, Events, product matrixFeatures, Use Cases, Pricing, Sign up
ConversionContact, Waitlist, Early AccessSign 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

ItemRecommendation
TitleCompany full name + positioning, e.g. [Company] — [Slogan] | AI Research & Products
Meta DescriptionCompany name, core business, partners; 150–160 chars
H1Company name or main slogan
URLCanonicalize www vs non-www (301)

Hub Content & Structure

ItemRecommendation
AboutCompany intro, founders, founding date, positioning; link to product sites
ProductsProduct matrix; each product links to its site
Research / NewsPapers, events, partnerships; increase brand mentions
FAQ"What is [Company]?" "What is [Product]?"; FAQ schema

Spoke (product.ai) Differentiation

ItemRecommendation
TitleProduct 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
SchemaSoftwareApplication 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 transition

Source and attribution

Source:kostja94/marketing-skillsinskills/strategies/commercial/domain/multi-domain-brand-seoat commit8dd89c5

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal