The commercial truck dealer SEO playbook

A commercial truck dealer does not sell to a person who woke up wanting a truck. It sells to a fleet manager who needs a 26,000 GVWR chassis with a 60 inch CA for a dump body, delivered before the paving season, serviced within two hours of the yard. That buyer searches by spec, by application, and by distance. Most truck dealer websites are built to answer none of those three. This playbook is how we fix that, in order, for a Class 3 to 8 dealer with one dealership location or twenty.

Why truck dealer SEO is a different sport

Retail car SEO is a fight for a shopper who already knows the model. Truck dealer SEO is a fight for a buyer who knows the job. The query is "class 6 box truck 26 ft liftgate near me" or "f-550 4x4 chassis cab 84 ca" or "kenworth t680 dealer central valley." The buyer is a fleet manager, an owner-operator, a municipal purchasing agent, or a body company sourcing chassis for a customer order. They search during the workday, from a desk or a cab, and they compare on spec, availability, and proximity to their service loop.

That changes the shape of the site you need. A retail dealer can live on a brand-plus-model taxonomy. A truck dealer needs three overlapping taxonomies: geography (every county and metro in the territory), application (dump, box, refuse, tractor, service body, wrecker), and spec (class, GVWR, wheelbase, CA, engine, transmission, axle configuration). The dealer that builds all three, and links them to each other, is the dealer that shows up whichever way the buyer phrases the need.

The second difference is fixed ops. A Class 8 tractor is a revenue machine for its owner, and downtime is measured in dollars per hour. Service and parts searches ("cummins x15 dealer near me," "freightliner service open saturday," "detroit dd15 aftertreatment repair") are a bigger share of a truck dealer's search demand than a car dealer's, and they are far more urgent. A truck dealer site that treats service as a single page with a form is leaving the most defensible traffic on the table.

The third difference is the OEM. Freightliner, International, Kenworth, Peterbilt, Volvo, Mack, Isuzu, Hino, and the Ford and Ram commercial programs all run dealer locator pages that rank for brand-plus-city. The OEM is not your competitor, but its locator will absorb the brand query unless your dealership page is stronger. Our franchised dealer work deals with the same dynamic on the retail side; on the truck side the OEM locator is often the only competitor in the map pack.

The five plays at a glance

Each play below has moves and a done-when. The order matters. Territory pages first because they win the map pack and the "dealer near me" queries that everything else depends on. Feed hygiene second because a broken feed poisons every VDP the site publishes. The listing-site play third because it decides how much of your inventory demand you keep. Fixed ops fourth because those pages compound for years. Spec content and AI citations last because they need the first four in place to have anything to cite.

Play 1: own the territory before the truck

Truck OEMs assign territories. Your dealership in the county seat is responsible for the whole county and probably three more. Buyers in those counties search "peterbilt dealer near me" and get a map pack that shows whichever dealership location Google associates with their location. If your only pages are one dealership location page and an SRP, you are relying on Google to guess that you serve a county 70 miles away. It will not guess. It will show the OEM locator, a competing brand's dealer in the next metro, or nothing.

The fix is a territory page set. One page per dealership location, one page per served county or metro without a dealership location. The county pages are not thin doorway pages. They carry what the buyer in that county needs: the nearest bay and how far it is, whether mobile service covers the county, delivery terms for new units, which industries you serve there (agriculture, construction, refuse, regional haul), and live inventory relevant to those industries. A county with three paving contractors and a quarry gets dump and mixer inventory on its page. A county on an interstate corridor gets day cabs and sleepers.

The Google Business Profile piece is not optional. Google's own guidance is one profile per physical location, and it says a service area should not extend much beyond about two hours of driving from the base, per the guidelines for representing your business on Google. For a truck dealer that maps well: your dealership profile with a service area that covers your mobile service radius, and a separate profile for every other dealership location. We cover the multi-location mechanics in depth in our multi-location Google Business Profile piece, and the same rules apply whether the dealership locations sell cars or Class 8 tractors.

Play 2: fix the inventory feed before you touch a page

Every truck VDP is a rendering of a feed row. If the feed row says the wheelbase is 0, the VDP says the wheelbase is 0, and so does the marketplace listing, and so does the Vehicle Ads listing, and so does whatever an AI engine reads when it crawls the page. Feed hygiene is the highest-leverage technical work a truck dealer can do because it repairs hundreds of pages at once. It is also the work most dealers skip, because the feed is "the DMS's problem" or "the website vendor's problem." It is your problem. You are the one whose name is on the page.

Start with a hand audit. Pull ten units at random and walk out to the lot with the printout. Compare GVWR, wheelbase, CA, body type and length, engine, transmission, rear axle ratio, suspension, mileage, and stock number. In our experience with truck dealer groups, the fields that go wrong most often are CA (missing or copied from a different wheelbase), body type (a chassis cab tagged as a box truck because the last unit with that stock prefix was a box), and GVWR (rounded to the class boundary instead of the plate value). Each of those errors ends a sale, because the body company or fleet buyer checks the plate before they sign.

Then standardize. Write a field dictionary that every department and every vendor uses: one name for each spec, one unit, one format. Pounds not tons. Inches for wheelbase and CA. Body length in feet with a decimal. Axle configuration as 4x2, 6x4, 8x6, not "tandem" in one row and "6x4" in the next. The dictionary is boring and it is the thing that makes the class pages, the application filters, and the structured data all work, because they filter on those fields.

Sold-unit handling deserves its own rule. A sold truck's VDP should 301 to the class or application page within a day. A 404 wastes whatever links and ranking the VDP had. A page that stays live for months saying "this unit has been sold" with no truck is worse: it ranks, the buyer clicks, and they learn you do not maintain your site. Our dealership SEO versus marketplaces analysis goes into why marketplaces win the freshness signal by default and what your own site has to do to keep up.

Play 3: listing sites are rented, VDPs are owned

TruckPaper and Commercial Truck Trader are not the enemy. They reach buyers you cannot reach: an owner-operator in another state, a fleet that only ever searches the marketplace, a broker sourcing a specific model year. Keep the feeds live. The mistake is treating the marketplace listing as the canonical version of the unit and your own VDP as an afterthought. When that happens, every spec search in your own territory lands on a marketplace page that shows six competing dealers next to your truck.

The play is to make your VDP the richest version of every unit. More photos than the marketplace listing, including the spec plate, the body interior, the frame rail behind the cab, and the tires. The full spec sheet. Upfit details, body brand, and lead time if the unit is in build. A unique description that says what the truck is for and who typically buys it. Financing and warranty notes. And the dealership that physically holds the unit, with a link to that dealership location page and its GBP.

The aggregation layer matters as much as the VDP. A buyer searching "used class 8 day cab for sale" is not going to land on one VDP. They land on a page that lists all of your day cabs. If that page is a generic SRP with URL parameters, the marketplace wins because its category page is cleaner. Build class and application pages that pull live inventory into a real page with a real heading, real copy about the category, and the filters a truck buyer uses (class, body, engine, transmission, mileage band, year). The VDP and SRP guide lays out the template rules for both page types.

Play 4: parts and service pages carry the uptime searches

A fleet manager with a tractor in limp mode does not search "truck dealer." They search the engine, the fault, and the town: "dd15 derate repair near me," "cummins isx dpf cleaning," "allison transmission service bay open now." Those searches are urgent, local, and high-value, and most truck dealer sites answer them with one "Service" page and a form. That page cannot rank for fifty engine-and-symptom queries. Fifty pages can.

Build the fixed ops section as its own site within the site. A page per service line, a page per engine family, a page per dealership location's parts counter, and a page for each capability that matters to a fleet: DOT inspections, PM contracts, mobile service, after-hours coverage, warranty work by OEM. Each page carries the symptoms the fleet manager searches, what the diagnosis usually involves, typical time in the bay, and how to schedule. The specifics are what rank and what get cited. Our auto repair local SEO and AI piece covers the symptom-page pattern for independent shops; the truck dealer version is the same pattern with engine families instead of consumer models.

Parts is a separate demand pool. Fleets and independent shops search part numbers, categories, and brands, and they search whether you deliver. A parts counter page per dealership location with delivery routes and cutoff times, plus category pages for the high-turn parts (filters, brakes, lighting, aftertreatment components, mirrors and glass), captures searches that the service pages do not. If the dealer runs a parts ecommerce storefront, that storefront needs its own fitment and category structure, which is a bigger topic we cover for aftermarket and OEM parts sellers.

The conversion end of fixed ops is where the traffic turns into repair orders. Every service page needs a route to a scheduler or a phone number that a human answers during bay hours, and the call needs to be tagged so the RO can be attributed. Fixed ops pages that rank but end in a generic contact form leak the urgency: the fleet manager calls the next dealer that shows a phone number.

Play 5: spec content and AI citations

Before a fleet buyer searches inventory they search the spec. What GVWR do I need for a 16 ft dump with a 10 yard body? What CA fits a 26 ft box? Is a Class 5 enough for a crew cab pulling an equipment trailer, or do I need a Class 6? The Federal Highway Administration's class boundaries, published by the Department of Energy's Alternative Fuels Data Center, run from Class 3 at 10,001 to 14,000 lb up to Class 8 above 33,000 lb, and a surprising number of buyers do not know which side of a boundary their job lands on. The dealer that explains it plainly earns the visit, and the visit ends on an inventory page.

Spec content is also what AI engines quote. When a fleet manager asks ChatGPT or Perplexity "what class truck do I need for a 20,000 lb payload" or "kenworth dealer near bakersfield with mobile service," the engine assembles an answer from pages it can parse and trust. A page with the GVWR table, the class boundaries, the payload math, and a clear statement of which dealership location serves which counties is exactly the kind of page that gets cited. A page that says "contact us for details" is not. We wrote up the mechanics of how AI engines pick which dealers to name and the same signals apply here: consistent entity data, quotable answers, and territory pages that say plainly where you operate.

Structured data belongs here because it is what makes the site legible to machines. Organization markup for the group, a local business entry per dealership location with the same name, address, phone, and hours as the GBP, and vehicle markup on the VDPs that reflects the cleaned feed. Google retired its dedicated vehicle listing rich result in 2025, so do not expect a special search feature from the markup. Add it anyway. The value is in giving every crawler, including the AI engines, a machine-readable statement of what the truck is and who holds it. Our generative engine optimization service tracks which of a dealer's pages get cited and feeds that back into what to write next.

How to sequence the ninety days

The plays overlap. Territory and feed work start the same week because they involve different people: the marketing lead and the web vendor on territory pages, the inventory manager and the DMS admin on the feed. The listing-site work follows the feed because it depends on clean VDPs. Fixed ops pages start once the dealership pages exist to link from. Spec content starts last and never stops.

Expect the first movement in the map pack and the territory queries inside the first month, because GBP and territory pages change what Google shows quickly. Inventory and fixed ops rankings typically take a quarter to settle, because they depend on crawl and on links between the new pages. AI citations lag both, because the engines need to encounter the new pages repeatedly before they trust them. The sequence in the Midwest truck dealer group case study, a composite drawn from this kind of engagement, followed this order, and the fixed ops pages ended up as the largest single source of tagged calls.

Reporting has to be built for a dealer principal who reads it in a minute. Territory rankings by county. Inventory leads by source. Fixed ops calls and scheduler bookings by dealership location. Citations by engine and by page. Our reporting and analytics service wires those four views into one dashboard so the plan can be judged on units, ROs, and parts tickets rather than on sessions.

What to do this week

Print ten VDPs and walk the lot. Compare every spec field to the plate. That one hour will tell you whether the feed is a Play 2 problem or a crisis. Then open Google in an incognito window, search your primary brand plus the name of a county you serve but do not have a dealership location in, and see what comes back. If the OEM locator or a competitor owns that result, Play 1 is your first month. If you have a dealership location page and it does not show, Play 1 is still your first month, because the page is not saying what it needs to say.

Then count your service pages. If the answer is one, the fixed ops play is where the fastest revenue is hiding, because the demand is already there and nobody in your metro is answering it. If you want us to run the audit and build the ninety-day sequence for your dealership locations, book a consultation and bring the feed export. We start with the lot walk.

See where you are cited today

A free snapshot audit of your rankings and AI citations before we ever talk.