Redirect type
- Permanent (301)
301 redirects are the default option. When using a 301, you're actually saying: this page has been moved permanently to X. With 301, you will move the SEO ranking of that page to the new destination. - Temporary (302)
With 302 redirects, you're actually saying: this page has been moved temporarily to X and it might be changed in the future. - Frame
With our frame option, your destination is 'iframed' on your source domain. This will show the original domain in the browser, but will load the destination via the frame. We don't recommend using this option, as SEO ranking is impacted and the user experience isn't great (the path for instance doesn't change on navigation). Note: not all destinations can be framed; the destination may block framing. Check your destination here. - Permanent (308)
308 redirects are basically the same as 301 redirects and are recommend to be used only when you have a specific use-case for them. The primary difference is that the 308 redirect guarantees that the method and the body will not be changed when the redirected request is made. See more info here. - Temporary (307)
307 redirects are basically the same as 302 redirects and are recommend to be used only when you have a specific use-case for them. The primary difference is that the 307 redirect guarantees that the method and the body will not be changed when the redirected request is made. See more info here.
Path forwarding
When path forwareding is enabled, the path is kept when redirecting to the destination.
Example:
Source: example.com
Destination: destination.com
Path forwarding: Yes
A request comes in on 'example.com/contact'. With path forwarding, this means it's redirected to 'destination.com/contact'.
You may use this with 'query string forwarding' to redirect both the path & the query string.
Query parameter forwarding
When query parameter forwarding is enabled, the query string is kept when redirecting to the destination.
Example:
Source: example.com
Destination: destination.com
Query string forwarding: Yes
A request comes in on 'example.com?page=342'. With query parameter fowarding enabled, this means it's redirected to 'destination.com?page=342'.
You may use this with 'path forwarding' to redirect both the path & the query string.
Example 2
Source: example.com
Destination: destination.com?ref=redirected
Query string forwarding: Yes
A request comes in on 'example.com?page=342'. With query parameter forwarding enabled, this means it's redirected to 'destination.com?page=342&ref=redirected'. Note that the query string of the destination and the incoming request is merged together. The incoming source parameters have a higher preference than the parameters of the destination.
Tracking
When tracking is enabled, this means that analytical data will be saved of the incoming traffic. This data is used for your redirect analytics. When disabled, only the datetime & full URL is tracked so we can keep count of the amount of hits for your account. Do note, no data is sold or used anywhere else! See our privacy policy as well.
