Multi Domain Brand Seo
Keep the parent company domain ranking first for brand queries when product lives on a separate .ai or .io domain, for solo founders with split company vs product sites.
Overview
Multi-domain-brand-seo is an agent skill most often used in Launch (also Idea, Operate) that aligns hub-spoke domains so the parent company site wins branded search over product or third-party URLs.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill multi-domain-brand-seoWhat is this skill?
- Scenarios: multi-domain stacks, product site outranking company.com, third-party directories diluting brand
- Goal: company/main site ranks first on brand queries; product domains target product keywords
- Cross-links domain-architecture for structure and rebranding-strategy for migrations
- Table-driven typical scenarios (entity confusion, Crunchbase/LinkedIn competition)
- First-use framing optional; subsequent runs go straight to recommendations
- Typical scenarios table covering multi-domain, brand competition, and entity confusion patterns
Adoption & trust: 726 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Searching your company name surfaces the product .ai site, directories, or reviews instead of your main corporate domain.
Who is it for?
Founders with company.com plus product.ai/io who need intentional brand vs product keyword split on Google.
Skip if: Single-domain startups, pure technical DNS cutovers without SEO entity goals, or general on-page SEO unrelated to brand cannibalization.
When should I use this skill?
User wants brand search optimization across multiple domains or mentions brand search, multi-domain SEO, company domain first, hub-spoke, or brand SERP control.
What do I get? / Deliverables
You get a prioritized brand-search playbook—query ownership, domain roles, and when to use domain-architecture or rebranding-strategy—for clearer branded SERPs.
- Brand-query ownership recommendations by domain role
- Scenario-matched mitigation checklist
- Pointers to domain-architecture or rebranding-strategy when structural change is needed
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Brand SERP control is a Launch/geo and seo concern but also matters in Operate when entity confusion persists and in Idea when choosing domains. SEO subphase covers brand query ownership, canonical signals, and hub-spoke differentiation on search results pages.
Where it fits
Choose whether product launches on .ai while keeping brand authority on .com before committing DNS.
Fix branded SERPs where Taboola-style third parties or the product domain sits above company.com.
Re-check brand queries after a sub-brand launch dilutes parent visibility.
How it compares
Brand SERP and multi-domain entity skill—not generic domain-architecture IA-only planning.
Common Questions / FAQ
Who is multi-domain-brand-seo for?
Solo builders and indie teams running separate company and product domains who care which URL appears for branded Google searches.
When should I use multi-domain-brand-seo?
Use in Launch/SEO for brand SERP fixes; in Idea when planning parent vs product domains; in Operate when monitoring confusion; when user says brand search, multi-domain SEO, hub-spoke, or parent vs product domain.
Is multi-domain-brand-seo safe to install?
Review the Security Audits panel on this Prism page before installing; the skill advises strategy rather than executing unchecked site changes.
Workflow Chain
Then invoke: domain architecture, rebranding strategy
SKILL.md
READMESKILL.md - Multi Domain Brand Seo
# 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 { "@con