Why every Dealer.com site fails our schema test

Every Dealer.com site we run through our free Site Health Score scanner returns the same flag in the AI Visibility category: schema not detected. The dealer principal sees the red mark and reasonably assumes their platform vendor failed them. The platform vendor, when asked, insists schema is present. Both are correct. The disconnect is technical, and it matters more than most dealers realize.

What the scanner sees

Our scanner, like Google's static crawler and like every AI search engine indexer in production today, fetches the raw HTML of a page on first request. It looks for JSON-LD schema markup inside the document. On a Dealer.com page, the raw HTML returns the page chrome, the navigation, and almost nothing else. The Vehicle schema, the AutoDealer schema, the BreadcrumbList schema: none of it is in the document the scanner receives.

Then the page loads JavaScript. Dealer.com's client-side framework executes, fetches inventory data from their APIs, and injects the schema into the DOM after render. Open the browser dev tools on a fully loaded Dealer.com VDP and you will find the schema right there. It is real. It is correctly formatted. It is just invisible to anything that does not execute JavaScript before reading.

Why this matters now and not five years ago

Google's web crawler, Googlebot, has been able to render JavaScript for years. So the conventional wisdom for a long time was: client-side schema is fine, Googlebot will see it. That conventional wisdom is now wrong on two fronts.

First, Googlebot's two-pass indexing means client-rendered content is indexed on a delay, sometimes a long delay, behind server-rendered content. For a high-velocity inventory page where vehicles cycle in and out within days, that delay is the difference between being in Google Vehicle Listings and being invisible.

Second, AI search engines, including ChatGPT browse, Perplexity, Claude with web access, and Gemini, almost universally do not execute JavaScript at scale. They fetch raw HTML. If your schema is not in that raw HTML, the AI does not know what your page is about. When a buyer asks Perplexity for "Buick dealers near me with a GMC Sierra in stock," the AI cannot recommend you because the AI never saw your inventory.

How big is the problem

Across the dealer audits we have run on Dealer.com sites, every single one has failed our static schema test. Every one. The platform's architecture decision propagates to every dealer on the platform. This is not one dealer's mistake. This is a category-wide visibility gap that the platform created and has not addressed.

We do not have a precise number on the traffic impact yet. The honest answer is: it depends on how much of your organic and AI-referral traffic comes from queries where schema is the deciding signal. For inventory queries, the ones with the highest commercial intent, our internal estimate is between 5 and 15 percent of available organic VDP traffic is being left on the table. For AI-referred traffic, which is a smaller but rapidly growing channel, the loss is closer to total.

What to do about it

The fix is not to switch platforms. The fix is to inject server-renderable schema yourself, independent of the platform vendor. The cleanest path is Google Tag Manager: a custom HTML tag that pulls inventory data from your DMS feed and writes properly formatted JSON-LD into the document head on initial load, before the platform's JavaScript runs.

This is not a five-minute fix. The schema needs to be accurate per VDP, not generic per page template. It needs to update as inventory changes. And it needs to validate cleanly against Google's Rich Results Test and the Google Vehicle Listings feed validator. We have built this for dealers. The implementation is part of our standard remediation work and ships in 7 to 14 days for most dealers.

If you are on Dealer.com and you have never had this conversation with anyone, your schema is invisible to every static crawler that touches your site. Run the free Site Health Score on your URL and the AI Visibility category will show you exactly what we see. From there, the fix path is documented and the implementation is reproducible.