Plan every redirect before you switch platforms.
Bring in your current URLs, choose where you are moving from and to, and get a page by page map: what keeps its address, what needs a 301 and what to check by hand. Then export it in the format your new host reads.
Build your redirect map
Your redirect map
Your map will appear here
Add your URLs and choose both platforms. You will see every page with its new address, and a file of 301 redirects to copy or download.
- URLs mapped
- 0
- Kept
- 0
- Redirect
- 0
- Check by hand
- 0
- Kept: the same address works on the new platform, no redirect needed.
- Redirect: the address changes; the export adds a 301 from old to new.
- Check by hand: a person should decide: drop it, merge it into another page or check the new address.
| Old URL | New URL | Status | Why |
|---|
Export your 301 map
Choose where the redirects will live. Every format sets 301 explicitly; check the file before you publish it.
Before you rely on the map
What the planner does not do
- It does not move content. Page copy, images and files still need to come across.
- It does not export your CMS. Blog posts and collections need their own import into the new platform.
- It does not check that the new pages exist. Test every redirect once the new site is live.
- It only reads what your sitemap lists. Pages missing from the sitemap need adding by hand.
After you switch
- Update internal links to the new addresses, so visitors and crawlers skip the redirect.
- Submit the new sitemap in Google Search Console and Bing Webmaster Tools.
- Watch Search Console for 404s and crawl errors in the first weeks, and add redirects for anything missed.
- Keep the redirects in place for at least a year.
FAQ
Questions about the planner
How it works, what it keeps and what to do with the file.
Do you keep the URLs I enter?
No. Pasted lists and uploaded files are read in your browser and never sent to us. When you enter a website address, our server reads its robots.txt and sitemap once, sends the page addresses back to your browser and forgets them. We only count how many plans are made each day.
Why are some pages marked to check by hand?
Some addresses need a decision rather than a rule: feeds, tag pages, old plain links like ?p=123, files, and cases the new platform does not document, such as capital letters in Framer paths. The planner suggests an address where it can, and you choose whether to include those suggestions in the export.
Which file should I use for an Astro site?
The redirect file of your host: _redirects for Cloudflare Pages or Netlify, or vercel.json for Vercel. Astro's own redirects setting writes meta refresh pages in a static build without an adapter, and those carry no 301 status.
Why does the Next.js export use statusCode 301?
In Next.js and Vercel, permanent: true sends a 308. The export sets statusCode: 301 instead, which the Next.js docs allow in place of permanent, so the map matches the 301 redirects you planned.
How many redirects can a platform hold?
Framer allows up to 2,500 per project, with lower limits on some plans. Webflow suggests no more than 1,000. Cloudflare Pages takes 2,000 static redirects in _redirects and Vercel 2,048. If you are over, merge old sections into fewer pages or use a pattern rule.