Redirect map deliverable spec — CSV of old→new URL with notes; sources are XML sitemap + Screaming Frog + GSC + Ahrefs/Semrush
The redirect map is the single most consequential deliverable in a same-domain migration.
Format: CSV with columns old_url, new_url, status_code, notes. Default status_code = 301.
Build it by combining four sources:
- WordPress XML sitemap (
/sitemap_index.xmlfrom Yoast/Rank Math/AIOSEO). - Screaming Frog crawl of the live site.
- Google Search Console Performance report — top URLs by impressions over the last 12 months.
- Ahrefs/Semrush — URLs with external backlinks.
Edge cases that consistently cause traffic loss (per Migration hidden-killers catalogue — the seven failure modes that appear in every post-mortem):
- Attachment pages (WordPress auto-creates one indexable page per uploaded image) — 301 to parent post or 410 if no parent.
- Author archives (
/author/janedoe/) — usually safe to 301 to/about/or 410. - Date archives (
/2019/03/) — almost never have inbound links; 410 is appropriate. - Category pagination (
/category/news/page/4/) — preserve at least first 2-3 pages. - Feed URLs (
/feed/,/category/news/feed/) — preserve at root level (/rss.xmlis modern convention;/feed/should redirect).
Sitemap continuity: keep the old sitemap.xml resolving (with 301'd URLs) for at least 30 days post-cutover. Submit the new sitemap immediately. Because the domain is unchanged, do not use Search Console's Change of Address tool — Google's docs say explicitly: "Don't use the Change of Address tool for the following moves: Changing address from http to https… Moving some pages from one location to another within your site."
Retention rule: maintain redirects for at least 180 days. Google: "Maintain the redirects for at least 180 days — longer if you still see any traffic to them from Google Search." GreenGeeks puts it more sharply: "Industry standard is 12 months minimum." See RULE: Keep migration 301 redirects in place for at least 12 months; never less than 180 days (Google's explicit floor).
Referenced by (3)
- reference Same-domain CMS migration with proper 1:1 redirects: 2-4 weeks of crawl turbulence; 4-8 weeks to full stability. The 523-day stat is domain-to-domain. relates-to
- reference Migration hidden-killers catalogue — the seven failure modes that appear in every post-mortem relates-to
- reference Low-risk cutover pattern for same-domain CMS migration — 2-week pre-flight, DNS TTL 300s, monitor 48h, keep WP firewalled 30 days depends-on