Webflow SEO: How to Set Up 301 Redirects and Fix Broken Links Without Losing Rankings

Webflow 301 Redirects and Broken Links: Protecting Rankings Through Every URL Change

The fastest way to lose search traffic in Webflow is not a bad title tag or a slow page. It is a URL that used to rank returning a 404. Every time you rename a page, restructure a folder, or delete an old CMS item, you break the link between Google's index and your content — and unless you redirect it, the ranking equity that URL earned simply evaporates.

The good news is that Webflow has a solid built-in redirect system. The catch, as always, is that it does nothing until you use it deliberately. This guide covers when to redirect, how to do it correctly in Webflow, and how to find the broken links that are quietly draining your authority.

Why 301 redirects matter more than people think

A 301 is a permanent redirect. It tells search engines that a page has moved for good and that roughly all of its accumulated ranking signals — backlinks, internal links, historical authority — should transfer to the new URL. A 302, by contrast, is temporary and does not reliably pass that equity.

When you skip the redirect, three things happen at once: users hit a dead end, Google slowly drops the URL from its index, and any backlinks pointing at the old address now point at nothing. On a site that has been earning links for a year, that is real money walking out the door.

• Slug or page-name changes — renaming /blog/webflow-tips to /guides/webflow-tips creates a new URL and orphans the old one.
• Folder restructures — moving pages under a new parent changes every child URL beneath it.
• Deleted CMS items — an unpublished or removed collection item returns a 404 at its old path.
• Domain or platform migrations — moving to Webflow from another CMS almost always changes URL patterns.

Setting up a 301 redirect in Webflow

Webflow handles redirects at the project level. Open Project Settings, go to the Publishing tab, and scroll to the 301 Redirects section. You add two values: the old path and the target path.

1. In the Old Path field, enter the path only — for example /old-page — not the full domain.
2. In the Redirect to Page field, enter the destination path, such as /new-page.
3. Save, then republish the site so the rule goes live.

Webflow also supports wildcard redirects, which are essential for bulk moves. A rule like /blog/(.*) redirecting to /guides/%1 will forward every URL under the old blog folder to the matching URL under the new one, preserving the slug. This turns a 200-URL migration into a single rule.

Rule of thumb: if a URL has ever been public, never let it 404. Redirect it to the closest relevant page — the new version, the parent category, or at worst the homepage.

Finding broken links before Google does

Redirects only help if you know which URLs are broken. Build a habit of auditing links from three angles:

• Google Search Console — the Pages report flags URLs returning 404 and 'Not found' errors that Google has already encountered.
• A crawl tool — a site crawler follows every internal link and lists any that resolve to a 404, including ones buried in old blog posts.
• Your own analytics — a spike in 404 pageviews after a publish is a signal that a recent change broke internal links.

Pay special attention to internal links, because you control those completely. If your navigation, footer, or an old article points at a URL you have since moved, update the link directly rather than relying on the redirect. Redirects add a hop; a clean internal link is always better.

A repeatable pre-publish checklist

• Before renaming a slug, note the old path and create the 301 in the same session.
• For any folder move, write a wildcard rule instead of dozens of one-off redirects.
• After a big change, crawl the site and fix internal links that still point at old URLs.
• Check Search Console weekly for new 404s and redirect anything with historical value.
• Never chain redirects — point the old URL straight at the final destination, not at another redirect.

Handled consistently, redirects make a redesign invisible to Google: rankings carry over, links keep working, and users never see a dead end. Handled carelessly, they are the single most common reason a site loses traffic after a relaunch.

Quilly is the AI content engine that writes, publishes, and ranks CMS content on autopilot — pulling real keyword demand, drafting on-brand articles, and pushing them straight to Webflow, WordPress, or a headless CMS. If you would rather rank than spend your week wrestling with SEO settings, start free.