How to Set Up Redirects in Framer

How do Framer redirects work?

Framer redirects are path-to-path rules stored in your project's Site Settings. When a visitor or crawler requests the old path, Framer answers with a permanent redirect to the new one, so the ranking signals of the old URL pass to the new page. There's no plugin and no server config to touch.

Redirects are one part of a bigger job. If you're moving a whole site, start with our website migration SEO checklist, which puts redirects in order with crawling, metadata and monitoring. This guide covers the Framer side in detail: the settings, wildcard rules, and a workflow for large blogs.

Two rules apply everywhere. A redirect only fires for a path that no live page answers, so delete or rename the old page first. And nothing happens until you publish, because redirects ship with the site like any other change.

How do you set up a 301 redirect in Framer?

You set up a Framer 301 redirect by adding an old path and a new destination in Site Settings, publishing, then verifying the status code. Each rule is quick to enter, which is why the planning matters more than the clicking.

1. 1

   Open Site Settings

   In the Framer editor, open Site Settings and find the Redirects section. Menu names shift between Framer releases, so check the current docs if you can't find it.

2. 2

   Add the old path

   Enter the path only, starting with a slash, such as /old-pricing. Don't paste the full domain, and match the old URL's exact spelling and case.

3. 3

   Add the destination

   Enter the new path, such as /pricing, or a full URL if the page moved to another domain. Pick the closest matching page, not the homepage.

4. 4

   Remove conflicting pages

   If a page still lives at the old path, delete it or change its slug. A live page and a redirect on the same path conflict.

5. 5

   Publish the site

   Redirects only go live with a publish. Staging previews won't show them.

6. 6

   Verify the status code

   Run the old URL through a redirect or header checker. You want one hop, a 301, and a 200 on the destination.

If you're coming from Webflow, the workflow will feel familiar. Our guide to Webflow 301 redirects covers the other side of the same move, which helps when you need to compare rules before cutover.

How does a Framer redirect wildcard behave?

A Framer redirect wildcard matches every path under a prefix, so one rule can move a whole folder. You use it when the structure changes but the slugs stay the same, such as /post/my-article becoming /blog/my-article.

Framer can also carry the matched part of the path into the destination, which is what makes folder moves work. The exact syntax has changed over time, so check Framer's current redirect documentation and test one rule on a real URL before you rely on it for hundreds.

Wildcards can't rewrite what's inside a path. If the old URL carries a date or category segment that the new one drops, each post needs its own rule. That's the case where a spreadsheet saves the day.

What's the best bulk redirect workflow for 100+ blog posts?

The best Framer bulk redirects workflow is to avoid most of them. Keep every blog slug identical when you import posts into the Framer CMS, keep the collection path the same, and the old URLs simply keep working.

1. Crawl the old blog and export every indexable URL, plus the URLs in Search Console's pages report and your top linked pages.
2. Build a redirect map with one row per old URL, its new URL, and a status. Our 301 redirect map template shows the columns.
3. Sort rows into three groups: unchanged (no rule), pattern change (one wildcard), and one-off changes (individual rules).
4. Write the wildcard first, publish, and test five URLs from that group.
5. Enter the one-off rules in Framer, working down the sheet and marking each row done.
6. Re-crawl the old URL list after publish and fix anything that returns a 404 or chains through two hops.

Where should old URLs redirect to?

Every old URL should redirect to the page that answers the same question. A post goes to the same post, a retired feature page goes to the page that replaced it, and a merged article goes to the article it was merged into.

Sending everything to the homepage is the most common shortcut and the most expensive one. Google tends to treat irrelevant redirects as soft 404s, so the old page's signals don't carry over. If a page has no equivalent and earned no links or traffic, letting it return a 404 is more honest than a bad redirect.

• Same content, new URL: redirect to the new URL.
• Merged content: redirect to the article that absorbed it.
• Retired, but had links: redirect to the closest parent page, such as the category or product page.
• Retired, no value: let it 404 and remove it from the sitemap.

How do you test Framer redirects after publishing?

Test Framer redirects by requesting every old URL and reading the response, not by clicking links in a browser. Browsers cache redirects and hide chains, so a page that looks fine may still pass through two hops.

Paste your old URL list into a crawler in list mode and check three columns: status code, number of hops, and final URL. Fix chains by pointing the first rule straight at the final page. Then watch Search Console for a few weeks. Our guide to traffic drops after a website migration covers what to check if the numbers dip.

When should redirects live outside Framer?

Redirects should live outside Framer when the old URLs belong to a domain or subdomain that Framer doesn't serve. If you're moving from blog.example.com to example.com/blog, the subdomain's host has to send the redirects, because Framer never sees those requests.

The same is true for a full domain move. The old domain needs its own redirect setup at its registrar, DNS provider or old host, which our guide to domain change SEO walks through. And if you're leaving Framer for code, the rules move into the new stack; see redirects in Next.js for the options there.