LeaderboardEvery site, rankedFree toolsChecks, no sign-upAgentsYour agent fixes itDocsThe API and MCP

Redirect checker

Follow an address hop by hop: each status code and where it points, chains, http to https and www moves, loops, and whether it ends at a page.

Every version of the address, one hopExample
  • http://example.com301
  • http://www.example.com301
  • https://example.com301
The one addresshttps://www.example.com/200
Not this: a chain of two hops where one would do

http://example.com301https://example.com301https://www.example.com/

Each version moves for good to the address chosen, in one step. Links and the sitemap name the final address, so they take no hop at all.

What does it check?

Rules from the rulebook, and how many of the sites mttr has read miss each.

  1. Settle on one addressRedirect http, https, www, and the bare domain to one address, so the site is not indexed as several.
    35%of sites miss it
  2. Link straight to the final addressPoint links and the sitemap at the final address, not at one that redirects.
    51%of sites miss it

Questions

What is the difference between a 301 and a 302?

A 301 says the page has moved for good, and search engines move its standing to the new address. A 302 says the move is for now.

How many redirects is too many?

One. Each hop costs time, and crawlers stop following after a few. Link straight to the final address.

Should http and www go to one address?

Yes. Every version of the address should take one hop to the one you chose.

The whole site

One page is one part. A read checks every page against the whole rulebook and says what to fix first.

Read a whole site