A car buyer does not start at your lot. They start on a phone, on a couch, with a listing site open in one tab and your website in another. If your inventory is slow to filter, your vehicle pages are thin, or the trade-in number takes a phone call to get, they finish the search somewhere else.
This is a practical guide to building a car dealership website on HubSpot CMS: the pages, the inventory setup, the schema that gets your vehicles into search results, and the forms that put a lead in your CRM instead of a voicemail. No dealer-platform contract, no six-month agency build.
What pages does a car dealership website need?
Dealer sites that sell cars share the same backbone. A shopper checks a predictable set of things before they walk in, and every one of them deserves a page.
- Home. What you sell, where you are, current hours, and a fast route into the inventory.
- Inventory (your SRP). The search results page. Filterable by make, model, body style, fuel, price, and condition.
- Vehicle detail pages (your VDPs). One page per car: gallery, spec table, price, mileage, VIN, and a test-drive action.
- Financing. How approval works, what you need from them, and a pre-qualification form.
- Trade-in. A valuation request that captures the vehicle they are replacing.
- Service and parts. Fixed ops pays the bills between sales. Give it a booking path of its own.
- About and team. Salespeople with names and faces. A used-car purchase is a trust purchase.
- Contact and hours. Address, map, phone, sales and service hours listed separately.
Your inventory is the website
On a dealership site, SRPs and VDPs are most of the pages you have, most of the pages Google indexes, and most of the pages a buyer ever sees. Everything else is supporting cast. Build those two well and the rest of the site can be simple.
The SRP has one job: let someone narrow a lot full of cars down to the three they care about, on a phone, without a page reload between every tap. Filters that respond instantly, a card that shows price and mileage before they click, and a way to open a vehicle without losing their place in the list.
The VDP has a different job: answer every question that stands between looking and driving. Photos that load fast, a full spec table, an honest price, the VIN, and a test-drive button that follows them down the page.
How do you get vehicles onto a HubSpot site?
This is the question that stops most dealers from considering HubSpot at all, and the answer is more boring than they expect. HubDB is a table inside HubSpot. Each row is a vehicle, each column a field: year, make, model, trim, mileage, price, body style, fuel, condition, VIN, photos. Templates read the table and build the SRP and the VDPs from it.
Your team edits rows the way they would edit a spreadsheet, and the site updates. Sell a car, change the row. Take in a trade, add a row. No developer in the loop, and no waiting on a platform vendor to push a change. If you already run an inventory feed, the same table is what a sync writes into.
The module that does this is Vehicle Inventory Pro, and it handles the filtering, the cards, and the detail view.
Vehicle schema, or why your cars stay invisible
Two dealers can list the same used sedan at the same price and only one of them shows up with the price and availability attached in search. The difference is structured data.
Vehicle schema on every VDP tells Google what the page is: make, model, year, mileage, price, condition, VIN. AutomotiveBusiness or LocalBusiness schema on your main pages tells it who and where you are, with name, address, phone, geo coordinates, and hours. Offer schema ties the price to the car. Review markup puts stars next to your name.
Most dealer sites skip this or inherit a half-built version from a platform template. Getting it right is a one-time setup that pays out on every vehicle you list after it.
What happens to a car after it sells?
Inventory turns over, which means your site is constantly retiring URLs. Handle it deliberately. A sold vehicle should redirect to the SRP or a similar in-stock car rather than leaving a dead page, and your sitemap should drop it. Leave the dead pages behind and you accumulate a site full of errors that drags on everything else you rank for.
The same discipline applies going the other way: a new vehicle should be in the sitemap the day it is listed, not the week after.
Financing and trade-in are the pages that convert
Inventory browsing is low intent. Someone can scroll cars for an hour and never raise a hand. The pages where people identify themselves are financing and trade-in, because both require them to tell you something about their situation.
Build them as forms, not phone numbers. A pre-qualification form that asks for the basics and sets expectations about what happens next. A trade-in form that captures the year, make, model, mileage, and condition of what they are driving now. Both land in HubSpot as a contact with the context attached, so your sales manager sees the trade details before they call back.
That is the part a dealer platform tends to hold hostage. On HubSpot the form, the contact, the follow-up sequence, and the reporting are the same system.
Test drives that book themselves
Put the test-drive action on every VDP and keep it visible while they scroll the spec table. It should ask for a name, a phone, a preferred day, and the vehicle they are asking about, prefilled. The request arrives as a contact tied to that car, and an automated confirmation goes out immediately so nobody sits wondering whether the form worked.
From there a workflow can assign the lead, remind the salesperson, and follow up if the appointment never gets confirmed.
Local SEO, because nobody drives two hours for a Civic
Dealerships live on local search. Someone types "used SUV near me" or "certified pre-owned [your town]" and you either appear or you do not. That comes down to unglamorous details: a consistent name, address, and phone across the web, a claimed and current Google Business Profile, separate sales and service hours in the markup, and location pages if you run more than one rooftop.
It is the same groundwork behind every local build we do. We rebuilt a gym's site around exactly this problem — structured for local search, tied to its map listing, and readable by AI answer engines. The Fight Fit case study walks through how it fits together.
Getting recommended by AI answer engines
A growing share of car shopping starts with a question typed into ChatGPT or an AI overview rather than a search box. Those systems read the same structured data Google does, and they need to confirm you have the car before they will mention you.
What helps: clean Vehicle schema on the VDPs so a model query can match your stock, plain question-and-answer sections on financing and trade-in pages, headings that state the question a shopper would ask, and pages that load without a wall of scripts in front of the content. None of that is a trick. It is the same clarity that helps a human buyer.
Do not forget the service department
Sales gets the attention, service gets the repeat visits. A service page with a booking form, a parts enquiry route, and honest hours turns a one-time buyer into someone who comes back every six months. It also captures searches your sales pages never will — brand-specific repair, recall work, seasonal tyre changes.
The theme that ships with all of it
Everything above assumes you have the templates and modules to build it. That is what Redline is: a HubSpot CMS theme for car dealerships, with the filterable inventory grid, the detail drawer, single-vehicle pages, financing and trade-in sections, and Vehicle schema already designed and wired. Your team edits it from the HubSpot editor. No CSS, no developer tickets.
The full demo is live at nopethemes.com/redline-preview, where you can filter the inventory and open a vehicle page before you decide. Redline is $349 one-time on the HubSpot Marketplace.
A realistic timeline
Two to three weeks from install to launch if your vehicle photos and specs are in reasonable shape. Longer if the photos need reshooting or the inventory data lives in someone's head. The pages and modules are already designed. What takes time is the part only you have: the cars, the photos, the financing terms you publish, and the people you put on the about page.
If your lot is moving but the website is the bottleneck, this is a two-week project with a $349 theme as the starting point. Want a hand setting it up on your portal? Get in touch. Or browse the rest of the Studio Nope themes.