BEFORE YOU START: This is not an additional paid module, and its available for all of our customers, but please contact our support team first and they will enable this feature on your platform.
URL Rewrite Rules allow you to redirect users from one URL to another within your storefront. This is typically used to correct outdated links, support campaign URLs, or ensure users land on the correct page when a URL has changed.
How URL Rewrite Works
When a user visits a URL, the platform checks the incoming request against your configured rules. The request is always evaluated using http:// and port :80, regardless of whether the site is secure.
Rules are processed from top to bottom, and only the first matching rule is applied. If no rule matches, the request continues as normal.
Creating a URL Rewrite Rule
Navigate to Storefront Management → URL Rewrite Rules, then select Add new record.
You will be asked to complete the following fields.
Pattern
This defines the URL the user is arriving on. It must match the incoming request exactly and include http:// and :80.
For example:
^http://www.example.com:80/old-page/$
Rewrite Pattern
This defines where the user should be redirected. This will typically be a secure URL.
For example:
https://www.example.com/new-page
Ignore Case
This optional setting allows the rule to match regardless of letter casing.
Use Redirect Permanent
Enable this to apply a permanent (301) redirect. This is recommended for most use cases.
Enabled
The rule must be enabled to take effect.
NOTE: For secured sites, we have to redirect to https instead of http.
Example
If users are visiting:
http://www.example.com:80/claim-offer
and should instead be redirected to:
https://www.example.com/t/claim-offer
you would configure the rule using the original URL as the Pattern and the destination as the Rewrite Pattern.
Troubleshooting
Most issues with URL Rewrite Rules are caused by small formatting differences in the Pattern field.
If a redirect is not working, first check that the Pattern matches the incoming URL exactly. Even a single unintended space — at the beginning, end, or within the URL — will prevent the rule from matching.
You should also avoid relying on additional characters such as /$. While these may appear in examples or tooltips, they are not always required and can prevent the rule from working in some cases. If a rule is not triggering, use the exact URL path without adding extra characters.
If the rule still does not apply, check that it is enabled and that no other rule above it is being matched first.
It is also important to ensure that the storefront alias used in the Pattern exists. If it does not, the request may be handled before the rewrite rule is evaluated.
Finally, test changes in a fresh browser session or incognito window to avoid cached results affecting the outcome.
Best Practice
Use clear and exact URL patterns, and keep rules as simple as possible. Place more specific rules higher in the list and test each rule after saving to confirm it behaves as expected.
Summary
URL Rewrite Rules rely on exact matching. Most issues are caused by small inconsistencies such as spacing, unnecessary characters, or rule order. By keeping patterns clean and testing thoroughly, you can ensure redirects work reliably across your storefront.