Redirect type
- Permanent (301)
301 redirects are the default option and the right choice for permanent domain moves, site migrations, and URL consolidation. When using a 301, you're telling browsers and search engines: this page has moved permanently to X. The SEO ranking of the original page transfers to the new destination. - Temporary (302)
With 302 redirects, you're saying: this page has been moved temporarily to X and it might change in the future. Use 302 for seasonal campaigns, A/B tests, or maintenance pages where you plan to restore the original URL. Not sure which one to pick? Read our comparison of 301 vs 302 redirects. - Frame
With our frame option, your destination is 'iframed' on your source domain. The original domain stays in the browser address bar, but the destination loads inside the frame. We don't recommend this option: search engines can't properly index framed content, the URL path doesn't update on navigation, and many destinations block framing entirely. Check whether your destination supports framing here. The frame redirect type is available from the Basic plan and up. - Meta refresh
With the meta refresh option, your visitors will be redirected with a typical <meta> with a zero-second timeout. This can be useful if you want to redirect visitors but do not want to use the 301/302 redirects for SEO reasons. The meta refresh redirect type is available from the Basic plan and up. - Permanent (308)
308 redirects are basically the same as 301 redirects and are recommended to be used only when you have a specific use-case for them. The primary difference is that the 308 redirect guarantees that the HTTP method and request body will not be changed when the redirected request is made. This matters for POST or PUT requests in API workflows. See more info here. - Temporary (307)
307 redirects are basically the same as 302 redirects and are recommended to be used only when you have a specific use-case for them. The primary difference is that the 307 redirect guarantees that the HTTP method and request body will not be changed when the redirected request is made. See more info here.
Path forwarding
When path forwarding is enabled, the path is kept when redirecting to the destination. This is especially useful during a domain migration, where you want every page on the old domain to land on the matching page at the new domain.
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 forwarding 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, analytical data is saved for all incoming traffic. This data powers your redirect analytics, where you can see hit counts, referrers, and geographic data. When tracking is disabled, only the datetime and full URL are recorded so we can keep count of the amount of hits for your account. No data is sold or used anywhere else. See our privacy policy for details.
