Your dealership is invisible to ChatGPT (and how to check)

There is a specific kind of bad news that never shows up in your analytics: the customer who never arrived. No session, no bounce, no abandoned form. They asked an assistant a question, got an answer that named a dealership, and drove there. If the dealership named was not yours, nothing in your reporting will ever tell you the conversation happened.

This is the part of the AI shift that is easy to miss. It does not look like a traffic drop. It looks like nothing at all.

What an assistant actually receives

Open your VDP and look at it. Now consider what arrives on the other end when a machine requests that same page.

On a large share of dealer sites, the answer is: a shell. The inventory grid is assembled in the browser by JavaScript after the page loads, so a fetch that does not execute scripts gets an empty container. The trim and package detail that a shopper reads off the window sticker lives inside a JPEG, which is opaque to a text model. The payment is calculated by a widget that runs client side. The current offers are a PDF, or worse, an image of a PDF. And the structured data, the machine-readable summary that says “this is a car, this is its VIN, this is its price, this is who sells it”, is either missing entirely or present in a thin, generic form that describes the dealership but not a single vehicle.

Then there is the quietest failure of all: the crawler policy. Cloudflare moved to gating AI crawlers by default, and plenty of dealer sites now block AI user agents without anyone in the store having made a decision about it. You can have flawless structured data and still be unreachable because a default setting somewhere says no.

Stack those together and the assistant is not being unfair to you. It genuinely cannot see what you have.

Why it recommends someone else

Assistants do not fail loudly. When a model lacks specific, current information about your store, it does not announce a gap. It answers the question with whatever it does have, which is usually one of three things.

It falls back to a third party. Marketplaces and aggregators invest heavily in machine-readable inventory, so their version of your stock is often more legible than yours. The buyer gets an answer built on someone else’s summary of your lot, complete with someone else’s lead form.

It falls back to a competitor. The store two exits down that happens to run a platform with clean structured data becomes the concrete, checkable recommendation. Concreteness wins. An assistant asked to name a dealer will name the one it can describe.

Or it falls back to generalities. It tells the buyer to check local dealers, which is another way of saying it could not help, and the buyer goes back to searching.

None of these outcomes generate a signal you can see. That is the whole problem.

The check takes about a minute

You do not have to take any of this on faith, and you should not. Run your own URL through the public checker at isitagentready.com. It looks at your live site the way an agent does and scores what a machine can actually read, understand and act on, from zero to one hundred across five levels.

Most dealers who run it for the first time land somewhere around twenty one out of one hundred. That is not a mark of a bad website. Plenty of stores scoring in the low twenties have genuinely excellent sites by every human measure: fast, attractive, converting well, recently redesigned. The score is measuring a different axis entirely, one that nobody was building for until very recently.

If you want to sanity check it yourself before trusting any tool, here are three things you can do in the next ten minutes.

Ask an assistant directly. Open ChatGPT or Claude and ask, in the voice of a real shopper in your market, which dealer has a specific kind of vehicle in a specific payment range. See who gets named. See whether the details about your store are current, or invented, or absent.

View the page source of a VDP, not the rendered page. In your browser use view-source rather than inspect, since inspect shows you the DOM after JavaScript has run. Search that raw source for the VIN and for application/ld+json. If the VIN is not there and there is no JSON-LD block describing the vehicle, a crawler that does not execute scripts is getting nothing.

Check your robots and your AI bot policy. Look for /robots.txt and see what it says about AI user agents. Then ask whoever manages your CDN whether AI crawler blocking is on. A surprising number of stores find the answer is yes and nobody chose it.

What fixing it actually means

The remedy is not a redesign. Your website is not the problem, and rebuilding it will not move this number much on its own.

What moves it is making the same inventory legible in a second form: complete schema.org markup for every vehicle and every offer, a per-VIN spec record that does not live inside an image, an llms.txt that tells an agent what you are and how to work with you, clean sitemaps, and a crawler policy that deliberately allows the agents you want to reach you. That is the readable floor.

Above that floor sits the part that actually wins the recommendation: a live connection, so an assistant queries your real inventory in the moment rather than relying on whatever it crawled last week, and real tools so it can estimate a trade, run a payment and hand you a lead inside the conversation.

The first step is just knowing. Run the check, get the number, and decide from there. Being invisible is a fixable condition. Not knowing you are invisible is the expensive part.