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:
- Scope: Full rebrand (name, domain, identity) vs partial (logo, messaging only)
- Domain change: Yes or no; old → new mapping
- Timeline: Target launch date; typical 4–12 weeks
- 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
Launch
Post-Migration
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
1---2name: rebranding-strategy3description: 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.4---5
6# Strategy: Rebranding
7
8Guides 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.
9
10**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.
11
12## Initial Assessment
13
14**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for brand and product info.
15
16Identify:
171. **Scope**: Full rebrand (name, domain, identity) vs partial (logo, messaging only)
182. **Domain change**: Yes or no; old → new mapping
193. **Timeline**: Target launch date; typical 4–12 weeks
204. **Channels**: Website, social, product UI, directories, email
21
22## Rebranding Timeline (Typical)
23
24| Phase | Duration | Focus |
25|-------|----------|-------|
26| **Audit & plan** | Weeks 1–2 | Brand audit; inventory touchpoints; migration plan |
27| **Prepare** | Weeks 2–6 | New assets; redirect mapping; staging; backup |
28| **Pre-launch** | Week 6–8 | Internal announcement; social handle check; teasers |
29| **Launch** | Week 8+ | Go live; 301 redirects; multi-channel announcement |
30| **Post-launch** | 2–4 weeks | Monitor search, traffic; fix 404s; iterate |
31
32**Principle**: Plan for months. Avoid changing domain and major structure in one migration—split into smaller migrations when possible.
33
34## 301 Redirect Best Practices
35
36| Practice | Purpose |
37|----------|---------|
38| **1:1 mapping** | Each old URL → most relevant new URL; never redirect all to homepage |
39| **301 (permanent)** | Use 301, not 302; 302 does not fully transfer SEO equity |
40| **No chains/loops** | Old URL → final destination directly; avoid A→B→C |
41| **Redirect mapping sheet** | Document every old→new mapping; prevents ~80% of migration failures |
42| **Don't block in robots.txt** | Redirected URLs should not be disallowed |
43
44### Common Mistakes
45
46- Redirect chains (multiple hops)
47- Redirect loops
48- Redirecting everything to homepage
49- Using 302 for permanent moves
50- Blocking redirected URLs in robots.txt
51
52## Domain Migration Checklist
53
54### Pre-Migration
55
56- [ ] Create SEO migration plan
57- [ ] Collect benchmarks (GA4, GSC, rankings)
58- [ ] Run site crawler; inventory all pages
59- [ ] Create redirect mapping sheet (old URL → new URL)
60- [ ] Purchase new domain; configure DNS
61- [ ] Technical SEO audit
62- [ ] Staging environment; backup
63- [ ] Check for manual penalties on both domains
64
65### Launch
66
67- [ ] Implement 301 redirects
68- [ ] Update Google Search Console (change of address)
69- [ ] Update sitemaps, robots.txt
70- [ ] Verify new site works; test redirects (curl, Screaming Frog)
71- [ ] Add GA4 annotation for migration date
72
73### Post-Migration
74
75- [ ] Monitor GSC coverage; fix "Page with Redirect" issues
76- [ ] Fix 404s immediately
77- [ ] Expect temporary ranking fluctuation (2–4 weeks)
78- [ ] Do not delete old site as fallback
79
80## Social Media Announcement
81
82### Three Phases
83
84| Phase | Actions |
85|-------|---------|
86| **Pre-Launch** | Finalize new identity; audit social presence; secure handles across platforms; internal alignment |
87| **Build Anticipation** | Tease with sneak peeks; cryptic visuals; influencer/ambassador previews; avoid announcing too soon |
88| **Execute** | All platforms updated together; new bios, handles, visuals; compelling rebrand story (why, not what) |
89
90### What to Avoid
91
92- Don't list steps or technical details—focus on story and benefit
93- Don't announce before all pieces are in place (mixed messaging)
94- Don't rely on one channel—multi-channel rollout
95- Don't bombard with "why we rebranded" unless it resonates
96
97### Rebrand Story
98
99- **Anchor**: Emotionally resonating narrative; why now; how it benefits customers
100- **Avoid**: "We changed our logo" / "We updated our website" without context
101
102## Internal Communication
103
104- Brief all employees before public launch
105- Explain strategic reasons; equip them to answer customer questions
106- Update email signatures, Slack, internal docs
107- Internal FAQ for common rebrand questions
108
109## Output Format
110
111- **Timeline** (phases, milestones)
112- **Redirect mapping** approach (template, tools)
113- **Migration checklist** (customized)
114- **Social announcement plan** (phases, channels, content angles)
115- **Internal communication** (briefing, FAQ)
116
117## Related Skills
118
119- **domain-selection**: Domain choice (Brand/PMD/EMD, TLD); informs new domain choice when rebranding
120- **domain-architecture**: Domain structure before/after rebrand
121- **website-structure**: New site structure after migration
122- **schema-markup**: Update Organization schema on new domain
123- **multi-domain-brand-seo**: When old and new domains coexist during transition
124- **branding**: Brand strategy, identity; rebranding implements the change
125- **brand-protection**: Sync impersonation checks when rebranding; update official domain declaration
126- **gtm-strategy**: Repositioning GTM; when repositioning includes rebrand
gabrielmoreira