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.
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand and product info.
Identify:
| 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.
| 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 |
| 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) |