Webflow

Webflow migration lost pages: fix 301 redirects

Use Webflow automatic slug redirects where they apply, then map folders, collections, and localized paths in the 301 redirect table.

Webflow can create a redirect when a page slug changes, but moving content between folders or collections and changing localized paths still needs a migration map. Add each missing old and new path under "Site settings > Publishing > 301 redirects," publish, then test every old URL and each locale separately.

Why Webflow does this

Webflow automates one narrow case. When you change a page slug in Page settings and check "Permanently redirect the old URL to this new one", it creates a 301 in Site settings > Publishing > 301 redirects. Moving a published page into or out of a folder changes its URL and breaks old links unless you add a redirect. Renaming a published CMS Collection URL also needs a redirect, although one capture rule can cover every Collection item.

Check it right now

Before changing anything, confirm what a crawler actually sees. The check is free, takes one URL and needs no account.

Run the check

How to fix it

Map each old URL to the equivalent new Webflow URL, then run the redirect checker on the old path.
Open Site settings > Publishing > 301 redirects.
Enter the old path in "Old path", enter the new path in "Redirect to path", click "Add redirect path", then publish the site.
For a renamed CMS Collection path, use Webflow's documented pattern: /old-collection-url/(.*) in "Old path" and /new-collection-url/%1 in "Redirect to path".
Add separate rules for localized paths. Webflow says a root redirect does not also apply to localized slugs or subdirectories.
Run the redirect checker on the exact old URLs and confirm each one reaches its matching final page in one permanent redirect.

Why it happens again

Webflow evaluates older redirects before newer ones. A broad wildcard added early can catch a request before a later specific rule. Sort the table by "Date created" when a correct-looking redirect goes to the wrong page.

stillindexed re-checks the URLs you give it every 30 minutes on Starter and alerts when a directive changes, at most 30 minutes after it does. It is a monitor rather than a crawler: it watches a list you choose and tells you when one of seven things changes. Card first, no trial, and a 30 day refund.

See what monitoring covers

Catching it next time

Fixing it once is the easy half. The setting that caused this can be changed again by anyone with access, and the page will keep returning 200 while it happens.

Other ways Webflow loses pages

A migration or redesign losing pages from search, on other platforms

Sources

Every claim about Webflow above is from their own documentation, read on 2026-08-30. Platforms change their settings; if one of these is out of date, their page wins and we would like to know.