Why the redirect map decides the migration
Search engines and other sites know your pages by their URLs. When a URL changes and nothing redirects it, the old address returns a 404, and the ranking and links it had stop counting. A redirect map is the list of every old URL and where it goes now. It is the step most migrations skip, and it is where every Plenor migration starts.
Download the template
Two files. The worksheet is where you plan: one row per old URL, with its traffic, a decision and the new path. The import file has only the three columns Framer accepts, so it goes straight into the plugin once it is filled in.
Redirect map worksheet (CSV): old_path, clicks_90_days, decision, new_path, notes
Framer redirect import file (CSV): from, to, expandToAllLocales
Both open in Google Sheets, Numbers or Excel. Replace the example rows with your own before you import.
Step 1: list every old URL
Use more than one source, because each one misses something:
The sitemap at /sitemap.xml lists the pages the old site wants indexed.
Search Console, under Pages, exports what Google has, including old URLs the sitemap forgot.
Analytics landing pages show which URLs real visitors arrive on.
A crawl of the live site finds pages that are linked but missing from the sitemap.
Paste everything into the worksheet as paths that start with a slash, then remove duplicates.
Step 2: decide what happens to each URL
Every row gets one of three decisions:
Keep. The new page uses the same path, so no redirect is needed. This is the cheapest outcome, so plan the new structure to keep paths where you can.
Redirect. The page moves or merges into another. Point it at the closest match, not at the homepage.
Drop. The page is gone and nothing replaces it, so it returns a 404. Drop only pages with no traffic and no links.
Sort by clicks_90_days and decide the top rows first. They carry most of the value.
Step 3: use wildcards for whole folders
When a whole folder moves, one rule can cover it. In Framer, * matches any path, and :1, :2 carry the matched parts into the new URL.
/posts/* to /blog/:1 moves every post from /posts to /blog and keeps its slug.
/blog/*/post/* to /article/:1/entry/:2 is Framer’s own example: two parts carried across.
Framer applies rules in the order shown in Site Settings, and you can drag them to change it. Keep exact rules above wildcards, and test each wildcard against real URLs from your list before you trust it.
Step 4: import the map into Framer
Redirects live in Site Settings, under Hosting, then Redirects. You can add them one by one there, or import the whole file with Redirect Sync, a free plugin from Framer. Its code is open source, and reading it settles the file format:
The file needs from and to, plus an optional expandToAllLocales. A fourth column makes the import fail.
The header row is optional. If the first row starts with from and to, it is read as headers.
Rows with an empty to are skipped, so undecided URLs can stay in the file.
A row whose from already exists updates that redirect instead of adding a second one.
from must be a relative path that starts with a slash.
Nothing changes until you publish the site. Import before DNS moves, publish, then test.
Step 5: test before and after the switch
Test on the live domain as soon as DNS moves, and again a day later. The checklist below takes ten minutes. On plenor.io, every redirect we tested answered with a 308, which Google treats the same as a 301: both mean the page has moved permanently.
In migration work people say 301 for any permanent redirect, and so do our own pages. On Framer that redirect is a 308.
What Framer redirects cannot do
Other domains. Framer redirects paths on the site’s own domain. Sending an old domain to the new site is set up where that domain is registered or hosted.
Capital letters. Paths are case-sensitive. On plenor.io, /Case-Studies/billables-ai returns a 404 while /case-studies/billables-ai works. If old links use capitals, map those spellings too.
CMS slug changes. Renaming a published CMS item does not update redirects. Add one by hand when you rename.
More than 2,500 rules. Framer’s plugin API refuses to add redirects past 2,500. Wildcards keep even a large blog well under that.
The Basic plan. Framer’s pricing lists site redirects on Pro, at $30 a month billed yearly, and not on Basic.
For what Search Console shows in the weeks after a move, see Is Framer good for SEO?. For the whole process, platform by platform, see WordPress to Framer and Webflow to Framer.
Sources
Checked on 4 November 2026.