Page rendering
Can AI read your vehicle pages?
Your bot protection is selective, and this scan can show it: a real browser gets through without ever seeing a challenge, yet our plain automated request was challenged and turned away. That is why everything looks normal in your own browser. The crawlers ChatGPT, Claude, and Perplexity read with do not run a browser or solve challenges, so they hit the same wall we did and cannot read your inventory. The cost lands on you, not the wall's vendor: when a shopper asks an assistant about your cars, it answers from whatever it can reach instead, third-party listing pages about you or a competitor whose site it can read, and that page gets your shopper. Allowlisting the AI crawlers in your bot product (in Cloudflare this is one rule) opens the door without weakening protection against real threats, and if you have already allowlisted them, this one clears. A VIN Index listing closes the gap from the other side: an inventory surface assistants can always read, with your site's security untouched.
VIN Index republishes every car as a page a crawler reads start to finish, without running a line of JavaScript.
See the detail
What we checked
Whether your vehicles are present in the raw HTML an AI crawler receives, and whether the named AI crawlers are allowed in.
How we tested
We fetch your page with no JavaScript (the way ChatGPT’s and Claude’s crawlers read), count the readable vehicles, and probe whether each engine’s crawler gets through.
What it means
If your cars only appear after JavaScript runs, most AI crawlers see an empty page and have nothing to cite when a buyer asks.
- Real browser render
- Got through, no challenge shown
- Automated crawler request
- Challenged / blocked
- Bytes returned to a no-JS crawler fetch
- 919 chars of HTML
- Vehicles readable in that HTML
- None
