Schema markup for dealership websites, explained without the code talk

Structured data — schema markup — is one of those topics where every explanation opens with a code sample, which is why most dealer principals decided years ago that it was somebody else’s problem.

Here is the version without the code.

What it actually is

Your homepage states your name, address, phone number and hours somewhere. A person reads that and understands it immediately. A machine reads it and sees text that might be your address, or might be part of a testimonial, or might belong to a second location, or might be the address of the photographer who shot the building.

Schema is a second copy of those same facts, written in a fixed format, in a part of the page nobody looks at. It says: this string is the legal business name. This is the phone number. These are the opening hours. This is the kind of business.

You are not adding information. You are removing ambiguity.

Nothing in your schema should be a fact that is not already visible on the page. If it is, that is a different and more serious problem.

Why it matters more than it used to

For years the payoff was cosmetic — star ratings in a search result, a nicer-looking listing. The payoff now is that an assistant assembling an answer about your store has to decide what it is confident enough to state.

A model summarising three dealerships will name the one whose details it is sure about. Facts sitting in unstructured prose get hedged, softened, or left out. That is the entire mechanism, and it is why this moved from a technical nicety to something worth twenty minutes of a general manager’s attention.

The four types a dealership needs

• AutoDealer — the core one. Name, address, phone, hours, price range, the brands you carry, links to your social profiles. One per rooftop.
• FAQPage — question and answer pairs in your own words. The cheapest item on this list and almost no dealer site has it, which makes it easy ground to take.
• BreadcrumbList — where a page sits in your site. Helps a machine understand that a model page belongs to a category rather than floating on its own.
• Vehicle — on inventory detail pages. Year, make, model, trim, VIN, mileage, price, availability.

That is the list. You do not need forty types, and a provider proposing a long one is usually generating them automatically without checking whether any of it is true.

How to check what you actually have

Five minutes, no technical knowledge required:

1. Open Google’s Rich Results Test and paste in your homepage URL.
2. Look for AutoDealer or LocalBusiness in what it finds.
3. Read the values, do not just check the box. Is the phone number right? Are the hours current? Is that the address of the building you are sitting in?
4. Repeat for one model page and one vehicle detail page.

The crawler check on this site reads the same markup and also tells you whether the AI crawlers are permitted to read the page at all, which is the question underneath this one.

The three failures I find most often

1. Nothing at all. Common on older custom builds, and common after a redesign quietly dropped it.
2. Malformed markup. Present, broken, and therefore ignored completely by every crawler that reads it. Usually one unescaped quotation mark in a business name or a street address. It looks perfect to a human and is invisible to a machine, which is the worst possible combination — everyone at the store believes it is handled.
3. Stale facts. Hours from before you changed Saturday close. A number routing to a disconnected tracking line. The previous address. This is the dangerous one, because a confident wrong answer sends a shopper to a locked door and they do not try again.

The third deserves an annual check on its own merits. Nobody updates schema when the store changes its hours, because nobody at the store remembers it exists.

Who does the work

If you are on a vendor platform — most stores are — this is a support ticket, not a project. Ask them one question: which schema types are on our homepage, our model pages and our vehicle detail pages, and can you send me the Rich Results Test output for one of each.

A competent provider answers within a day. A provider who cannot answer at all has told you something useful about the rest of what they do.