How to Set Up 301 Redirects in Webflow

Changed a URL and now your traffic is hitting a dead end?

Learning how to set up 301 redirects in Webflow prevents broken links, preserves your search rankings, and keeps visitors on track when pages move or disappear.

Every site migration, URL restructure, or deleted page creates orphan paths that frustrate users and hurt SEO.

Permanent redirects solve this by automatically routing old URLs to new destinations.

This guide walks you through accessing the redirect panel, creating single and bulk redirects, handling CMS collections, using wildcard patterns, and troubleshooting common errors.

Takes about 10 minutes. No coding required.

What Is a 301 Redirect in Webflow?

A 301 redirect is a permanent URL redirection that automatically sends visitors and search engines from an old path to a new destination.

Setting up 301 redirects in Webflow routes traffic when you change page slugs, delete pages, restructure your site, or migrate from another platform.

This process preserves link equity and prevents broken links that hurt your search rankings.

Users need this when reorganizing URL structure, consolidating content, or switching to a new domain.

This guide covers 7 steps requiring 5-10 minutes and basic Webflow knowledge.

Prerequisites

Before you start, gather these requirements:

• Active Webflow account with site access (Starter plan or higher)
• Admin or Editor permissions on the project
• Published site connected to hosting
• List of old URLs and corresponding new paths
• Basic understanding of URL structure and page slugs

Time estimate: 5-10 minutes for manual setup, 15-20 minutes for bulk CSV import.

Skill level: Beginner-friendly, no coding required.

Step 1: How Do You Access the 301 Redirects Panel in Webflow?

Open your Webflow dashboard, select your project, click Site Settings, navigate to the Publishing tab, and scroll to the 301 Redirects section where two input fields appear for old and new paths.

Action

1. Webflow Dashboard: Log in and click your project name
2. Site Settings: Click the gear icon in the left sidebar
3. Publishing tab: Select from the top navigation menu
4. 301 Redirects section: Scroll down past hosting options

You see two empty fields labeled “Old Path” and “Redirect to Path” with an “Add Redirect Path” button.

Purpose

The redirect panel centralizes all URL mapping rules.

Accessing this location first prevents confusion when managing multiple redirect rules across your site.

Step 2: How Do You Create a Single Page Redirect?

Enter the old URL path in the first field using relative format like /old-page, add the new destination path in the second field, click Add Redirect Path, then publish your site to activate the permanent redirect rule.

Action

1. Old Path field: Enter /old-page-slug (no domain, start with /)
2. Redirect to Path field: Enter /new-page-slug or full external URL
3. Add Redirect Path button: Click to save the rule
4. Publish site: Redirects activate only after publishing

The redirect appears in your list immediately.

Test by entering the old URL in a new browser tab.

Purpose

Single page redirects handle individual URL changes without affecting other pages.

The HTTP status code 301 tells Google this move is permanent, transferring page authority to the new location.

Step 3: How Do You Redirect an Entire Folder Using Capture Groups?

Use wildcard syntax with (.) in the old path and %1 in the new path to redirect all pages within a folder simultaneously, matching any URL that starts with the specified directory structure.

Action

1. Old Path syntax: Enter /old-folder/(.)
2. New Path syntax: Enter /new-folder/%1
3. Special characters: Escape hyphens with %2D if needed
4. Result: /old-folder/page-name redirects to /new-folder/page-name

The capture group (.) grabs everything after the folder name.

The %1 placeholder inserts that captured text into the new path.

Purpose

Folder redirects save time during major site restructuring.

Instead of creating dozens of individual redirect rules, one wildcard pattern handles the entire directory and any future pages added to it.

This approach reduces your redirect manifest size and improves user experience by maintaining consistent URL patterns.

Step 4: How Do You Redirect Static Pages When Changing Slugs?

Modify the page slug directly in Webflow Designer, check the automatic redirect option that appears, and the platform creates the 301 redirect rule without manual entry in Site Settings.

Action

1. Pages panel: Click the page icon in the left sidebar
2. Page Settings: Click the gear icon next to your page name
3. Slug field: Change /old-slug to /new-slug
4. Checkbox: Select “Permanently redirect old URL to new URL”

Webflow handles the redirect mapping automatically.

Publish your site to activate the change.

Purpose

Automatic slug redirects prevent broken links when reorganizing your navigation structure.

No manual entry required for routine page updates.

Step 5: How Do You Handle CMS Collection Item Redirects?

CMS items require manual redirect setup because Webflow does not auto-generate 301 rules when you change dynamic page slugs in the Collections panel.

Action

1. CMS Collections: Open your collection (Blog Posts, Products, etc.)
2. Edit item: Click the specific collection item
3. Slug field: Note the old slug before changing it
4. Site Settings: Manually add redirect in Publishing > 301 Redirects
5. Path format: Use /collection-slug/old-item-slug

Archive or unpublish the item first if the old URL conflicts with your redirect.

Purpose

Dynamic content needs extra attention to preserve backlink value and search rankings.

Missing this step creates crawl errors in Google Search Console.

Step 6: How Do You Bulk Import Redirects Using CSV?

Upload a CSV file containing multiple redirect rules at once, useful during site migrations when you need to map dozens or hundreds of old URLs to new destinations simultaneously.

Action

1. CSV structure: Two columns with headers “Old Path” and “New Path”
2. Format paths: Start each with / (e.g., /old-page,/new-page)
3. Import button: Click in the 301 Redirects section
4. Upload file: Select your prepared CSV
5. Review: Check imported rules for errors

Use tools like Screaming Frog or HTML Table to CSV Converter to generate your redirect mapping spreadsheet.

Purpose

Bulk import saves hours during website restructuring or platform migration.

One upload handles what would take dozens of manual entries.

Step 7: How Do You Redirect to an External URL?

Enter a full URL with https:// protocol in the destination field to send visitors from your Webflow page to a completely different domain or subdomain.

Action

1. Old Path: Enter your internal path like /old-page
2. Redirect to Path: Enter full URL like https://external-site.com/page
3. Protocol required: Always include https:// or http://
4. Test redirect: Verify destination loads correctly

External redirects work for subdomain routing, affiliate links, or domain consolidation.

Purpose

Route traffic to external resources while maintaining your old domain forwarding setup.

Useful when merging multiple sites or pointing to third-party tools.

Verification

Confirm your redirects work correctly before considering the job done.

• Browser test: Enter old URL, watch address bar update to new URL
• HTTP status check: Use a redirect checker tool to verify 301 response code
• Google Search Console: Monitor for crawl errors over the next few days
• Site Settings list: Confirm redirect appears in your 301 Redirects panel
• Sitemap update: Submit updated sitemap to search engines

Clear browser cache if redirects appear stuck on old destinations.

Troubleshooting

Redirect Not Working After Setup

Solution: Publish your site; redirects only activate after publishing changes to your live domain.

Conflict With Existing Page

Solution: Delete, archive, or change the slug of any live page before creating a redirect for that path.

Webflow cannot redirect to a URL that already exists as a published page.

Redirect Loop Error

Solution: Check for circular redirect paths where Page A points to Page B and Page B points back to Page A.

Remove one rule from the redirect chain.

CMS Page Redirect Fails

Solution: Archive or unpublish the CMS item first, then create the redirect rule in Site Settings.

Special Characters Cause Errors

Solution: Replace special characters with URL encoding (hyphen becomes %2D, space becomes %20).

Avoid wildcards in paths unless using proper capture group syntax.

Too Many Redirects Slowing Site

Solution: Use wildcard redirects for entire folders instead of individual page rules.

Review and remove outdated redirects annually.

Related Processes

Continue building your Webflow skills with these related guides:

• How to use Webflow for beginners
• How to create a blog in Webflow with CMS collections
• How to hide a page in Webflow before redirecting
• How to delete a site in Webflow after migration
• How to add Google Analytics to Webflow to track redirect traffic
• How to transfer a Webflow site to another account

FAQ on How To Set Up 301 Redirects In Webflow

What Is a 301 Redirect in Webflow?

A 301 redirect is a permanent URL redirection that sends visitors and search engines from an old path to a new destination.

Webflow handles this server-side, returning an HTTP status code that tells browsers the page has moved permanently.

How Do I Access the Redirects Panel in Webflow?

Open your project, click Site Settings, select the Publishing tab, then scroll to the 301 Redirects section.

You see two input fields for old and new paths plus an Add Redirect Path button.

What Is the Difference Between 301 and 302 Redirects?

301 redirects are permanent and transfer link equity to the new URL.

302 redirects are temporary, telling search engines to keep indexing the original path. Webflow uses 301 by default for all redirect rules.

Can I Redirect an Entire Folder in Webflow?

Yes. Use wildcard patterns with capture groups.

Enter /old-folder/(.) as the old path and /new-folder/%1 as the destination. Every page within that folder redirects automatically to the matching new location.

How Do I Bulk Import Redirects in Webflow?

Prepare a CSV file with two columns: Old Path and New Path.

Go to Site Settings, Publishing tab, click Import in the 301 Redirects section, and upload your file. All rules import at once.

Do 301 Redirects Affect SEO?

Properly configured 301 redirects preserve your search rankings by transferring link equity from old URLs to new ones.

Missing redirects create broken links and crawl errors that hurt your site in Google Search Console.

Why Is My Webflow Redirect Not Working?

Most common cause: you forgot to publish.

Redirects only activate after publishing your site. Also check for conflicts with existing live pages and clear your browser cache to see changes.

Can I Redirect to an External URL in Webflow?

Yes. Enter the full destination URL including https:// protocol in the Redirect to Path field.

This works for subdomain routing, domain consolidation, or sending traffic to third-party platforms.

How Do I Redirect CMS Collection Pages?

CMS items require manual redirect setup.

Note the old slug, change it in your collection, then add the redirect rule manually in Site Settings. Include the full path like /blog/old-post-slug.

Is There a Limit to Redirects in Webflow?

Webflow has no strict limit, but large redirect lists increase your manifest file size.

Use wildcard redirects for folders instead of individual rules. Review and remove outdated redirects annually for better performance.

Conclusion

Knowing how to set up 301 redirects in Webflow keeps your site healthy during URL changes, domain migrations, and content reorganization.

You now have the redirect rules in place to preserve link equity and prevent 404 errors.

Single page redirects handle quick fixes. Capture groups manage entire folders. CSV imports save time during large migrations.

Test every redirect after publishing. Monitor Google Search Console for crawl errors over the following weeks.

Run a redirect audit annually to remove outdated rules and keep your sitemap clean.

Traffic routing problems disappear when your URL mapping stays current.

Bookmark this guide. You will need it the next time a page slug changes or a client requests a domain switch.