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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionmulti-domain-brand-seoExecute the skills CLI command in your project's root directory to begin installation:
Fetches multi-domain-brand-seo from kostja94/marketing-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate multi-domain-brand-seo. Access via /multi-domain-brand-seo in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
309
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
309
stars
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:
Prerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
kostja94/marketing-skills
laguagu/claude-code-nextjs-skills
Useful defaults in multi-domain-brand-seo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend multi-domain-brand-seo for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
multi-domain-brand-seo reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for multi-domain-brand-seo matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in multi-domain-brand-seo — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for multi-domain-brand-seo matched our evaluation — installs cleanly and behaves as described in the markdown.
multi-domain-brand-seo is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
multi-domain-brand-seo reduced setup friction for our internal harness; good balance of opinion and flexibility.
I recommend multi-domain-brand-seo for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
multi-domain-brand-seo is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 55