Use Cases



We're excited to announce the release of wildcard redirects. Users can now redirect whole paths such as /about/*/ instead of making redirects for every single one of its immediate subfolders. This allows for more flexibility and power when creating redirects as they're handled dynamically.

What are wildcard redirects?

Wildcard redirects allow for an asterisk (*) to stand-in for a subfolder value. Instead of using a static path to create the redirect, WebEngine will be able to dynamically handle redirects.


  • Redirect whole paths. For example, creating a redirect from /about/*/ will redirect /about/ and all of its immediate subfolders.

  • Replace a subdirectory with a wildcard in the middle of a path. For example, creating a redirect from /about/*/team/ will redirect every a single path part between /about/ and /team/.

  • Replace multiple paths. Asterisks can be used to replace multiple paths such as /about////team-members//.

wildcard redirect example gif

How does it work?

WebEngine will attempt to render a URL but if that item is not found, WebEngine looks for a redirect for the path you're trying to render. If it finds a redirect, it will then attempt render the corresponding target. If the From path is a wildcard redirect, WebEngine looks for the asterisk wildcard value and dynamically forms paths to the target. In the example below the From path is /about/*/ so everytime a user tries to go to /about/ or any of its immediate subfolders (eg. in /about/team//team/ is an immediate subfolder of /about/) will redirect. Click on the image below to expand it.


Get more details from our wildcard redirect documentation at Zesty.org.

Try wildcard redirects now

Login to Zesty.io and create some wildcard redirects!

By Kim Koga

Experienced writer, editor, and solutions engineer. I love to write instructional documentation to help customers achieve their dreams. Github: https://github.com/kakoga

Related Articles