Your Inventory Pages Don't Exist Until Somebody Opens Them
Here's a test that takes about ninety seconds and will probably ruin your morning.
Open your dealership's used inventory page. Right-click anywhere on it and choose "View Page Source." Then hit Ctrl+F and search for the stock number of a car you know is sitting on your front line right now. If the browser tells you there are zero matches, you just learned that the most valuable page on your website is, as far as most AI engines are concerned, an empty room.
There are two versions of your website
Every page on your site exists twice. There's the version your server hands out — raw HTML — and there's the version that appears on the screen after the browser finishes running the code. For a lot of pages those two are close enough. For inventory, they usually aren't.
Most dealer website platforms build search results and vehicle detail pages as applications, not documents. The server sends a mostly empty shell. Then JavaScript in the browser goes and gets your inventory feed, pulls back the cars, and paints them onto the page. A shopper never notices — the whole thing takes a second. But nothing about that car was ever in the file the server actually sent.
Google's crawler handles this reasonably well. It renders JavaScript, though on its own schedule and with a budget it decides. The crawlers feeding AI answers are a different story. GPTBot, ClaudeBot, PerplexityBot and their cousins are built for speed and scale, and for the most part they take the raw HTML and move on. If your Certified 2023 X3 only appears after code runs, there's a good chance the engine your shopper is talking to has never seen it.
Why this bites dealers harder than most businesses
A restaurant writes its menu into a page once and it sits there in plain HTML for three years. Our business doesn't work that way. Inventory turns weekly. Prices move. Specials expire. Everything a shopper actually wants to know about your store lives in a feed — and feeds get rendered, not written.
So the pages that describe your dealership in general terms are usually fine. It's the pages that describe what you have for sale that go missing. That's exactly backwards from what you want, because the question shoppers bring to AI is almost never "tell me about this store." It's "who near me has a low-mileage certified X3 under fifty grand."
This is also the quietest problem on this list. Nothing breaks. Your site looks great. Your vendor's analytics show pages loading fine. Traffic doesn't crater in a way anyone can point at. You simply stop being an available answer, and there is no report anywhere that tells you it happened.
Four questions for your website vendor
You don't need to become a developer to run this down. You need to ask four specific things and refuse to accept a vague answer.
One: are our SRPs and VDPs server-side rendered or pre-rendered for crawlers? "Yes" is the answer you want. "Our pages are fully indexed by Google" is not an answer to the question you asked.
Two: show me the raw HTML of a live VDP. Not a screenshot of the page — the source. The year, make, model, trim, mileage, price, and VIN should all be in there before any script runs.
Three: is our vehicle schema in the initial HTML, or injected by JavaScript? Structured data that gets added after load has the same problem as the copy around it. If the labels only appear after the browser runs the code, the crawler that didn't run the code never sees them.
Four: do we serve the same content to GPTBot, ClaudeBot, and PerplexityBot as we do to Googlebot? Some platforms have pre-render rules that fire for Google and nothing else, which was a defensible choice in 2019 and is a bad one now.
What you can fix without waiting on anybody
Vendor timelines being what they are, don't sit still. The pages you control directly — model landing pages, department pages, your finance and service content, an FAQ built to actually answer questions — can be written as ordinary text and published as ordinary HTML. That content is readable by every crawler that comes by, and it's where a lot of your AI visibility is going to come from while the inventory question gets sorted out.
Make sure your Google Business Profile is current, too. When the engines can't read your inventory, that profile is doing more of the work than you think.
The uncomfortable part of this one is that it isn't a content problem you can write your way out of. It's a plumbing problem, and it's been sitting under most dealer websites for years without anyone having a reason to look. Now there's a reason.
If you want a starting point, run your store through the free AEO check at aeowhisperer.com. It takes a minute and it'll tell you what the engines can actually see when they come looking for your store — which is usually less than what you see.