Redirect Checker

Read the results

A link can open the right page and still take an unnecessary detour. A redirect checker exposes those steps: the URL requested, the status returned and the next address in the server’s Location header.

Start with the destination. Is it the page you intended, and did it return a successful response? Then work back through the chain. A move to another hostname may be deliberate; a move from HTTPS back to HTTP deserves a closer look.

Google treats permanent and temporary redirects differently when selecting a canonical URL. A redirect is a signal, not proof that a page has been indexed. Google’s redirect guidance explains the distinction.

Fix a chain

Suppose an old article takes this route: /old-guide/ to /guide-2024/ to /guide/. If the last page is the permanent replacement, send the old URLs directly there. Update internal links too, so visitors do not need a redirect at all.

A loop is different. If page A points to B and B points back to A, the journey never ends. Check redirect plugins, server rules and CDN settings together. Conflicting HTTP-to-HTTPS or www rules are worth investigating.

Check a move

After changing a slug or domain, test the old address. Testing only the new URL can miss a broken forwarding rule. Check a few important deep pages, not just the homepage, and include query strings used in campaigns.

Keep the replacement relevant. Sending every deleted article to the homepage may resolve the address without answering what the visitor came for. Once the route is correct, review the destination’s canonical and robots signals with the SEO Checker.

Browser differences

GET requests inspect the response and a bounded portion of its body. HEAD asks for headers without the body; some servers handle it differently. If HEAD returns an unexpected error, compare GET before changing your site. MDN’s HTTP reference covers redirect behavior and request methods.

This tool follows HTTP redirects, not JavaScript navigation. It reports Refresh headers and HTML meta refresh when found, but does not follow them. It also does not bring your cookies, login session or browser’s HSTS settings. Request times come from our server and are not a page-speed score.

A stopped chain has no confirmed final destination. The report keeps the responses it received and explains whether it stopped at a loop, an unsafe address, a timeout or its hop cap. Submitted URLs and reports are not saved in this checker’s usage log or report cache; ordinary hosting logs are separate.

Publisher links

Before submitting a guest article, check that its target URL leads directly to the intended page. A clean route avoids sending readers through outdated pages, but it does not establish publisher quality or guarantee rankings.

Choose publishers below, or ask our blogger outreach team to research them. Approved guest post orders retain the dofollow placement and Google indexing guarantee specified in their confirmed terms.

Request a shortlist

Send your target page, topic and market. We will check publisher fit and confirm terms before you approve a placement.