v3 · What do AI bots actually see when they render?

Of 15 sites where v2 found UA-discrimination signals, 1 blocked us even with a full Chromium pretending to be the bot (so the block runs at the WAF/edge), 2 let the same Chromium through (meaning v2's HTTP block was only at the CDN-rule layer and a JS-rendering bot would bypass it), 1 served bot UAs noticeably more content than real Chrome even after JS execution (still doing dynamic rendering in 2026), and 1 served the same rendered page to everyone.

Generated 2026-05-18 23:08 UTC · headless Chromium (Playwright) for 15 sites × 7 UAs · sibling of the v2 HTTP-only audit.

v2 was a pure HTTP probe — it did not execute JavaScript. v3 launches a real Chromium for each (site, UA) pair, waits for the page to settle, and captures the post-JS DOM and a screenshot. This separates three failure modes that v2 conflates: (a) the WAF/edge rejects the UA → 4xx in v3 too; (b) the CDN serves a thin shell HTML to bot UAs but the JS bundle is identical → v2 said "blocked" but a real browser renders the page anyway; (c) the application discriminates after rendering → both v2 and v3 show divergent content.

ebay.com

Why picked: ClaudeBot-only vendetta — 1 of 4 eBay properties that explicitly block Anthropic

v2 HTTP-only said: ai_blocked (AI avg 3.8/5), blocks claudebot

v3 rendered verdict: mixed: 0/6 bot UAs render content

Chrome desktop
chrome_desktop
HTTP 200
title: Electronics, Cars, Fashion, Collectibles & More | eBay
text: 5,878 chars
JSON-LD:
Googlebot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.com/ Call log: - navigating to "https://www.ebay.com/", w
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Bingbot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.com/ Call log: - navigating to "https://www.ebay.com/", w
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Applebot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.com/ Call log: - navigating to "https://www.ebay.com/", w
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
ChatGPT-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.com/ Call log: - navigating to "https://www.ebay.com/", w
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Claude-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.com/ Call log: - navigating to "https://www.ebay.com/", w
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Perplexity-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.com/ Call log: - navigating to "https://www.ebay.com/", w
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:

ebay.de

Why picked: ClaudeBot-only block — same pattern as ebay.com, separate region

v2 HTTP-only said: ai_blocked (AI avg 2.2/5), blocks claudebot

v3 rendered verdict: mixed: 0/6 bot UAs render content

Chrome desktop
chrome_desktop
HTTP 200
title: eBay.de | Elektronik, Autos, Mode, Sammlerstücke, Möbel und mehr Online-Shopping
text: 7,574 chars
JSON-LD:
Googlebot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.de/ Call log: - navigating to "https://www.ebay.de/", wai
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Bingbot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.de/ Call log: - navigating to "https://www.ebay.de/", wai
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Applebot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.de/ Call log: - navigating to "https://www.ebay.de/", wai
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
ChatGPT-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.de/ Call log: - navigating to "https://www.ebay.de/", wai
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Claude-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.de/ Call log: - navigating to "https://www.ebay.de/", wai
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Perplexity-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.ebay.de/ Call log: - navigating to "https://www.ebay.de/", wai
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:

kleinanzeigen.de

Why picked: ClaudeBot-only block — also eBay-owned, confirms the org-wide policy

v2 HTTP-only said: ai_blocked (AI avg 3.2/5), blocks claudebot

v3 rendered verdict: mixed: 0/6 bot UAs render content

Chrome desktop
chrome_desktop
HTTP 200
title: Kleinanzeigen – früher eBay Kleinanzeigen. Anzeigen gratis inserieren mit Kleina
text: 8,146 chars
JSON-LD: WebSite
Googlebot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.kleinanzeigen.de/ Call log: - navigating to "https://www.klein
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Bingbot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.kleinanzeigen.de/ Call log: - navigating to "https://www.klein
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Applebot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.kleinanzeigen.de/ Call log: - navigating to "https://www.klein
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
ChatGPT-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.kleinanzeigen.de/ Call log: - navigating to "https://www.klein
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Claude-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.kleinanzeigen.de/ Call log: - navigating to "https://www.klein
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Perplexity-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.kleinanzeigen.de/ Call log: - navigating to "https://www.klein
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:

nike.com

Why picked: ClaudeBot-only block — independent of eBay; pure brand-level Anthropic policy

v2 HTTP-only said: ai_blocked (AI avg 3.0/5), blocks claudebot

v3 rendered verdict: Edge block holds even with full Chromium — WAF rejects on UA at every layer

Chrome desktop
chrome_desktop
HTTP 200
title: Nike. Just Do It. Nike FI
text: 3,105 chars
JSON-LD: WebPage
Googlebot
googlebot
HTTP 403
title: Access Denied
text: 192 chars jaccard 1% vs Chrome 6% · SHA
JSON-LD:
Bingbot
bingbot
HTTP 403
title: Access Denied
text: 192 chars jaccard 1% vs Chrome 6% · SHA
JSON-LD:
Applebot
applebot
HTTP 403
title: Access Denied
text: 192 chars jaccard 1% vs Chrome 6% · SHA
JSON-LD:
ChatGPT-User
chatgpt_user
HTTP 403
title: Access Denied
text: 192 chars jaccard 1% vs Chrome 6% · SHA
JSON-LD:
Claude-User
claude_user
HTTP 403
title: Access Denied
text: 192 chars jaccard 1% vs Chrome 6% · SHA
JSON-LD:
Perplexity-User
perplexity_user
HTTP 403
title: Access Denied
text: 192 chars jaccard 1% vs Chrome 6% · SHA
JSON-LD:

canadiantire.ca

Why picked: ClaudeBot-only block AND 5.9× more bytes to other AI bots than to real Chrome

v2 HTTP-only said: ai_blocked (AI avg 3.8/5), blocks claudebot

v3 rendered verdict: mixed: 0/6 bot UAs render content

Chrome desktop
chrome_desktop
HTTP 200
title: Shop Canada’s Top Department Store Online & at 500+ Locations | Canadian Tire
text: 33,847 chars
JSON-LD: Action, ContactPoint, Corporation, EntryPoint, PostalAddress, SearchAction, WPFooter, WPHeader, WebSite
Googlebot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.canadiantire.ca/ Call log: - navigating to "https://www.canadi
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Bingbot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.canadiantire.ca/ Call log: - navigating to "https://www.canadi
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Applebot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.canadiantire.ca/ Call log: - navigating to "https://www.canadi
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
ChatGPT-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.canadiantire.ca/ Call log: - navigating to "https://www.canadi
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Claude-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.canadiantire.ca/ Call log: - navigating to "https://www.canadi
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Perplexity-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.canadiantire.ca/ Call log: - navigating to "https://www.canadi
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:

amazon.co.uk

Why picked: Real Chrome gets 30 KB; Googlebot/Bingbot get 900 KB — textbook dynamic rendering

v2 HTTP-only said: ai_blocked (AI avg 0.0/5), blocks gptbot chatgpt_user claudebot perplexitybot

v3 rendered verdict: v2 said blocked but real Chromium with bot UA passes — block is at HTTP/CDN layer only

Chrome desktop
chrome_desktop
HTTP 202
title: Amazon.co.uk: Low Prices in Electronics, Books, Sports Equipment & more
text: 29,523 chars
JSON-LD:
Googlebot
googlebot
HTTP 202
title: Amazon.co.uk: Low Prices in Electronics, Books, Sports Equipment & more
text: 1,542 chars jaccard 6% vs Chrome 5% · SHA
JSON-LD:
Bingbot
bingbot
HTTP 202
title: Amazon.co.uk: Low Prices in Electronics, Books, Sports Equipment & more
text: 27,765 chars jaccard 57% vs Chrome 94% · SHA
JSON-LD:
Applebot
applebot
HTTP 202
title: Amazon.co.uk: Low Prices in Electronics, Books, Sports Equipment & more
text: 27,799 chars jaccard 57% vs Chrome 94% · SHA
JSON-LD:
ChatGPT-User
chatgpt_user
HTTP 202
title: 500 - Amazon.co.uk
text: 166 chars jaccard 0% vs Chrome 0% · SHA
JSON-LD:
Claude-User
claude_user
HTTP 202
title: 503 - Service Unavailable Error
text: 343 chars jaccard 1% vs Chrome 1% · SHA
JSON-LD:
Perplexity-User
perplexity_user
HTTP 202
title: 503 - Service Unavailable Error
text: 343 chars jaccard 1% vs Chrome 1% · SHA
JSON-LD:

coupang.com

Why picked: 5.3× more content to search bots than to real users

v2 HTTP-only said: ai_blocked (AI avg 0.0/5), blocks gptbot chatgpt_user claudebot perplexitybot

v3 rendered verdict: Chrome itself failed to render — IP-walled even for full browsers

Chrome desktop
chrome_desktop
HTTP 403
title: Access Denied
text: 195 chars
JSON-LD:
Googlebot
googlebot
HTTP 200
title: 로켓배송으로 빠르게, 로켓와우 멤버십으로 할인과 무료 반품까지 | 쿠팡
text: 14,476 chars jaccard 0% vs Chrome 7423% · SHA
JSON-LD: MerchantReturnPolicy, MonetaryAmount, Organization, PostalAddress
Bingbot
bingbot
HTTP 200
title: 로켓배송으로 빠르게, 로켓와우 멤버십으로 할인과 무료 반품까지 | 쿠팡
text: 14,476 chars jaccard 0% vs Chrome 7423% · SHA
JSON-LD: MerchantReturnPolicy, MonetaryAmount, Organization, PostalAddress
Applebot
applebot
HTTP 403
title: Access Denied
text: 195 chars jaccard 73% vs Chrome 100% · SHA
JSON-LD:
ChatGPT-User
chatgpt_user
HTTP 403
title: Access Denied
text: 195 chars jaccard 73% vs Chrome 100% · SHA
JSON-LD:
Claude-User
claude_user
HTTP 403
title: Access Denied
text: 195 chars jaccard 73% vs Chrome 100% · SHA
JSON-LD:
Perplexity-User
perplexity_user
HTTP 403
title: Access Denied
text: 195 chars jaccard 73% vs Chrome 100% · SHA
JSON-LD:

uniqlo.com

Why picked: Googlebot gets 3× the Chrome content

v2 HTTP-only said: ai_blocked (AI avg 0.0/5), blocks gptbot chatgpt_user claudebot perplexitybot

v3 rendered verdict: mixed: 1/6 bot UAs render content

Chrome desktop
chrome_desktop
HTTP 200
title: Women's Clothing & Accessories | UNIQLO US
text: 1,745 chars
JSON-LD:
Googlebot
googlebot
HTTP 200
title: Women's Clothing & Accessories | UNIQLO US
text: 1,745 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD:
Bingbot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.uniqlo.com/us/en/ Call log: - navigating to "https://www.uniql
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Applebot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.uniqlo.com/us/en/ Call log: - navigating to "https://www.uniql
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
ChatGPT-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.uniqlo.com/us/en/ Call log: - navigating to "https://www.uniql
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Claude-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.uniqlo.com/us/en/ Call log: - navigating to "https://www.uniql
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Perplexity-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.uniqlo.com/us/en/ Call log: - navigating to "https://www.uniql
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:

shopping.yahoo.co.jp

Why picked: 7-8× more to bots — Japanese pre-render-for-bots pattern

v2 HTTP-only said: ai_blocked (AI avg 0.0/5), IP-walled, blocks gptbot chatgpt_user claudebot perplexitybot

v3 rendered verdict: Chrome itself failed to render — IP-walled even for full browsers

Chrome desktop
chrome_desktop
HTTP 403
title: 【お知らせ】欧州経済領域(EEA)およびイギリスからご利用のお客様へ - Yahoo! JAPAN
text: 1,730 chars
JSON-LD:
Googlebot
googlebot
HTTP 200
title: Yahoo!ショッピング - LINEアカウント連携でPayPayポイント毎日5%!ネット通販
text: 7,859 chars jaccard 2% vs Chrome 454% · SHA
JSON-LD:
Bingbot
bingbot
HTTP 200
title: Yahoo!ショッピング - LINEアカウント連携でPayPayポイント毎日5%!ネット通販
text: 8,328 chars jaccard 2% vs Chrome 481% · SHA
JSON-LD:
Applebot
applebot
HTTP 200
title: Yahoo!ショッピング - LINEアカウント連携でPayPayポイント毎日5%!ネット通販
text: 7,989 chars jaccard 2% vs Chrome 461% · SHA
JSON-LD:
ChatGPT-User
chatgpt_user
HTTP 403
title: 【お知らせ】欧州経済領域(EEA)およびイギリスからご利用のお客様へ - Yahoo! JAPAN
text: 1,730 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD:
Claude-User
claude_user
HTTP 403
title: 【お知らせ】欧州経済領域(EEA)およびイギリスからご利用のお客様へ - Yahoo! JAPAN
text: 1,730 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD:
Perplexity-User
perplexity_user
HTTP 403
title: 【お知らせ】欧州経済領域(EEA)およびイギリスからご利用のお客様へ - Yahoo! JAPAN
text: 1,730 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD:

amazon.com

Why picked: HTTP-202 IP-walls our datacenter regardless of UA — does a real browser change anything?

v2 HTTP-only said: unreachable (AI avg 0.0/5), blocks gptbot chatgpt_user claudebot perplexitybot

v3 rendered verdict: v2 said blocked but real Chromium with bot UA passes — block is at HTTP/CDN layer only

Chrome desktop
chrome_desktop
HTTP 202
title: Amazon.com
text: 142 chars
JSON-LD:
Googlebot
googlebot
HTTP 202
title: Amazon.com
text: 142 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD:
Bingbot
bingbot
HTTP 202
title: Amazon.com
text: 142 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD:
Applebot
applebot
HTTP 202
title: Amazon.com
text: 142 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD:
ChatGPT-User
chatgpt_user
HTTP 202
title: 500 - Amazon.com
text: 166 chars jaccard 8% vs Chrome 116% · SHA
JSON-LD:
Claude-User
claude_user
HTTP 202
title: Sorry! Something went wrong!
text: 0 chars jaccard — vs Chrome 0% · SHA
JSON-LD:
Perplexity-User
perplexity_user
HTTP 202
title: Sorry! Something went wrong!
text: 0 chars jaccard — vs Chrome 0% · SHA
JSON-LD:

ikea.com

Why picked: Blocks all 4 declared AI bots at edge — major retailer with clear anti-AI stance

v2 HTTP-only said: ai_blocked (AI avg 0.0/5), IP-walled, blocks gptbot chatgpt_user claudebot perplexitybot

v3 rendered verdict: Chrome itself failed to render — IP-walled even for full browsers

Chrome desktop
chrome_desktop
HTTP 403
title: Attention Required! | Cloudflare
text: 685 chars
JSON-LD:
Googlebot
googlebot
HTTP 403
title: Attention Required! | Cloudflare
text: 685 chars jaccard 97% vs Chrome 100% · SHA
JSON-LD:
Bingbot
bingbot
HTTP 403
title: Attention Required! | Cloudflare
text: 685 chars jaccard 97% vs Chrome 100% · SHA
JSON-LD:
Applebot
applebot
HTTP 403
title: Attention Required! | Cloudflare
text: 685 chars jaccard 97% vs Chrome 100% · SHA
JSON-LD:
ChatGPT-User
chatgpt_user
HTTP 403
title: Attention Required! | Cloudflare
text: 685 chars jaccard 97% vs Chrome 100% · SHA
JSON-LD:
Claude-User
claude_user
HTTP 403
title: Attention Required! | Cloudflare
text: 685 chars jaccard 97% vs Chrome 100% · SHA
JSON-LD:
Perplexity-User
perplexity_user
HTTP 403
title: Attention Required! | Cloudflare
text: 685 chars jaccard 97% vs Chrome 100% · SHA
JSON-LD:

costco.com

Why picked: Blocks all 4 declared AI bots — see if it's UA-layer or IP-layer

v2 HTTP-only said: ai_blocked (AI avg 0.0/5), blocks gptbot chatgpt_user claudebot perplexitybot

v3 rendered verdict: Chrome itself failed to render — IP-walled even for full browsers

Chrome desktop
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.costco.com/ Call log: - navigating to "https://www.costco.com/
title:
text: 0 chars
JSON-LD:
Googlebot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.costco.com/ Call log: - navigating to "https://www.costco.com/
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Bingbot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.costco.com/ Call log: - navigating to "https://www.costco.com/
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Applebot
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.costco.com/ Call log: - navigating to "https://www.costco.com/
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
ChatGPT-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.costco.com/ Call log: - navigating to "https://www.costco.com/
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Claude-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.costco.com/ Call log: - navigating to "https://www.costco.com/
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:
Perplexity-User
no shot
HTTP — goto:Error:Page.goto: net::ERR_HTTP2_PROTOCOL_ERROR at https://www.costco.com/ Call log: - navigating to "https://www.costco.com/
title:
text: 0 chars jaccard — vs Chrome — · SHA
JSON-LD:

kogan.com

Why picked: Unique pattern — only GPTBot allowed, blocks the other 3

v2 HTTP-only said: unreachable (AI avg 1.2/5), blocks chatgpt_user claudebot perplexitybot

v3 rendered verdict: Chrome itself failed to render — IP-walled even for full browsers

Chrome desktop
chrome_desktop
HTTP 403
title: kogan.com
text: 0 chars
JSON-LD:
Googlebot
googlebot
HTTP 403
title: kogan.com
text: 0 chars jaccard — vs Chrome — ✓ SHA
JSON-LD:
Bingbot
bingbot
HTTP 403
title: kogan.com
text: 0 chars jaccard — vs Chrome — ✓ SHA
JSON-LD:
Applebot
applebot
HTTP 403
title: kogan.com
text: 0 chars jaccard — vs Chrome — ✓ SHA
JSON-LD:
ChatGPT-User
chatgpt_user
HTTP 403
title: kogan.com
text: 0 chars jaccard — vs Chrome — ✓ SHA
JSON-LD:
Claude-User
claude_user
HTTP 403
title: kogan.com
text: 0 chars jaccard — vs Chrome — ✓ SHA
JSON-LD:
Perplexity-User
perplexity_user
HTTP 403
title: kogan.com
text: 0 chars jaccard — vs Chrome — ✓ SHA
JSON-LD:

walmart.com

Why picked: AI-ready control — should serve identical content to all UAs

v2 HTTP-only said: ai_ready (AI avg 5.0/5)

v3 rendered verdict: Full content parity — same rendered page to every UA

Chrome desktop
chrome_desktop
HTTP 200
title: Walmart | Save Money. Live better.
text: 1,477 chars
JSON-LD: EntryPoint, Organization, SearchAction, WebSite
Googlebot
googlebot
HTTP 200
title: Walmart | Save Money. Live better.
text: 1,674 chars jaccard 52% vs Chrome 113% · SHA
JSON-LD: EntryPoint, Organization, SearchAction, WebSite
Bingbot
bingbot
HTTP 200
title: Walmart | Save Money. Live better.
text: 1,477 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD: EntryPoint, Organization, SearchAction, WebSite
Applebot
applebot
HTTP 200
title: Walmart | Save Money. Live better.
text: 1,477 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD: EntryPoint, Organization, SearchAction, WebSite
ChatGPT-User
chatgpt_user
HTTP 200
title: Walmart | Save Money. Live better.
text: 1,477 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD: EntryPoint, Organization, SearchAction, WebSite
Claude-User
claude_user
HTTP 200
title: Walmart | Save Money. Live better.
text: 1,477 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD: EntryPoint, Organization, SearchAction, WebSite
Perplexity-User
perplexity_user
HTTP 200
title: Walmart | Save Money. Live better.
text: 1,477 chars jaccard 100% vs Chrome 100% ✓ SHA
JSON-LD: EntryPoint, Organization, SearchAction, WebSite

samsung.com

Why picked: AI-ready control — pure SSR-for-everyone

v2 HTTP-only said: ai_ready (AI avg 4.0/5)

v3 rendered verdict: Bot UAs got ~79% of the Chrome content — slight UA discrimination

Chrome desktop
chrome_desktop
HTTP 200
title: Samsung US | Mobile | TV | Home Electronics | Home Appliances | Samsung US
text: 4,103 chars
JSON-LD: Brand, Corporation, ImageObject, Organization, OwnershipInfo, WebPage, WebSite
Googlebot
googlebot
HTTP 403
title: Access Denied
text: 198 chars jaccard 1% vs Chrome 4% · SHA
JSON-LD:
Bingbot
bingbot
HTTP 200
title: Samsung US | Mobile | TV | Home Electronics | Home Appliances | Samsung US
text: 4,119 chars jaccard 99% vs Chrome 100% · SHA
JSON-LD: Brand, Corporation, ImageObject, Organization, OwnershipInfo, WebPage, WebSite
Applebot
applebot
HTTP 200
title: Samsung US | Mobile | TV | Home Electronics | Home Appliances | Samsung US
text: 2,975 chars jaccard 74% vs Chrome 72% · SHA
JSON-LD: Brand, Corporation, ImageObject, Organization, OwnershipInfo, WebPage, WebSite
ChatGPT-User
chatgpt_user
HTTP 200
title: Samsung US | Mobile | TV | Home Electronics | Home Appliances | Samsung US
text: 4,091 chars jaccard 98% vs Chrome 99% · SHA
JSON-LD: Brand, Corporation, ImageObject, Organization, OwnershipInfo, WebPage, WebSite
Claude-User
claude_user
HTTP 200
title: Samsung US | Mobile | TV | Home Electronics | Home Appliances | Samsung US
text: 4,091 chars jaccard 98% vs Chrome 99% · SHA
JSON-LD: Brand, Corporation, ImageObject, Organization, OwnershipInfo, WebPage, WebSite
Perplexity-User
perplexity_user
HTTP 200
title: Samsung US | Mobile | TV | Home Electronics | Home Appliances | Samsung US
text: 4,091 chars jaccard 98% vs Chrome 99% · SHA
JSON-LD: Brand, Corporation, ImageObject, Organization, OwnershipInfo, WebPage, WebSite