Skewcheck Launch checklist Redirect map template
Redirect map template for website migrations
Updated · By SwynQ Labs Private Limited
A redirect map is a list of every old URL on a site and the new page each one should go to. It is the single most useful document in a migration: it decides which redirects you add, it is what you test against at launch, and it is the record you hand to the client afterwards.
Here is the one we use, free, as a plain CSV that opens in Google Sheets, Excel or Numbers. No email needed.
Download the redirect map template (CSV)
Plus two import-ready starter files:
What's in the template
The template has one row per old URL. The five example rows show each kind of decision; delete them before you start.
| Column | What goes in it |
|---|---|
priority | high, medium or low. High = pages that get search clicks or have links from other sites. These get mapped and checked first. |
old_url | The full old URL, exactly as the old site served it, including any trailing slash or query string. |
old_path | The same URL without the domain, for example /about-us/. Webflow and Framer both want paths, not full URLs. |
new_path | The path of the new page that best replaces it. Leave it empty if the page is being retired. |
action | redirect, redirect (wildcard), keep (same path on the new site, no redirect needed), retire-404 or retire-410. |
found_in | Where you found the URL: Search Console, analytics, the old sitemap, CMS export, Wayback Machine, links report. |
search_clicks_16m | Clicks from the Search Console Performance report over the last 16 months. Optional, but it makes priority obvious. |
linking_sites | How many sites link to it (Search Console's Links report). Optional. |
notes | Anything a reviewer needs: "merged into /services", "client to decide", "renamed post". |
launch_check_status | The first status code the old URL returns after launch: 301 or 308 is right, 302 or 404 is not. |
launch_check_hops | How many redirects it takes to reach the final page. It should be 1. |
launch_check_final_url | Where it actually ended up. It should match new_path. |
day7_check_status | The same check a week after launch. |
checked_on | The date of the last check. |
How to fill it in
- List the old URLs. Export pages from Search Console (Performance report, Pages tab, last 16 months), your analytics landing pages, the old sitemap.xml and a CMS export. Add linked pages from Search Console's Links report, and any PDFs and images that are linked or found in search. If the old site is already offline, the Wayback Machine has its old addresses. Paste them all into
old_urland remove duplicates. - Mark priority. Anything with search clicks or links from other sites is
high. - Fill
new_pathwith the closest replacement page. A post goes to the same post at its new address, a service page to the new service page. Don't send everything to the homepage: Google warns that redirecting many old URLs to one irrelevant page such as the home page may be treated as a soft 404. - Choose the action. If the path is unchanged, it's
keep. If the content is gone with no replacement,retire-404orretire-410is correct, and Google's guidance says so. If a whole folder moved and the slugs didn't change, one wildcard row can cover it. - Get it approved. Send the sheet to whoever owns the content before anything is imported. The
notescolumn is where they answer.
Turning the map into an import file
Copy the old_path and new_path of every redirect row into the file for your platform.
Webflow
Webflow's CSV import wants two columns: old path, then redirect-to path, one redirect per row, up to 16 MB. Two things to know first:
- An import replaces every existing redirect on the site. Export the current redirects (Site settings > Publishing > 301 redirects > Export), add your rows to that exported file, and import the combined file.
- Webflow doesn't document a required header row. Our starter file has one (
Old path,Redirect to path). Before importing, replace that first line with the first line of your own Webflow export, so the layout matches exactly what Webflow produced.
Wildcards in Webflow use capture groups: /blog/(.*) → /insights/%1. Specific rows must be added before broad wildcards, because Webflow runs older redirects first. The full walkthrough is in Webflow migration redirects.
Framer
Framer imports redirects through its Redirect Sync plugin. The file needs a from column and a to column; from paths start with / and are relative. The optional expandToAllLocales column (true or false) maps to Framer's "Expand to All Locales" setting. Our starter file has all three columns.
Wildcards in Framer use * with :1, :2 to reuse what matched: /blog/* → /insights/:1. Redirects need a plan that includes them (Pro or Enterprise on Framer's pricing page). The full walkthrough is in Framer migration redirects.
Other platforms
The map itself works for any move, including to or from WordPress. Paste old_path and new_path into whatever redirect tool the new platform has, and check its own documentation for the import format.
After launch: use the check columns
Once the new site is live, test every old URL and fill in the check columns. Each one should answer with a single 301 or 308 to its new_path, and that page should return 200, have no leftover noindex, not be blocked by robots.txt, and carry a canonical that points to itself, not to staging. Both platform guides include a short terminal script that checks the whole list at once. Run it again 7 days later.
Then keep the redirects. Google recommends keeping them for as long as possible, generally at least a year.
Don't want to build it yourself?
Send us the old site and the new one, and we'll build the map for your top 10 traffic pages, free, within 48 hours.
If you want the whole job done, Migration Repair is $500 per site (₹40,000 + GST in India): every old URL that gets search traffic mapped, the redirects put in, a live check at launch and again 7 days later, and a record for the client. We don't promise rankings or traffic.
Email hello@swynq.com for your free top-10 map · How Migration Repair works
Questions
What is a redirect map?
A list of every old URL on a site and the new page each one should redirect to, with a decision for each: redirect, keep or retire. It is what you import redirects from and what you test against after launch.
Do I need to give an email address to download the template?
No. The CSV downloads directly.
Which URLs should go in a redirect map?
Every old URL that gets search traffic, has links from other sites, or appears in the old sitemap, plus linked PDFs and images. Search Console, analytics, the old sitemap, a CMS export and the Wayback Machine are the usual sources.
Should every old URL redirect somewhere?
No. Redirect each one to its closest replacement. If content was removed and nothing replaces it, letting it return 404 or 410 is correct. Don't send old pages to the homepage instead.
Can I import this file straight into Webflow or Framer?
Use the platform starter files. For Webflow, export your existing redirects first, because an import replaces them, and match the header line of your own export. For Framer, import the from and to columns with the Redirect Sync plugin.