Permanent or temporary
Codes 301 and 308 indicate a permanent redirect, while 302 and 307 indicate a temporary redirect. Compare the code in the report with how this URL is expected to work.
Loading page
This may take a few seconds.
Loading page
This may take a few seconds.
If reChecker is not working correctly, describe the problem and the page where it happened. Leave an email or phone number; we will reply after checking.
301/302 redirect chain
About the check
A redirect sends a visitor from one URL to another. The check tracks server-side HTTP redirects and shows the responses, headers, and destination URLs.
Codes 301 and 308 indicate a permanent redirect, while 302 and 307 indicate a temporary redirect. Compare the code in the report with how this URL is expected to work.
Intermediate URLs help identify extra steps and duplicate URLs. For example, 301 → 301 → 200 means two redirects before a successful response. This is an example for learning purposes, not a result from a website check.
Make sure the redirect chain ends at the intended URL and the page is accessible. A 200 response alone doesn't confirm that visitors reached relevant content.
After the check
Changes are made to website or server settings. reChecker shows how they perform and helps you verify updates.
A redirect can be configured in .htaccess on Apache, in the Nginx configuration, in a CMS, or in an application handler. Check these settings, starting with the first unexpected redirect.
If multiple URLs lead to the same page, set up a direct redirect where that fits your site’s logic. Check that another rule doesn’t send visitors back.
After making a fix, rerun the check for the original URL. Compare HTTP and HTTPS, and the www and non-www addresses. If the redirect wasn’t followed or a request failure is shown instead of an HTTP status code, the response from the next URL hasn’t been confirmed.
A redirect automatically sends a visitor or bot from one URL to another. A permanent redirect uses code 301 or 308; a temporary one uses 302 or 307. For example, after a page moves, a redirect sends visitors from the old address to the new one.
The public report shows the check date, overall score, errors found, and measured values.
We describe data sources, crawler limitations, counting rules, and cases that require a manual review.
We don't publish anonymous quotes or ratings without a verifiable original source. Case studies will be published only with the owners' consent.
Get help understanding the report, fixing technical issues or setting up regular monitoring. We will discuss the scope and cost before starting.