How to fix 404 errors on Webflow
Webflow 404s typically show up after you rename pages, restructure your CMS collections, or redesign a site. Webflow has a built-in 301 redirect tool that even supports wildcards — here's how to use it, and how to catch the URLs you forget.
Why 404 errors happen on Webflow
- A page slug or folder was renamed, so the old URL path no longer exists.
- A CMS collection or its URL structure changed (e.g. /blog/ became /articles/).
- You redesigned or replatformed and old URLs weren't mapped.
- External links or search results point to removed pages.
How to fix 404 errors on Webflow, step by step
- 1
Open the 301 Redirects panel
In your Webflow project, go to Site Settings → Publishing → 301 Redirects.
- 2
Add a redirect
Enter the 'Old Path' (e.g. /old-page) and the 'Redirect to Page' (e.g. /new-page), then click Add Redirect Path.
- 3
Use wildcards for bulk patterns
Webflow supports wildcard redirects: set Old Path to /blog/(.*) and Redirect to /articles/%1 to move an entire folder in one rule. This is ideal for CMS restructures.
- 4
Publish and test
Publish the site for redirects to take effect, then visit the old URL to confirm the 301 works.
Automatically rescue every 404 on Webflow
Webflow's redirect tool is great, but it only handles URLs you remember to add. Redirect Mapper's snippet lives on your Webflow 404 page (Page Settings → Custom Code), detects any 404 in real time, and sends the visitor to the closest live page from your sitemap automatically — then logs it so you can add a permanent Webflow rule later.
Frequently asked questions
Yes. In Site Settings → Publishing → 301 Redirects you can use wildcard patterns like /blog/(.*) → /articles/%1 to redirect an entire folder or URL pattern with a single rule, which is useful when you restructure a CMS collection.