To set up a 301 redirect in Webflow, go to Site Settings > Publishing > 301 redirects, enter the old URL path and the new destination path, click Add redirect path, then publish the site. This permanently routes traffic from an old URL to a new one, preserving ranking power and preventing 404s. You can add redirects one at a time for a single URL change, or import many at once with a CSV file.
Without that mapping, old bookmarks, external links, and indexed results still point to pages that no longer exist. A 301 tells browsers and search engines the move is permanent.
To add a redirect manually in Webflow:
/old-url)/entirely/new-url/structure)After publishing, test by opening the old path in a new tab. If you are redirecting a page that still exists on the site, first change its slug, save it as a draft, or delete or archive it first, otherwise the live page will resolve before the redirect can fire.
Once the single-redirect basics are covered, the next question is how to handle dozens or hundreds of URLs at once. Webflow added native CSV import and export for redirects under Site Settings > Publishing > 301 redirects, and the safe workflow is always export first, then edit, then import.
Back up your current rules from Site settings > Publishing > 301 redirects > Export. Your file requires two columns (old paths and redirect-to paths) with one row per redirect. Keep paths root-relative (e.g., /old-blog/post to /new-blog/post), preserve leading slashes, and use the escape-character doc Webflow links for special characters.
To import, go to the same 301 redirects panel and click Import, then drag in the CSV and publish the site for changes to take effect. The platform overwrites all existing redirects on import, so if you add 50 rows to a site that had 200, you must include all 250 in the new file. If the file contains invalid rows, import fails and Webflow emails you a copy with error guidance. Each upload is limited to a maximum file size of 16MB.
On volume, third-party implementation guides describe Webflow as limiting the number of redirects allowed per site. Check your site's Publishing settings for the current enforced cap before a large migration, since Webflow adjusts limits over time.
For pattern matching, Webflow does not support true regex. It uses a simple wildcard placeholder that applies the (.*) pattern to a specific path part or querystring param value, like /blog/(.*) -> /news/%1. Query parameters must be matched explicitly in that form; you cannot write broad regex alternations or lookaheads.
Uploading a new CSV replaces your entire redirect list — export a backup first or you will lose existing rules.
Migrating a full site to Webflow without losing rankings means mapping every live URL to a relevant Webflow destination before DNS cutover and publishing that map with the new site, so no legacy URL returns a 404 on day one.
The CSV mechanics matter most in exactly one scenario: migrating an entire site's worth of URLs at once. That is when the prep work decides whether link equity and traffic carry over.
A concrete migration workflow
1. Export the full legacy inventory. Crawl the old domain with a crawler like Screaming Frog to capture all URLs, status codes, titles, and internal links. Pull additional sources you control: sitemap.xml, WordPress Pages/Posts export, Shopify Products URL list, Google Search Console Pages report, and analytics landing pages. Moz's migration guide recommends keeping a copy of the old site's crawl data for several months after migration because you will need it to diagnose gaps.
2. Identify what must redirect. Filter to indexable pages: 200 responses, self-referencing or no canonical, no meta robots noindex, and not blocked in robots.txt. Then tag priority URLs by organic traffic, revenue, and backlinks. Those drive your 1:1 mapping first.
3. Build the redirect map before cutover. In a sheet, create columns for Old Path (Webflow expects root-relative paths like /old-blog/post), New Path (/blog/post), and Intent. Redirects are managed in Site Settings > Publishing > 301 redirects and are relative to the root domain, which shapes how you write the old paths.
4. Normalize for structure changes. Align trailing slashes to how Webflow serves pages, consolidate folder renames into pattern rules where possible, and decide on removed content. For discontinued products or posts with no close match, map to the closest relevant category page rather than the homepage to preserve user intent. For localized variants like /es/old-url, create separate rules because Webflow treats localized slugs independently.
5. Sequence for zero gap. Upload the full redirect map to the Webflow project while it is still on the webflow.io staging domain and publish it. Only then connect the custom domain and set it as default, then update DNS. Keep the legacy CMS live for 24-48 hours to catch any requests that hit the old origin during propagation. As Moz notes, redirect implementation is a phase where things often go wrong, so redirect mapping requires careful attention to detail and testing on staging before launch.
Mapping every old URL to a new one is only useful if you can prove, after publishing, that each redirect actually fires correctly.
Webflow's native redirect tool only creates 301 Moved Permanently redirects; you cannot select a 302 status in Site Settings > Publishing > 301 redirects. That distinction matters because a 301 and a 302 instruct browsers and search engines to treat the original URL very differently.
The common mistake is assuming the Webflow UI lets you pick temporary vs. permanent, or using a permanent redirect for a short-term swap because it is the only option available. When the move is truly temporary, a 301 can cause search engines to drop the original URL from the index and consolidate signals to the destination, which is slow to undo.
HTTP semantics make the difference clear. The HTTP 301 Moved Permanently response indicates the requested resource has been permanently moved to the URL in the Location header. MDN notes that search engines receiving this response will attribute links to the original URL to the redirected resource, passing the SEO ranking to the new URL.
By contrast, 302 Found is a temporary redirect. Browsers continue to request the original URL on subsequent visits, and search engines typically keep the original URL indexed and do not fully transfer ranking signals to the new location.
Webflow documents this boundary directly. The help center frames its tool as Use 301 redirects to route traffic from an old URL to a new URL and notes there are other types of redirects (such as 302 redirects, which indicate a temporary relocation) but 301 redirects are best used if you need to permanently route incoming traffic to a new URL. There is no toggle for 302 in the native hosting settings.
Use Webflow's 301 when the old URL is gone for good: page retired, slug restructured, content merged, or domain changed. Reserve temporary behavior for cases where the original will return: a short-term A/B test, seasonal campaign takeover, or maintenance placeholder. If you truly need a 302 on a Webflow-hosted domain, you must implement it outside Webflow, for example via a reverse proxy or edge worker, not through the built-in redirect list.
A valid Webflow 301 redirect shows as HTTP 301 in your browser's Network panel and ends with a single HTTP 200 at the new URL. Redirect type sorted, mapping done, CSV uploaded: none of it is confirmed working until it's tested.
Start with the browser. In Chrome DevTools open Network, turn on Preserve log so the redirect response stays visible across the navigation, then load the old path. You should see the old URL with Status 301 and a Location header pointing to the new path, followed immediately by the new path at 200. If you see 404, the old path in Webflow does not match exactly; if you see 302 or two 301s in a row, you have a temporary redirect or a chain adding latency.
For the full site, crawl instead of clicking. Switch Screaming Frog SEO Spider to List Mode, upload your pre-migration URL list from analytics and Search Console, enable Advanced > Always Follow Redirects, then crawl. Export Reports > Redirect Chains and Reports > All Redirects. That All Redirects report records start URL, final URL, number of hops, and flags loops so you can audit at scale. Also run a fresh crawl of the live domain to catch internal links that still point to old URLs and would create chains.
Use this verification sequence after every publish:
Fix chains by pointing each old URL directly at its final destination, fix loops by removing the circular rule, and fix lingering 404s by adding the missing old-path entry in Publishing > 301 redirects and republishing.
Zero 404s on old URLs for a week and every legacy link returning 301 is what "done" looks like on paper, but that clean status only protects existing rankings. Keeping the site visible afterward requires a monitoring cadence and continuous publishing, not a one-time fix.
HarperFlow publishes highly structured articles featuring FAQs, data tables, and direct-answer blocks that meet the rigorous citation standards required by AI search engines. By continuously auditing and improving your content through AI answer analytics, HarperFlow helps your site build long-term authority and visibility that outlasts ad-dependent strategies.
A clean redirect audit closes the migration risk, but it isn't the end of the visibility story. Old URLs still get crawled, new pages compete, and equity fades if nothing new earns attention.
Use a short post-migration checklist:
Once that rhythm is stable, growth depends on publishing. A migrated site that stops after redirects keeps what it had; it does not earn new topics or queries.
Fixing 301 redirects protects existing rankings; it does not grow new visibility — that requires ongoing publishing.
For teams that moved to Webflow to simplify operations, sustaining momentum after the migration means continuing to add well-structured, sourced articles to the blog. A tool like HarperFlow, which automates research, writing, and publishing of citation-ready articles directly to Webflow, fits here when the goal is building durable organic demand rather than treating the redirect map as the finish line.
No. Webflow's built-in redirect panel only creates 301 Moved Permanently redirects. If you need a true temporary redirect for a test or seasonal swap, you must handle it outside Webflow using a reverse proxy or edge worker.
New imports overwrite all existing redirects in Webflow. Before importing, export your current list from Site settings > Publishing > 301 redirects > Export and merge all old and new rows into one file.
Yes. Adding a redirect path in the settings does not activate it until you publish. After every manual add or CSV import, publish the site and then test the old URL in a new tab.
The most common reason is the original page still exists as a live page, so Webflow serves it before the redirect can fire. Change its slug, set it to draft, archive or delete it, then republish, and double-check that your old path uses root-relative format like /old-url.
Webflow does not support full regex. It supports a simple wildcard using the (.) pattern for a path part or querystring param value, such as /blog/(.) to /news/%1, without alternations or lookaheads.
301 redirects in Webflow are relative to your root domain and won't apply automatically to localized slugs or subdirectories. If you have /es/old-url you need a separate explicit rule for that localized path.
The CSV needs two columns for the old paths and redirect to paths, one row per redirect, with root-relative values like /old-blog/post and /new-blog/post and leading slashes preserved. You import it from Site settings > Publishing > 301 redirects.
Yes, each upload has a maximum file size of 16MB. If import fails, Webflow emails you a copy with error guidance so you can fix formatting issues and re-upload.