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.
What this skill does
# 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 in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".