Redirect Mapping Template
A clean redirect mapping template for SEO migrations, redesigns, replatforming, and URL restructures. Copy a spreadsheet-ready format, build old-to-new URL pairs faster, track redirect type and notes, and reduce launch mistakes before the site goes live.
Start here
Recommended flowUse a redirect mapping template to keep migration logic organized
A redirect mapping template is a structured way to document which old URLs should resolve to which new URLs. It helps SEO teams, developers, and content owners keep migration logic visible, reduce last-minute guesswork, and prevent valuable pages from being left behind during launch.
This page is designed for practical execution. It gives you a reusable spreadsheet format, quick copy rows, and common redirect patterns you can adapt for platform migrations, folder changes, product URL updates, domain moves, and site restructures.
Use this page when you need a clean starting point for mapping, reviewing, sharing, and validating redirect work across teams.
Build a redirect mapping row in seconds
"/old-page/","/new-page/","301","Planned","Closest equivalent page"
/old-page/ /new-page/ 301 Planned Closest equivalent page
Copy the redirect template that fits your workflow
CSV header template
Use this as the column header row for a mapping sheet.
"Old URL","New URL","Redirect Type","Status","Notes"
Mapping row template
Use one row per old URL so ownership and QA remain clear.
"/old-url/","/new-url/","301","Planned","Closest matching destination"
Simple redirect rule
Useful for implementation examples and developer handoff notes.
Redirect 301 /old-url/ https://example.com/new-url/
Return rule example
Useful for documenting final destination behavior at server level.
rewrite ^/old-url/$ https://example.com/new-url/ permanent;
When redirect mapping templates help most
Domain migration
Document how old domain paths connect to the new domain so equity and user journeys transfer more cleanly.
CMS or platform change
Track slug changes, template differences, and removed pages when the system generating URLs changes.
Category restructure
Map legacy category paths and product URLs to the closest new architecture instead of broad fallbacks.
Content consolidation
Handle merged articles, retired pages, and replaced assets with notes that explain why each mapping exists.
How to use redirect mapping templates correctly
Use one source URL per row
This makes implementation, QA, ownership, and exception handling much easier to follow.
Prefer precise destinations
The best redirect usually lands on the most relevant new page, not a broad section or homepage.
Track implementation status
A simple status field helps separate planned rows, implemented rows, and rows that still need validation.
Validate live responses
A mapping sheet is only complete after live testing confirms the redirects behave as intended.
Before handing your mapping sheet to development
1. Confirm top URL coverage
Review core pages, categories, assets, and traffic drivers so important legacy URLs are not missed.
2. Review destination quality
Make sure each target is the closest relevant page and not a weak substitute.
3. Add implementation notes
Flag merged pages, removed content, dynamic patterns, and edge cases that may need special handling.
4. Prepare QA ownership
Decide who checks live status, who fixes misses, and how validation results get logged after launch.
Redirect Mapping Template FAQ
What is a redirect mapping template?
A redirect mapping template is a structured sheet used to match old URLs with new destinations, redirect types, status notes, and migration comments.
When should I create a redirect mapping sheet?
It is best to create the sheet early in a migration, before launch work becomes rushed and legacy URLs become harder to trace.
What columns should a redirect mapping template include?
A practical minimum is old URL, new URL, redirect type, status, and notes. Larger projects may add owner, priority, traffic, or QA result columns.
Should every removed page redirect somewhere?
Not always. Some pages may deserve retirement, but important legacy URLs usually need thoughtful destination choices rather than being ignored.
Why is redirect mapping important for SEO?
It helps preserve continuity between old and new URLs, reduces broken paths, and makes migrations easier to review and validate.
Should I use 301 or 302 in my template?
Many permanent migration cases use 301, while temporary situations may use 302. The template helps document that decision clearly row by row.
Can I paste this page directly into Elementor?
Yes. This output is MAIN-only HTML designed for an Elementor HTML widget.
What should happen after the sheet is complete?
After the sheet is prepared, implementation and post-launch QA should confirm that every important mapping works correctly on the live site.
Build cleaner redirect logic and make migration handoff easier to manage
Start with this mapping template, then combine it with a migration checklist and post-launch review workflow so redirects stay organized from planning through launch QA.