Redirect Rule
Redirect Smart, No Code Required.
The Redirect Rules component enables you to define redirection logic, including permanent or temporary redirects, directly within your content layer. Whether you’re restructuring your site, fixing broken links, or launching a new section, you can easily manage URL redirects without touching server configuration files.
Once deployed, these rules are automatically applied, enhancing navigation, preserving SEO, and creating a seamless experience for both users and search engines.

Effortless Redirect Management
No Developer Dependency.
Create redirects directly in your content UI.Full URL Flexibility.
Supports patterns, wildcards, and slugs.SEO-Friendly Handling.
Avoid broken links and improve crawlability.
Powerful and Scalable
Live immediately after deployment.
No external systems or manual syncs required.Granular Status Control.
Choose 301, 302, 307, 308, and more.Use dynamic segments and splats.
Perfect for bulk content migrations or cleanup.
Use Cases
Redirects are crucial for ensuring that users and search engines reach the correct destination, even when URLs change. With Vertex Forge’s Redirect Rules, you have complete control over your URL mappings through content, making it easy to:
Set up 301 permanent redirects after renaming or moving a page
Apply temporary 302/307 redirects for testing or campaign landing pages
Use wildcards or slugs to redirect entire folders or dynamic routes (e.g., /blog/:year/:slug)
Resolve 404 errors with intelligent fallbacks
Proxy or remap routes internally with a status code 200
Whether you’re launching new sections or maintaining legacy links, these rules ensure a smooth user experience and maintain your SEO integrity.
Configuration Options & Features
Redirect Rules provide fast, flexible, and code-free redirection control, directly within your content system. With full support for patterns, wildcards, and status codes, it’s the easiest way to ensure your users land exactly where they should.
Whether you’re migrating content, cleaning up URLs, or fixing broken links, Vertex Forge puts the power of redirects in your hands.
Simple. Flexible. SEO-safe.
Redirects are finally done right.
Source
The original URL or pattern you want to redirect from. This can be:
Static: /old-page
Wildcard: /blog/*
Dynamic segments: /blog/:year/:month/:slug
This defines which incoming requests should trigger the redirect.
Destination
The target URL you want to redirect to. This can also include dynamic or wildcard segments that match the source.
Examples:
/new-page
/news/:year/:month/:slug
/
Wildcard support and :splat variables allow full flexibility.
Code
Select the appropriate code based on your use case, SEO objectives, and anticipated user experience.
301 – Moved Permanently
Best for SEO as it informs search engines that the URL has been permanently changed.
302 – Found / Temporary
Used for temporary changes
303 – See Other
Typically for redirecting after form submissions
307 – Temporary Redirect
Keeps request method (e.g., POST); safer than 302 in many cases
308 – Permanent Redirect
Same as 301 but retains the method and is recommended for APIs or forms
200 – Okay / Proxy
Used to serve another route’s content at a different path without redirection