Sold units still look available
The feed must drive VDP status. A shopper should not drive for a VIN that left the lot.
Live inventory that matches a dealer visit
Automotive to Make Live Inventory Match a Dealer Visit
A shopper books a visit from a VDP. The unit is sold, or the rooftop is a city clone. This work makes the public lot match what a person can still see on the drive.
- Lot
- VIN
- Rooftop
- Visit
Position
The lot is the catalog. The visit is the checkout.
Search intent is a shopper who named a model year and wants a unit they can see. Keyword targeting maps that query to a nameplate hub and a stock-aware VDP. Electronics spec sheets are not this job. Travel itineraries are not this job.
Electronics specifications
Open electronics for model, protocol, compatibility, and a device cart. That is not a dealer lot.
Open Electronics specificationsLocal SEO delivery
Open local SEO to implement dealer-market and service-area visibility.
Open Local SEO deliveryBusiness Profile operations
Open this for profile governance, categories, locations, and listing work.
Open Business Profile operationsIndustry chooser
Open the hub when vehicle retail has not yet been selected.
Open Industry chooserTopical relevance is model, live inventory, rooftop, and service. Semantic keywords are nameplate and trim names written on those pages. Keyword density is not a metric.
AI search and generative search will quote a price if they can fetch a live VDP. AIO will skip a unit that the feed already sold. Entity optimization starts with VIN or stock identity plus a rooftop that exists.
LLM visibility is a later prompt check. First the feed and the visit path must agree.
When this fits
Use this when the VDP and the lot disagree
You retail vehicles. Public pages show sold units and cloned rooftops. The job is lot, VIN, rooftop, visit.
Prior years orphan when the new model launches
Nameplate hubs need an owned end state. Deleted year pages break inbound model queries.
OEM brochure copy fills every rooftop
Entity optimization needs dealer identity. Identical city clones fail a visit test.
Service intent lands on a sales grid
Appointment paths must stay distinct. A shopper who needs a service drive should not hit a new-car VDP.
Process
Lot. VIN. Rooftop. Visit.
We prove the unit is on the lot, then we prove the rooftop, then we book the visit.
-
Lot
Open the inventory feed beside the model hub. Confirm which units are still public. Topical relevance is live stock, not an electronics accessory list.
Outcome A public set that matches the feed.
-
VIN
Trace one stock number through the VDP. Sold, in transit, and available need honest states. Keyword targeting does not keep a sold VDP as if it were new.
Outcome A VDP rule with an owner and an end state.
-
Rooftop
Match the VDP to a dealer you operate. Entity optimization uses a real address and hours, not a city template.
Outcome Rooftop pages that a visitor can use.
-
Visit
Book sales or service from the same unit or rooftop. If the form ignores the stock number, the automotive path is unfinished.
Outcome A visit check tied to the same VIN or service type.
Deliverables
What the dealer group can operate
Artifacts follow the feed and the rooftop. They are not a travel itinerary packet.
Nameplate and lot map
Query classes mapped to model-year hubs and stock-aware VDPs.
VDP status brief
Available, in transit, sold, and successor rules.
Rooftop truth list
Dealers you operate. City clones marked for close.
Visit path brief
Sales and service forms that carry stock number or appointment type.
Handoff sheet
Owner, review date, and whether local SEO or Business Profile work is next.
Benefits
What clearer automotive decisions change
Shoppers drive for units that exist
The VDP matches the lot, not last week’s feed.
Rooftops stop cloning
Dealer pages name a place you can visit.
Service keeps its own door
Appointment intent does not drown in sales grids.
Specialists inherit the VIN rule
Technical and local work receive feed fields, rooftops, and checks.
Methodology
The feed is the source, the visit is the test
The unit of work is a vehicle search system tied to a real rooftop. Device specs wait on electronics.
We start with the inventory feed and one VDP. Search results show how people name models. The site shows where those names point at sold units.
We classify demand by lot and rooftop. Missing year hubs, sold VDPs, and fake dealers get different treatments.
The dealer group confirms the lot. SEO does not invent a VIN. Publication follows confirmation.
Acceptance is a feed-true VDP, a real rooftop, and a visit form that matches. Measurement records use. It is not a traffic guarantee.
- Automotive consulting lead Keeps the lot map and prepares the handoff.
- Inventory owner Confirms feed fields and VDP status rules.
- Rooftop owner Confirms dealer identity and hours.
- Web owner Implements hubs, VDPs, and appointment templates.
- Analytics owner Tracks visit and sold-VDP paths without inflating cause.
First working session
Put the inventory feed beside one VDP
We follow one unit from feed to visit.
We open the feed and a live VDP. We trace stock number, price, and rooftop through the template. Conflicts are logged with the source.
We inspect neighboring objects: nameplate hubs, prior years, service paths, city dealer pages. We decide URL, sold state, or close.
The session ends with a first decision on that unit. Missing feed ownership is an operations action.
A second VIN tests the rule, especially where new, used, and service split the visit.
AI systems
Let models quote units that are still on the lot
Generative search will send a shopper to a sold VIN if the VDP still looks live.
Entity optimization starts with nameplate and stock identities that match the feed. AI search and AIO may summarize a VDP, skip it, or mix a marketplace. We prepare fetchable status and test outputs. We do not claim placement.
Keep stock identity stable
VIN or stock number, title, and markup should agree.
Publish status in text
Sold and available cannot live only in a dealer widget.
Measure LLM visibility separately
Dated prompts and recorded answers.
Schema
Markup should describe the unit on the lot
Structured data cannot create a rooftop.
Mark vehicles that are still available
Do not attach offers to a sold VDP that has no end state.
Use AutoDealer only for a real rooftop
Address and hours must match operations.
Recheck after each feed run
Valid markup can still describe a unit that left overnight.
Who we work with
Dealer-group digital leads, inventory owners, and service directors
The people who own the lot must review. SEO cannot certify a VIN they do not stock.
Retail leadership
Names which rooftops and nameplates stay public.
Feed and web teams
Keep VDP status current and close city clones.
Analytics teams
Watch visit and sold-unit paths within the evidence you have.
Questions
Frequently asked questions
What does automotive consulting decide?
It decides whether live lot inventory still matches a dealer visit. Search intent is nameplate, VIN or stock, rooftop, and an appointment. Electronics spec sheets and travel itineraries are other doors.
Why start with an inventory feed?
The feed is what a shopper should find on the VDP. Keyword targeting sends people to a model. If the feed and the page disagree, the visit wastes a trip.
What happens when a unit sells?
The VDP needs an owned end state. Delete without a parent breaks inbound links. Entity optimization prefers a sold state that points to the nameplate or a similar unit still on the lot.
How is this not electronics consulting?
Electronics is a device SKU and a spec table. Automotive is a vehicle on a lot and a rooftop you can visit. Do not put a works-with list on a VDP.
How is this not travel consulting?
Travel sequences destination and season before a trip books. Automotive sequences inventory before a dealer visit. Do not put an itinerary on a service-drive page.
How should keyword density work on a VDP?
Keyword density is not a metric. Name the trim and the stock number where they identify the unit. Repeating “deal of the week” cannot replace a VIN-aware status.
Can you guarantee more showroom traffic?
No. Supply and demand move. We commit to feed-true VDPs and real rooftops. We do not guarantee rank or visits.
What should we bring first?
Bring the inventory feed, one live VDP, rooftop records, and service appointment paths. We will mark where the lot and the page disagree.
Dealer path, not a spec sheet or a trip
Does this inventory feed still match the VDP a shopper would drive to?
Bring the inventory feed, one live VDP, rooftop records, and service appointment paths. We will name the first lot decision and whether electronics or travel is the wrong door.
- VIN-aware status
- Nameplate parent
- Real rooftop
- Visit that matches the lot
Start with the inventory feed. We check it against a VDP someone might visit this week.