Playbook: catch redirect chains crawlers suffer through

Playbook: catch redirect chains crawlers suffer through
Logs show the hops Search Console summarizes away.
→ Google's redirect-handling doc — Googlebot follows up to ~10 hops, but each wastes budget. Takeaway: any 301→301→200 in logs is fixable to a single hop.
→ awk for 3xx-by-URL — filter $9 ~ /^3/ and Googlebot, count per target. Takeaway: high-frequency 302s are often a config bug, not intent.
★ Pick of the week — Barry Adams' "302 audit from logs" — temporary redirects that have lived for months. Takeaway: grep for 302 on canonical URLs; those should almost always be 301.
→ curl -IL — manually trace the chain a log row implies. Takeaway: confirm the full path before you blame the wrong rule.
Logs tell you which redirects crawlers hit often — fix those first, not the prettiest ones.