SiteSpect offers multiple types of redirects
In addition to traditional 301/302 redirects, SiteSpect offers unique URL Rewrite functionality. It changes the path on the request, not the response. This innovative approach virtually eliminates the delay associated with standard redirects, providing a seamless and efficient user experience while preserving SEO benefits.
Redirect Type | Title | Description |
Origin | URL Rewrite | Allows a redirect to a new URL without changing the URL the user sees in the browser's address bar (must be on the same domain)* |
301 | Issues an HTTP response status code 301 (Moved Permanently) and the redirected URL shows in the browser's address bar | |
302 | Issues an HTTP response status code 302 (Moved Temporarily) and the redirected URL shows in the browser's address bar | |
Response | URL Redirect (aka Internal) | Allows a redirect to a new URL without changing the URL the user sees in the browser's address bar (must be on the same domain)* |
301 | Issues an HTTP response status code 301 (Moved Permanently) and the redirected URL shows in the browser's address bar | |
302 | Issues an HTTP response status code 302 (Moved Temporarily) and the redirected URL shows in the browser's address bar |
Origin Redirect: SiteSpect redirects on the request, before the request reaches the origin server. Use this type of redirect when your triggers do not require using a page source trigger. This type of redirect is the most performant. (Found in the menu under Origin)
Response Redirect: SiteSpect redirects on the response, after the origin server returns the page but before the page reaches the end user. Use this type of redirect when your triggers do require using a page source trigger. This type of redirect is less performant than an origin redirect but generally still a perceptibly fast option. (Found in the menu under Redirect)
* With URL Rewrites, if you want to use a completely different domain, please see Alternative Proxy (requires a system configuration setup).