Automotive Sales & Service · project showcase · inventory and page generation
Every vehicle page built from one feed — including on the day the vehicle sells
A dealership's inventory turns over continuously; its website usually runs on a different clock. Paid ads point at individual cars. This is the page-generation system built from the feed itself, where the hardest, most carefully designed page is the one for a vehicle that has just sold.
At a glance
The engagement in brief
Services
- Web Development
- Technical SEO
- Landing Pages
- Content Systems
- CRO
- Reporting
Stack
- Inventory feed
- Generated vehicle pages
- Structured data
- Redirect rules
- Lead form with vehicle identifier
- Photography standard
- Google Analytics 4
- Google Tag Manager
The situation
What we walked into
Two systems describe the same cars on two different schedules. The feed knows what is on the lot this morning; the website knows what was on the lot when somebody last touched it. Advertising sits on top of both and points at specific vehicles by name and price. The gap between the feed and the page is where a click lands on a car that is gone, a price that has moved, or a photograph set that belongs to a different trim, and none of those failures announce themselves to anybody inside the dealership.
The design constraint was that a vehicle sold at four in the afternoon must not still have a live advertisement pointing at its page the next morning.
What we found
The diagnosis
01
The sold vehicle is the hardest page on the site
It cannot return a 404, it cannot stay live as though the car is available, and it should not silently redirect to the homepage, which is the most common choice and the worst one. The right answer is a page that says the vehicle has gone and offers the three closest current matches, generated from the same feed that removed it.
02
A lead form without a vehicle identifier destroys the only attribution that matters
A dealership does not need to know that a lead came from the website. It needs to know which car the person was looking at, because that determines who follows up, what they say, and whether there is anything comparable to offer if the car is gone. The identifier travels with the submission into the CRM and it is a single field.
03
Model pages and vehicle pages answer different questions and have different lifespans
A model landing page is written once and earns for years. A vehicle page exists for as long as the car is on the lot. Generating both from the same feed but treating them as one page type is how dealerships end up with thousands of thin pages and nothing that ranks.
04
Structured data is the cheapest part of the build and the first thing to drift
It is generated from the record rather than maintained by hand, for the same reason the address is: anything typed twice will eventually disagree with itself, and the version search engines read is the one nobody looks at.
The number behind it
What this is built around
**95% of car shoppers use online resources before visiting a dealer and 61% call after researching** (Invoca / LSA), and auto *service* now converts paid search at **15.51%** vs **6.01%** for vehicle sales (WordStream 2026) — so a dead vehicle page wastes the highest-intent traffic the dealer buys.
What we built
The system
The feed is the source. Each vehicle record generates a detail page, its structured data, its photograph set and a lead form carrying the vehicle identifier as a hidden field. Model landing pages are authored separately and reference the feed for current availability rather than being generated from it. A sold rule fires from the feed: the detail page converts to a gone-page with three current alternatives, a redirect is written, and the vehicle is flagged for ad pause in the same pass. Reporting joins lead records back to the feed so performance can be read by model, trim and days on lot rather than by page URL.
The sequence
How it was delivered
Week 1
Feed mapping
Feed fields mapped to page templates, gaps and inconsistencies documented against the DMS
Owner: OmniFlow
Weeks 2–4
Page generation
Detail pages, structured data and photograph handling generated from the record
Owner: OmniFlow
Weeks 3–5
Sold rule
Gone-page with three current alternatives, redirect rule, ad pause flag, all fired from the feed
Owner: OmniFlow
Weeks 4–6
Attribution
Vehicle identifier carried into the CRM, reporting joined back to the feed by model and trim
Owner: OmniFlow + dealership CRM
Outcome
What shipped
This entry makes no performance claim. It documents a generation system and the rule set that keeps it honest as inventory turns. The test applied throughout was what happens on the day a car sells: whether the page, the redirect, the advertisement and the CRM all learn about it from the same event, or whether four separate people have to remember.
Reporting
What you would actually see
These are the surfaces this engagement is run and measured from, shown with representative figures built around the benchmarks cited on this page. Every account we run reports into views like these, and you keep ownership of all of them.
These are demo dashboards. They show the reporting surfaces this engagement is run and measured from, with representative figures generated around the published benchmarks cited on this page — not a client account and not a client result. Live reporting for your own account replaces every number here.
Google Analytics 4
Automotive Sales & Service · all web data
Sessions
4,603
+71.4%
Key events
112
+89.2%
Session key event rate
2.4%
+0.7%
Engagement rate
61.6%
+7.7%
Sessions by month
Dashed line marks the month the engagement started.
| Session default channel group | Sessions | Key events | Rate |
|---|---|---|---|
| Organic Search | 1,764 | 54 | 3.1% |
| Paid Search | 1,091 | 28 | 2.6% |
| Direct | 874 | 28 | 3.2% |
| Referral | 437 | 15 | 3.4% |
| Organic Social | 436 | 11 | 2.5% |
CRM pipeline
Automotive Sales & Service · inbound and outbound
Leads created
141
+93.1%
Qualified
71
+107.1%
Meetings booked
42
+111.7%
Answered on first attempt
72.9%
+16.8%
Leads created by month
Dashed line marks the month the engagement started.
| First-touch source | Leads | Qualified | Meetings |
|---|---|---|---|
| Google Ads — high intent | 44 | 22 | 10 |
| Organic search | 38 | 19 | 9 |
| Business Profile — call | 27 | 14 | 6 |
| LinkedIn outbound | 20 | 10 | 5 |
| Referral | 13 | 7 | 3 |
Honestly
What we would do differently
We generated the pages before we built the sold rule, which produced a system that was very good at creating pages and had no opinion about ending them. Within a fortnight there were live pages for cars that had gone and live ads pointing at them. Sold handling belongs in the first release alongside page generation, not in the second one after somebody notices.
Next
Start the same conversation
Start the same conversation
Tell us what you are working on and we will say plainly whether this is the right shape of engagement for it.