// Guest access available · one URL per run
Follow up to 10 server-side HTTP responses. Review 3xx status codes, Location targets, repeated URLs, host or scheme changes, the final captured status, and measured request time.
> Target_URL
5 free checks · No signup · Free
Follow Location targets until a non-redirect response or a safety, timeout, loop, or 10-response stop condition.
Stop when a later redirect target repeats an exact URL already requested in this run.
Distinguish captured permanent, temporary, final, and error response codes without predicting indexing.
Report when an HTTP starting URL reaches an HTTPS final target; certificate and HSTS checks are separate.
Show whether the submitted and final hostnames differ in their www prefix; canonical intent is not inferred.
Sum server-side request durations for this run. It is not a visitor field metric or fixed per-hop cost.
Ways to go deeper with this site:
It traces one submitted public URL with a server-side HEAD request and falls back to a small GET request for servers that reject HEAD. It records HTTP status responses and follows Location targets for up to 10 fetched responses. It does not render HTML or execute JavaScript.
It treats 301 and 308 as permanent redirects, 302 and 307 as temporary redirects, and follows any 3xx response that supplies a valid Location target, including 303. Status choice depends on intended duration and method behavior; an observed code is evidence, not an automatic defect.
The tracer stores each exact URL it requests and stops if a later target repeats one. It also stops at 10 fetched responses, which can catch a non-repeating redirect sequence without proving an exact loop.
No. Each run traces one submitted URL. Use a crawl-based redirect mapper or a tested migration URL list when you need coverage across many internal links and old destinations.
No. It follows HTTP 3xx responses with Location headers. Because it does not render the page or execute scripts, client-side and HTML refresh behavior is outside the trace.
It is the wall-clock duration observed by WebEnture while requesting the chain, not a visitor field metric or a fixed per-hop penalty. Geography, DNS, TLS, caching, connection reuse, server load, request method, and network conditions can change the result.
Technical SEO Signals
Review crawl-captured metadata, directives, URL patterns, statuses, links, and JSON-LD presence
Redirect Mapper
Trace the entered URL and public scheme/www variants, then compare those HTTP responses with redirect and link evidence retained by the crawl
Crawl Timing
Compare crawl response-completion times across public pages
Broken Links
Report unreachable links and redirect responses found in the crawl
The checker submits a server-side HEAD request and falls back to a small GET request when the server rejects HEAD. It follows HTTP responses manually, records each URL, status code, status text, Location target, and request duration, and stops at a non-redirect response, a repeated URL, a blocked or invalid target, a timeout, or 10 fetched responses. It does not render HTML, execute JavaScript, detect meta refresh, or display complete response headers.
Permanent 301 and 308 responses are appropriate when a resource has moved permanently; 302, 303, and 307 describe temporary or method-specific behavior. Search systems combine redirects with other canonicalization signals, so this trace cannot predict indexing, PageRank transfer, or ranking changes. Use it to confirm the observed route, then compare the result with your URL mapping, internal links, canonicals, sitemaps, Search Console, server logs, and the requirements of the client making the request.
Start with inaccessible final responses, repeated URLs, invalid or missing Location headers, and important internal links that still request an avoidable chain. Do not replace a temporary redirect with a permanent one solely because the tool found a 302 or 307. Confirm purpose, destination equivalence, request methods, CDN and origin rules, caching, query-string handling, analytics, and rollback needs. After a change, repeat the trace and test representative URLs in a browser and the relevant search or monitoring tools.