rebranding-strategy
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection.
Best use case
rebranding-strategy is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection.
Teams using rebranding-strategy should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/rebranding/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How rebranding-strategy Compares
| Feature / Agent | rebranding-strategy | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain redirect." For domain choice, use domain-selection.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Strategy: Rebranding Guides rebranding execution: domain change, 301 redirects, migration checklist, and communication (social media, internal). Plan for months, not days or weeks. See **domain-selection** for initial domain choice; **domain-architecture** for domain structure decisions; **multi-domain-brand-seo** when multiple domains coexist. **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 brand and product info. Identify: 1. **Scope**: Full rebrand (name, domain, identity) vs partial (logo, messaging only) 2. **Domain change**: Yes or no; old → new mapping 3. **Timeline**: Target launch date; typical 4–12 weeks 4. **Channels**: Website, social, product UI, directories, email ## Rebranding Timeline (Typical) | Phase | Duration | Focus | |-------|----------|-------| | **Audit & plan** | Weeks 1–2 | Brand audit; inventory touchpoints; migration plan | | **Prepare** | Weeks 2–6 | New assets; redirect mapping; staging; backup | | **Pre-launch** | Week 6–8 | Internal announcement; social handle check; teasers | | **Launch** | Week 8+ | Go live; 301 redirects; multi-channel announcement | | **Post-launch** | 2–4 weeks | Monitor search, traffic; fix 404s; iterate | **Principle**: Plan for months. Avoid changing domain and major structure in one migration—split into smaller migrations when possible. ## 301 Redirect Best Practices | Practice | Purpose | |----------|---------| | **1:1 mapping** | Each old URL → most relevant new URL; never redirect all to homepage | | **301 (permanent)** | Use 301, not 302; 302 does not fully transfer SEO equity | | **No chains/loops** | Old URL → final destination directly; avoid A→B→C | | **Redirect mapping sheet** | Document every old→new mapping; prevents ~80% of migration failures | | **Don't block in robots.txt** | Redirected URLs should not be disallowed | ### Common Mistakes - Redirect chains (multiple hops) - Redirect loops - Redirecting everything to homepage - Using 302 for permanent moves - Blocking redirected URLs in robots.txt ## Domain Migration Checklist ### Pre-Migration - [ ] Create SEO migration plan - [ ] Collect benchmarks (GA4, GSC, rankings) - [ ] Run site crawler; inventory all pages - [ ] Create redirect mapping sheet (old URL → new URL) - [ ] Purchase new domain; configure DNS - [ ] Technical SEO audit - [ ] Staging environment; backup - [ ] Check for manual penalties on both domains ### Launch - [ ] Implement 301 redirects - [ ] Update Google Search Console (change of address) - [ ] Update sitemaps, robots.txt - [ ] Verify new site works; test redirects (curl, Screaming Frog) - [ ] Add GA4 annotation for migration date ### Post-Migration - [ ] Monitor GSC coverage; fix "Page with Redirect" issues - [ ] Fix 404s immediately - [ ] Expect temporary ranking fluctuation (2–4 weeks) - [ ] Do not delete old site as fallback ## Social Media Announcement ### Three Phases | Phase | Actions | |-------|---------| | **Pre-Launch** | Finalize new identity; audit social presence; secure handles across platforms; internal alignment | | **Build Anticipation** | Tease with sneak peeks; cryptic visuals; influencer/ambassador previews; avoid announcing too soon | | **Execute** | All platforms updated together; new bios, handles, visuals; compelling rebrand story (why, not what) | ### What to Avoid - Don't list steps or technical details—focus on story and benefit - Don't announce before all pieces are in place (mixed messaging) - Don't rely on one channel—multi-channel rollout - Don't bombard with "why we rebranded" unless it resonates ### Rebrand Story - **Anchor**: Emotionally resonating narrative; why now; how it benefits customers - **Avoid**: "We changed our logo" / "We updated our website" without context ## Internal Communication - Brief all employees before public launch - Explain strategic reasons; equip them to answer customer questions - Update email signatures, Slack, internal docs - Internal FAQ for common rebrand questions ## Output Format - **Timeline** (phases, milestones) - **Redirect mapping** approach (template, tools) - **Migration checklist** (customized) - **Social announcement plan** (phases, channels, content angles) - **Internal communication** (briefing, FAQ) ## Related Skills - **domain-selection**: Domain choice (Brand/PMD/EMD, TLD); informs new domain choice when rebranding - **domain-architecture**: Domain structure before/after rebrand - **website-structure**: New site structure after migration - **schema-markup**: Update Organization schema on new domain - **multi-domain-brand-seo**: When old and new domains coexist during transition - **branding**: Brand strategy, identity; rebranding implements the change - **brand-protection**: Sync impersonation checks when rebranding; update official domain declaration - **gtm-strategy**: Repositioning GTM; when repositioning includes rebrand
Related Skills
seo-strategy
When the user wants to plan SEO strategy, prioritize SEO work, or understand the SEO workflow. Also use when the user mentions "SEO strategy," "SEO plan," "SEO roadmap," "SEO priority," "SEO audit," "SEO workflow," "where to start SEO," "SEO approach," "organic growth strategy," "why SEO," "SEO value," or "search strategy." For technical/crawl audit execution, use seo-audit. For keyword research, use keyword-research. For AI search visibility, use generative-engine-optimization.
retention-strategy
When the user wants to reduce churn, improve customer retention, or plan lifecycle marketing. Also use when the user mentions "retention," "churn," "customer lifecycle," "churn prevention," "at-risk customers," or "loyalty program." For lifecycle, use growth-funnel.
pmf-strategy
When the user wants to validate product-market fit, measure PMF, or plan before scaling. Also use when the user mentions "PMF," "product-market fit," "product market fit," "Sean Ellis test," "very disappointed," "vitamin vs painkiller," "PMF validation," "premature scaling," or "validate before scale." For GTM after validation, use gtm-strategy.
indie-hacker-strategy
When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.
gtm-strategy
When the user wants to plan go-to-market strategy, GTM framework, or market entry. Also use when the user mentions "GTM," "go-to-market," "market entry," "new market," "repositioning," "PLG," "sales-led," "product-led," "marketing-led," "ICP," "buyer persona," "GTM motion," or "market expansion." For launch checklist, use product-launch.
cold-start-strategy
When the user wants to plan cold start, get first users, or launch a new product with zero traction. Also use when the user mentions "cold start," "cold start problem," "first users," "seed users," "finding users," "finding early users," "Fiverr Upwork," "comment outreach," "Twitter search users," "product launch strategy," "0 to 1 growth," "early-stage acquisition," "launch channels," "get first customers," "Product Hunt launch," "AppSumo," "LTD," "indie hacker," "bootstrapping," or "solo founder." For directory listing copy and submissions, use directory-submission. For Product Hunt day-of execution, use product-hunt-launch. For GTM motion design, use gtm-strategy.
pricing-strategy
When the user wants to plan, design, or optimize pricing strategy and structure. Also use when the user mentions "pricing strategy," "pricing model," "pricing tiers," "freemium," "value-based pricing," "anchoring," "price structure," or "monetization strategy." For pricing page, use pricing-page-generator.
discount-marketing-strategy
When the user wants to plan, implement, or optimize discount and promotional pricing strategy. Also use when the user mentions "discount strategy," "promo code," "coupon," "redeem code," "lifetime deal," "LTD," "AppSumo," "Black Friday," "Cyber Monday," "BFCM," "seasonal sale," or "promotional pricing." For pricing page, use pricing-page-generator.
paid-ads-strategy
When the user wants to plan paid ads strategy, allocate ad budget, or choose paid channels. Also use when the user mentions "paid ads," "paid media," "PPC," "SEM," "web ads," "app ads," "TV ads," "CTV," "OOH," "banner ads," "ad network," "ad alliance," "Taaft ads," "Shopify App Store ads," "Google Ads," "Meta Ads," "PMF testing," "PMF validation," "test product-market fit with ads," "ad spend," "ad budget," "ROAS," "paid acquisition," "Quality Score," or "ad-to-page alignment." For Google Ads execution, use google-ads. For Meta Ads execution, use meta-ads. For landing page alignment, use landing-page-generator.
open-source-strategy
When the user wants open source strategy, OSS commercialization, or open source growth. Also use when the user mentions "open source strategy," "OSS strategy," "open source commercialization," "open source to paid," "open core," "COSS," "commercial open source," "GitHub stars strategy," "DevHunt," "open source marketing," "open source growth," "Llama," "Dify," "Cursor," "open source business model," or "developer tools directory." For GitHub tactics, use github.
localization-strategy
When the user wants to plan or implement localization strategy for multilingual and global growth. Also use when the user mentions "localization," "multilingual," "i18n," "global expansion," "market entry," "localization strategy," "hreflang," "multi-language SEO," or "international SEO." For translation workflow, glossary, and style guide, use translation.
content-strategy
When the user wants to plan content for SEO, create content calendar, or build topic clusters. Also use when the user mentions "content strategy," "content plan," "topic clusters," "pillar content," "pillar page," "cluster articles," "editorial calendar," "content hub," "content planning," "content clusters," "topic cluster strategy," "content strategy for SEO," or "content calendar." For editorial mix, use content-marketing.