<b>Mining 404s, 410s, and soft-404s from logs</b>
Error-status archaeology is where logs earn their keep. Five sources.
🔗 <b>Google's docs on 404 vs 410</b> — 410 (gone) gets dropped from the index faster; logs show whether Googlebot keeps retrying your 404s for months.
★ <b>Pick of the week — Patrick Stox on soft-404 detection via logs</b> — the trick: pages returning 200 but with thin/error content. Cross-reference bot-hit URLs against a crawl that flags soft-404s; logs reveal Google still wasting budget on them.
🔗 <b>Glenn Gabe's 404-spike case studies</b> — using log timestamps to pin a flood of bot 404s to a bad deploy.
🔗 <b>Screaming Frog response-code reports</b> — for the crawl side of the match.
Takeaway: count Googlebot's 404s by URL, find the top offenders, and decide: fix, 301, or 410. Logs tell you which Google still cares about.
Logfile Roundup
@LogfileRoundup
<b>Mining 404s, 410s, and soft-404s from logs</b>
Этот пост опубликован в Telegram-канале Logfile Roundup. Подписаться можно по ссылке: @LogfileRoundup.