Migrations
Preserve rankings when URLs change
How do we change URLs without losing what already ranks?
For redesigns, replatforms, domain moves, slug changes and the 404s that appear after a relaunch. It plans the redirect map, implements it for the framework in use, and verifies every mapping on the served output.
Paste into Claude Code, Cursor, Codex or any agent that can open a link. If yours cannot, use Copy full text.
Reach for it when you say
- “We're redesigning”
- “Moving domain or CMS”
- “We changed our URLs”
- “404s after relaunch”
Installed as a skill, it triggers on requests like these by itself.
- Step 01Recognise when a change is a migration
- Step 02Diagnose what exists and what will change
- Step 03Plan the redirect map and fix it in the framework
- Step 04Verify on the served output
- Step 05Report what changed and why it matters
Three modes, three ways in
Run it in audit mode first: it records findings and changes nothing. Then fix applies only the findings you approve, and re-check re-tests them later. Switch modes on the prompt above.
- 01Paste the link promptOne line that points your agent at the skill on GitHub. Nothing to install, always the latest version.
- 02Paste the full textFor agents that cannot open links. The skill is self-contained, so this works in any chat.
- 03Install the packInstalled as skills, it triggers by itself when you describe the problem, and can hand work to the other skills.
Questions about this skill?
Ask me on LinkedIn, or open an issue on GitHub if something is wrong or missing.