Dealership Schema Markup Guide

Structured data will not rescue a bad website. On a decent one it changes how search engines and answer engines describe your store.

A web page is written for people. A search engine reads the same page and has to infer what everything on it means. Is that number a price, a mileage figure or a stock number. Is that address the dealership's or the manufacturer's. Is that block of text a description of the vehicle or a legal disclaimer.

Schema markup removes the guessing. It is a block of structured data placed on the page, invisible to visitors, that labels the facts explicitly. This is a vehicle. Its make is this. Its price is this number in US dollars. It is offered by this business, at this address, with this phone number.

The standard is maintained at schema.org and the major search engines agreed to read it, which is why it is worth doing rather than a niche technique. The recommended format is JSON LD, a block of labelled data placed in the page source rather than wrapped around the visible text. That distinction matters practically: JSON LD can be added without touching your page layout, which is why it is the only sane choice for a dealership site that a vendor controls.

Be clear about what it is not. It is not a ranking factor in the direct sense. Adding markup to a page that nobody links to and nobody visits does not move it up. What markup does is make you eligible for richer presentation and make your facts machine readable, which is increasingly how customers encounter you before they ever see your site.

There are hundreds of schema types. A dealership needs about six, and getting those six right beats a sprawling implementation of twenty.

AutoDealer. The type for the business itself, a subtype of LocalBusiness. It belongs on your homepage and your contact page and carries name, address, phone, opening hours, geographic coordinates, price range and links to your verified profiles elsewhere. Every rooftop gets its own, with its own address and phone. A group that publishes one business entity for six stores has told search engines it has one store.

Vehicle and Car. The type for an individual unit on a listing page. The useful fields are make, model, model year, VIN, mileage with its unit, body type, colour, fuel type, transmission, drive configuration and number of doors. Populate what you actually know and leave the rest out.

Offer. The price, currency, availability and the business making the offer, attached to the vehicle. This is what allows a price to be understood as a price.

BreadcrumbList. Cheap to add, genuinely useful, and it improves how your listing paths are displayed.

FAQPage. For pages that genuinely answer questions. Do not fabricate questions to qualify.

Organization and WebSite. Sitewide identity and your internal search, so your brand is understood as an entity rather than a string.

A dealership's inventory pages are the bulk of its indexable surface, so this is where markup either pays off or creates a mess at scale.

The right way to do this is to generate it from your feed rather than by hand. Whatever populates your vehicle detail page should also populate the structured data, so the two can never disagree. If your feed changes a price at 6am, the markup changes with it. Hand written markup goes stale within a week and stale markup is worse than none, because you are now publishing a price you are not honouring.

This is one of the practical arguments for a single inventory source. My Inventory Link ingests a dealer's live feed with VIN, trim, mileage, price and photos and serves it through a public inventory API and per salesperson inventory sites built from a template. When one source feeds the listing, the salesperson pages and the structured data, the numbers cannot drift apart. A feed is not required to use the platform at all, but if you have one, using it as the single source is what keeps markup honest.

Two rules for scale. Only mark up vehicles that are actually available, and remove markup when the unit sells rather than leaving a sold car published as an active offer. And never mark up a price you are not prepared to honour on the phone, because the markup is a public statement and advertising rules do not care that a plugin generated it. More on the listing side at vehicle listing optimization.

Local is where dealership markup most often goes wrong, and the failure is structural rather than technical.

Each rooftop is a separate business location with its own name, address, phone number and hours. Your markup has to reflect that. The common error in a group is publishing group level identity on every store's pages, which collapses six locations into one entity in the eyes of a search engine and undermines the local visibility of every store including the strongest one.

Keep the details consistent with your verified business profiles and your listings elsewhere on the web. Consistency across those sources is one of the oldest local signals and it is still doing work. A phone number that appears three ways across your site, your profile and your directory listings is a small inconsistency with a cumulative cost.

Mark departments honestly. Sales, service and parts frequently have different hours and often different phone numbers, and a customer who calls the service line at 7pm because your markup published sales hours has a bad first experience with your store. If you run distinct channel numbers for tracking, be deliberate about which number is published as the canonical business number rather than letting a tracking number leak into your structured data. There is more on the wider local picture at local SEO for car dealerships and, for groups, multi location SEO.

This is the area where dealerships get themselves into trouble, so it is worth being blunt.

Search engines restrict self serving review markup, meaning markup about your own business placed on your own site by you. The guidance has tightened repeatedly, and implementations that once produced star ratings in search results largely no longer do. Publishing an aggregate rating you assembled yourself, on your own pages, is at best ineffective and at worst a manual action risk.

What is legitimate is marking up genuine reviews of a specific product or item where the review content is really on the page and really written by customers. What is not legitimate is inventing an aggregate rating, marking up reviews collected elsewhere as if they were yours, or marking up a page that has no visible reviews on it at all. The rule underneath all guidance here is simple: the markup must describe what a human visitor can actually see on that page.

The same rule kills most of the shortcuts. FAQ markup on a page with no visible FAQ. Offer markup with a price the page does not display. Vehicle markup on a page listing forty vehicles rather than one. Every one of those is the same mistake, and it is the mistake that gets structured data ignored across an entire site rather than on a single page.

Practical sequence for a store that does not have a developer sitting in the office.

First, find out who controls your website templates. For most dealerships that is your website provider, and the honest answer is that inventory and homepage markup is their job. Ask them what schema types they output today, whether the vehicle data is generated from your feed, and whether you can see a sample. Many providers already do a competent version of this and stores are unaware.

Second, handle the pages you control yourself. Landing pages, campaign pages and salesperson pages sit outside the main site template in most stores. LeadLocate's lead page builder gives each page its own URL through per page URL settings, and personal salesperson websites are separate addresses too. Those are your pages, so mark them up deliberately rather than leaving them bare.

Third, validate before you publish and after. Use the schema validation tools the search engines publish, check a real page rather than a paste of the code, and then check again a week later on a live URL, because a template change or a caching layer can strip a block silently.

Fourth, monitor. Structured data errors appear in search console reporting, and the useful habit is checking after any website release rather than once a year. Most broken markup on dealership sites was working when it was installed. The pairing with technical health matters too, and core web vitals covers the performance half of the same job.

From reviewing dealer sites, the same handful come up again and again.

Markup that disagrees with the page. A price in the structured data that no longer matches the price displayed. This is the most common and the most damaging, because it can look like deliberate misrepresentation.

Sold vehicles left marked as available. A dead listing with an active offer in the data is a bad answer given confidently.

One business entity for a group. Covered above and worth repeating because it is invisible until somebody looks.

Marking up a listing grid as a single vehicle. The type does not match the page and the whole block gets discarded.

Copying markup from another dealership. It happens more than you would think, and the giveaway is somebody else's address sitting in a competitor's page source.

Treating markup as the SEO plan. It is plumbing. It helps a page that deserves to rank be understood properly. It does not create authority, relevance, links or content. If your inventory pages are thin and your model pages do not exist, structured data is not your bottleneck. An SEO audit will tell you what is.

The reason to care has shifted. Structured data used to be about star ratings and rich snippets in a list of blue links. Increasingly it is about being readable by systems that answer questions directly rather than sending a click.

When a customer asks an assistant which dealerships near them have a specific model under a specific price, something has to decide what your store is, where it is, what it has and what it costs. Explicit, accurate, machine readable facts are how you participate in that answer. Ambiguous pages get skipped, not penalized, which is worse because it is silent.

The practical implication for a dealership is that the facts have to be right at the source and kept current automatically. That is a data discipline problem more than a markup problem. A store with one authoritative inventory feed and a template that generates markup from it will be described accurately. A store with three inventory sources and hand edited pages will be described inconsistently, and no amount of markup fixes the underlying disagreement.

We cannot guarantee visibility in any search result or answer engine, and any vendor who does is selling something they do not control. What is within your control is publishing accurate, current, structured facts about your store and your vehicles, and that is worth doing on its own merits.

We are not your website provider and we do not sell a full dealership website platform, so the markup on your main site and your inventory template is theirs to implement. Ask them the questions above.

What we do provide is the surface next to it. Lead pages with per page URL settings, personal salesperson websites, a free live chat widget for your site, customer facing deal pages, and Inventory Link to ingest your feed so one source of vehicle data drives everything downstream. Those are pages you control, they are frequently the pages your campaigns actually point at, and they are worth marking up properly. See landing page optimization for the conversion side of the same pages.

Around them sits the part that decides whether traffic turns into anything: source tagged lead intake, a phone validator and an email validator, SMS and MMS with RCS and SMS fallback, click to call with recording and transcription, follow up processes and drip campaigns, and three layers of reporting. Search visibility that lands in an inbox nobody works is an expensive way to feel busy.

Pricing is month to month with no long term contract, from $199 on CRM Only and $799 for programs including exclusive local leads. Detail on the pricing page, or contact us and we will tell you plainly whether we are the right piece of your problem.

Does schema markup improve dealership rankings?

Not directly. It makes your facts machine readable and makes you eligible for richer presentation. A page that nobody links to and nobody visits does not rise because markup was added. Treat it as plumbing that helps a good page be understood.

Which schema types should a dealership use?

AutoDealer for the business, Vehicle or Car plus Offer on individual listing pages, BreadcrumbList for navigation, FAQPage where a real FAQ is visible, and Organization plus WebSite sitewide. Six types done correctly beats twenty done loosely.

Can we mark up our customer reviews to get star ratings?

Self serving review markup about your own business on your own site is restricted and largely no longer produces stars. Genuine reviews visible on the page for a specific item can be marked up. Never publish an aggregate rating you assembled yourself.

Should each rooftop in a group have its own markup?

Yes. Each location needs its own business entity with its own name, address, phone and hours. Publishing group level identity on every store's pages collapses your locations into one entity and weakens local visibility for all of them.

Does LeadLocate add schema markup to our website?

Not to your main site, because we are not your website provider and do not sell a full dealership website platform. We provide lead pages with their own URLs, salesperson websites, a chat widget and Inventory Link, which are pages and data you control.

How often should markup be checked?

After every website release, and at minimum quarterly. Most broken dealership markup was working when it was installed and was later stripped by a template change or a caching layer. Validate a live URL rather than a code sample.

See lead pages, chat and the follow up engine that decide whether search visibility becomes a conversation. Month to month, no long term contract.