AEO & GEO for Dealers
Schema Markup for Car Dealerships: The AutoDealer + FAQ + Vehicle Stack That Gets You Cited
Schema markup for car dealerships is structured JSON-LD data that tells AI engines exactly who you are, where you sell, what you stock, and how customers rate you. The stack that gets you cited is AutoDealer, FAQPage, Vehicle, Review with AggregateRating, and Organization with sameAs — each feeding machine-readable facts that ChatGPT, Gemini, and Google AI Overviews can quote with confidence.
If you want AI search to recommend your store, schema markup for car dealerships is the layer that does the quiet, unglamorous work of making your facts machine-readable. Schema — also called structured data — is JSON-LD code that sits in your page and labels everything for the engine: this is the dealership name, this is the address, this is the rating, this is a vehicle for sale. ChatGPT, Gemini, Claude, and Google’s AI Overviews can read your prose, but they extract clean, citable entities far more reliably when you hand them the answer in structured form instead of making them guess.
Here is the part nobody tells you, and it is the whole reason I wrote this. Most dealer sites already have schema — your website vendor injected it the day they built the site. The problem is that vendor-generated schema is routinely incomplete, generic, or flat-out wrong: the wrong NAP, a missing areaServed, hours that changed two years ago, or Vehicle markup that does not match what is actually on the VDP. And incorrect structured data is worse than none, because you are not leaving the engine to figure it out — you are actively teaching it the wrong facts about your store. This guide walks the five schema types every dealership needs, why AI uses each one, and exactly how to fix yours in WordPress.
Want to know how AI describes your store right now?
Before you touch a line of code, see what ChatGPT and Google AI Overviews are actually saying about you.
Run your free AI Visibility Check →Why “We Already Have Schema” Is the Trap, Not the Win
When I tell a fellow GM their store needs schema work, the reflex answer is always “our vendor handles that.” They do — and that is precisely the issue. Platform-default schema is built to be generic across thousands of rooftops, so it ships with templated values that nobody on your team ever verified. I have personally seen dealer pages publish an old phone number, a previous owner’s business name, and a service-department address copied onto the sales page, all wrapped in valid-looking JSON-LD.
Incorrect structured data isn’t a neutral mistake — it’s a confident lie you’ve handed the AI to repeat.
An AI engine does not know your hours changed or that you moved across town. It trusts the structured data because that is what structured data is for. So the broken-but-present schema gets quoted, your NAP conflicts with your Google Business Profile, the engine sees inconsistency, and your store gets described vaguely or skipped entirely. The first move is never “add schema.” It is “audit the schema you already have, then fix or replace it.”
1. AutoDealer / LocalBusiness — Your Identity Anchor
AutoDealer schema is the structured-data anchor that tells AI engines your dealership’s name, address, phone, geo-coordinates, opening hours, and service area. It is a specialized subtype of LocalBusiness, so it carries every local property an engine needs to recommend you for “near me” and city-level car-shopping queries.
This is the single most important block for a dealership, and it is the one most often wrong. AutoDealer is a subtype of LocalBusiness and AutomotiveBusiness, which means it inherits all the local properties — address, geo, telephone, openingHoursSpecification — and adds the signal that you specifically sell cars. AI engines lean on this to answer the highest-intent questions there are: “Where can I buy a [make] near [city]?”
Get four things exactly right: NAP (name, address, phone — must match your Google Business Profile character-for-character), geo (latitude/longitude so map-grounded engines place you correctly), openingHoursSpecification (current hours, separated by department if sales and service differ), and areaServed (the cities and counties you actually pull customers from). Here is a correct, copy-pasteable AutoDealer block:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "AutoDealer",
"@id": "https://www.yourdealership.com/#dealer",
"name": "Your Dealership Name",
"image": "https://www.yourdealership.com/showroom.jpg",
"url": "https://www.yourdealership.com/",
"telephone": "+1-908-555-0142",
"priceRange": "$$",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Auto Mall Drive",
"addressLocality": "Bridgewater",
"addressRegion": "NJ",
"postalCode": "08807",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 40.5934,
"longitude": -74.6046
},
"areaServed": [
{ "@type": "City", "name": "Bridgewater" },
{ "@type": "City", "name": "Somerville" },
{ "@type": "City", "name": "Bound Brook" }
],
"openingHoursSpecification": [
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
"opens": "09:00",
"closes": "20:00"
},
{
"@type": "OpeningHoursSpecification",
"dayOfWeek": "Saturday",
"opens": "09:00",
"closes": "18:00"
}
],
"sameAs": [
"https://www.facebook.com/yourdealership",
"https://www.instagram.com/yourdealership"
]
}
</script>2. FAQPage — Pre-Writing the AI’s Answers for It
FAQPage schema marks up the question-and-answer pairs on a page so AI engines can lift each answer as a standalone, citable response. For dealerships, it is the most direct way to feed engines clean answers about financing, trade-ins, hours, test drives, and inventory — the exact follow-ups buyers ask mid-conversation.
FAQPage is the closest thing to writing the AI’s answer for it. When you wrap a real question and a complete answer in this schema, you hand the engine a pre-formed quote. The rules are simple but strict: the Q&A must be visible on the page (do not mark up hidden content), and each answer should be a full, standalone sentence or two — no “see above,” no pronouns pointing elsewhere — because engines quote these answer strings nearly verbatim.
Put FAQPage on your financing page, your trade-in page, service pages, and model guides. Here is a correct block built for a dealership’s high-intent questions:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Do you offer financing for buyers with bad credit?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Our finance team works with multiple lenders and specializes in subprime and first-time-buyer approvals. You can get pre-qualified online in minutes without affecting your credit score."
}
},
{
"@type": "Question",
"name": "Can I get an instant value for my trade-in online?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Enter your VIN and mileage on our trade-in page for an instant market-based offer, then bring the vehicle in for a final appraisal. The online figure is honored for seven days."
}
},
{
"@type": "Question",
"name": "Do I need an appointment to test drive a vehicle?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Appointments are recommended but not required. Booking ahead guarantees the exact vehicle is cleaned, charged or fueled, and waiting when you arrive."
}
}
]
}
</script>“We ran an experiment on our financing page: same copy, but we wrapped the top eight questions in proper FAQPage schema and rewrote each answer to be self-contained. Within a few weeks, when shoppers asked ChatGPT about bad-credit financing in our area, our exact answer language started coming back in the response — almost word for word. That is the whole game. Schema didn’t change what we said; it changed whether the machine could quote us.”
3. Vehicle / Car — Markup for Your VDPs
Vehicle schema (the Car subtype) marks up each individual vehicle on your detail pages — make, model, year, VIN, mileage, price, condition, and fuel type. It lets AI engines match a specific shopper’s query to a specific unit in your inventory instead of guessing from unstructured listing text.
Every vehicle detail page (VDP) should carry Vehicle or its Car subtype, nested with an Offer for price and availability. This is where engines connect “find me a low-mileage used [model] under $30k near [city]” to an actual car you have. The critical discipline: the schema must match the page. If the VDP says 38,000 miles and $28,995, the JSON-LD must say the same — mismatches are exactly the kind of “broken but present” schema that erodes trust. Key properties to populate: brand, model, vehicleModelDate (year), vehicleIdentificationNumber (VIN), mileageFromOdometer, itemCondition, fuelType, and an offers object with price, priceCurrency, and availability. Most dealers generate this from the inventory feed — so audit a live VDP’s source to confirm the feed is producing accurate, complete markup, not a stub.
Your VDP schema is only as honest as your inventory feed — a stale feed publishes confident misinformation at scale.
4. Review + AggregateRating — The Trust Signal AI Weighs
Review and AggregateRating schema expose your star rating and review count as structured data, giving AI engines a quantified trust signal. When an engine decides which of several local dealerships to recommend, a clean 4.7-from-1,200-reviews datapoint is exactly the kind of fact it surfaces to justify a recommendation.
AI engines are constantly making a “who do I recommend?” judgment, and reputation is a heavy input. AggregateRating nested inside your AutoDealer entity gives the engine a number it can quote: rating value and review count. You can also mark up individual Review items with author and rating. One firm rule from Google’s guidelines: only mark up reviews genuinely collected on or for your site, and never self-serving fabricated ratings — that is a manual-action risk. Pull your rating from a legitimate source and keep it current. A simple, correct aggregateRating nests right into the AutoDealer block:
"aggregateRating": {
"@type": "AggregateRating",
"ratingValue": "4.7",
"reviewCount": "1284",
"bestRating": "5",
"worstRating": "1"
}For the deeper connection between reviews and AI recommendation, see our companion guide on how Google reviews shape what AI says about your dealership.
5. Organization + sameAs — Your Entity & Identity Layer
Organization schema with a sameAs array defines your dealership as a single, consistent entity across the web by linking your site to your social profiles, Google Business Profile, and other authoritative listings. This is how AI engines resolve “is this the same business?” and build a confident, unified picture of your store.
This is the layer that turns scattered mentions into one recognized entity. The sameAs property is a list of URLs that all point to the same organization — your Facebook page, Instagram, LinkedIn, YouTube, Yelp, and ideally your verified Google Business Profile and Wikidata entry if you have one. When AI engines crawl those links and find consistent NAP and branding at each, they stop guessing and start treating your dealership as a defined node in their knowledge graph. Inconsistency here — a different name on Yelp, an old address on Facebook — fractures the entity and makes the engine less confident recommending you. Keep AutoDealer and Organization aligned, and make their sameAs lists agree.
AI doesn’t recommend businesses it can’t confidently identify — entity clarity is the price of admission.
6. How to Implement & Validate in WordPress
You have two clean paths in WordPress, and you do not need to be a developer for either.
Option A — Rank Math (recommended for most dealers)
Rank Math has a built-in Schema Generator. For your homepage and contact page, use the Local Business schema type and set the category to AutoDealer, then fill in NAP, hours, and geo through the visual editor — no hand-coding. For per-page custom blocks (like a tailored FAQ), use Rank Math’s Custom Schema builder and paste your JSON. The advantage: Rank Math keeps the markup attached to the post, so it survives theme changes.
Option B — Raw JSON-LD via “Insert Headers and Footers”
For full control, write the JSON-LD by hand (using the examples above) and inject it with a plugin like WPCode or Insert Headers and Footers, scoping each block to the right page. This is how you handle anything the schema plugin can’t express cleanly. Whichever route you choose, never run two plugins emitting conflicting LocalBusiness schema at once — pick one source of truth.
Then Validate — Every Time
Adding schema without validating it is how broken schema happens in the first place. Two tools, in order:
- Google’s Rich Results Test — confirms your page is eligible for rich results and flags errors and warnings the way Google itself parses them. Fix every error.
- The Schema.org Validator — a stricter structural check against the vocabulary. Use it to catch property and nesting mistakes the Google tool may overlook.
Re-validate after any site redesign, plugin update, or inventory-feed change — dealer platforms are notorious for silently overwriting custom markup.
Not sure which of your schema blocks are broken?
AEO Whisperer scans your store’s structured data and AI visibility, then shows you exactly what to fix first.
Run your free AI Visibility Check →Which Schema to Fix First
For nearly every dealership, fix AutoDealer / LocalBusiness first — verify the NAP, hours, geo, and areaServed match your Google Business Profile exactly. It is the schema AI leans on hardest for “near me” and city-level shopping queries, and it is the one vendors most often get wrong. Once your identity anchor is clean and validated, layer on FAQPage for the fastest citation wins, then Vehicle, Review, and Organization. Identity before everything: an engine that can’t trust who and where you are won’t recommend you no matter how good the rest is.
Frequently Asked Questions
Does schema markup directly improve my dealership’s AI search ranking?
Schema is not a direct ranking factor, but it makes your facts machine-readable. AI engines extract entities — your name, hours, location, inventory, ratings — far more reliably from JSON-LD than from prose. Clean schema raises the odds your store is described and recommended correctly.
My website vendor already added schema. Do I still need to do this?
Probably yes. Most dealer platforms inject generic, incomplete, or outdated schema by default — wrong NAP, missing areaServed, stale hours, or Vehicle markup that does not match the VDP. Incorrect structured data is worse than none because it teaches AI engines the wrong facts. Audit what is already there first.
What schema type should a car dealership use — AutoDealer or LocalBusiness?
Use AutoDealer, which is a specialized subtype of LocalBusiness and AutomotiveBusiness. AutoDealer inherits every LocalBusiness property (address, geo, hours, telephone) and signals to engines that you specifically sell vehicles, which is the context AI needs to recommend you for car-shopping queries.
Can I add FAQPage schema to a dealership blog post or service page?
Yes. FAQPage schema works on any page with a genuine question-and-answer section — blog posts, financing pages, service pages, and model guides. Each answer must be visible on the page and written as a complete, standalone response, because AI engines quote these answer strings nearly verbatim.
How do I validate my dealership schema after I add it?
Run the URL through Google’s Rich Results Test to confirm eligibility and catch errors, then use the Schema.org Validator for a strict structural check. Fix every error and review every warning. Re-test after each site or inventory-feed change, since dealer platforms frequently overwrite custom markup.
Common Questions About Dealership Schema
- What format should dealership schema be in — JSON-LD or microdata?
- JSON-LD, which Google explicitly recommends and is the easiest to inject and maintain in WordPress.
- Does FAQ schema still show rich results in Google search?
- Google limited FAQ rich snippets for most sites, but the structured data still feeds AI engines and AI Overviews, so it remains worth adding.
- How often should I re-validate my schema?
- After every site redesign, plugin update, or inventory-feed change, plus a routine quarterly check.
- Can wrong schema get my dealership penalized?
- Fabricated reviews or markup that doesn’t match visible content can trigger a Google manual action, so accuracy is non-negotiable.
- Where do I put the AutoDealer schema on my site?
- On your homepage and contact page at minimum, as one consistent block, not duplicated with conflicting values across pages.
- Do I need Vehicle schema on every single VDP?
- Yes — each detail page should carry its own Vehicle markup matching that exact unit’s price, mileage, and VIN.
- What’s the difference between sameAs and areaServed?
- sameAs links your identity across platforms; areaServed lists the cities and counties your dealership sells to.
- Will Rank Math conflict with my dealer platform’s built-in schema?
- It can — if your platform already emits LocalBusiness schema, disable one source so engines don’t see two conflicting entities.
- Does schema help with voice search and AI assistants too?
- Yes — the same structured facts power voice answers and assistant responses, not just text-based AI search.
- How do I know if AI is actually citing my store?
- Run an AI visibility check that queries the major engines and reports how your store is described and whether it’s recommended.
Dealer Schema Implementation Checklist
A field-tested, paste-into-your-CMS punch list for getting your dealership’s structured data correct and AI-ready — in priority order.
- Audit existing schema with the Rich Results Test before adding anything new.
- Verify AutoDealer NAP matches your Google Business Profile character-for-character.
- Add accurate geo coordinates and current openingHoursSpecification (by department if needed).
- List every city and county in areaServed that you actually draw customers from.
- Wrap your top financing, trade-in, and test-drive questions in FAQPage schema with standalone answers.
- Confirm Vehicle markup on a live VDP matches the page’s price, mileage, and VIN.
- Nest a current, legitimate AggregateRating inside your AutoDealer block.
- Align Organization sameAs links across every social and listing profile.
- Validate with both the Rich Results Test and the Schema.org Validator — fix all errors.
- Re-validate after every site, plugin, or inventory-feed change.
Explore More
See exactly how AI sees your dealership
Schema is the foundation. AEO Whisperer shows you what the engines do with it — how your store is described, scored, and recommended across ChatGPT, Gemini, and Google AI Overviews.
Run your free AI Visibility Check → See how AI describes your storeSources
- AutoDealer type definition — Schema.org
- Rich Results Test — Google
- Introduction to structured data markup — Google Search Central
- Schema Markup Validator — Schema.org
- 2026 AI Vehicle Research Study — Ekho
- Car Buyer Journey Study — Cox Automotive
- Google zero-click searches 2026 study — Search Engine Land
