How to Set Up 301 Redirects in Webflow Without Losing SEO Equity

Why One Bad URL Change Can Tank Your Webflow Site Traffic

A founder client renamed a handful of pages during a quick rebrand, published the Webflow site, and watched her organic traffic drop by 40 percent within two weeks. The old URLs still ranked in Google. The new URLs had no history. Visitors who clicked the old search results landed on 404 pages, bounced, and Google interpreted the pattern as a sitewide quality drop. A 10-minute redirect setup would have prevented the whole thing.

According to Ahrefs research from 2024, sites that migrate URLs without proper 301 redirects lose on average 38 percent of their organic traffic within 30 days, and roughly 25 percent of that loss becomes permanent. Moz research from 2025 confirms that a well-configured 301 redirect preserves 90 to 99 percent of the link equity from the old URL, while a 404 or a soft redirect loses all of it. The stakes on this small technical detail are enormous for any Webflow site that has existing organic traffic.

This tutorial covers how to set up 301 redirects natively in Webflow, when to use them, which URLs need them, how to test that they work, and the common mistakes that break SEO even with redirects in place.

What Is a 301 Redirect and Why Does It Preserve SEO?

A 301 redirect is an HTTP status code that tells browsers and search engines that a URL has permanently moved to a new location. When Google sees a 301, it transfers the ranking signals, link equity, and historical authority from the old URL to the new one over the following weeks. This is fundamentally different from a 302 temporary redirect or a 404 error, which do not transfer equity at all.

The mechanics matter because search engines rank individual URLs, not domains. If your homepage has 200 backlinks accumulated over three years and you rename the homepage URL without a 301, you effectively start from zero on the new URL. All 200 backlinks point to a dead page, and the new page has no backlink history.

A proper 301 redirect solves this by signaling continuity. Google sees the old URL, follows the redirect, indexes the new URL, and transfers the ranking signals. The process takes anywhere from a few days to several weeks depending on crawl frequency, but the signal transfer is reliable when the redirect is configured correctly.

When Does a Webflow Site Actually Need 301 Redirects?

A Webflow site needs 301 redirects whenever a URL changes: slug renames, page deletions with replacement content, collection slug restructures, folder reorganizations, domain migrations, and HTTPS migrations. Any time an old URL that visitors or search engines might have cached or linked to disappears, you need a redirect pointing to the closest equivalent current URL.

Common scenarios that trigger redirect needs. Renaming a blog post slug from "complete-guide-webflow-seo" to "webflow-seo-guide" loses every backlink to the old URL if no redirect is set. Deleting an obsolete service page without redirecting traffic to a related current service page forfeits the accumulated authority. Restructuring your blog URLs from /blog-post/slug to /blog/slug changes the full URL pattern and needs bulk redirects for every existing post.

Webflow-specific cases include switching from the default Webflow subdomain to a custom domain, migrating from another platform like WordPress or Squarespace to Webflow, and consolidating multiple regional sites into a single Webflow site with Localization.

Where Do You Set Up 301 Redirects in Webflow?

Set up 301 redirects in Webflow by navigating to Site Settings, Publishing, and the 301 Redirects section. Webflow provides a native redirect manager that accepts one-to-one mappings of old paths to new paths. Redirects configured here apply at the server level, issuing true HTTP 301 status codes that search engines recognize correctly.

The interface accepts two inputs per redirect. Old Path is the URL segment after your domain, including the leading slash. New Path is the destination URL, also with a leading slash for internal URLs or a full URL for external destinations. Click Add Redirect Path to save each entry. Webflow supports up to 500 redirects on the CMS plan and unlimited on the Business plan.

Important detail: Webflow's 301 Redirects feature is only available on paid plans with custom domain publishing. The free Webflow subdomain does not support redirects. If you are still on the free plan and need redirects, upgrading to Basic or CMS is a prerequisite.

How Do You Set Up Wildcard and Pattern-Based Redirects?

Webflow supports wildcard redirects using the asterisk character to match dynamic URL segments. A wildcard redirect from /old-blog/* to /blog/* catches every URL under /old-blog/ and redirects to the corresponding path under /blog/. This is essential when you restructure a CMS collection slug and need to redirect hundreds of URLs with one rule instead of configuring each individually.

The wildcard captures everything after the asterisk position and reinserts it at the corresponding asterisk in the destination. So /old-blog/webflow-seo redirects to /blog/webflow-seo. This works for any pattern where the segment after the change is identical between old and new URL structures.

Wildcards do not handle more complex rewriting. If the slug itself changes in addition to the folder, you need individual one-to-one redirects for each affected URL. For a blog with 200 posts where both the folder and the slug changed, you need 200 manual redirect entries or a combination of wildcard and individual rules.

How Do You Handle Redirects When Migrating From WordPress to Webflow?

Migrating from WordPress to Webflow typically requires bulk redirect setup because WordPress URL structures almost never match Webflow's default patterns. Export your WordPress URL list, map each old URL to the closest equivalent Webflow URL, and import the mappings into Webflow's 301 Redirects section. This preserves the organic traffic you built on WordPress during the migration.

The step-by-step process. Export a CSV of all your WordPress URLs using a plugin like Export All URLs or a custom Yoast sitemap export. For each URL, identify the corresponding Webflow URL. For posts, the mapping is usually direct: old WordPress slug maps to new Webflow CMS slug. For WordPress category pages, map them to the corresponding Webflow category collection URL. For WordPress tag pages, decide whether to redirect to your blog index or to the closest category page.

After mapping, enter each redirect in Webflow's redirect manager or submit in bulk through the Webflow Data API if you have more than a few hundred. My tutorial on migrating from WordPress to Webflow without losing SEO covers the full migration process in detail, of which redirects are one critical step.

What About Redirects for HTTPS Migration and Subdomain Changes?

HTTPS migrations rarely need manual redirects on Webflow because Webflow automatically redirects all HTTP requests to HTTPS by default. Subdomain changes are different: moving from www to root domain or vice versa requires a specific Webflow Site Settings configuration, not manual redirects. Go to Publishing, set your preferred primary domain, and Webflow handles the redirect automatically.

Domain migration is another case where Webflow simplifies what would otherwise be complex. If you change your site from oldbrand.com to newbrand.com, configure both domains in Webflow Site Settings with newbrand.com as primary, and Webflow redirects oldbrand.com requests to newbrand.com. This happens at the DNS and server level without requiring individual redirect entries.

For trailing slash handling, Webflow is permissive: both /blog/post and /blog/post/ resolve to the same page. You do not need explicit redirects between the two forms. Webflow normalizes internally.

How Do You Test That Your 301 Redirects Actually Work?

Test redirects by opening the old URL in a browser and confirming it loads the new URL with no intermediate errors. Check the HTTP response code using Chrome DevTools, with the Network tab open and Preserve Log enabled. The first request should return a 301 status, followed by the new URL returning 200. If you see a 302, 404, or any other code, the redirect is misconfigured.

Batch testing tools help when you have many redirects. Screaming Frog SEO Spider in list mode accepts a list of old URLs and reports the status code each returns. For a migration with 200 redirects, a single Screaming Frog run in 10 minutes confirms every redirect is resolving correctly. Ahrefs and Semrush both offer similar batch testing within their audit tools.

Google Search Console also surfaces redirect issues over time. Under Pages, the Indexing report flags 404s and redirect loops. Check this weekly for the first month after any major URL change, since new redirect issues often surface after Google recrawls the site.

What 301 Redirect Mistakes Are Most Common on Webflow Sites?

The most common mistakes are chaining multiple redirects together, redirecting to 404 pages, using 302 temporary redirects instead of 301 permanent, creating redirect loops, and missing redirects for URLs that visitors actually cached. Each of these either loses SEO equity or breaks user experience, often both.

Redirect chaining means URL A redirects to URL B which redirects to URL C. Google follows at most a few hops, and each hop dilutes the equity transfer. Consolidate chains so A redirects directly to C, skipping intermediate destinations. This is common when sites have been restructured multiple times and old redirects point to URLs that have since been moved again.

Redirecting to a 404 page is surprisingly common. Someone sets up a redirect to a URL that itself no longer exists, creating a broken chain. Always test the destination URL returns a 200 status before setting up a redirect to it.

Using 302 instead of 301 passes only temporary authority. Webflow's native redirect manager issues 301s, so this mistake is mostly relevant when you configure redirects through custom code at Cloudflare or another layer. If custom code is in the picture, verify it issues 301 explicitly.

How Do You Audit Your Existing Webflow Site for Missing Redirects?

Audit your Webflow site for missing redirects by pulling the list of URLs that Google has indexed, comparing against your current site structure, and flagging URLs that now 404 or return unexpected errors. Google Search Console's Pages report under Indexing surfaces URLs Google has crawled that no longer resolve correctly.

For sites with existing backlinks, Ahrefs Site Audit and Semrush both identify broken links pointing to your domain from external sources. Each broken backlink is a missed redirect opportunity. Set up 301 redirects for high-value backlinks pointing to dead URLs, and you recover the link equity those backlinks were supposed to deliver.

Internal broken links also need attention. If other pages on your Webflow site link to URLs you have deleted, Webflow does not automatically flag these. Run a Screaming Frog crawl of your live site and look for internal links returning 404. Fix by either updating the link destination or setting up a redirect. My post on how internal linking shapes SEO and AI citations covers the broader internal link hygiene that interacts with redirect strategy.

How Do You Set Up Redirects for Your Webflow Site This Week?

If you are planning a URL change, set up redirects before publishing the change. Navigate to Site Settings, Publishing, 301 Redirects, and add an entry for every old URL mapping to the new URL. Publish the site. Test each redirect by visiting the old URL in an incognito browser and confirming it resolves to the new URL with a 301 status code.

If you recently published URL changes without setting up redirects, audit your Google Search Console for 404 errors in the Pages report and set up redirects retroactively. Traffic recovery takes two to four weeks as Google recrawls and propagates the redirect signals, but the recovery is real and measurable.

If you want help planning a URL migration on your Webflow site or auditing existing redirects for gaps, I am happy to walk through it. Let's chat.