Saltar al contenido

Comprobador de redirecciones

Esta herramienta aún no funciona

La interfaz está construida y el texto ya está publicado, pero la herramienta en sí llega en una entrega posterior. No hay nada roto: simplemente todavía no hay nada que ejecutar aquí.

What this tool does

A redirect checker follows a URL the way a browser and a crawler do: it sends a request, reads the status code, and if the server answers with a redirect it follows the Location header to the next address. It repeats that until it reaches a page that answers 200, or until the chain loops or grows too long. What comes back is the whole path, not just the destination.

That path is where the problems hide. A single 301 costs almost nothing. Four of them stacked on top of each other cost crawl budget on every visit, delay the first byte for real users, and are much harder to notice — because the page still loads and still looks correct.

How to use it

Paste one URL per line and run the check. Every line is followed independently, so a broken address in the middle does not stop the rest, and the report names the line that failed instead of failing the whole batch.

  • Use the exact URL you are worried about, including http or https and any trailing slash. Those differences are usually what creates the redirect in the first place.
  • Check both the www and non-www form of a domain. They should end at the same address, and exactly one of the two should be the one that redirects.
  • Run the check again after any change to a redirect rule. Rules interact, and a new one often lands in front of an old one.

Reading the result

A 301 says the move is permanent and search engines should transfer the old address to the new one. A 302 says the move is temporary and the old address should be kept. Using 302 for a permanent move is the most common mistake this tool surfaces, and it quietly holds a page back for as long as it stays in place.

A chain of two is worth fixing when it is easy. A chain of three or more is worth fixing regardless: point the first address straight at the final one and delete the steps in between.

What it does not do

It reads the response the server gives to a plain request. It does not run JavaScript, so a redirect performed in the browser after the page loads will not appear here. That kind of redirect is invisible to this check by design, and is worth avoiding for the same reason it is invisible.