Framer redirects explained: paths, wildcards and :slug

Where to find redirects in Framer

Open your project and go to Site Settings → Redirects. Each rule has an old URL and a new URL. Publish the site to apply the changes.

Framer’s help article covers the basics. Here’s how each kind of rule works in practice.

Exact paths

The simplest rule sends one path to another:

/about-us → /about

Use these for individual pages you’ve renamed or merged.

Wildcards with *

A * matches anything, including slashes. That makes it useful for whole sections:

/blog/* → /journal

This sends /blog/hello-world and /blog/2022/07/18/hello-world to /journal.

On its own, a wildcard throws away the matched part. Every old post lands on the same page. That’s fine for a retired section, but not for a renamed one.

Keeping the path with capture groups

To carry the matched part over, use :1, :2 and so on in the new URL. Each one refers to a * in the old URL, in order:

/blog/* → /journal/:1

Now /blog/hello-world goes to /journal/hello-world. With two wildcards:

/blog/*/post/* → /article/:1/entry/:2

Matching single segments with :slug

A * can span several segments. When you want exactly one segment between slashes, use a named segment like :slug:

/work/:slug → /projects/:slug

You can name segments however you like and rearrange them:

/blog/:year/:month/:day → /article/:year-:month-:day

This turns /blog/2022/07/18 into /article/2022-07-18, but it won’t match deeper paths like /blog/2022/07/18/category/post.

Rule order matters

When more than one rule could match, the order decides. Framer lets you drag and drop rules to set their priority.

Put specific rules above general ones:

1. /blog/framer-tips → /guides/framer

2. /blog/* → /journal/:1

If the wildcard came first, it would catch framer-tips before the specific rule got a chance.

Framer doesn’t update redirects for you

If you rename a page’s path on the canvas or a CMS item’s slug, Framer doesn’t create a redirect automatically. It also doesn’t update existing rules.

Make it a habit: whenever you change a slug on a published page, add a redirect from the old one.

What Framer redirects can’t do

Framer redirects only work on paths of the domain your project uses. You can’t redirect a different domain to your Framer site from inside Framer.

So oldstudio.com → newstudio.com needs to happen before the request reaches Framer, at the DNS level. We walk through that in how to redirect an old domain to a Framer site, and compare the two approaches in Redirect Supply vs Framer redirects.

Redirects and the Framer CMS

CMS collections are where most slugs change. A few practical habits help:

• Decide on slug rules early. Changing the collection’s URL prefix later means a wildcard redirect for every old item.

• Redirect when you rename an item. Changing a single post’s slug needs a single rule from the old slug.

• Use one wildcard for a renamed collection. If /blog/:slug becomes /journal/:slug, one rule covers every post.

• Keep a list of changes. Framer doesn’t track slug history, so note old slugs when you change them.

Trailing slashes and capital letters

Framer URLs usually have no trailing slash. If your old site used them, as WordPress does, include rules for both versions of your important URLs, or test that the slashed version still lands where you expect.

A quick checklist before publishing

• Specific rules above wildcard rules.

• Capture groups used wherever the path should be kept.

• No rule that points to another redirected URL, which would create a chain.

• Old slugs added for any page you renamed.

After you publish, run a few old URLs through our redirect tester to confirm each one returns a single redirect and lands on the right page.