Webflow Wildcard Redirects Explained (Setup Guide + Examples)

A webflow wildcard redirect sends many old URLs to new ones with a single rule. You add it in Site Settings, under the Publishing tab, in the 301 Redirects section. Use (.*) in the Old Path to match any text. Then use %1 in the Redirect to Path to reuse what was matched. Save and publish, and every matching URL forwards to the right page.

Moving pages around can break your links. A single page redirect fixes one URL at a time. That gets slow when you move a whole folder. This is where wildcard redirects help. One rule can forward hundreds of URLs at once. This guide explains the syntax, the steps, and real examples.

We handle Webflow migrations and redirects for clients every month at theCSS Agency. These are the exact steps and rules our team uses.

What Is a Wildcard Redirect?

A wildcard redirect is a rule that matches many URLs with one pattern. The wildcard stands for any text in the URL. So instead of one rule per page, you write one rule for a whole group.

Think of a folder with 200 blog posts. You do not want 200 separate rules. A wildcard redirect handles all 200 at once. It matches every URL in that folder and forwards each to the new spot.

Wildcard Redirect vs Regular 301 Redirect

Both send an old URL to a new one. The difference is scale.

• A regular 301 redirect matches one exact URL. You set the old path and the new path by hand.
• A wildcard redirect matches a pattern. One rule covers every URL that fits the pattern.

Use a regular redirect for a single page. Use a wildcard redirect for a whole folder or a full site change.

Why Wildcard Redirects Matter for SEO

Redirects protect your search rankings. When a URL changes, a 301 redirect passes most of its ranking value to the new page. It also keeps visitors from hitting a 404 error.

A wildcard redirect does this at scale. During a migration, it saves the ranking value of a whole section. That is why redirects are a key step in any site move.

When to Use a Wildcard Redirect in Webflow

Not every job needs a wildcard. Use one when many URLs change in the same way. Here are the most common cases.

Site Migration

You moved to Webflow from another platform. The old URLs used a different folder name. A wildcard redirect forwards the whole set to the new structure.

Folder or URL Restructure

You renamed a section, like /posts to /blog. Every URL under that folder needs to move. One wildcard rule handles them all.

Removing or Renaming a Section

You deleted an old services folder. You want all its URLs to point to the new services page. A wildcard rule sends every old URL to the right place.

Does Webflow Support Wildcard Redirects?

Yes. Webflow has built-in support for 301 redirect rules, including wildcards. You do not need extra tools or code. The feature lives in your site settings. It works on both the staging domain and your custom domain.

There is one thing to note. Your plan sets a limit on how many redirects you can add. Check your plan if you have a very large list.

Webflow Wildcard Redirect Syntax

The syntax has two parts. You need both for a wildcard to work.

The Wildcard: (.*)

You place (.*) in the Old Path field. This pattern means "match any text here." It captures everything that comes after your folder name. Webflow saves that matched text so you can reuse it.

The Capture Reference: %1

You place %1 in the Redirect to Path field. This inserts the text that (.*) matched. So the end of the old URL carries over to the new URL. If you use two wildcards, the second one becomes %2.

Here is the idea in one line:

• Old Path: /posts/(.*)
• Redirect to Path: /blog/%1

A visit to /posts/my-article now lands on /blog/my-article. The my-article part carried over.

How to Set Up a Wildcard Redirect in Webflow

Follow these steps in order. Each one is quick.

Step 1: Open Site Settings

Open your project. Click the settings icon, or go to your project dashboard. Then open Site Settings for that project.

Step 2: Go to the Publishing Tab

Inside Site Settings, click the Publishing tab. Scroll down until you see the 301 Redirects area.

Step 3: Find the 301 Redirects Section

This section has two fields. One is Old Path. The other is Redirect to Path. This is where every redirect rule goes.

Step 4: Add the Old Path With a Wildcard

In the Old Path field, type your folder and add the wildcard. For example, type /posts/(.*). Always start the path with a slash.

Step 5: Add the Redirect Path With %1

In the Redirect to Path field, type the new folder and add %1. For example, type /blog/%1. This carries the old page name to the new URL.

Step 6: Save and Publish

Click Add Redirect Path to save the rule. Then publish your site. Redirects only work after you publish. Test a few URLs once the site is live.

Webflow Wildcard Redirect Examples

Here are real patterns you can copy. Change the folder names to match your site.

Example 1: Move a Whole Blog Folder

You changed /posts to /blog. You want each post to keep its name.

Result: /posts/seo-tips now goes to /blog/seo-tips.

Example 2: Redirect an Old Folder to One Page

You removed an old services folder. You want every old URL to land on one new page.

Result: every URL under /old-services/ goes to /services. Here you do not need %1, because all traffic goes to a single page.

Example 3: Change a URL Structure After Migration

You moved from another platform. The old site used /product. Your new site uses /shop.

Result: /product/blue-shirt now goes to /shop/blue-shirt.

Example 4: Send an Old Section to the Home Page

You retired a whole section and have no matching new pages.

Result: every URL under /legacy/ goes to your home page. Use this only when no better match exists.

How to Test Your Redirects

Testing takes two minutes and saves headaches. Do this after you publish.

• Open an old URL in your browser. Confirm it lands on the new page.
• Try two or three URLs from the same folder.
• Check that the page name carried over when you used %1.
• Use a redirect checker tool to confirm the status is 301.

If a redirect does not fire, review the path spelling and the wildcard.

Common Wildcard Redirect Mistakes

A few small errors cause most problems. Watch for these.

Redirect Loops

A loop happens when a page redirects to itself, or to a page that points back. This traps the browser. Make sure the new path is different from the old path.

Missing Leading Slash

Every path must start with a slash. posts/(.*) will fail. /posts/(.*) will work. Check both fields.

Wrong Capture Number

If you use one wildcard, the reference is %1. A second wildcard becomes %2. Using the wrong number sends users to a broken URL.

Forgetting to Publish

Redirects do not work in the Designer or Preview. You must publish the site first. Then test on the live domain.

Best Practices for Webflow Redirects

Use these tips to keep your redirects clean and safe.

• Map your old URLs before you start, so you do not miss any.
• Use a wildcard for whole folders, and single rules for one-off pages.
• Keep the new path as close to the old one as you can.
• Avoid chains, where one redirect points to another redirect.
• Test the most important pages first, like top blog posts and service pages.
• Keep a simple list of your rules for future reference.

Wildcard Redirects and SEO

Redirects are a core part of a safe site move. A Webflow 301 redirect tells search engines the move is permanent. It passes most of the old page's ranking value to the new page.

Set your redirects before or at launch, not weeks later. Early redirects keep your rankings and your traffic steady. They also stop visitors from hitting dead links. For a full migration, pair your redirects with an updated sitemap.

Conclusion

A webflow wildcard redirect saves hours during a site move. One rule can forward a whole folder of URLs. The pattern is simple. Use (.*) in the Old Path to match any text. Use %1 in the Redirect to Path to carry that text over. Then publish and test.

Start by listing the folders that changed. Add one wildcard rule per folder. Check a few URLs on the live site. Your links and your rankings stay safe.

Planning a bigger migration or worried about lost rankings? theCSS Agency handles Webflow migrations with full redirect maps. Book a call to protect your traffic during the move.

Frequently Asked Questions

1. Does Webflow support wildcard redirects?

Yes. Webflow supports wildcard 301 redirects in Site Settings, under the Publishing tab. You use (.*) in the Old Path and %1 in the Redirect to Path.

2. What is the wildcard symbol in a Webflow redirect?

The wildcard is (.*). It matches any text in that part of the URL. Webflow saves the matched text so you can reuse it with %1.

3. How do I redirect a whole folder in Webflow?

Add a rule with the folder and a wildcard, like /blog/(.*). Set the new folder with %1, like /articles/%1. Then save and publish.

4. Do Webflow redirects pass SEO value?

Yes. Webflow redirects are 301 permanent redirects. A 301 passes most of the old page's ranking value to the new page.

5. Why is my Webflow redirect not working?

Most often the site is not published, or the path is missing a leading slash. Publish the site, check both paths, and test on the live domain.

6. Can one Webflow redirect send many URLs to one page?

Yes. Use a wildcard in the Old Path and a single new path with no %1. Every matching URL then lands on that one page.

7. How many redirects can I add in Webflow?

The limit depends on your plan. Check your plan details if you have a very large redirect list.