Redirecciona códigos de & estado

Comprobador de redireccións

Follow any URL's redirect chain hop by hop, and catch the ones costing you rankings.

Segue a cadea completa Sen rexistro

Seguindo a cadea de redireccións...

A solicitar cada salto á súa vez e ler o seu código de estado.

Que aspecto ten unha redirección saudable. One hop, a 301 or 308 for a permanent move, and a 200 at the end, with no chains, no loops, no bouncing between HTTP and HTTPS or www and non-www. Each extra hop sheds a little link equity and slows the page, so point the source straight at the final URL.

Como rastrexar a cadea de redirección dun URL

Catro pasos desde un URL a unha redirección limpa e de salto único.

1

Apegar o URL

Enter the full URL you want to test, including https, for example https://example.com/old-page. This is the starting point of the trace.

2

Rastrexar as redireccións

Prema Rastrexar as redireccións e seguiremos cada salto como o faría un navegador ou rastreador, rexistrando cada URL e o estado HTTP exacto que devolveu.

3

Ler a cadea de saltos

See each step colour-coded by status (green for a permanent 301 or 308, amber for a temporary 302, 303 or 307, red for a 4xx or 5xx error), with the final destination at the end.

4

Actuar sobre os avisos

Review the flagged issues (long chains, temporary redirects for permanent moves, loops, mixed HTTP and HTTPS) and fix them so the source points straight at the final URL in one hop.

Redirixir as preguntas

A 301 is a permanent redirect: it tells search engines the page has moved for good, passes the ranking signals along to the new URL, and the target replaces the source in the index. A 302 (and its stricter siblings 303 and 307) is temporary: it says "the page is briefly somewhere else, keep the original indexed." The practical trap is using a 302 for a move that is actually permanent, so you keep the old URL in the index and you don't cleanly consolidate ranking signals onto the new one. For a permanent move, always use a 301 (or 308, its method-preserving equivalent).
Si, un pouco, e suma. Cada salto extra é outra petición que o navegador e o rastreador teñen que facer antes de chegar ao contido real, polo que a páxina parece máis lenta e cada redirección pode perder unha pequena cantidade de equidade de ligazón. Google xeralmente segue varios saltos, pero non ten que seguir para sempre, e as cadeas longas desperdician o orzamento de rastreo nos sitios grandes. A solución é sinxela: mantéñao nun só salto apuntando o URL de orixe directamente ao destino final en vez de a outra redirección. Se a páxina A redirixe a B redirixe a C, actualice A para que apunte directamente a C.
A 404 means "not found": the page is missing, but it might come back, so search engines keep checking for a while. A 410 means "gone": you removed it on purpose and it isn't returning. When you deliberately retire a page and have nothing to redirect it to, a 410 tells crawlers to drop it from the index faster and more cleanly than a 404, and it stops them re-requesting a URL you never intend to restore. Use a 301 when there is a good replacement to send visitors to; use a 410 when the page is genuinely gone and a redirect would be misleading.
A redirect loop happens when URLs send visitors back and forth without ever landing on a real page: A redirects to B and B redirects back to A, so the browser gives up with a "too many redirects" error. Find the cycle by tracing the chain (this tool stops and flags it), then break it: decide on one canonical destination and make everything point there, or turn one of the URLs into a real 200 page. Common causes are conflicting rules, such as one for HTTP to HTTPS and another for www that disagree, or a trailing-slash rule fighting a CMS redirect. Resolve the conflict so a single, consistent rule wins.

Queres ver as túas redireccións a escala?

The free checker traces one URL at a time and is rate-limited. Auditing thousands of URLs for broken chains, loops and temporary redirects that should be permanent, and catching new ones before they cost you rankings, is part of the managed service.

✓ Ferramenta libre: un URL á vez Auditorías de todo o sitio: plans xestionados

Mapas de redirección masivos, comprobacións programadas tras unha migración e alertas cando un 301 limpo se converte silenciosamente nunha cadea ou nun 404. Consulte os plans na páxina de prezos.

Ver os plans xestionados →
API do desenvolvente

Úsalo por programación

Every tool is available through one authenticated REST API on the Pro and API plans. Wire it into your CI, CMS, or dashboards.

curl -X POST https://seo.bike/api/v1/redirect-check \ -H "Authorization: Bearer sk_live_yourkey" \ -H "Content-Type: application/json" \ -d '{"url": "http://example.com/old-page"}'
200 OK
{ "ok": true, "result": { ... } }
Obter unha chave API → Medido, prezo por chamada. Nivel gratuíto para a ferramenta interactiva de riba.
Check every page of your site, not one at a time
Pro connects Google Search Console, fetches every page Google skipped, every broken page and every page that ranks low, and writes what to fix on each one.
See how Pro works