content-migration
Content-Migration handles the technical and strategic planning required to move content between platforms, domains, or URL structures while preserving search visibility, user bookmarks, and system integrations. Use this skill when executing a CMS transition, consolidating multiple sites, splitting one site into multiple properties, changing URL patterns, performing a domain rebrand or merger, or merging content inventories from disparate sources.
git clone --depth 1 https://github.com/rampstackco/claude-skills /tmp/content-migration && cp -r /tmp/content-migration/dist/pi/.agents/skills/content-migration ~/.claude/skills/content-migrationSKILL.md
# 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) - 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
Run a comprehensive WCAG accessibility audit covering perceivable, operable, understandable, and robust principles. Use this skill whenever the user wants to audit accessibility, review WCAG compliance, fix accessibility issues, prepare for accessibility certification, address an accessibility lawsuit risk, or systematically improve a site's accessibility. Triggers on accessibility audit, WCAG audit, a11y audit, accessibility compliance, ADA compliance, screen reader test, keyboard navigation, accessibility report, fix accessibility, axe scan. Also triggers when accessibility issues have been reported and need systematic remediation.
How to produce ad creative that converts at performance scale. Hook patterns, format selection, video pacing, variation systems, sequential testing methodology, fatigue detection, brand-voice alignment without conversion dilution, and platform-specific creative norms. Triggers on ad creative, ad design, hook patterns, ad video pacing, creative testing, ad variations, creative refresh, creative fatigue, refresh ad creative, video ads for Meta, TikTok creative, LinkedIn ad creative, ad asset library. Also triggers when a team is producing creative at scale, planning a creative test cycle, or auditing why creative is not converting.
How to read paid media dashboards without fooling yourself. Attribution models, platform reporting quirks, multi-platform reconciliation, ROAS vs LTV horizon traps, statistical noise in performance metrics, incrementality testing, and the failure modes that produce expensive lessons. Triggers on read paid media dashboard, attribution analysis, ROAS vs LTV, multi-platform reconciliation, ad incrementality, geo holdout, conversion lift study, ghost bidding, paid media reporting, board-deck paid media metrics, blended CAC, MMM, MTA, last-click attribution. Also triggers when a marketer is about to scale, kill, or rebudget a campaign based on platform metrics, or when reconciling platform reports against warehouse revenue.
Run a structured after-action review (postmortem, retrospective) on a launch, incident, or completed project to capture timeline, root cause analysis, contributing factors, and actionable lessons. Use this skill whenever the user wants to run a postmortem, retrospective, AAR, or after-action review on any past event. Triggers on after-action report, AAR, postmortem, retrospective, retro, post-incident review, what went well what didn't, lessons learned, blameless postmortem, root cause analysis, RCA, five whys. Also triggers when the user has just shipped something or just resolved an incident and wants to capture learnings.
How humans and AI compose in content workflows. Where AI legitimately participates, where humans must own, hybrid workflow patterns, voice ownership preservation, the AI slop problem, disclosure and transparency, team calibration, and the ethics of intellectually honest AI-assisted content production. Triggers on AI content workflow, AI-assisted writing, hybrid content production, AI in editorial, AI slop, AI disclosure, AI usage policy, AI content ethics, voice preservation with AI, team AI calibration. Also triggers when content feels generic despite quality tools, when team AI usage has drifted into inconsistency, or when a regulated or trust-sensitive context requires explicit AI policy.
Design measurement frameworks including event taxonomy, KPI hierarchy, dashboard architecture, attribution models, and analytics implementation strategy. Use this skill whenever the user wants to plan analytics, design dashboards, build event taxonomies, define KPIs, set up tracking, or audit existing measurement. Triggers on analytics strategy, measurement plan, event taxonomy, tracking plan, KPI framework, dashboard design, north star metric, attribution model, conversion tracking, GA4 setup, Mixpanel setup, analytics audit. Also triggers when the user has data but no clear way to use it, or wants to make decisions but doesn't know what to track.
Direct visual and creative work for campaigns, photography, illustration, video, and branded experiences. Use this skill whenever the user wants to brief a photographer, direct illustrators, plan a creative campaign, develop visual concepts, write a creative direction document, or evaluate creative work for fit. Triggers on art direction, photo brief, photography brief, illustration brief, campaign concept, creative concept, visual direction, mood board, look and feel, visual treatment, video direction. Also triggers when the user has approved brand identity but needs to extend it into specific creative deliverables.
Plan and run backups, set recovery objectives, and run disaster recovery drills. Use this skill when defining RPO/RTO targets, designing backup architecture, deciding what to back up and how often, planning for full-region or platform outages, or running a restoration drill. Triggers on backup, restore, RPO, RTO, disaster recovery, DR, business continuity, what if the database is gone, what if our hosting goes down, recovery drill, ransomware planning. Also triggers when an incident reveals a gap in restoration capability.