If you change a URL, move to Webflow from another platform, or delete a page, you need a 301 redirect. It tells browsers and search engines that the page has moved permanently, so visitors don’t hit a 404 and the old URL’s search value passes to the new one.
This guide covers every kind of redirect people ask about in Webflow: single 301 redirects, wildcard redirects, bulk CSV imports, redirects for CMS items, and redirecting to an external URL.
How to set up a 301 redirect in Webflow
Redirects live in your site settings and need a paid Site plan (or a Workspace on a paid plan).
- Go to Site settings → Publishing → 301 redirects.
- In Old path, enter the URL you want to redirect from, for example /old-page.
- In Redirect to path, enter the new URL, for example /new-page.
- Click Add redirect path.
- Publish your site. Redirects don’t take effect until you publish.
Paths are relative to your root domain, so you enter /old-page rather than the full address.
If the old URL still exists as a live page, Webflow won’t redirect it. Delete the page, save it as a draft or change its slug first. The same goes for CMS items: archive, delete, unpublish or draft the item, or change its slug.
The automatic redirect when you change a slug
If you change a page’s slug in Page settings, tick Permanently redirect the old URL to this new one and Webflow creates the 301 for you. You can see it afterwards in the same 301 redirects list. This is the easiest option for one-off changes.
Wildcard redirects in Webflow
When a whole folder has moved, you don’t need one rule per page. A wildcard redirect uses a capture group, (.*), in the old path and reuses what it matched in the new path as %1.
- Folder to folder: Old path /blog-old/(.*) → Redirect to path /blog/%1. So /blog-old/my-post goes to /blog/my-post.
- Many pages to one: Old path /collections/(.*) → Redirect to path /collections. Every old URL in the folder lands on one page.
- Multiple variables: Old path /blogs/(.*)/(.*) → Redirect to path /articles/%1/%2.
A few rules that trip people up:
- Escape special characters in the old path. Put a % before these characters in the Old path: % - & * ( ) = _ + ?. You don’t need to escape the Redirect to path.
- Order matters. Redirects run from oldest to newest, so create specific rules before a broad wildcard, or the wildcard will catch the request first.
- Query strings: to match a URL like /post?id=5 you write the old path with escapes, such as /post%?id%=(.*). Don’t put a trailing slash directly before the question mark, because Webflow strips it before matching and the rule won’t fire.
- Localised or subfolder URLs need their own rule. A rule for /old-url won’t also cover /es/old-url.
Wildcards only work when the part of the URL after the folder stays identical. If slugs are changing as well, you’ll need individual rules, or a mix of both.
Bulk import: redirects from a CSV
For migrations with hundreds of URLs, importing a CSV is far quicker than adding them one by one.
- Go to Site settings → Publishing → 301 redirects and click Import.
- Upload a CSV with two columns, old paths and new paths, one redirect per row (16MB maximum).
- Publish the site.
Watch out: a new import overwrites all existing redirects. Click Export first, add your new rows to that file, then import the combined file. If any row is invalid the import fails and Webflow emails you with details.
Webflow suggests keeping the total to around 1,000 rules, because every rule is written into the site’s manifest file. That’s another reason to use wildcards wherever the URL pattern allows.
