explainx.ainewsletter3.4k
AI/ML

multi-domain-brand-seo▌

kostja94/marketing-skills · updated Apr 8, 2026

MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.

$npx skills add https://github.com/kostja94/marketing-skills --skill multi-domain-brand-seo
0 commentsdiscussion
summary

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.

skill.md

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

{
  "@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
how to use multi-domain-brand-seo

How to use multi-domain-brand-seo on Cursor

AI-first code editor with Composer

1

Prerequisites

Before installing skills in Cursor, ensure your development environment meets these requirements:

  • ›Cursor installed and configured on your development machine
  • ›Node.js version 16.0+ with npm package manager (verify with node --version)
  • ›Active project directory or workspace where you want to add multi-domain-brand-seo
2

Execute installation command

Execute the skills CLI command in your project's root directory to begin installation:

$npx skills add https://github.com/kostja94/marketing-skills --skill multi-domain-brand-seo

The skills CLI fetches multi-domain-brand-seo from GitHub repository kostja94/marketing-skills and configures it for Cursor.

3

Select Cursor when prompted

The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:

◆ Which agents do you want to install to?
│
│ ── Universal (.agents/skills) ── always included ────
│ • Amp
│ • Antigravity
│ • Cline
│ • Codex
│ ●Cursor(selected)
│ • Cursor
│ • Windsurf
4

Verify installation

Confirm successful installation by checking the skill directory location:

.cursor/skills/multi-domain-brand-seo

Reload or restart Cursor to activate multi-domain-brand-seo. Access the skill through slash commands (e.g., /multi-domain-brand-seo) or your agent's skill management interface.

⚠

Security & Verification Notice

We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.

Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.

Additional Resources

›View source code on GitHub›Skills CLI documentation›Learn more about Cursor›What are agent skills?

List & Monetize Your Skill

Submit your Claude Code skill and start earning

GET_STARTED →

Use Cases▌

Task Automation & Efficiency

Automate repetitive workflows and reduce manual effort

Example

Generate reports, summarize documents, draft communications

✓

Save 3-5 hours per week on routine tasks

Knowledge Enhancement

Learn new skills, understand complex topics, get expert guidance

Example

Explain concepts, provide examples, suggest learning resources

✓

Accelerate learning and skill development by 2x

Quality Improvement

Enhance output quality through reviews, suggestions, and refinements

Example

Review drafts, suggest improvements, catch errors

✓

Improve work quality by 30-40% with less effort

Implementation Guide▌

Prerequisites

  • ›Claude Desktop or compatible AI client with skill support
  • ›Clear understanding of task or problem to solve
  • ›Willingness to iterate and refine outputs

Time Estimate

15-45 minutes depending on use case complexity

Installation Steps

  1. 1.Install skill using provided installation command
  2. 2.Test with simple use case relevant to your work
  3. 3.Evaluate output quality and relevance
  4. 4.Iterate on prompts to improve results
  5. 5.Integrate into regular workflow if valuable

Common Pitfalls

  • ⚠Expecting perfect results without iteration
  • ⚠Not providing enough context in prompts
  • ⚠Using skill for tasks outside its intended scope
  • ⚠Accepting outputs without review and validation

Best Practices▌

✓ Do

  • +Start with clear, specific prompts
  • +Provide relevant context and constraints
  • +Review and refine all outputs before using
  • +Iterate to improve output quality
  • +Document successful prompt patterns

✗ Don't

  • −Don't use without understanding skill limitations
  • −Don't skip validation of outputs
  • −Don't share sensitive information in prompts
  • −Don't expect skill to replace human judgment

💡 Pro Tips

  • ★Be specific about desired format and style
  • ★Ask for multiple options to choose from
  • ★Request explanations to understand reasoning
  • ★Combine AI efficiency with human expertise

When to Use This▌

✓ Use When

Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.

✗ Avoid When

Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.

Learning Path▌

  1. 1Familiarize yourself with skill capabilities and limitations
  2. 2Start with low-risk, non-critical tasks
  3. 3Progress to more complex and valuable use cases
  4. 4Build expertise through regular use and experimentation

Discussion

Product Hunt–style comments (not star reviews)
  • No comments yet — start the thread.
general reviews

Ratings

4.6★★★★★55 reviews
  • ★★★★★Alexander Li· Dec 28, 2024

    Useful defaults in multi-domain-brand-seo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Olivia Brown· Dec 16, 2024

    I recommend multi-domain-brand-seo for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Chaitanya Patil· Dec 12, 2024

    multi-domain-brand-seo reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Anaya Torres· Dec 4, 2024

    Registry listing for multi-domain-brand-seo matched our evaluation — installs cleanly and behaves as described in the markdown.

  • ★★★★★Hassan Brown· Nov 23, 2024

    Useful defaults in multi-domain-brand-seo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.

  • ★★★★★Jin Sanchez· Nov 19, 2024

    Registry listing for multi-domain-brand-seo matched our evaluation — installs cleanly and behaves as described in the markdown.

  • ★★★★★Rahul Santra· Nov 15, 2024

    multi-domain-brand-seo is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

  • ★★★★★Hassan Taylor· Nov 7, 2024

    multi-domain-brand-seo reduced setup friction for our internal harness; good balance of opinion and flexibility.

  • ★★★★★Piyush G· Nov 3, 2024

    I recommend multi-domain-brand-seo for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.

  • ★★★★★Aisha Garcia· Nov 3, 2024

    multi-domain-brand-seo is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.

showing 1-10 of 55

1 / 6