A blog owner explains why visitors may be blocked from accessing their site, due to anti-crawler measures targeting old browser User-Agent strings. High-volume crawlers (often for LLM training data) frequently spoof outdated Chrome user agents, triggering blocks. The post also addresses edge cases: Inoreader and Feedly users seeing the error page due to those services fetching feeds with old User-Agent headers, Vivaldi users needing to adjust User-Agent Brand Masking settings, and archive.today users being indistinguishable from malicious crawlers due to their use of old Chrome UAs and suspicious IP practices.
