ebay.com
Why picked: ClaudeBot-only vendetta — 1 of 4 eBay properties that explicitly block Anthropic
v3 rendered verdict: mixed: 0/6 bot UAs render content

ebay.de
Why picked: ClaudeBot-only block — same pattern as ebay.com, separate region
v3 rendered verdict: mixed: 0/6 bot UAs render content

kleinanzeigen.de
Why picked: ClaudeBot-only block — also eBay-owned, confirms the org-wide policy
v3 rendered verdict: mixed: 0/6 bot UAs render content

nike.com
Why picked: ClaudeBot-only block — independent of eBay; pure brand-level Anthropic policy
v3 rendered verdict: Edge block holds even with full Chromium — WAF rejects on UA at every layer







canadiantire.ca
Why picked: ClaudeBot-only block AND 5.9× more bytes to other AI bots than to real Chrome
v3 rendered verdict: mixed: 0/6 bot UAs render content

amazon.co.uk
Why picked: Real Chrome gets 30 KB; Googlebot/Bingbot get 900 KB — textbook dynamic rendering
v3 rendered verdict: v2 said blocked but real Chromium with bot UA passes — block is at HTTP/CDN layer only







coupang.com
Why picked: 5.3× more content to search bots than to real users
v3 rendered verdict: Chrome itself failed to render — IP-walled even for full browsers







uniqlo.com
Why picked: Googlebot gets 3× the Chrome content
v3 rendered verdict: mixed: 1/6 bot UAs render content


shopping.yahoo.co.jp
Why picked: 7-8× more to bots — Japanese pre-render-for-bots pattern
v3 rendered verdict: Chrome itself failed to render — IP-walled even for full browsers







amazon.com
Why picked: HTTP-202 IP-walls our datacenter regardless of UA — does a real browser change anything?
v3 rendered verdict: v2 said blocked but real Chromium with bot UA passes — block is at HTTP/CDN layer only







ikea.com
Why picked: Blocks all 4 declared AI bots at edge — major retailer with clear anti-AI stance
v3 rendered verdict: Chrome itself failed to render — IP-walled even for full browsers







costco.com
Why picked: Blocks all 4 declared AI bots — see if it's UA-layer or IP-layer
v3 rendered verdict: Chrome itself failed to render — IP-walled even for full browsers
kogan.com
Why picked: Unique pattern — only GPTBot allowed, blocks the other 3
v3 rendered verdict: Chrome itself failed to render — IP-walled even for full browsers







walmart.com
Why picked: AI-ready control — should serve identical content to all UAs
v3 rendered verdict: Full content parity — same rendered page to every UA







samsung.com
Why picked: AI-ready control — pure SSR-for-everyone
v3 rendered verdict: Bot UAs got ~79% of the Chrome content — slight UA discrimination






