Technical SEO
Crawl, render, index, migrate
- Access
Stage 1: Access
Redirect chain checker
Checks up to 50 URLs or old-to-new pairs for hop count, each status code, loops and mismatched targets, for migrations and link clean-ups.
Free to use. No login, nothing stored.
What it checks
Access- Hop count and the status of each hop
- Loops and chains longer than one hop
- Mixed HTTP and HTTPS hops
- Final target compared with the expected new URL
- CSV export of the results
Method question for this stage: Can crawlers reach and render every key page?
Run the check
Results
No check run yet
- Info
One table row per URL: hops, every status in the chain, the final status and the final URL
Flags per row: loop, chain longer than one hop, HTTP and HTTPS mixed, final error, mismatch against the expected URL, temporary redirect. Summary rows below the table count each flag and link the rule.
A clean redirect moves visitors; whether Google has moved its signals shows in Search Console over weeks. The Technical SEO service covers the migration itself.
How we check
The rules this tool tests, and where they come from
A result is a check against a published rule, not a prediction. Every row shows its working.
Rules and sources
Links go to the operator's or standards body's own documentation. We do not link to third-party summaries.
Read more
Next step
Fix what it finds
This check belongs to the Access stage of the Crawl-to-Citation Method. The service below covers the fix; the Diagnostic ranks it against everything else.
Most engagements start with the Search Visibility Diagnostic ($2,500).
It covers all six method stages, so what this tool finds is ranked against everything else before you commit to any work.
Book the diagnosticRedirect questions
What a chain costs, what a mismatch is, and what a temporary status means.
Still have questions? Book a callWhy does a chain of two or three hops matter if it still arrives?
Google documents following up to ten redirect hops, so a short chain is followed. Each hop still costs a round trip for every visitor and crawler, and each one is a rule someone can break later. After a site move the usual cause is stacking: HTTP to HTTPS, then non-www to www, then old path to new path. Collapse them so the old URL answers with one redirect straight to the final URL.
What counts as a mismatch against the expected new URL?
The final URL after all hops is compared with the one you typed after the arrow. Host case and a trailing slash are ignored, so example.com/page and example.com/page/ match. A different path, a different host, a query string that appears or disappears, or a different scheme is reported as a Warning with both URLs shown. A line with no arrow is checked without an expectation.
Does a 302 or 307 hurt a migration?
Google states that it treats a long-standing 302 as permanent, so a temporary status does not block the move. It does leave the intent ambiguous, and some other systems take it literally and keep the old URL. For a permanent change use 301 or 308. The tool reports temporary statuses as Info so you can decide, not as an error.
Last reviewed