Webflow 301 Redirect: Fix a Broken Link in Under 5 Minutes

A Webflow 301 redirect permanently sends visitors and search engines from an old URL to a new one, so you don't lose traffic, links, or rankings when a page moves. Open Site settings, add the old path and new URL under the SEO tab, then republish to make it live.

What a Webflow 301 Redirect Does (and Why You Need One)

When you delete, rename, or restructure a page in Webflow, the old URL still exists in Google's index and in links pointing at your site from elsewhere. Visit it without a redirect and you get a 404 error. A 301 redirect fixes that by telling browsers and search engines the content moved permanently, and it passes along most of the original page's ranking value (Google Search Central).

This matters more than it sounds. If a blog post, product page, or service page earned backlinks or ranking position, losing it to a dead link wastes that equity. A correctly configured 301 redirect preserves it. That's the whole point of setting one up the moment a URL changes.

Before you touch any settings, it helps to confirm what's actually happening on the page in question. SearchBlueprint's free Redirect Checker traces the full redirect chain for any URL, shows you the status code at each hop, and flags loops or dead ends, useful for confirming a Webflow 301 redirect actually fired the way you expect, or catching a page that's still returning a 404.

Why 301, Specifically

Webflow's redirect tool only creates 301s, not 302s. That's intentional. A 301 tells search engines the move is permanent, so they transfer ranking signals to the new URL and eventually drop the old one from the index (Google Search Central). A 302 implies a temporary move and search engines tend to keep indexing the original. For a page that's gone for good, 301 is the right code almost every time.

How to Set Up a 301 Redirect in Webflow (Step by Step)

Webflow builds redirects into the project itself, so you don't need a third-party app for a basic fix. Here's the process:

1. Open your project and go to Site settings.
2. Click the SEO tab in the settings panel.
3. Scroll down to the 301 Redirects section.
4. Enter the old page's path in the first field, just the path, like /old-page, not the full domain.
5. Enter the destination in the second field. This can be a path on the same site or a full external URL.
6. Click the button to add the redirect, then save your settings.
7. Republish the site. Redirects saved in settings don't go live until you publish.

That last step trips people up constantly. You can add ten redirects, close the tab, and assume you're done, but if you never hit publish, none of them work. Always republish and then test the old URL in a browser to confirm it forwards correctly.

If you manage a WordPress site alongside your Webflow project, the setup looks different, see WordPress 301 Redirect: Fix a Broken Link in 3 Steps for that platform's process. The underlying goal is the same: preserve the old URL's ranking value while pointing visitors to the right page.

When Webflow's Built-In Redirects Are Enough, and When They're Not

Here's where you need to be honest with yourself about scale. Webflow's native redirect tool is genuinely good for what it's built for: a handful of one-off moves. It gets strained once the job grows.

One URL vs. an Entire Site Migration

Fixing one broken link after renaming a page is exactly what the built-in tool is for. Add the path, add the destination, republish, done. That's a two-minute job and there's no reason to reach for anything else.

A full site migration is a different animal. If you're moving from WordPress or Squarespace into Webflow and bringing over fifty or a hundred URLs, entering each one by hand in the SEO settings is slow and error-prone. There's no bulk CSV upload in the native tool, so every redirect is a manual row.

A One-Off Fix vs. a Recurring Problem

If broken links keep appearing, because content gets reorganized often, or because you're running an agency managing redirects across client sites, the native tool still works, but it offers no monitoring. It won't tell you when a redirect breaks later or when someone deletes a page without adding one.

Scenario	Webflow's native tool	What you'll likely need instead
Single page renamed or deleted	Sufficient, add one redirect, republish	Nothing extra
Full domain or CMS migration (50+ URLs)	Possible but slow, one entry at a time	A spreadsheet-driven plan before you start, checked against a redirect audit
Wildcard patterns (e.g., entire old blog folder)	Not supported	A manual redirect per URL, since Webflow has no pattern matching
Ongoing redirect monitoring across many pages	Not built in	Periodic checks with a redirect checker tool

Before any migration, run the old URLs through a redirect checker to confirm which ones are actually live and which already 404. That single check often reshapes the whole migration plan, because you'll find dead URLs nobody remembered existed.

For a deeper look at preserving rankings specifically, not just fixing a broken link, but protecting the SEO value behind it, How to Do a 301 Redirect Without Losing Your Rankings walks through the mechanics in more depth.

Common Mistakes With Webflow 301 Redirects

Most redirect problems in Webflow come down to a short list of repeatable errors.

Mistake	Why it breaks the redirect	Fix
Forgetting to republish	Settings save but never go live on the published site	Republish after every redirect change, every time
Including the full domain in the "old path" field	Webflow expects a relative path, not https://yoursite.com/old-page	Enter just /old-page
Creating a redirect loop	New URL points back to the old one, or to another redirect that loops back	Check the final destination loads directly with no further redirect
Typo in the old path	The redirect never matches the real URL, so visitors still hit a 404	Copy the exact path from the browser address bar
Redirecting to an unrelated page	Confuses visitors and signals low relevance to search engines	Redirect to the closest matching live page, not just the homepage

A redirect loop is the one worth double-checking every time. It's invisible until someone actually clicks the link, and then the browser just spins. Running the finished redirect through a checker tool catches this before a visitor does.

If you're moving a Shopify store's product or collection pages instead of a Webflow site, the loop risk is similar but the settings live elsewhere, see Shopify 301 Redirect: The 5-Minute Fix for a Broken Link for that setup. And if you're coming from Squarespace, the comparable guide is Squarespace 301 Redirect: Set One Up in 5 Minutes.

According to Google's own guidance on redirects and search, a 301 is the correct choice whenever a page's move is permanent, since it consolidates indexing signals onto the destination URL rather than splitting them across both (Google Search Central).

FAQs

Does a Webflow 301 redirect hurt my SEO rankings?

No, not when set up correctly. A 301 passes most of the original page's ranking signals to the new URL (Google Search Central). The risk isn't the redirect itself, it's forgetting one, creating a loop, or pointing it to an unrelated page.

How long does it take for a Webflow 301 redirect to show up in Google?

Google typically recrawls and updates its index within days to a few weeks, depending on how often it crawls the site (Google Search Central). The redirect works for visitors immediately after you publish; the search index just takes time to catch up.

Can I redirect an entire folder of URLs at once in Webflow?

Not with wildcards, no. Webflow's native tool requires one specific old path per redirect rule. For a folder with many URLs, you'll add each one individually or plan the migration with a spreadsheet first.

Why isn't my Webflow redirect working after I added it?

The most common reason is forgetting to republish the site after saving the redirect in settings. The second most common reason is a typo in the old path field, it needs to match the URL exactly.

Can I redirect a Webflow page to an external domain?

Yes. The destination field accepts a full external URL, not just a path on the same site. This is useful when consolidating a separate domain into your main Webflow project.

Put the Redirect to the Test

Set up the redirect in Site settings, republish, then check the old URL loads the new page with no detour or loop in between. A Webflow 301 redirect that's configured but never verified is the most common way broken links slip back onto a live site. If you want a second set of eyes on how your redirects and overall SEO setup are performing, talk to the team and get a sample report walking through exactly what's working and what needs attention.

Resources / References

1. Google Search Central