My redirect isn't working
If a redirect you have created is not behaving as expected, work through the following checks.
Check the redirect is enabled
Open the redirect in Retour and confirm it is enabled. A disabled redirect will not fire even if the source URL is an exact match.
Check the source URL is correct
The source URL must match the URL being requested exactly. Confirm that your source URL is entered as a path without the domain- for example /old-page not https://yoursite.com/old-page. Also check for trailing slashes: /old-page and /old-page/ are treated as different URLs.
Check for a query string mismatch
If the URL being requested includes a query string- for example /old-page?ref=newsletter- and your redirect is set to match /old-page, there may be a mismatch depending on how the plugin is configured. Try visiting the URL without the query string to see if the redirect fires correctly. Contact your site administrator if query string handling needs to be adjusted.
Clear your browser cache
Browsers cache redirect responses aggressively. If you have previously visited the old URL and received a response, your browser may be serving that cached response rather than making a fresh request. Try the URL in a private or incognito browser window to bypass the cache.
Check whether another redirect is taking priority
If multiple redirects could match the same URL, the one with the highest priority setting will take effect. If an unexpected redirect is firing, check whether another rule is overriding yours. See the article on redirect priority for more detail.
Check the redirect is enabled
Open the redirect in Retour and confirm it is enabled. A disabled redirect will not fire even if the source URL is an exact match.
Check the source URL is correct
The source URL must match the URL being requested exactly. Confirm that your source URL is entered as a path without the domain- for example /old-page not https://yoursite.com/old-page. Also check for trailing slashes: /old-page and /old-page/ are treated as different URLs.
Check for a query string mismatch
If the URL being requested includes a query string- for example /old-page?ref=newsletter- and your redirect is set to match /old-page, there may be a mismatch depending on how the plugin is configured. Try visiting the URL without the query string to see if the redirect fires correctly. Contact your site administrator if query string handling needs to be adjusted.
Clear your browser cache
Browsers cache redirect responses aggressively. If you have previously visited the old URL and received a response, your browser may be serving that cached response rather than making a fresh request. Try the URL in a private or incognito browser window to bypass the cache.
Check whether another redirect is taking priority
If multiple redirects could match the same URL, the one with the highest priority setting will take effect. If an unexpected redirect is firing, check whether another rule is overriding yours. See the article on redirect priority for more detail.