Multi Domain Brand Seo

作者 kostja948dd89c57395e無授權條款1K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫2 天前更新

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.

僅含說明Marketing & Sales

AI 產生的概覽

指導多網域品牌搜尋最佳化，讓公司主網域在品牌字詞查詢中排名領先產品網域。

功能: 此技能提供在公司擁有多個網域（例如母公司網站與產品網站）時最佳化品牌搜尋的說明。它定義了樞紐—分支模型、差異化規則、關鍵字蠶食檢查、頁面最佳化清單、帶 subOrganization 的 Organization 結構化資料、內部連結方案，以及包含樞紐與分支對應的輸出格式。產出的是結構化 SEO 方案，而非檔案或程式碼。
適用情境: 適用於公司擁有多個網域、希望主網域或公司網域在品牌字詞查詢中排名第一的情境。也適合涉及品牌搜尋結果頁控制、實體混淆，或母公司網域與產品網域爭奪品牌字詞的情況。
執行需求: 無需指令碼或特殊工具，僅為說明性文件。它引用 domain-architecture、schema-markup、serp-features、entity-seo 和 rebranding-strategy 等相關技能，並假定代理能夠處理 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

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"
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

{  "@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]"    }  ]}

{  "@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

來源與署名

來源：kostja94/marketing-skills位於skills/strategies/commercial/domain/multi-domain-brand-seo提交8dd89c5

授權條款：無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

Multi Domain Brand Seo

SEO: Multi-Domain Brand Search

Typical Scenarios

Hub-Spoke Model

Differentiation

Avoid Cannibalization

Optimization Checklist

Hub (company.com) On-Page

Hub Content & Structure

Spoke (product.ai) Differentiation

Schema (Hub)

Entity & Knowledge Panel

Output Format

Related Skills

來源與署名

更多來自 kostja94/marketing-skills 的技能

Website Structure

Domain Selection

Product Launch

Seo Audit

Growth Funnel

Research Sources

更多Marketing & Sales技能

Deal Sourcing

Investment Proposal

Content Strategy

Call List

Lead Triage

Draft Outreach