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" or "domain migration". For domain choice, use domain-selection.4metadata:5 source: https://skillmd.com/skills/ariadoss/rebranding-strategy6 version: 1.0.17---89# Strategy: Rebranding1011Guides 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.1213**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.1415## Initial Assessment1617**Check for project context first:** If `.claude/project-context.md` or `.cursor/project-context.md` exists, read it for brand and product info.1819Identify:201. **Scope**: Full rebrand (name, domain, identity) vs partial (logo, messaging only)212. **Domain change**: Yes or no; old → new mapping223. **Timeline**: Target launch date; typical 4–12 weeks234. **Channels**: Website, social, product UI, directories, email2425## Rebranding Timeline (Typical)2627| Phase | Duration | Focus |28|-------|----------|-------|29| **Audit & plan** | Weeks 1–2 | Brand audit; inventory touchpoints; migration plan |30| **Prepare** | Weeks 2–6 | New assets; redirect mapping; staging; backup |31| **Pre-launch** | Week 6–8 | Internal announcement; social handle check; teasers |32| **Launch** | Week 8+ | Go live; 301 redirects; multi-channel announcement |33| **Post-launch** | 2–4 weeks | Monitor search, traffic; fix 404s; iterate |3435**Principle**: Plan for months. Avoid changing domain and major structure in one migration—split into smaller migrations when possible.3637## 301 Redirect Best Practices3839| Practice | Purpose |40|----------|---------|41| **1:1 mapping** | Each old URL → most relevant new URL; never redirect all to homepage |42| **301 (permanent)** | Use 301, not 302; 302 does not fully transfer SEO equity |43| **No chains/loops** | Old URL → final destination directly; avoid A→B→C |44| **Redirect mapping sheet** | Document every old→new mapping; prevents ~80% of migration failures |45| **Don't block in robots.txt** | Redirected URLs should not be disallowed |4647### Common Mistakes4849- Redirect chains (multiple hops)50- Redirect loops51- Redirecting everything to homepage52- Using 302 for permanent moves53- Blocking redirected URLs in robots.txt5455## Domain Migration Checklist5657### Pre-Migration5859- [ ] Create SEO migration plan60- [ ] Collect benchmarks (GA4, GSC, rankings)61- [ ] Run site crawler; inventory all pages62- [ ] Create redirect mapping sheet (old URL → new URL)63- [ ] Purchase new domain; configure DNS64- [ ] Technical SEO audit65- [ ] Staging environment; backup66- [ ] Check for manual penalties on both domains6768### Launch6970- [ ] Implement 301 redirects71- [ ] Update Google Search Console (change of address)72- [ ] Update sitemaps, robots.txt73- [ ] Verify new site works; test redirects (curl, Screaming Frog)74- [ ] Add GA4 annotation for migration date7576### Post-Migration7778- [ ] Monitor GSC coverage; fix "Page with Redirect" issues79- [ ] Fix 404s immediately80- [ ] Expect temporary ranking fluctuation (2–4 weeks)81- [ ] Do not delete old site as fallback8283## Social Media Announcement8485### Three Phases8687| Phase | Actions |88|-------|---------|89| **Pre-Launch** | Finalize new identity; audit social presence; secure handles across platforms; internal alignment |90| **Build Anticipation** | Tease with sneak peeks; cryptic visuals; influencer/ambassador previews; avoid announcing too soon |91| **Execute** | All platforms updated together; new bios, handles, visuals; compelling rebrand story (why, not what) |9293### What to Avoid9495- Don't list steps or technical details—focus on story and benefit96- Don't announce before all pieces are in place (mixed messaging)97- Don't rely on one channel—multi-channel rollout98- Don't bombard with "why we rebranded" unless it resonates99100### Rebrand Story101102- **Anchor**: Emotionally resonating narrative; why now; how it benefits customers103- **Avoid**: "We changed our logo" / "We updated our website" without context104105## Internal Communication106107- Brief all employees before public launch108- Explain strategic reasons; equip them to answer customer questions109- Update email signatures, Slack, internal docs110- Internal FAQ for common rebrand questions111112## Output Format113114- **Timeline** (phases, milestones)115- **Redirect mapping** approach (template, tools)116- **Migration checklist** (customized)117- **Social announcement plan** (phases, channels, content angles)118- **Internal communication** (briefing, FAQ)119120## Related Skills121122- **domain-selection**: Domain choice (Brand/PMD/EMD, TLD); informs new domain choice when rebranding123- **domain-architecture**: Domain structure before/after rebrand124- **website-structure**: New site structure after migration125- **schema-markup**: Update Organization schema on new domain126- **multi-domain-brand-seo**: When old and new domains coexist during transition127- **branding**: Brand strategy, identity; rebranding implements the change128- **brand-protection**: Sync impersonation checks when rebranding; update official domain declaration129- **gtm-strategy**: Repositioning GTM; when repositioning includes rebrand