Dealer sites and used car listings usually load their inventory through a widget, which means Google never sees a single vehicle.
A car dealer or automobile website works when inventory renders as real indexable pages rather than loading through a widget, when test drive and service bookings take one tap, and when pricing is clear enough that a buyer can shortlist. Most dealer sites in NCR fail the first of those without anyone realising.
This is the defining technical failure of the category. Vehicles loaded through a JavaScript widget from another domain are invisible to search. Server-rendered listing pages on your own domain are the difference between a site with a hundred cars and no traffic and one that ranks.
Someone searching for a specific model and variant wants a page about it, with price, variant, kilometres, ownership and photographs. A filterable grid with no individual pages ranks for nothing.
The conversion is a test drive or a showroom visit, not a purchase. Make it a single obvious action bookable on WhatsApp, because that is where automotive enquiries arrive here.
Service customers are a different visitor with a different urgency from car buyers. They want slot availability, pickup and drop, and rough cost, and they should not have to navigate a sales site to find it.
EMI indication, documentation needed and how exchange valuation works. These questions come up in every conversation, and answering them on the site shortens the sales cycle.
Vehicle galleries are heavy and buyers browse on phones. Compression, modern formats and lazy loading below the fold, otherwise the listing nobody waits for is not a listing.
| Problem | What it costs |
|---|---|
| Inventory in a JavaScript widget | Not a single vehicle is indexed |
| No individual vehicle pages | Invisible for model and variant searches |
| Service buried inside the sales site | Service customers leave |
| No price on used listings | Buyers cannot shortlist |
| No WhatsApp | Loses the dominant enquiry channel |
| Sold vehicles deleted | Throws away pages that had begun ranking |
| Ask them | Good answer | Walk away if |
|---|---|---|
| Who owns the site and files? | You do, unconditionally, in the contract | Ownership depends on staying with them |
| Can I open three sites you built? | Live URLs you can check | Screenshots and a PDF |
| What is explicitly not included? | A written list with change pricing | Everything is included |
| How will we know it worked? | A metric agreed before work starts | Activity reports |
The exclusions question decides whether the final invoice matches the quote.
Almost always because inventory loads through a JavaScript widget from a third-party domain, so search engines never see the vehicles. Server-rendered listing pages on your own domain are the fix and the single biggest difference in this category.
For used inventory, yes, or at minimum a page per model and variant. Someone searching for a specific model wants a page about it. A filterable grid with no underlying pages gives search engines nothing to rank.
A test drive booking or a showroom visit, not an online purchase. Make it one obvious tap, and offer WhatsApp, because automotive enquiries in this market arrive there more than through forms.
Same site, separate path. Service customers have different urgency and different questions from car buyers, and making them navigate a sales-focused site to book a service loses a large share of them.
Yes. Buyers shortlist on price and a listing without one gets skipped. If the price is negotiable, say so alongside the figure rather than omitting it entirely.
Archive them, marked as sold, rather than deleting. They accumulate ranking over time and demonstrate turnover, and deleting throws away pages that had begun to gain traction.
Send us what you are trying to fix and we will tell you what it takes, what it costs, and whether we are the right people for it. If we are not, we will say so.