Check Redirect Chain

A redirect chain occurs when URL A redirects to URL B, URL B redirects to URL C, and so on. Each redirect adds latency to page loading, and search engine crawlers have a limited crawl budget. Ideally, an old URL should redirect directly to the final destination.

200 (OK). Indicates a successful request and successful retrieval of data, if any was present in the header or body of the response

200 (OK). Indicates a successful request and successful retrieval of data, if any was present in the header or body of the response

301 (Moved Permanently). This status code tells the user that a permanent redirect to another page or site has occurred

302 (Found/Moved Temporarily). The requested URI has been temporarily moved to a new address. Taken from the Location field

403 (Forbidden). The server understood the request but refuses to fulfill it. Access to the resource is denied in this case

404 (Not Found). The server received the client's request but could not find a document matching it

500 (Internal Server Error). This is any error on the server side, rather than the client side

502 (Bad Gateway). The proxy or gateway server received an invalid response from the backend

504 (Gateway Timeout). The proxy or gateway server did not receive a response from the backend within the allotted time

0 (No Response). Not an actual server response code. Indicates that a connection was never established or no response was received at all. Usually caused by network-level blocking (e.g. DPI), the site being unreachable, a dropped connection, or a request timeout

Full list of HTTP status codes

The tool only changes the User-Agent header. A real search bot differs from our request in other ways, so the site's response may not match:

• IP address. Many sites and security services (Cloudflare, WAFs) verify bots by IP ranges and reverse DNS. A request from our server won't pass this check and may get a different response or be blocked.
• Request type. We only check response headers (a HEAD request) without downloading the page. Some servers respond to HEAD differently than to GET.
• JavaScript. The tool doesn't execute scripts, so redirects done via JavaScript or meta refresh won't be detected. Search bots can process them.
• Other headers and cookies. Language (Accept-Language), cookies, region and request frequency can also affect a redirect.

If the result matters for SEO, also check Google Search Console and Yandex Webmaster reports to see what the bot actually received.

A redirect loop occurs when URLs redirect to each other in a never-ending cycle. The tool will stop after the 10th step. Common causes include conflicting HTTP-to-HTTPS and www/non-www redirect rules, caching plugins, or a CDN redirecting requests in the opposite direction. Check your .htaccess/nginx rules and your CDN's SSL settings.

Ideally, just one. Google recommends keeping redirects to a minimum, although it can follow multiple consecutive redirects. However, long redirect chains should be avoided.

The redirect may be performed via JavaScript or meta http-equiv="refresh", or the website may respond differently depending on cookies or the user's region. The tool only checks HTTP Location headers.

Some websites redirect mobile users to a separate version, send bots to a different page, or show a fallback page to older browsers. Changing the User-Agent helps you detect these differences.

301 and 308 are permanent redirects. Search engines transfer ranking signals to the new URL and may eventually replace the old URL in search results. 302 and 307 are temporary redirects, so the old URL may remain in the index. The difference between 301 and 308 (and between 302 and 307) lies in how they handle the request method. 307 and 308 guarantee that the method (such as POST) is preserved, whereas 301 and 302 may change it to GET in some clients.

Enter a URL starting with http:// and/or www. The table should show a single 301 redirect to the preferred URL. If there are two or more steps, consider consolidating the redirect rules.