SEO and GEO on Dealer.com
Dealer.com is the Cox Automotive dealer website platform and the one we see most often at franchised dealership locations. It is OEM-certified across most manufacturer programs, which is why so many dealer groups end up on it. We get rankings and AI citations out of it by working the parts you control: custom pages, page-level metadata, redirects, the blog, and the inventory feed behind the SRP and VDP.
What Dealer.com lets you change, and what it does not
Every OEM-certified platform has a ceiling. On Dealer.com the ceiling sits at the template. Almost everything above it is yours.
Templates are vendor-owned
The SRP, VDP, and core page layouts are Dealer.com templates. You pick settings, modules, and order. You do not edit the markup. Template-level requests go to your Cox rep or a support ticket.
Custom pages are open
The page editor lets you build landing pages, model research pages, service pages, and location pages with your own copy, headings, images, and internal links. This is where most of the ranking gains live.
Inventory comes from the feed
VDP content is generated from the DMS or inventory management feed. Trim, options, photos, comments, and pricing on the VDP are only as good as the feed. We fix the feed, not the page.
Schema is partly baked in
The platform emits vehicle and dealer structured data on its own. Fields are often incomplete and you cannot inject arbitrary JSON-LD on inventory pages. Custom pages allow more, within the editor's limits.
Page speed is shared
Core Web Vitals on Dealer.com sites depend heavily on third-party scripts the dealer adds: chat, digital retailing, trade tools, pixels. You control the script list. The platform controls the rest.
Redirects and URLs
301 redirects are managed from the admin console. Inventory URL patterns are platform-defined. Custom page slugs are yours, which matters when consolidating old pages.
What we usually find on a Dealer.com site
A typical first-30-day audit across a franchised dealership. Scores are a composite of technical, on-page, and citation checks.
Title and H1 patterns repeat the same year-make-model string with no trim, stock number, or city, so hundreds of VDPs compete with each other.
The Dealer.com stack, layer by layer
Each layer has a different owner. Knowing who to ask, and for what, is most of the work.
How a Dealer.com engagement runs
Audit first, then a roadmap sorted by what you can ship without waiting on anyone.
Crawl every dealership location
Full crawl of each store on the platform, Search Console review per property, feed field audit, script inventory, and a citation check across ChatGPT, Perplexity, and Google AI Overviews for your metro.
Roadmap by owner
Every finding gets an owner: you, your inventory manager, or Cox. Fixes you can ship in the admin console go first. Vendor requests get written up with the evidence a rep needs.
Build and fix
We build custom pages, rewrite metadata patterns, load redirects, fix feed comment templates, trim scripts, and publish the content that earns citations. Vendor tickets run in parallel.
Measure and expand
Rankings by market, VDP sessions, leads, and AI mentions reported monthly per dealership location. New pages and content each month based on what moved.
What we run on Dealer.com sites
Dealer.com questions, answered
See what your Dealer.com site is leaving on the table
A free snapshot of rankings, crawl issues, feed gaps, and AI citations across your dealership locations.