Redirect Map Template: Free CSV Download
By MoveLedger · Reviewed September 23, 2026
A redirect map records where each old URL should send a visitor. Start with this small CSV, replace the sample paths, and check the structure before your developer applies it.
source,target,status /old-service,/services/new-service,301 /old-guide,/guides/new-guide,301
What each column means
| Column | Use | Common mistake |
|---|---|---|
| source | The old exact path or full URL. | Mixing /old-page with https://example.com/old-page. |
| target | The intended replacement URL. | Pointing at another redirect rather than the final page. |
| status | The intended HTTP redirect code, such as 301. | Leaving a temporary code in a permanent migration plan. |
Build the map in four passes
- Inventory: collect old URLs and keep the original list alongside the map.
- Decide: label every old URL as unchanged, redirected, retired, or unresolved. Only redirect decisions belong in this CSV.
- Map: select a relevant replacement for each moved page. Write the final destination, not an intermediate route.
- Review: paste the CSV into the checker, resolve errors, and document any intentional exceptions.
Keep a separate decision sheet
The two example rules are a format demonstration, not a migration plan for your site. Keep owner, reason, review date, and decision columns in a working sheet. Extra uniquely named columns can remain in a MoveLedger review CSV, but your platform's importer may require a different format.
An old URL missing from the map is not automatically a mistake. It may remain unchanged or have no suitable replacement. The checker flags it for a human decision.
CSV preparation tips
- Save as UTF-8 CSV, with commas separating fields.
- Put a field containing a comma inside double quotes. Escape an embedded double quote by doubling it.
- Keep one source per row and remove accidental whitespace.
- Do not mix full URLs and relative paths for the same route; MoveLedger keeps them distinct.
- Preserve meaningful query strings, case, and trailing slashes.
This template is for review. It is not an Apache, Nginx, or CMS configuration file. For Shopify's importer, use the Shopify CSV template.
Validate before and after deployment
The free checker finds structural loops, chains, conflicting sources, duplicates, and inventory gaps in up to 1,000 rules. It does not request the URLs. After deployment, request the old URLs with an HTTP checking tool and confirm that visitors reach the right content.
Google recommends mapping old URLs to their new destinations as part of a site move. See Google's site move documentation.