Guides · Dealership
What a dealership website must have
By the Lead Friendly team · Published August 15, 2026 · Updated August 15, 2026
Short answer: A dealership website needs six things that work: one indexable page per vehicle, correct per-vehicle structured data, an inventory feed to the marketplaces your shoppers use, trade-in and financing capture that lands in a CRM rather than an inbox, fast mobile pages, and a phone number someone (or something) actually answers. Everything else — video backgrounds, chat widgets, badges — is optional and mostly is not what sells the car.
The six that matter
| Requirement | Why it decides the outcome | How to verify it |
|---|---|---|
| One indexable URL per vehicle (a VDP) | Shoppers search for a specific year/make/model near them. Without a per-vehicle page there is nothing for that search to land on. | Search your own site for a specific stock unit. If only a filtered list comes back, you have no VDPs. |
| Per-vehicle structured data | Vehicle or Car schema is how Google and AI assistants read price, mileage, VIN, and availability rather than guessing from page text. | Run one VDP through Google's Rich Results Test and confirm a vehicle entity is detected. |
| Inventory feed / syndication | Most used-car demand starts on marketplaces, not on dealer sites. No feed means your lot is invisible where shoppers actually look. | Ask which destinations receive a feed and when the last successful push ran. |
| Trade-in + financing capture | These are the two highest-intent actions on a dealer site. Both are worthless if the submission goes to a shared inbox. | Submit a test lead. It should appear as a contact record with source attribution in under a minute. |
| Fast mobile pages | Dealership traffic is overwhelmingly mobile, often on a phone in someone's hand at a competitor's lot. | Test a VDP — not the homepage — on a throttled mobile connection. |
| A phone number that gets answered | Dealership shoppers still call, and calls convert far better than forms. An unanswered call is a sold car at another store. | Call your own main line at 7pm on a Saturday and see what happens. |
Try Lead Friendly free for 7 days
AI voice agents + CRM + TCPA-gated compliance. 30 minutes included. No card required.
Vehicle detail pages are the whole product
A dealership homepage is a lobby. The vehicle detail page is the product, and it is the page that earns organic traffic and AI citations, because it is the only page that answers a specific shopper's specific question.
A VDP worth having carries a unique title and description with year, make, model, trim, and location; the full photo set with real alt text; price, mileage, VIN, and drivetrain as structured data rather than as an image; a visible and correct availability status; and a clear next action that is not just a phone number in the footer. Pages that instead render the whole inventory through JavaScript with no per-vehicle URL are the single most common reason a dealer's cars never appear in search.
Structured data, written for machines that answer questions
Structured data used to be about rich snippets. It is now also how AI answer engines decide whether they can state a fact about your inventory confidently enough to cite you.
For a dealer site that means Vehicle or Car markup on each VDP with price, mileage, VIN, body type, and availability; AutoDealer markup on the site with address, hours, and phone matching your Google Business Profile exactly; and BreadcrumbList so the hierarchy from inventory to individual car is explicit. Mismatched hours or phone number between your site and your profile is a small error that quietly suppresses local visibility.
Availability is the field most often wrong. A sold vehicle left marked in stock trains both crawlers and shoppers to distrust the whole feed.
What you can safely skip
Full-screen video heroes that delay the first render on a phone. Auto-playing audio. Stock photography of cars you do not have. Award badges and certification logos above the inventory. A chat widget nobody is staffed to answer — an unanswered chat is worse than no chat, because the shopper has now been ignored twice.
The spec, as a checklist to hand a vendor
- One crawlable URL per in-stock vehicle, present in the XML sitemap.
- Vehicle or Car structured data on every VDP, validating clean.
- AutoDealer structured data with NAP identical to the Google Business Profile.
- An inventory feed with a named destination list and a visible last-successful-push timestamp.
- Trade-in and financing forms posting into a CRM with source attribution, not to email.
- Mobile VDP render measured on a throttled connection, not a desktop score.
- A tracked phone number, with a documented answer path outside business hours.
- Sold vehicles removed from the sitemap and marked unavailable, not silently 404ing.
Frequently asked questions
What is a VDP on a dealership website?
A VDP is a vehicle detail page — one dedicated page for a single car in your inventory, with its own URL, photos, specifications, price, and structured data. It is the page a shopper lands on from a search for a specific year, make, and model, and it is the unit of content search engines and AI assistants actually index. A site that shows inventory only as a filterable list, with no individual URLs, has no VDPs and effectively no organic presence for its cars.
Does a small dealership need inventory syndication?
Yes, and usually more than a large one does. Most used-vehicle shopping begins on marketplaces rather than on dealer websites, so a small lot with no feed is competing only for the shoppers who already know its name. Syndication is what puts a twenty-unit lot in front of the same audience as the franchise store down the road.
What structured data does a car dealership website need?
Vehicle or Car markup on every vehicle detail page carrying price, mileage, VIN, body type, and availability; AutoDealer markup for the business with address, hours, and phone matching your Google Business Profile exactly; and BreadcrumbList to make the inventory hierarchy explicit. This is what lets Google show rich results and lets AI answer engines state facts about your cars with enough confidence to cite the source.
How fast should a dealership website be?
Judge the vehicle detail page on a throttled mobile connection, not the homepage on desktop, because that is the page and the context that matter. The practical bar is that the main photo and the price are readable without waiting. The most common cause of a slow dealer VDP is unoptimised photography — twenty full-resolution images loaded eagerly will beat any amount of other optimisation.
Do dealership websites still need a phone number?
Phone calls remain the highest-intent action on a dealership site by a wide margin, and dealership shoppers call at hours no showroom is staffed. The question is not whether to publish the number but what happens at 7pm on a Saturday when it rings. If the honest answer is voicemail, that is the gap to close before redesigning anything.
See it on your own calls
Pick your industry, paste your website, and hear your AI agent take a call. Free for 7 days. No credit card required.
Start free trial