domain-architecture
When the user wants to decide domain structure for multiple products or brands—subfolder vs subdomain vs independent domain. Also use when the user mentions "subfolder vs subdomain," "subdirectory vs subdomain," "multiple products domain," "multiple websites," "brand architecture," "branded house," "house of brands," "where to host product," "domain structure," or "hub-spoke domain." For brand SERP, use multi-domain-brand-seo.
What this skill does
# Strategy: Domain Architecture Guides domain structure decisions for multiple products or brands: subfolder (subdirectory), subdomain, or independent domain. Covers brand architecture (Branded House vs House of Brands) and Hub-Spoke principles when multiple domains coexist. See **domain-selection** for initial domain choice (Brand/PMD/EMD, TLD); **website-structure** for single-domain page planning; **rebranding-strategy** for domain change and migration; **multi-domain-brand-seo** for brand search optimization. **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. ## Initial Assessment **Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for product portfolio and growth goals. Identify: 1. **Product count**: Single product vs multiple products/brands 2. **Brand strategy**: Unified brand vs distinct brands 3. **Current state**: Planning from scratch vs consolidating existing domains 4. **Constraints**: Tech stack, team, budget ## Domain Structure Options | Structure | Example | SEO Authority | Brand Independence | Typical Use | |-----------|---------|---------------|-------------------|-------------| | **Subfolder** | company.com/product-a | Shared with main domain | Low | Products under one brand; SMB; content consolidation | | **Subdomain** | product.company.com | Treated separately by Google | Medium | Separate product experience; tech isolation; support/docs | | **Independent domain** | product.ai | None shared | High | Acquired brands; different markets; distinct brand identity | ### When to Use Each | Choose | When | |--------|------| | **Subfolder** | Products share value proposition; want to strengthen main domain; SMB; blog, tools, features under one brand | | **Subdomain** | Need separate tech stack (e.g., app vs marketing); support portal; docs; distinct UX but same brand | | **Independent domain** | House of Brands; acquired company; different audience; different TLD (e.g., .ai for AI product) | **SEO consensus**: Subfolders typically outperform subdomains for most cases—authority flows to the main domain. Subdomains require separate SEO effort. ## Brand Architecture | Model | Description | Domain Tendency | Examples | |-------|-------------|-----------------|----------| | **Branded House** | One master brand; products use functional descriptors | Subfolder or subdomain | Google (google.com/search, google.com/maps), FedEx | | **House of Brands** | Each brand independent; parent hidden | Independent domains | Unilever (dove.com, axe.com) | | **Sub-brands / Endorsed** | Sub-brands with parent endorsement | Subdomain or independent | FedEx Express, Marriott Bonvoy | **Decision factors**: Business strategy, market positioning, product overlap, resource availability. ## Hub-Spoke (Multiple Domains Coexist) When company main site (company.com) and product site (product.ai) both exist: | Role | Domain | Focus | |------|--------|-------| | **Hub** | company.com | Brand, About, Research, product matrix; brand queries | | **Spoke** | product.ai | Product features, pricing, signup; product queries | **Principles**: - Hub links to Spoke (Products section); Spoke links back (About, Footer, "A [Company] product") - Spoke avoids competing for brand queries in Title; Hub avoids competing for product keywords - See **multi-domain-brand-seo** for brand search optimization. ## Output Format - **Recommendation** (subfolder / subdomain / independent) with rationale - **Brand architecture** fit (Branded House / House of Brands / Sub-brands) - **Domain mapping** (e.g., product A → company.com/product-a) - **Hub-Spoke** guidance (if multiple domains) - **Related** next steps (website-structure, rebranding-strategy) ## Related Skills - **domain-selection**: Initial domain choice (Brand/PMD/EMD, TLD); single-site use case - **website-structure**: Plan pages within a domain; single-domain structure - **rebranding-strategy**: Domain change, 301 redirects, migration - **multi-domain-brand-seo**: Brand search control when Hub and Spoke coexist - **branding**: Brand strategy, positioning; domain architecture implements brand structure
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".