kostja94/marketing-skills

rebranding-strategy

When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement.

Quelltext ansehen

Verwendung

  1. Installationsbefehl kopieren und das Quellpaket vor der Installation in der eigenen Agentenumgebung prüfen.
  2. Benötigte Werkzeuge, Zugangsdaten und Hosts im Original prüfen.
  3. Eingabe und gewünschtes Ergebnis beschreiben und die Ausgabe mit den Quellen abgleichen.
npx skills add https://github.com/kostja94/marketing-skills --skill rebranding-strategy

Vor dem Start

  • Die Installation umfasst weder Modellabo noch API-Kontingent oder Dateizugriffsrechte.
  • Sterne und Installationen zeigen Aktivität, keine unabhängige Qualitäts- oder Sicherheitsprüfung.
Originales Skill-Dokument

Aus dem Quell-Repository gerendert; Überschriften, Beispiele, Code, Tabellen, Links und Bilder bleiben erhalten.

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

Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

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)

PhaseDurationFocus
Audit & planWeeks 1–2Brand audit; inventory touchpoints; migration plan
PrepareWeeks 2–6New assets; redirect mapping; staging; backup
Pre-launchWeek 6–8Internal announcement; social handle check; teasers
LaunchWeek 8+Go live; 301 redirects; multi-channel announcement
Post-launch2–4 weeksMonitor 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

PracticePurpose
1:1 mappingEach 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/loopsOld URL → final destination directly; avoid A→B→C
Redirect mapping sheetDocument every old→new mapping; prevents ~80% of migration failures
Don't block in robots.txtRedirected 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

PhaseActions
Pre-LaunchFinalize new identity; audit social presence; secure handles across platforms; internal alignment
Build AnticipationTease with sneak peeks; cryptic visuals; influencer/ambassador previews; avoid announcing too soon
ExecuteAll 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

Verwandte Aufgaben

aus demselben Repository

Weitere Skills

Alle Skills
kostja94
Community

youtube-seo

When the user wants to optimize YouTube videos for search, create video descriptions, or improve channel visibility. Also use when the user mentions "YouTube SEO," "YouTube description," "YouTube tags," "YouTube thumbnail," "YouTube title," "YouTube channel," or "video SEO." For YouTube ads, use youtube-ads.

Installationen / 1h
3
GitHub Stars
1127
Aktualisiert
6. Nov.
kostja94
Community

brand-visual-generator

When the user wants to define, audit, or apply visual identity (typography, colors, spacing, design tokens, frontend aesthetics). Also use when the user mentions "brand style guide," "visual identity," "design system," "typography," "color palette," "brand guidelines," "AI brand aesthetics," "brand colors," "font choices," "spacing system," "design tokens," "motion," "distinctive design," "frontend aesthetics," "PowerPoint theme," "Google Slides brand," or "slide master colors." For brand story,

Installationen / 1h
2
GitHub Stars
1115
Aktualisiert
6. Nov.
kostja94
Community

medium-posts

When the user wants to write, publish, republish, or optimize posts on Medium.com (canonical tags, distribution, Medium SEO). Also use when the user mentions "Medium," "Medium article," "Medium story," "Medium publishing," "canonical Medium," or "publish on Medium." Not for general parasite SEO when Medium is not the target platform—use parasite-seo. For AI search visibility strategy, use generative-engine-optimization.

Installationen / 1h
2
GitHub Stars
1115
Aktualisiert
6. Nov.
kostja94
Community

breadcrumb-generator

Deprecated compatibility entry for Breadcrumb construction. This component is now maintained in Bricks; install and use component-builder to build a new Breadcrumb.

Installationen / 1h
1
GitHub Stars
1115
Aktualisiert
6. Nov.