Framer migration redirects: map, import and check them

Before you start: what Framer needs

• A plan that includes redirects. On Framer's pricing page, "Site redirects" is included on the Pro and Enterprise plans, not on Basic. Check this before launch day, not on it.
• Where they live: Site Settings → Hosting → Redirects. (They used to be in the Domains dashboard.)
• Publish to apply. Framer says to publish or update the site for redirect changes to take effect.
• Sub-paths only. Framer can only redirect paths within the site's current domain. If the domain is changing too, the old domain's redirect to the new one is set up with the old domain's hosting provider; then you connect the new domain in Framer and add the path redirects there.

1. Find every old URL that needs a redirect

Start from the old site, not the new one. Each source catches pages the others miss:

• Search Console, Performance report, Pages tab, with the date range set to the last 16 months so seasonal pages appear. These pages get search clicks.
• Analytics landing pages: where visitors from search, email, social and ads arrive.
• Search Console's Links report: pages other sites link to.
• The old sitemap and a CMS export: everything that exists, including quiet pages.
• Files and images that are linked or found in search. Google's site-move guide says to include them.
• The Wayback Machine, if the old site is already offline.
• The old site's existing redirects. If it came from Webflow, export them (Site settings > Publishing > 301 redirects > Export). Bring the ones that still matter across, pointed straight at the final Framer page so you don't create chains.

Keep each URL exactly as the old site served it. Framer's WordPress migration guide makes the point that /about/ and /about are different URLs, so if the old site used trailing slashes, map those forms.

2. Map each old URL to its closest new page

Write one row per old URL with the new page that best replaces it.

• Closest match, not the homepage. Google warns that redirecting many old URLs to one irrelevant page such as the home page can be treated as a soft 404. Framer's own migration guide says the same. Several old pages merged into one new page can all go to that page.
• Removed with no replacement? Return a 404 or 410. Google's guidance treats that as the right outcome.
• Keep slugs where you can. If the old blog was /blog/post-title, keeping that structure in Framer means no redirect at all.
• Prioritise. Mark the pages with the most search clicks and links as high priority. If you need to trim the list to fit your plan, those stay.

The free redirect map template has columns for all of this.

3. Use wildcards so the list stays short

Wildcards let one rule cover a whole folder, which matters on a plan with a redirect limit. Framer supports three patterns:

So a blog moving from /blog/{slug} to /insights/{slug} can be one rule (/blog/* → /insights/:1) instead of one row per post. That only works when every slug stayed the same; posts that were renamed still need their own rows, placed above the wildcard. Check the result on a few real URLs before you rely on it.

Order matters. In Site Settings → Hosting → Redirects you can drag rules to set their priority. Put specific redirects above the broad wildcard that would otherwise catch them.

How many redirects can you have? Framer's pricing page doesn't publish a per-plan number for redirects, so check what your plan allows in the project before you finalise the list. Framer's developer documentation says a project can have up to 2,500 redirects at most. If your map is bigger than your plan allows, cover folders with wildcards, then keep the individual rows for the pages with the most traffic and links.

4. Add the redirects: one by one or by CSV

A few redirects: Site Settings → Hosting → Redirects, enter the old URL and the new URL, then publish.

A long list: use Framer's Redirect Sync plugin (made by Framer). Choose Import and select a CSV with a from column and a to column:

from,to
/about-us/,/about
/services/web-design-old,/services/web-design
/blog/*,/insights/:1

• from paths must start with / and be relative paths, not full URLs.
• An optional expandToAllLocales column (true or false) maps to the "Expand to All Locales" setting, for sites using Framer's localisation.
• If a row's from matches an existing redirect, the import updates that redirect.
• Export first anyway. Redirect Sync also has an Export that downloads every redirect in the project as a CSV. Take one before any import so you have a backup.

Then publish.

One Framer-specific catch: if you later change a page's path on the canvas or in the CMS, Framer doesn't update your redirect settings automatically. Update the redirect, or add a new one, whenever a path changes.

5. Publish, then check every old URL

For every old URL in your map, check that:

1. The first response is a permanent redirect. Framer's own WordPress migration checklist expects permanent 308 redirects, not temporary 302s. Google treats 301 and 308 as permanent redirects.
2. It takes one hop straight to the final page. Google advises against chains.
3. The new page returns 200, not a 404.
4. The new page can be indexed: no noindex left on from staging, not blocked by robots.txt, and a canonical that points to itself (canonical points to staging).
5. The new page is in the sitemap, and the redirected old URLs aren't.

From a terminal, with one full old URL per line in old-urls.txt:

while IFS= read -r url; do
  [ -z "$url" ] && continue
  first=$(curl -s -o /dev/null -w '%{http_code} %{redirect_url}' "$url")
  final=$(curl -s -o /dev/null -L --max-redirs 10 -w '%{http_code} %{num_redirects} %{url_effective}' "$url")
  echo "$url | first: $first | final: $final"
done < old-urls.txt

Look for first: 301 or first: 308, and final: 200 1 (a live page after one hop). A 404 first means the redirect is missing; a hop count above 1 means a chain. Then run the free Skewcheck page check on the most important new pages.

6. Check again 7 days later, and keep the redirects

Redirects break after launch: a page path changes, a CMS item is removed, a wildcard catches something it shouldn't. Run the same check a week later.

Keep the redirects in place. Google recommends keeping them for as long as possible, generally at least a year, and says a small to medium-sized site can take a few weeks for most pages to move in search, with visibility fluctuating meanwhile. If the domain changed, submit a Change of Address in Search Console for the old domain (Google says it is only for domain or subdomain moves).

Mistakes we see most often

• Launching on a plan without redirects and finding out after the DNS switch.
• Every old URL sent to the homepage.
• Full URLs in the from column.
• A wildcard placed above the specific rules it should sit below.
• Old trailing-slash URLs left unmapped.
• A page path changed after launch with the redirect left pointing at the old one.
• Testing only in a browser, which hides 302s, chains and noindex.

Want it done for you?

Migration Repair is our done-for-you service for sites moving to Framer or Webflow. We find the old URLs that get search traffic, map each one to its new page with you, give you the redirects ready for Framer (or put them in ourselves if you add us as an editor), and check every one live at launch and again 7 days later. You get a record of every old URL, where it now goes, and the status we saw. There's a real WordPress-to-Framer example on the Migration Repair page.

• Free first: a redirect map for your top 10 traffic pages within 48 hours.
• Then: Migration Repair at $500 per site (₹40,000 + GST in India), agreed before we start. We don't promise rankings or traffic.

Email hello@swynq.com for your free top-10 map · How Migration Repair works

Also useful: Launching a Framer site: the checklist · Webflow migration redirects · Traffic dropped after a migration?

Questions