The platform owns the template. You own the seam.
Most dealer-group sites run on a managed platform, and that platform decides what the technical work can even be.
Dealer.com, DealerOn, Dealer Inspire, DealerSocket, Sincro, Dealer eProcess. Each one owns the template, the inventory feed, and some portion of the head markup. The group owns the strategy sitting on top. Technical SEO is everything that lives in the gap between those two facts.
This is why generic technical SEO advice fails on dealer sites. Half of it assumes you can edit anything, which you cannot, and the other half assumes the constraint is permanent, which it also is not. What is actually editable differs by vendor and sometimes by contract. Some instances allow injected structured data and custom page types. Others restrict head markup and route robots and sitemap changes through a vendor ticket.
So the first move is never a fix. It is establishing what this specific instance permits, in writing, before anything gets committed to. How the work runs per platform →
Working inside the constraint is not a compromise position. A group that migrates to escape a technical problem usually inherits a new set of them plus a traffic drop, which is the most expensive way to solve a schema issue ever devised.
- Platform owns
- Template structure, the inventory feed, VDP generation, most of the rendering path.
- Usually editable
- Injected structured data, custom page types, internal linking, on-page content.
- Vendor ticket
- Robots directives, sitemap composition, canonical logic, parameter handling.
- Genuinely fixed
- Core rendering behavior, and whatever the contract says it is.
The line moves per vendor and per contract. Assuming it is a fast way to commit to something you cannot deliver.
Four workstreams, in the order they usually matter.
They are not equally urgent on every site. The audit decides the order, because fixing Core Web Vitals on a site the engines cannot parse is money spent on the wrong layer.
Schema deployment
Inventory, location, FAQ, organization, and review markup, validated against the formats AI engines consume rather than against a generic rich-result test. Vehicle schema is the piece dealer platforms most often ship incomplete. The vehicle schema detail →
Crawl architecture
Robots directives, sitemap hygiene, internal linking, parameter handling, faceted nav indexation. Inventory generates URLs faster than anyone governs them, and crawl budget spent on filter combinations is crawl budget not spent on pages that convert.
Core Web Vitals
Diagnosis and prioritization, separating what the platform controls from what the group's own tag stack is doing. On most dealer sites the largest single cost is third-party scripts nobody has audited since they were added.
Migration integrity
When a group changes vendors, the old URL set gets mapped to the new one before launch, the markup that has to survive is specified, and post-launch checks catch what slipped. Migrations fail as SEO projects far more often than as design projects.
Schema is the floor, not the limit.
The schema layer is where AI search visibility and traditional SEO meet, which is why it gets oversold in both directions.
- What schema does. It removes ambiguity. An engine reading marked-up inventory knows what the page is, what the business is, where it operates, and what is in stock, instead of inferring all four and occasionally inferring wrong.
- What schema does not do. It does not confer rank, and it does not make a site citable on its own. A perfectly marked-up group with no corroboration anywhere else still loses to an equal competitor that third-party sources describe. Why corroboration decides citations →
- Why it matters more now. A generated answer has to justify itself from sources it parsed. Markup that resolves cleanly is the difference between being a usable source and being skipped, and skipped is not a ranking you can see in a report.
- Where dealer platforms fall short. Vehicle schema is routinely shipped partial: offers without price, listings without availability, organization markup that disagrees with the Google Business Profile two clicks away. Each of those is an ambiguity an engine has to resolve, and it resolves them conservatively.
If neither classic search nor AI engines can crawl and render your content properly, there is no content strategy good enough to compensate. That is the whole argument for doing this layer first. What runs on top of it →
Common questions about technical SEO.
What does technical SEO cover for a car dealership?
Four workstreams: schema deployment across inventory, location, FAQ, organization, and review markup; crawl architecture, covering robots directives, sitemap hygiene, internal linking, parameter handling, and faceted nav indexation; Core Web Vitals diagnosis and prioritization; and migration playbooks for vendor changes. These matter more on a dealer site than on most sites because the inventory layer generates URLs continuously without anyone deciding to.
Can you do technical SEO on Dealer.com or DealerOn without migrating?
Yes, and no migration is required. The platform owns the template, you own the strategy on top, and the technical work lives in the seam. What is editable differs by vendor and sometimes by contract, so the first step is establishing what your specific instance permits rather than assuming. VulcanAX does not sell websites and has no interest in moving you. Platform detail →
Does schema markup help a dealership rank?
Not directly. It removes ambiguity, which is a different and increasingly valuable thing. Structured data tells an engine what a page is, what the business is, where it operates, and what is in stock, reducing the chance it guesses wrong or skips the page. For AI answer engines this matters more than for classic ranking, because a generated answer has to justify itself from parsed sources. Schema is the floor, not the limit.
Why do dealership sites have crawl problems?
Because inventory generates URLs faster than anyone governs them. Faceted nav multiplies filter combinations into indexable pages, vehicle detail pages appear and disappear as stock turns, and parameterized sort and pagination URLs pile up underneath. Crawl budget goes to near-duplicates and dead stock instead of the pages that convert. The fix is directive and architecture work, not content.
What happens to SEO when a dealer group switches platforms?
Traffic drops, unless the migration is run as an SEO project rather than a design project. The failure modes repeat: URL patterns change without redirects, injected schema is not reproduced on the new build, and the new template drops content that was carrying rankings. A playbook maps the old URL set to the new one before launch and sets the checks that catch what slipped after.
Is technical SEO a separate charge?
No. It is included in the published tier price: $1,165 per rooftop per month at Core, $1,615 at Compete, $2,425 at Command, with a banded volume discount for groups (10% off at 2–3 rooftops, 20% at 4–7, 28% at 8–14, 32% at 15+) and a flat one-time onboarding fee charged once per group. Separating it would mean doing the same crawl and schema work twice. Full pricing →
Find out what the engines can actually read.
The baseline audit reports which AI engines name your store and why, and the technical and schema issues standing between your site and a citation come with it, ranked by how much they matter. On most dealer sites the top item is something the platform shipped and nobody checked.