What is a redirect path?
A 301 or 308 generally signals a permanent move; 302 or 307 generally signals a temporary one. A single intentional redirect can be useful during migration. A chain passes through several URLs. A loop returns to a URL already visited, so there is no reachable final page.
Why trace it?
Extra hops add latency and complicate maintenance. Loops prevent visitors and crawlers from reaching content. A crawler also stops after its configured safety limit; reaching that limit does not establish where the chain would eventually end. Redirects do not automatically destroy rankings.
What SEOTera observes and cannot prove
Page Audit records whether the requested page redirects, crosses domains or downgrades from HTTPS to HTTP. Site Audit flags observed internal links through redirects, chains, loops and paths that hit its configured safety limit. The result describes this crawl and may differ for other user agents or regions.
Trace the path manually
Use browser network tools with cache disabled or a command-line request that displays each response and Location header. Record the starting URL, status, next URL and final response. Check whether a cross-domain target is an intentional migration, and whether any HTTPS page sends users to HTTP.
Check canonical, hreflang and sitemap targets
These signals generally work best when they reference the intended final URL rather than a redirecting intermediate address. Their dedicated guides own the detailed canonical, hreflang and sitemap diagnostics; a redirect finding alone does not tell you which preferred URL search engines selected.
Common causes
A migration rule can overlap with a slash or lowercase rule. Old CMS links may still point to transitional URLs. HTTP and HTTPS rules can disagree, or two domains can redirect back to each other. A chain can also accumulate as successive site moves are layered without cleanup.
1. Identify the intended final URL
Check the actual content and migration plan before editing rules. If the path crosses domains, verify ownership and whether the new domain is intentional. Preserve a stable, secure final address.
2. Remove loops and shorten paths
Fix conflicting redirect rules in the server, CDN or application. Point internal links directly to the final page where appropriate. Update canonical, hreflang and sitemap references according to their own semantics, and avoid an HTTPS-to-HTTP downgrade.
3. Follow and re-audit
Request the original and final URLs, verifying status and Location at each hop. Rerun Site Audit and inspect the affected source links. If SEOTera still reaches its safety limit, continue investigating the path rather than assuming a destination was verified.
Chain and direct destination
If A redirects to B and B redirects to C, update internal links to C when C is the intended public page. Keep an appropriate external-facing redirect from A if old bookmarks need it, but avoid making your own navigation take the detour.
A → B → C becomes internal link → CRelated SEOTera checks
These checks cover signals within this topic. An observation or warning needs context; it does not always mean a change is required.
- HTTP redirect
http-redirect-occurred - Cross-domain redirect
http-cross-domain-redirect
Sources and further reading
Related guides
Trace redirects across your site
Site Audit reports observed internal redirect links, chains, loops and paths stopped at its safety limit.