Most automotive SEO programs are still built on location-page templates and content approaches that have not changed in years. AI-search visibility, cannibalization analysis, and structured-data discipline are rarely part of the picture. The standard that is table stakes in SaaS, finance, or healthcare barely exists here.
VulcanAX is the practice of one automotive SEO specialist, Matthew Chilinski, working on dealer group domains directly. The audit, the schema, the content, and the reporting all come from the same desk.
How the work is structured
An engagement starts with a technical audit: full crawl, schema validation, Core Web Vitals, AI-visibility baseline. Every finding is scored by severity and commercial impact. That document belongs to the client, not to the engagement.
From there, work flows monthly from GSC data: new pages, optimizations, and consolidations driven by what the market is actually telling you. AI-search surfaces are built for and monitored alongside classic search: ChatGPT, Perplexity, Google AI Overviews. A two-page monthly data review and a quarterly business review close the loop.
Four things that do not change
- Data drives the calendar. GSC decides what gets built, optimized, or removed each month. A preset content calendar is not a strategy.
- AI-search is a first-class surface. Buyers reach AI answers before search results pages. Visibility on those surfaces is built for and reported on alongside classic search.
- One person is accountable. Strategy and execution come from the same person, without an account manager between them.
- Everything you get, you keep. Audits, maps, and reports belong to the client to use and keep independently.
What one automotive SEO consultant covers
Dealer groups ask for a consultant, a specialist, or an expert and usually mean the same thing: someone who can read a domain, say plainly what is wrong with it, and then go fix that. The titles are interchangeable. The staffing model behind them is not.
Here the crawl, the schema, the cannibalization map, the content, and the monthly read of Search Console are owned end to end by one person, so nothing is lost translating a strategy document into work orders for somebody else. The trade is a small roster: five dealer groups at a time, one client per market.
The practice is based in Columbus, Ohio, and works with dealer groups nationwide. The rate card and the volume bands are published on the pricing page, and the home market has its own read on automotive SEO in Columbus.
Who this is built for, and who it is not
The client cap makes this worth stating plainly rather than leaving to a call. Five dealer groups at a time means turning work down, so it is better for everyone if the mismatch is obvious early.
- Multi-rooftop groups on a managed platform whose SEO line item has gone quiet. Usually three to fifteen stores, often across more than one state or OEM. The group-level version of this work is dealer group SEO.
- Single-point dealers who read their own Search Console and have gone as far as self-taught SEO takes them.
- Groups watching competitors appear in AI answers while they do not, and unable to get a straight explanation of why.
- Digital operations managers who need documented monthly deliverables they can hold a vendor to.
- Buyers who want a number before a call. The entire rate card is published.
- Agencies needing execution under their own brand. White-label detail sits on the agencies page.
The mismatches are just as specific. Anyone outside automotive retail, because the methodology is built around inventory feeds, VDPs, rooftop structure, and OEM constraints, and it does not transfer cleanly. Groups that want paid media managed, since VulcanAX does not run PPC or paid social and will say so rather than sell it badly. Dealers whose direct competitor already signed, because one client per market is absolute rather than a preference. Groups that need an account manager and a named team on an org chart, a structure that does not exist here. And anyone who needs a ranking locked to a date, which is a sales artifact rather than a search outcome.
