skills/strategies/commercial/domain/multi-domain-brand-seo/SKILL.md
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.
npx skillsauth add kostja94/marketing-skills multi-domain-brand-seoInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
| 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 |
| 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 |
| 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 |
| 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) |
| 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 |
| Item | Recommendation |
|------|----------------|
| Title | Product 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 |
| Schema | SoftwareApplication with author or publisher pointing to Company |
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]"
}
]
}
See entity-seo for full entity optimization. Key for multi-domain:
data-ai
When the user wants to add or optimize Twitter Card metadata for X (Twitter) link previews. Also use when the user mentions "Twitter Card," "twitter:card," "twitter:image," "twitter:title," "X preview," or "tweet preview." For Facebook/LinkedIn previews, use open-graph.
testing
When the user wants to add or optimize Open Graph metadata for social sharing. Also use when the user mentions "Open Graph," "og:tags," "og:title," "og:image," "og:description," "Facebook preview," "LinkedIn preview," or "social share preview." For X (Twitter) link previews, use twitter-cards. For SERP title/description, use title-tag and meta-description.
tools
When the user wants to create, optimize, or structure Terms of Service page. Also use when the user mentions "terms of service," "terms and conditions," "terms of use," "user agreement," "ToS," "legal terms," "service agreement," or "terms page." For legal overview page, use legal-page-generator.
development
When the user wants to create or optimize a shipping or delivery information page. Also use when the user mentions "shipping," "delivery," "shipping policy," "delivery times," "shipping page," "free shipping," "shipping rates," "delivery options," "shipping info," "cross-border shipping," "international delivery," or "order tracking." For legal overview, use legal-page-generator.