Skip to main content
skill CX Codex

content-migration — Claude Code skill: migrate content while preserving SEO

The content-migration skill guides you through moving content across platforms, domains, or URL structures without losing search positions, user bookmarks, or integrations. Use it for CMS migrations, site consolidations, or restructuring.

MIT 281 installs ★ 1,107 updated 2026-10-19

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add rampstackco/claude-skills --skill content-migration -a claude-code
Open on GitHub

What content-migration does

content-migration breaks the process into six phases: inventory (collect all URLs, traffic, backlinks), audit (decide what to keep, update, merge, or delete), URL mapping (set up 301s and 410s), staging and testing, cutover (with stakeholder communication), and monitoring for the next 30–90 days.

Each phase includes concrete steps: exporting from your current CMS, analyzing Search Console data, testing redirects, and tracking traffic recovery. Every content decision gets recorded in a spreadsheet that becomes the migration source of truth. The skill works stack-agnostic: WordPress to headless, mergers, domain rebrands, custom builds.

You'll need access to your current platform, 12 months of traffic data, Search Console, and backlink analysis tools. Without a complete inventory and URL map, the migration will almost certainly lose traffic.

What it helps with

  • plan a CMS migration without losing search rankings
  • build a redirect map for hundreds or thousands of URLs
  • merge multiple sites into one while preserving inbound links
  • restructure URLs and move traffic to new paths
  • catch and fix errors in the first 30 days after cutover

Example prompts for the agent

  • Walk me through migrating from WordPress to a headless setup—what could break and how do I prevent it
  • Generate a redirect map for moving to a new domain; we have roughly 2000 pages
  • Give me a testing checklist for redirects before we switch DNS

How to install content-migration

1Skills CLI (Vercel)

npx skills add rampstackco/claude-skills --skill content-migration -a claude-code

2Manually: put the files in place

~/.claude/skills/content-migration/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/content-migration/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about content-migration

How do I install content-migration in Claude Code?

Run npx skills add rampstackco/claude-skills --skill content-migration -a claude-code, then open ~/.claude/skills/content-migration/SKILL.md.

What does content-migration do?

It walks you through six phases: building a complete inventory of old URLs, auditing which content to keep or update, mapping every redirect, staging the new site, executing the cutover, and monitoring traffic recovery for 30–90 days afterward. Each phase has concrete checklists and rules to prevent losing traffic or rankings.

What do I need before starting?

Access to your current platform, traffic data for the past year, Search Console access, and a backlink analysis tool. You'll also need decisions on every page—keep it, refresh it, merge it with another, redirect it, or delete it—and a complete map of old URLs to new ones.

Source text

SKILL.md · MIT
---
name: content-migration
description: "Move content between platforms, domains, or URL structures while preserving SEO equity, user bookmarks, and integrations. Use this skill when planning a CMS migration, replatforming, consolidating sites, changing URL structures, or merging content from multiple sources. Triggers on content migration, replatform, CMS migration, domain migration, URL restructure, redirect map, site merge, content consolidation, migration plan, post-migration drop. Also triggers when planning a launch that involves moving existing content."
category: cross-cutting
catalog_summary: "Platform migrations with SEO equity preservation"
display_order: 2
---

# Content Migration

Move content from one platform, domain, or URL structure to another without breaking SEO, user bookmarks, or downstream integrations. Stack-agnostic.

---

## When to use

- Migrating from one CMS to another (e.g., WordPress to a headless setup)
- Consolidating multiple sites into one
- Splitting one site into multiple
- Changing URL structures
- Domain migration (one brand to another, mergers, rebrands)
- Migrating from a custom build to a platform (or vice versa)
- Content audit-driven cleanup as part of a larger move

## When NOT to use

- A net-new site with no existing content (no migration needed)
- Single-page edits or content updates within an existing site (use `content-and-copy`)
- Performance or technical SEO improvements without URL changes (use `seo-technical`)
- Routine content audits (use `seo-content-audit`)

---

## Required inputs

- The source: current platform, current URL structure, current content inventory
- The destination: target platform, target URL structure, target capabilities
- The reason for migration (drives priority of what to preserve)
- Constraints (timeline, budget, downtime tolerance)
- Stakeholders (SEO, content, dev, comms, support)

---

## The framework: 6 phases

Every content migration follows the same arc. Skipping a phase is how migrations go badly.

### Phase 1: Inventory

You can't migrate what you don't know. Build a complete map of what exists.

For each piece of content:
- URL
- Title
- Content type (article, landing page, product, doc, etc.)
- Status (live, draft, archived, scheduled)
- Last modified
- Author or owner
- Traffic (last 12 months), or state the gap per the data-availability rule
- Backlinks (top external referrers)
- Internal links pointing to it
- Embedded assets (images, video, downloads)

Pull from: CMS export, XML sitemap, server logs, analytics, search console, backlink tool.

The inventory is a spreadsheet. It's the source of truth for the rest of the migration.

### Phase 2: Audit and decide

For each piece of content, decide:

- **Keep:** migrate as-is
- **Update:** migrate with edits (refresh, expand, fix)
- **Merge:** combine with another piece, redirect both old URLs to the new
- **Redirect:** don't migrate; redirect to a related page
- **Delete:** don't migrate, no redirect (use sparingly; only for clearly low-value pages)

This is `seo-content-audit` work. The migration is the time to do it; not the time to skip it.

For each "Update" or "Merge," document the specific changes.

### Phase 3: Map URLs

The URL map is the most important migration artifact.

| Old URL | New URL | Status code | Reason |
|---|---|---|---|
| /old/path | /new/path | 301 | Direct equivalent |
| /old/page-1, /old/page-2 | /new/merged | 301 | Merged content |
| /old/deprecated | /related/replacement | 301 | Closest replacement |
| /old/junk | (none) | 410 | Intentionally gone |

Rules:
- 301 (permanent redirect) for content that has a new home
- 410 (gone) for intentionally deleted content
- Avoid 404 (not found) where 410 is more accurate
- Never redirect everything to the homepage; specific is always better
- Map every URL with traffic or backlinks; lower-priority URLs can be patterned

For domain migrations, use a 1:1 path mapping by default (`old.com/page` → `new.com/page`) with specific overrides where structure changes.

### Phase 4: Build and stage

Build the destination. Don't skip a staging environment.

- Set up the new platform with the new content
- Implement the URL map (most platforms support a redirect file or rule)
- Verify a representative sample of redirects work
- Test critical user flows (signup, purchase, contact)
- Validate analytics, monitoring, and integrations
- Test from search engine perspective: robots.txt, sitemap, canonicals

If possible, get the destination crawled by Google before the cutover, so it's already indexed when redirects flip.

### Phase 5: Cut over

The actual switch. Plan it like a launch (and use `launch-runbook` alongside this skill).

Pre-cutover:
- Comms to stakeholders (date, expected impact)
- Comms to users if downtime expected
- Support team prepped for likely questions
- Lower DNS TTL the day before (1-3 days for safety)
- Backup of source platform (in case rollback is needed)

Cutover:
- Redirect rules go live
- DNS changes go live
- New sitemap submitted to search engines
- Old sitemap removed or updated
- Internal links audited and updated to point to new URLs (where possible)
- Status page or banner if user-visible disruption

Immediately post-cutover:
- Smoke test top 50 pages from the inventory
- Verify redirects are 301 (not 302)
- Verify search console for errors
- Watch real-time traffic for unexpected drops
- Watch error logs for missing assets, broken integrations

### Phase 6: Monitor and recover

The migration isn't done at cutover. The next 30-90 days reveal problems.

Watch:
- **Traffic:** expect a temporary drop (10-30% is common); should recover in 4-8 weeks. A persistent drop beyond that is a problem.
- **Indexing:** new URLs should be crawled and indexed. Check coverage in search console.
- **Rankings:** track top keywords. A position drop is normal; a position cliff is a sign of a redirect or canonical problem.
- **Backlinks:** check that linked-from-elsewhere pages still resolve to the right destination.
- **404s:** any URL getting 404s that should have been redirected? Add to the map.
- **User reports:** support tickets, social media. Are users finding their old links?

Common 30-day fixes:
- Add missed redirects from 404 patterns
- Update internal links you missed
- Re-submit sitemap if indexing stalls
- Investigate and fix any crawl errors

---

## Workflow

### Step 1: Set the scope

What's in scope? What's out? Write it down. Migrations expand if not bounded.

### Step 2: Build the inventory

Pull every URL, traffic, backlinks, internal links. The spreadsheet is the artifact.

### Step 3: Decide per piece

Keep, update, merge, redirect, delete. Document decisions.

### Step 4: Map URLs

The complete redirect map. Reviewed by SEO and content stakeholders.

### Step 5: Build the destination

In a staging environment. Real content (or representative content). Real redirects.

### Step 6: Test

- Sample of redirects (top 20 by traffic, top 20 by backlinks, edge cases)
- Critical flows (signup, checkout, contact)
- Analytics and monitoring
- Search-engine perspective (robots.txt, sitemap, canonicals)

### Step 7: Cut over

Following the cutover checklist. Have rollback ready.

### Step 8: Monitor

Daily for the first week. Weekly for the first month. Monthly through 90 days.

### Step 9: Document the result

What worked. What didn't. Lessons. (See `after-action-report`.)

---

## Failure patterns

**No URL inventory.** Migration team thinks they have everything. They don't. Old PDFs, archived posts, marketing landing pages with backlinks. Build the inventory.

**302 redirects instead of 301.** 302 is temporary. SEO equity doesn't reliably pass. Use 301 unless you have a specific reason.

**Redirecting everything to the homepage.** "We'll let users find their way." They won't. They'll bounce. Map specifically.

**Long redirect chains.** /a → /b → /c → /d. Each hop loses a little equity and adds latency. Collapse to /a → /d.

**Forgetting non-HTML URLs.** PDFs, images, downloads. They have URLs too. They have backlinks too. Include in the map.

**Forgetting query strings.** `/page?id=123` is a different URL than `/page`. Patterns or specific maps for query string variants.

**Ignoring trailing slashes.** `/page` and `/page/` are different to most servers. Pick one canonical form. Redirect the other.

**No staging.** The first time the migration runs is in production. Things break. Stage and test.

**Stage that's too different from production.** Different DNS, different CDN, different platform. Tests pass on staging, fail on production. Stage as close to prod as feasible.

**Leaving the source live.** Two sites serving the same content. Duplicate content, split equity, user confusion. Take down the source after confirming the destination is solid.

**Leaving the source domain unrenewed.** Domain expires, redirects break, traffic dies. Renew the source domain for a long time, even if you're not using it.

**Big-bang migration with no rollback plan.** Something goes wrong. Now what? Plan rollback before cutover.

**Cutover during a busy period.** End of quarter, holiday season, big campaign. Bad timing. Pick a quiet period.

**No comms.** Users find their bookmarks broken with no warning. Some won't come back. Communicate.

**Migration as a one-time event.** It's not done at cutover. Monitor for 30-90 days. Fix what surfaces.

**Treating migration as just a dev project.** SEO, content, support, comms all need to be involved. Cross-functional from day one.

---

## Output format

A migration plan document includes:

- **Scope:** what's in, what's out
- **Inventory:** the URL spreadsheet
- **Audit decisions:** keep, update, merge, redirect, delete
- **URL map:** old to new, with status codes
- **Architecture:** new platform setup, redirect implementation
- **Cutover plan:** the runbook for switch day
- **Rollback plan:** if it goes wrong
- **Monitoring plan:** what's watched, for how long
- **Comms plan:** internal and external
- **Owners and timeline:** who does what when

---

## If required data is unavailable

This skill's output depends on data, measurements, or tool results it cannot generate on its own. When a required input, tool, or data source is unavailable or unverifiable, the sanctioned output is the deliverable with the gap stated: what was needed, what was actually obtained or verified, and which parts of the output are affected. Fabricating, estimating, or interpolating a required number to complete the deliverable is never sanctioned. A stated gap is a complete answer.

---

## Reference files

- [`references/migration-runbook.md`](references/migration-runbook.md): Step-by-step runbook for cutover day, including pre-flight checks, the actual switch, immediate verification, and the first 24 hours of monitoring.

© rampstackco · MIT · rampstackco/claude-skills

Similar skills

All skills for SEO and GEO →

From the same set102

The whole set →
domain-strategy domain-strategy guides DNS architecture planning, canonical domain choices between apex and www, registrar security audits, and redirect strategies across multi-domain portfolios. CX Codex +1 283installs documentation-strategy documentation-strategy is a Claude Code skill that designs a documentation system for a team or product, helping choose what to document, where to store docs, and how to keep them current. CX Codex +1 282installs content-refresh-system content-refresh-system is a skill for Claude Code and other platforms that runs quarterly audits and prioritizes refreshes by signals. It triggers on content refresh questions, traffic erosion or lifecycle management. CX Codex +1 282installs comparison-tool-design comparison-tool-design guides the design of side-by-side product and plan comparison tools that help users make decisions rather than dumping unweighted feature tables. CX Codex +1 282installs feature-launch-playbook feature-launch-playbook — an operational guide to launching features: positioning, sales and support enablement, rollout strategies with rollback triggers, and measuring post-launch metrics. CX Codex +1 280installs upgrade-flow-design The upgrade-flow-design skill plans SaaS free-to-paid journeys, including paywall timing, upgrade paths, win-back flows, and churn prevention. CX Codex +1 279installs dependency-management dependency-management turns third-party packages into a policy: how often to update, how fast to patch, and whether a new library earns its place. CX Codex +1 278installs user-feedback-aggregation user-feedback-aggregation — a skill for collecting user feedback across channels (support tickets, NPS, in-app, calls, social, customer councils) and turning it into a decision signal. CX Codex +1 278installs

Project sponsors

Companies that keep this analytics open