Redirect Chain & Variant Reviewer

After the website crawl, it traces the entered URL plus public HTTP/HTTPS and www/apex variants. Each trace follows server-side HTTP redirects for up to 10 fetched responses. It also reviews any 3xx statuses, Location targets, and matching links that the crawl happened to retain.

The crawler normally follows a redirect and records the final page, so the intermediate status and Location target can disappear from crawl data. The live probe requests selected starting variants with HEAD and fallback GET requests, but it covers only those variants and can differ from a browser or search crawler.

No. Permanent redirects suit moves intended to remain in place; temporary redirects suit temporary behavior, and method handling also matters. Confirm routing intent, destination equivalence, caches, request methods, and rollback needs before changing a status.

Not necessarily. The report shows which public variants responded and where they ended, but DNS, product architecture, subdomain ownership, and security policy determine which variants should exist. A missing variant is evidence to review, not an automatic defect.

An initial guest website scan is available without signing up. The live variant probe also uses a Quick Tool allowance. A Free account includes 5 scans and 15 Quick Tool uses per month; Pro and Agency plans include unlimited scans and Quick Tool uses.

No. It is a fixed heuristic based on loops, chain length, temporary statuses, final-target differences, failed variants, and HTTP-to-HTTPS patterns. Use the HTTP evidence with your migration map, server logs, Search Console, canonicals, sitemaps, browser tests, and performance measurements.