Every dealer we talk to has the same question in a different accent: is my website vendor holding back my SEO? The honest answer is that every dealer platform holds back some things and none of them holds back everything. They are built to serve OEM programs, inventory feeds, and compliance rules for thousands of dealership locations at once, and that means the template is shared and the feed is the product. The ceiling is real. It is also usually higher than the dealer thinks, and the work that gets you to it is work most dealers have not done yet.
What a dealer platform controls, and why
A dealer website platform is not a CMS with a car theme. It is a hosted system that ingests inventory from the DMS or a feed provider, renders it into search results pages and vehicle detail pages, enforces OEM brand rules and legal disclaimers, syndicates specials and incentives, and serves the whole thing to hundreds or thousands of dealership locations from shared templates. The OEM certifies the platform for its co-op program, and certification means the platform promises the OEM that certain things look and behave the same at every store.
That is why the VDP looks the way it does and why you cannot move the price block. It is why the SRP URL carries the parameters it carries. It is why schema on inventory pages is whatever the platform emits. None of that is the vendor being difficult. It is the vendor keeping its OEM certification, which is what makes your co-op dollars eligible. The trade is a site that ranks acceptably for your brand and your city out of the box, at the cost of a site you cannot restructure. For most franchised dealership locations that trade is correct, and the franchised dealer program we run assumes it.
The ceiling comes from the same place. Two dealership locations on the same platform, same OEM, same metro, start with nearly identical sites. The one that ranks higher is the one that used the open surface: built the pages the template does not ship, wrote the copy, earned the links, kept the Business Profile clean, and connected all of it. When both have done that, the ceiling is reached and the platform itself becomes the constraint. Most dealers are nowhere near it.
The ceiling, platform by platform
What follows is a category-level read of each platform we work on regularly. Capabilities change with package tiers, OEM programs, and release cycles, so treat this as what dealers typically can and cannot change rather than a feature list, and confirm the specifics for your package with your rep. We link to our platform pages for the detail on how we work inside each one.
| PLATFORM | TYPICALLY LOCKED | TYPICALLY OPEN | WHERE THE CEILING TENDS TO SIT |
|---|---|---|---|
| Dealer.com (Cox Automotive) | VDP and SRP templates, inventory feed structure, core schema, URL patterns | Custom pages, page copy and metadata, blog, image assets, internal links, navigation within limits | Custom page build and depth; dealers who fill the page library reach a high ceiling |
| DealerOn | Inventory templates, feed, base schema | Custom pages, metadata, content blocks, blog, localized landing pages | Content volume on custom pages; the platform gives more page-level control than many |
| Dealer Inspire (Cars Commerce, WordPress-based) | Inventory rendering layer, OEM-compliant templates | Wide page authoring through the WordPress layer, custom post types in many packages, metadata, blog | High. The WordPress base means the open surface is large; the ceiling is usually effort, not platform |
| DealerFire (DealerSocket / Solera) | Inventory templates, feed, schema on inventory pages | Custom pages, metadata, blog, specials pages | Custom page depth and how well the pages link back to inventory |
| Sincro (Ansira) | OEM program templates, inventory structure | Page copy, metadata, custom pages within the program's allowance | Program allowances vary by OEM; the ceiling is often the program, not the platform |
| CDK Global websites | Inventory templates, feed, DMS-driven structure | Custom pages, metadata, content sections, blog | Custom page build; DMS integration is the strength, page flexibility is where dealers hit limits |
| Overfuel | Core inventory rendering and structured page framework | Page content, metadata, custom pages, with an emphasis on performance and structure | Newer platform with a smaller install base; the ceiling is less mapped, and the open surface is designed for content |
A few notes behind the table. Dealer Inspire is the outlier because its WordPress foundation gives a dealer or an agency an authoring layer that most certified platforms do not expose, which is why groups with real content programs often end up there. Dealer.com and DealerOn both have a mature custom page system that most dealership locations use for a handful of pages and could use for a hundred. Sincro's ceiling is frequently the OEM program allowance rather than the platform. CDK's advantage is how tightly it connects to the DMS, which shows up in inventory freshness. Overfuel is built more recently and leans into page performance and structured content, but with a smaller install base the edges are less well mapped.
Illustrative: share of the platform's open surface a typical franchised dealership has actually used when we audit it, by platform family. Same pattern everywhere: most of the room is unused.
The four things almost no platform lets you change
First, the VDP template. Layout, the order of the blocks, the price and disclaimer treatment, the lead form, the photo gallery. On OEM-certified packages this is locked by design, and the dealer's influence is limited to what flows in from the feed (photos, descriptions, options) and to any custom content module the platform exposes below the fold. Second, the SRP structure: the URL pattern, the parameters, the filter behavior, and whether filtered views are indexable. A dealer can sometimes request a change to indexation rules, but the structure is the platform's. Third, the schema on inventory pages. The platform emits it. Note that Google retired its dedicated vehicle listing rich result and removed the documentation for it in September 2025, per its search documentation changelog, so the inventory markup a platform emits is now about machine readability rather than a search feature. Fourth, the inventory feed structure: which fields exist and how they are named is set upstream, between the DMS, the feed provider, and the platform.
The practical consequence is that a dealer cannot fix inventory-page SEO by editing inventory pages. They fix it by fixing the feed (photos, descriptions, option data, sold-unit handling) and by building the pages around inventory that the template does not ship: model landing pages, body-style pages, trim comparisons, local pages. Our Vehicle Ads and SEO alignment piece covers the feed side; the rest of this piece is about the pages.
The five things almost every platform does let you change
First, pages you create. Every platform in the table supports custom pages, and this is where most of the SEO ceiling lives. Model research pages, body-style pages ("used trucks," "hybrid SUVs"), trim and comparison pages, financing and credit pages, service line pages, parts pages, and local pages for the cities you sell into. A dealership location with five custom pages and a dealership location with eighty custom pages are on the same platform with very different ceilings. Second, the copy and metadata on those pages and on most standard pages: title tags, meta descriptions, headings, body copy, and often the image alt text. Third, internal linking. Most platforms let you add links inside page content and in some navigation slots, which is enough to connect the custom pages to each other and to the inventory they support.
Fourth, images and media: file names, alt text, and the images themselves on non-inventory pages. Fifth, a blog or news section, which nearly every platform includes and nearly every dealership location leaves empty or fills with OEM press releases. A blog on a dealer domain that publishes genuinely local, genuinely specific content (which models are on the lot for towing season, what the service drive sees in winter, how the local incentive stacks) is one of the few surfaces that AI engines cite from dealer sites, because it reads like a person wrote it. The how AI engines recommend car dealers breakdown goes into why that kind of page gets named and the template pages do not.
When a content layer beats a vendor switch
A platform migration is expensive in ways that do not show on the invoice. URLs change and redirects are never perfect. Custom pages are rebuilt by hand, and some are lost. Rankings dip during the transition and take a quarter or two to recover, sometimes longer. The OEM program may require the new vendor anyway, which removes the choice. And at the end of it, the dealer is on a different platform with the same empty open surface, because the problem was never the platform.
A content layer is the alternative: keep the platform, and treat its open surface as the site you actually build. Custom pages for every model, body style, and city. Service and parts pages for every line. A blog that publishes on a schedule. Metadata written by hand. Internal links that connect all of it to inventory. A Business Profile per dealership location that agrees with the site. And measurement that shows which pages produce leads and ROs. This is the same work you would do after a migration, done now, without the migration. In our experience it reaches the platform's real ceiling in two to three quarters, and most dealership locations never hit that ceiling because the demand they compete for is satisfied before the platform runs out of room.
Switch when the open surface is genuinely full and the constraint is structural: you need indexable filtered inventory views the platform cannot provide, you need page-level control the platform does not expose at any tier, or the platform's rendering makes pages slow in a way the vendor cannot fix. Switch when the OEM program changes and the choice is made for you. Switch when the group is consolidating dealership locations onto one platform for operational reasons and SEO is along for the ride. Do not switch because a dealership location with fifteen pages is not ranking; that dealership location needs pages. The multi-location dealer group case study, a composite, went the content-layer route on the platform the group already had, and the group's rankings moved before the vendor conversation ever happened.
The decision in one table
| SYMPTOM | LIKELY CAUSE | CONTENT LAYER OR SWITCH |
|---|---|---|
| Ranks for brand plus city, nothing else | Custom pages not built | Content layer |
| Ranks for models, not for used body styles or local terms | Body-style and local pages missing | Content layer |
| Inventory pages have thin descriptions and few photos | Feed, not platform | Fix the feed on the current platform |
| Filtered inventory views cannot be indexed and you need them | Platform SRP structure | Ask the vendor; switch if the answer is no and the demand justifies it |
| Pages are slow and the vendor cannot improve it | Platform rendering | Switch, after confirming the measurement |
| OEM program mandates a vendor change | Program | Switch, with a redirect plan |
| Group consolidating on one platform | Operations | Switch, with the content layer rebuilt on the target |
| Blog empty, metadata default, few internal links | Effort | Content layer |
What to do before you call your rep
Count the custom pages on the site and list what they cover. Count the blog posts from the last twelve months. Pull the title tags for the top fifty pages and see how many are the platform default. Check whether the service and parts departments have more than one page each. Then open the platform's admin and find the limit on custom pages for your package. If you have used less than half of it, you have found your ceiling and it is not the platform. Build the pages. Write the metadata. Publish weekly. Link it together.
If you have used the open surface and the constraint really is structural, then the conversation with the vendor is specific: this is the indexation rule we need, this is the page control we need, this is the speed we need, can you provide it at any tier. A yes keeps you on the platform. A no makes the switch a decision rather than a guess. Either way, our audit service starts with exactly this inventory of what the platform has locked and what the dealership has left unused, and the result is a page list you can start on the same week.
See where you are cited today
A free snapshot audit of your rankings and AI citations before we ever talk.
Josh leads SEO and generative engine work for dealerships, truck dealers, fleets, and automotive software companies at Something Inc., getting them ranked and cited across every major AI engine.