Overview
This page reorganizes the current documentation into blocks that are easier to consult inside the product. The central recommendation stays the same: write rules that cover as many scenarios as possible and always validate the source, destination, code and priority before saving.
Why it matters
Direct impact on the website
Traffic preservation
Old URLs continue to route visitors to the right content even after changes to the site's architecture.
SEO and authority
Redirects help transfer relevance from the old page to the new one and reduce losses in organic ranking.
User experience
Removing 404 errors makes navigation more predictable and reinforces trust in the website.
Rebranding and domain changes
In migration scenarios, well-defined redirects maintain continuity and minimize operational impact.
Recommended patterns
Source with RegEx
Without trailing slash
With trailing slash
More flexible: with or without slash
Step by step in Studio CMS
Setup flow
1. Open the redirects area
In the side menu, open the Redirect Rules section.
2. Create a new rule
Click the + button in the top-right corner to add a new redirect.
3. Define the source URL
Enter the old URL that should be intercepted and, when it makes sense, use the /?$ format to cover both variants.
4. Define the destination URL
Indicate the new page the user should be sent to.
5. Choose the code and priority
The current documentation recommends using 301 as the code and 1 as the priority.
6. Save and test
After saving, validate the behavior directly in the browser to confirm that the rule responds as expected.
Checklist before publishing
Quick validation
- Confirm that the source does not conflict with other existing rules.
- Validate that the final destination is already published and accessible.
- Use 301 only when the change is permanent.
- Test variations with and without a trailing slash, especially in legacy structures.
See also
Related pages