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#

ScenarioDescriptionMultiple 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 brandEntity confusionLegacy brands, sub-brands, directories dilute brand perceptionGoalBrand queries → company.com first; product.ai → product keywords only

Hub-Spoke Model#

RoleDomainResponsibilityHubcompany.comBrand #1; About, Research, ecosystem, product matrixSpokeproduct.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, prospectsKeywordsBrand name, company name, industryProduct features, use casesContentMission, About, Research, Events, product matrixFeatures, Use Cases, Pricing, Sign upConversionContact, 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#

ItemRecommendationTitleCompany full name + positioning, e.g. [Company] — [Slogan] | AI Research & ProductsMeta DescriptionCompany name, core business, partners; 150–160 charsH1Company name or main sloganURLCanonicalize www vs non-www (301)

Hub Content & Structure#

ItemRecommendationAboutCompany intro, founders, founding date, positioning; link to product sitesProductsProduct matrix; each product links to its siteResearch / NewsPapers, events, partnerships; increase brand mentionsFAQ"What is [Company]?" "What is [Product]?"; FAQ schema

Spoke (product.ai) Differentiation#

ItemRecommendationTitleProduct name + product description, e.g. [Product] — [Core function] or [Product keyword] | [Product]; avoid brand-onlyAbout"A product of Company"Footer"© [Company]" or "A [Company] Product" + link to company.comSchemaSoftwareApplication 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