Rebranding Strategy
Plan a domain migration, 301 redirect map, and rebrand communications so traffic and trust do not collapse at cutover.
Overview
Rebranding Strategy is an agent skill most often used in Launch (also Operate, Grow) that plans domain migrations, 301 redirects, checklists, and rebrand announcements for solo builders changing brand identity.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill rebranding-strategyWhat is this skill?
- Scopes full vs partial rebrand and old→new domain mapping in an initial assessment
- Typical 4–12 week timeline with phased migration checklist
- 301 redirect and domain migration guidance paired with communication plans
- Cross-channel checklist: website, social, product UI, directories, email
- Points to domain-selection, domain-architecture, and multi-domain-brand-seo for adjacent decisions
- Typical rebranding timeline 4–12 weeks in skill guidance
Adoption & trust: 780 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are renaming or changing domains and fear broken links, lost SEO, and inconsistent messaging across product and social channels.
Who is it for?
Indie SaaS founders executing a real domain change with SEO equity to preserve and limited staff to run migration plus comms.
Skip if: A cosmetic logo refresh with no URL or domain impact, or initial domain purchase before a product exists—use domain-selection instead.
When should I use this skill?
User wants to plan or execute a rebrand, domain change, 301 redirects, migration, or announcement; triggers include rebranding, domain migration, and domain redirect phrasing.
What do I get? / Deliverables
You leave with a scoped rebrand plan, timeline, redirect/migration checklist, and channel communication outline aligned to a target launch date.
- Scoped rebrand assessment (full vs partial, domain change yes/no)
- Migration and 301 redirect checklist aligned to a target launch date
- Channel communication outline for web, social, product UI, directories, and email
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
A rebrand with domain change is primarily a search and discoverability risk, so Launch/SEO is the canonical shelf even though execution touches operations and growth channels. 301 redirects, indexation, and URL equity are the critical failure mode; the skill centers migration checklist and SEO-safe domain change before announcement choreography.
Where it fits
Build a 301 redirect list and migration window before flipping DNS to the new brand domain.
Coordinate hosting, TLS, and redirect validation during cutover night without dropping canonical URLs.
Decide full vs partial rebrand scope before committing engineering time to in-app string and asset replacements.
How it compares
Use for migration and announcement execution, not for first-time domain shopping or static brand guidelines without a cutover plan.
Common Questions / FAQ
Who is rebranding-strategy for?
Solo builders and tiny teams changing product name or domain who must coordinate redirects, site updates, and public announcements without a dedicated rebrand agency.
When should I use rebranding-strategy?
At Launch when mapping 301s before go-live, at Operate during DNS and redirect cutover, and at Grow when refreshing directory listings and social handles after the new brand ships.
Is rebranding-strategy safe to install?
It is procedural marketing guidance only; review the Security Audits panel on this Prism page and validate redirect and DNS changes in staging before production cutover.
SKILL.md
READMESKILL.md - Rebranding Strategy
# 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 b