multi-domain-brand-seo
Compare original and translation side by side
🇺🇸
Original
English🇨🇳
Translation
ChineseSEO: Multi-Domain Brand Search
SEO:多域名品牌搜索
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.
当一家公司拥有多个域名时(例如company.com和product.ai),需确保公司主站在品牌查询中排名第一。产品站点应聚焦产品关键词,不与主站竞争品牌排名。如需了解结构决策,可查看domain-architecture;如需了解域名变更与迁移,可查看rebranding-strategy。
调用规则:首次使用时,如有必要,先用1-2句话说明本技能的覆盖范围及重要性,再提供核心输出。后续使用或用户要求跳过说明时,直接输出核心内容。
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 |
| 场景 | 说明 |
|---|---|
| 多域名布局 | 公司主站(company.com)、产品站点(product.ai / product.io) |
| 品牌查询竞争 | 产品站点或第三方平台(Crunchbase、LinkedIn、评论网站)可能在品牌查询中超过主站排名 |
| 实体混淆 | 遗留品牌、子品牌、目录平台会稀释品牌认知 |
| 优化目标 | 品牌查询结果中company.com排名第一;product.ai仅聚焦产品关键词 |
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 |
| 角色 | 域名 | 职责 |
|---|---|---|
| 中心站 | company.com | 品牌排名第一;承载关于我们、研究内容、生态系统、产品矩阵等 |
| 辐射站 | product.ai | 聚焦产品关键词、功能、定价;明确标注“由[Company]出品”并链接回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 |
| 维度 | 中心站(company.com) | 辐射站(product.ai) |
|---|---|---|
| 目标受众 | 投资者、合作伙伴、媒体、开发者 | 产品用户、潜在客户 |
| 核心关键词 | 品牌名、公司名、行业术语 | 产品功能、使用场景 |
| 内容方向 | 企业使命、关于我们、研究成果、活动、产品矩阵 | 产品功能、使用场景、定价、注册入口 |
| 转化目标 | 联系我们、等待列表、提前试用 | 注册、免费试用、购买 |
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)
- 中心站不针对辐射站的产品关键词(例如“虚拟 staging”、“AI设计工具”)
- 辐射站不针对中心站的品牌关键词(标题避免仅使用品牌名;需添加产品描述)
- 内部链接:中心站→辐射站(产品页面);辐射站→中心站(关于我们、页脚)
Optimization Checklist
优化检查清单
Hub (company.com) On-Page
中心站(company.com)页面内优化
| Item | Recommendation |
|---|---|
| Title | Company full name + positioning, e.g. |
| Meta Description | Company name, core business, partners; 150–160 chars |
| H1 | Company name or main slogan |
| URL | Canonicalize www vs non-www (301) |
| 项目 | 优化建议 |
|---|---|
| 标题 | 公司全称+定位,例如 |
| 元描述 | 包含公司名、核心业务、合作伙伴;长度控制在150-160字符 |
| H1标签 | 公司名或核心口号 |
| URL规范 | 将www与非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 |
| 项目 | 优化建议 |
|---|---|
| 关于我们 | 公司介绍、创始人、成立时间、定位;链接至各产品站点 |
| 产品矩阵 | 展示全产品线;每个产品链接至对应站点 |
| 研究/新闻 | 学术论文、活动、合作信息;增加品牌提及量 |
| 常见问题 | 包含“什么是[Company]?”“什么是[Product]?”等问题;添加FAQ Schema |
Spoke (product.ai) Differentiation
辐射站(product.ai)差异化设置
| Item | Recommendation |
|---|---|
| Title | Product name + product description, e.g. |
| About | "A product of Company" |
| Footer | "© [Company]" or "A [Company] Product" + link to company.com |
| Schema | SoftwareApplication with |
| 项目 | 优化建议 |
|---|---|
| 标题 | 产品名+产品描述,例如 |
| 关于产品 | 标注“[Company]出品(链接至https://company.com)” |
| 页脚 | 标注“© [Company]”或“[Company]旗下产品”并链接至company.com |
| Schema设置 | 使用SoftwareApplication类型,将 |
Schema (Hub)
中心站Schema设置
Use Organization schema with to define product relationships:
subOrganizationjson
{
"@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]"
}
]
}使用Organization Schema并通过定义产品关系:
subOrganizationjson
{
"@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
实体与知识面板
- Consistency: Same brand name, description, logo across all platforms
- Entity Home: Authoritative About page on Hub as primary reference
- Knowledge Panel: Claim via Google; suggest updates when available
- WikiData / Wikipedia: Can support Knowledge Panel generation
- 一致性:所有平台使用相同的品牌名、描述、logo
- 实体主页:将中心站的权威“关于我们”页面作为主要参考源
- 知识面板:通过Google认领;如有更新建议及时提交
- WikiData/Wikipedia:可辅助生成知识面板
Output Format
输出格式
- Hub vs Spoke mapping (domains, roles)
- On-page checklist (Hub and Spoke)
- Schema (Organization with subOrganization)
- Internal linking plan
- Cannibalization check
- 中心站与辐射站映射(域名、角色)
- 页面内优化清单(中心站与辐射站)
- Schema代码(包含subOrganization的Organization类型)
- 内部链接规划
- 关键词内耗检查
Related Skills
相关技能
- domain-architecture: Hub-Spoke structure; when to use multiple domains
- schema-markup: Organization, SoftwareApplication; subOrganization
- serp-features: Knowledge Panel, Sitelinks; brand SERP
- rebranding-strategy: Domain change; 301 redirects during transition
- domain-architecture:中心-辐射式结构;多域名适用场景
- schema-markup:Organization、SoftwareApplication;subOrganization类型
- serp-features:知识面板、站点链接;品牌SERP
- rebranding-strategy:域名变更;过渡期间的301重定向