Free Tool

4.9/5

Free Webflow Redirect Generator

Build Webflow 301 Old-Path → Redirect-to-Path rules with wildcard support, copy clean rules straight into Project Settings → Publishing.

Redirect rules

Wildcard match (Webflow appends /*, every URL under this path)

Webflow only supports 301 Permanent redirects from Project Settings → Publishing. No bulk CSV import, paste rules in one at a time, or use the TSV output to paste into a spreadsheet first.

How to add in Webflow

1. In Webflow Designer go to Project Settings → Publishing → 301 Redirects.

2. For each row above, paste the Old Path and Redirect to Path into the two input fields, click + Add Redirect Path.

3. Webflow does not support bulk CSV import, you have to add rules one at a time in the UI. The TSV output above gives you a tracking sheet to mark each off as you add it.

4. Click Publish at the top right, redirects only take effect on the next publish.

Wildcard tip: /old/* → /new/* matches every URL under /old/ and forwards the captured segment to /new/. Without /* on the destination, the segment is dropped.

Tired of re-publishing Webflow to change one redirect?

Point campaign URLs at Flyn short links, edit destinations from anywhere, no Webflow login or re-publish required. Plus full per-click analytics every Webflow redirect lacks.

Try Flyn free

How to Create Webflow Redirects in 3 Steps

Enter your old and new paths

Add rows of Old Path and Redirect to Path. Tick wildcard match (/*) to forward every URL under a prefix to the equivalent new prefix.

Copy the rules

Get the arrow-view for visual review or the TSV view for a spreadsheet checklist as you add each rule to Webflow.

Paste into Webflow and Publish

Project Settings → Publishing → 301 Redirects. Paste each rule. Click Publish, redirects only fire after the next publish.

Webflow 301 Redirects: How They Work

Webflow stores 301 redirects under Project Settings → Publishing → 301 Redirects. Each rule is two fields: Old Path (the URL you want to redirect from) and Redirect to Path (where it goes). Always 301, there is no 302 / 307 option.

Two things every Webflow user gets wrong: (1) Webflow does NOT auto-redirect when you rename a page or CMS item slug, old URLs silently 404 until you add a redirect; (2) redirects only fire after you Publish, saving the rule is not enough.

Example Webflow rules:

/old-page              →  /new-page
/blog/old-category/*   →  /blog/new-category/*       (wildcard)
/portfolio-2024        →  https://case-studies.com   (external)

When to Add a Webflow Redirect

Because Webflow does not auto-redirect anything, you need a redirect for every structural change:

Situation	Why it matters
Renamed a page slug or CMS item slug	Webflow does NOT auto-redirect when slugs change, old backlinks 404 silently. Add the redirect manually every time.
Restructured your blog CMS collection	Bulk move with a wildcard: /blog/* → /articles/* in one rule, covering thousands of posts.
Migrating from WordPress, Squarespace, or another platform to Webflow	Map every old URL to its new Webflow path before launching, protect every backlink.
Deleted a CMS item	Send the deleted URL to the closest replacement or to the parent category, never to the homepage (soft-404 risk).
Pages that exist in only one language	For localized sites, redirect missing language variants to the default locale instead of letting them 404.
Old marketing campaign URLs	Send /promo-summer-25 to /promo or /collections/sale rather than leaving as 404 after the campaign ends.

Pro tip

Webflow strips query strings on redirect, UTMs are lost. For ad and email campaigns, route through a Flyn short link instead: Flyn preserves UTMs through the redirect, and the destination is editable without re-publishing Webflow.

Webflow Redirect Best Practices

Don't

Always 301 a renamed slug (Webflow does NOT auto-redirect)

Trust the CMS to handle slug changes automatically

Use wildcards (/*) for bulk prefix moves

Add 500 individual rules when one wildcard would do

Click Publish, redirects do not fire until then

Save and forget, staging behavior differs from published

Redirect to the closest topical page

Send everything to / (Google soft-404 risk)

Use Flyn for marketing URLs that change destinations

Lock campaign destinations into Webflow redirects

Test in incognito after publish

Trust the cached browser view of the site

Marketing Redirects Belong Outside Webflow

Edit without re-publishing

Point a Flyn link at any new destination from anywhere, no Webflow login, no Publish click, no waiting for the publish queue.

Real per-link analytics

See clicks by country, device, referrer, hour. Webflow 301s give you zero visibility, Flyn shows you everything.

UTMs preserved through redirect

Webflow strips query strings. Flyn passes UTMs (and any params) through to the final destination intact.

302 / 307 when you need it

For temporary redirects (A/B tests, campaigns), Flyn supports every status code Webflow hides from you.

Frequently Asked Questions

What format does Webflow expect for redirects?

Two columns in Project Settings → Publishing → 301 Redirects: "Old Path" and "Redirect to Path". Both are paths starting with /. The destination can be a path or a full external URL. Webflow only supports 301 Permanent redirects, there is no 302/307 option.

Can I bulk-import redirects into Webflow?

No, Webflow has no bulk CSV import for 301 redirects (as of 2026). You have to add each redirect manually in Project Settings → Publishing. The tool above gives you a clean copy-paste source for each rule, plus a TSV view for a spreadsheet you can use as a checklist as you add them one by one.

How do wildcard redirects work in Webflow?

Add /* to the end of both source and destination. Example: /blog/* → /news/* matches every URL under /blog/ and forwards the captured part to /news/. So /blog/launch becomes /news/launch automatically. Without /* on the destination, Webflow drops the captured segment, every URL under /blog/ would end up at /news/ (likely a soft 404 risk).

When do Webflow redirects take effect?

Only after you click Publish at the top right of Webflow Designer. Just saving the redirect in Project Settings is not enough. The live site keeps the old behavior until the next publish. This catches a lot of people during migrations: they add 200 redirects, leave, come back days later, and wonder why nothing redirects.

Will Webflow auto-create redirects when I change a page slug?

No, unlike WordPress and Shopify, Webflow does NOT auto-redirect when you rename a page slug or a CMS collection item slug. You have to add the redirect manually. This is the most common Webflow SEO mistake: silently losing rankings on renamed pages because no redirect was set up.

Can I redirect from a Webflow URL to an external site?

Yes, the "Redirect to Path" field accepts full URLs like https://other-site.com/page. Useful for: redirecting old marketing pages to a new external domain, sending old portfolio URLs to an external case-study site, or pointing legacy paths at your blog on a subdomain. The 301 is still issued by Webflow before the cross-domain hop.

How many redirects can Webflow handle?

Webflow does not document a hard limit. Sites with thousands of redirects work, but the Project Settings UI becomes hard to manage past a few hundred, and Webflow has no search/filter inside the redirect list. For very large migrations, prioritize the URLs with actual traffic (Search Console) and let zero-traffic legacy URLs 404 if they have no backlinks.

Does Webflow strip query strings or pass them through?

Webflow strips the query string on redirect, so /old-page?utm=foo redirects to /new-page (UTMs lost). This is destructive for ad campaigns. The fix: point campaign URLs at a Flyn short link instead of using Webflow redirects, then Flyn preserves UTMs and query params through to the destination.

Will the redirects affect SEO ranking?

301 Permanent redirects transfer between 90-99% of the old URL's link equity to the new URL, for content-similar redirects. Always redirect to the closest topical match, not the homepage. The biggest Webflow SEO failure case is publishing major site restructures without setting up redirects, then losing all the rankings on backlinked URLs.

How do I find which URLs need redirects in my Webflow migration?

Three sources: (1) Search Console → Performance → Pages, every URL with clicks or impressions; (2) your old sitemap.xml, every URL that was indexed; (3) Ahrefs / Semrush "Best by links", URLs with backlinks. Map each to the closest new URL, build the redirect list, paste into Webflow before you publish the new site.

Can I delete a Webflow redirect later?

Yes, go to Project Settings → Publishing → 301 Redirects, hover over the row, click the X. The change takes effect on the next publish. Note Webflow has no version history for redirects: if you delete by mistake, you have to re-add manually. For high-value redirects you may need to roll back, keep them in the TSV export above as a backup.

Do Webflow redirects work for CMS Collection items?

Yes, CMS item URLs (like /blog/post-slug for a Blog Posts collection) follow the same Old Path → Redirect to Path rules. When you change a CMS item slug, the old URL 404s unless you add a redirect manually. For bulk CMS slug changes, use wildcard redirects where possible (/old-collection-prefix/* → /new-collection-prefix/*).

More Free Redirect & Audit Tools

Cover every CMS format and audit every step of the migration. New to this? Read the website migration redirect checklist.

Webflow does not auto-redirect, you have to

Webflow 301 redirects keep your structural SEO intact through site changes. Flyn keeps your marketing URLs editable forever, with full per-click analytics on every campaign.

Start free, no credit card Read the API Docs