Redirect Mapper

What it does

Compares an old URL list (from a sitemap export, crawl, or CSV) against the new site structure and proposes one-to-one 301 mappings based on matching titles, slugs, and content similarity. Flags old URLs with no clear new-site match so they get a deliberate decision instead of a silent 404.

Install

This skill isn't packaged in an installable registry. It's a plain SKILL.md file you can copy directly. Copy it from the SKILL.md tab and save it at the path for your assistant:

Use it in your AI assistant

Claude Code

.claude/skills/redirect-mapper/ (or ~/.claude/skills/redirect-mapper/ for all projects)

GitHub Copilot (VS Code)

.github/skills/redirect-mapper/

OpenAI Codex

.codex/skills/redirect-mapper/

Cursor

.cursor/skills/redirect-mapper/ (or ~/.cursor/skills/redirect-mapper/ globally)

Compatibility

Any WordPress site. Redirects are written to whatever redirect plugin is active (Redirection, Yoast's redirect manager, Rank Math redirections) or to the server's redirect rules if none is active.

The complete SKILL.md for this skill:

---
name: redirect-mapper
description: Use when a user is migrating or restructuring a WordPress site and needs a 301 redirect map from old URLs to new ones. Triggers on "redirect map", "301 redirects", "URL migration", or "site restructure redirects".
---

# Redirect Mapper

## When to use
The user is changing URL structure, merging content, or relaunching a site and needs old URLs mapped to their new destinations before the old ones go live as 404s.

## Procedure
1. Get the full list of old URLs (sitemap export, crawl, or CSV) and the new site's current URL structure.
2. Match each old URL to a new URL by title similarity, slug overlap, and content topic, in that priority order.
3. For old URLs with no reasonable match, mark them for redirect to the closest parent category or the homepage, and flag them separately as "no direct match."
4. Output the map as a simple old-URL to new-URL table with the match confidence noted for each row.
5. On approval, write the redirects into the site's redirect plugin, or output the rule set for the user to hand to whoever manages the server config.

## Guardrails
- Never redirect a large batch of unrelated old URLs to the homepage as a default, that pattern is treated as a soft-404 signal by search engines.
- Flag chains (old URL A already redirects to B, now B needs to redirect to C) so the user fixes them into a single hop instead of stacking redirects.