AnalyseSpider
ENDE
A URL uses the protected live fetchLive results may be cached for one hourPasted responses stay in this browserRedirect analysis guide
Enter a URL or paste captured responsesThe tool chooses the right mode
Start with a URL or an example

You do not need to collect HTTP headers yourself. Enter a domain for a live check, or use one of these examples to see how the result works.

A single URL uses the same protected crawler gateway as the main check. Pasted blocks are analysed locally; each needs a URL: line and an HTTP status line.

Enter a URL or paste captured responses.

One chain, several separate decisions

If you only have a URL: paste it into the field above. AnalyseSpider follows at most three public HTTP redirects through the protected gateway and builds the response blocks for you.

If you already have headers: paste each observed response block. That mode makes no network request and is useful for private test environments or a response captured with browser developer tools or curl.

A status and Location field establish an observed hop. They do not establish that the destination is indexable, canonical, live in every request context, or equivalent to the source page.

Apply the redirect-chain workflow

What the JSON contains

The export contains normalised request URLs, statuses, Location fields, resolved destinations, findings, unknowns, and an analysis timestamp. It excludes the raw pasted block.