rebranding-strategy by kostja94/marketing-skills
npx skills add https://github.com/kostja94/marketing-skills --skill rebranding-strategy指导品牌重塑执行:域名变更、301重定向、迁移清单以及沟通(社交媒体、内部)。规划以月为单位,而非数天或数周。关于初始域名选择,请参阅 domain-selection;关于域名结构决策,请参阅 domain-architecture;当多个域名共存时,请参阅 multi-domain-brand-seo。
调用时机:在首次使用时,如果合适,可以先用1-2句话说明此技能涵盖的内容及其重要性,然后提供主要输出。在后续使用或用戸要求跳过时,直接提供主要输出。
首先检查项目上下文:如果存在 .claude/project-context.md 或 .cursor/project-context.md 文件,请读取以获取品牌和产品信息。
识别:
| 阶段 | 持续时间 | 重点 |
|---|---|---|
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
| 第1-2周 |
| 品牌审计;盘点接触点;迁移计划 |
| 准备 | 第2-6周 | 新资产;重定向映射;暂存环境;备份 |
| 发布前 | 第6-8周 | 内部公告;检查社交媒体账号;预告 |
| 发布 | 第8周+ | 上线;实施301重定向;多渠道公告 |
| 发布后 | 2-4周 | 监控搜索、流量;修复404错误;迭代 |
原则:按数月进行规划。避免在一次迁移中同时变更域名和主要结构——尽可能拆分为多次较小的迁移。
| 实践 | 目的 |
|---|---|
| 1:1映射 | 每个旧URL → 最相关的新URL;切勿将所有旧URL重定向到首页 |
| 301(永久) | 使用301,而非302;302不能完全传递SEO权重 |
| 避免链式/循环重定向 | 旧URL → 直接跳转到最终目标;避免A→B→C |
| 重定向映射表 | 记录每个旧→新映射;可防止约80%的迁移失败 |
| 不要在robots.txt中屏蔽 | 重定向后的URL不应被禁止抓取 |
| 阶段 | 行动 |
|---|---|
| 发布前 | 确定新标识;审计社交媒体存在;确保跨平台账号;内部协调一致 |
| 营造期待 | 通过预览片段制造悬念;使用神秘视觉元素;影响者/大使预览;避免过早宣布 |
| 执行 | 所有平台同时更新;新的简介、账号、视觉元素;引人入胜的品牌重塑故事(为什么,而非是什么) |
每周安装量
188
代码库
GitHub星标数
239
首次出现
2026年3月5日
安全审计
安装于
cursor170
gemini-cli169
kimi-cli169
codex169
opencode169
github-copilot169
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.
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand and product info.
Identify:
| 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.
| 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 |
| 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) |
Weekly Installs
188
Repository
GitHub Stars
239
First Seen
Mar 5, 2026
Security Audits
Gen Agent Trust HubPassSocketPassSnykPass
Installed on
cursor170
gemini-cli169
kimi-cli169
codex169
opencode169
github-copilot169
社交媒体内容策略指南:创建、优化与互动全流程 | 营销技能
40,400 周安装