What works for dealership website SEO?

Dealership search advice tends to arrive as a long list of tips with no order. The order matters more than the tips. A site that search engines cannot read gains nothing from better headings, and a site with inconsistent business details gains little from structured data. This guide is an audit in the order we work through it on a dealer group’s site we run, with the reasons for each step.

Can search engines read and index the actual pages?

Retrieval comes first. Search results and the AI answers built on them draw from the same ordinary index, so a page that is not crawled and indexed normally does not exist for either. Google’s overview of how Search works describes the pipeline; the practical checks are below.

Check initial HTML, responses and robots

Fetch each important page without a browser and read what comes back. The main text, headings and links should be in that initial HTML. Many crawlers, including most AI crawlers, do not run page scripts, so content assembled in the browser can be invisible to them.

Then check the responses. Live pages should return a success status; removed pages should return “not found” or a permanent redirect, not a success page that says the content is gone. Read robots.txt and the robots meta tags on a sample of pages. A stray noindex left over from a staging site is one of the most common reasons a dealership site disappears.

Keep canonicals and sitemaps consistent

Every indexable page should declare one canonical address on the production domain, and the sitemap should list exactly those canonical addresses — nothing marked noindex, nothing that redirects. The sitemaps protocol allows a last-modified date; include it only when it reflects a real change to the page, because engines ignore dates that move without reason. Priority and change-frequency fields are ignored and can be left out.

If the site is reachable on more than one host name, the canonical tags carry the consolidation; make sure every variant points at the same production address.

What helps people and search engines identify the dealership?

Identity is about agreement. The dealership’s name, street address, phone number and hours should read the same on the website, the business profile, map listings and the major directories. Engines and AI systems cross-check these sources, and disagreement makes them less confident about which facts to repeat.

On the website, put those facts in plain text on the home page and the contact page, not only inside an image or a script. Mentions and reviews on other sites matter a great deal here, which is why off-site consistency usually outranks on-site tweaks.

What should each useful page answer?

Every page worth indexing should answer a question a shopper or owner actually asks, and answer it differently from the other pages on the site. A service page answers what the department does, when it is open and how to book. A model page answers what is distinctive about that model at this dealership, not what the manufacturer’s site already says.

Put the direct answer and the key facts near the top, under a heading phrased the way people ask. Use plain tables for comparisons and short lists for steps. Avoid producing many near-identical pages for nearby towns; pages that exist only to funnel searches from each city to the same content are treated as low value.

Which structured data and search features still apply?

Structured data describes a page in a vocabulary engines understand. It can make a page eligible for some search features, but it does not create rankings or guarantee that an AI answer cites the page. Controlled studies have found no measurable citation lift from markup alone. Treat it as accurate labelling, not as a lever.

Separate supported features from retired ones

Check the current structured data gallery before adding markup, because the list changes. As of October 2026, several features once recommended for dealerships no longer produce enhanced results: FAQ rich results stopped appearing in 2026, the vehicle listing result was dropped in 2025, and how-to results and the sitelinks search box were retired before that. Organization markup on the home page, accurate business details and article markup on genuine articles remain useful.

Do not manufacture review stars

Review stars that a business marks up about itself, from reviews it collects and controls, are not eligible for star results, and self-serving rating markup can draw a manual action. If reviews matter to shoppers, show them as visible text with the source and an as-of date, and let review platforms carry the stars.

How should you measure and maintain the work?

Measure what you can observe: which pages are indexed, which queries show the site, which pages receive visits from search and from AI assistants. Keep a short log of what changed and when, so a movement in the numbers can be matched to a cause.

Treat submission as submission, not indexing

Submitting a sitemap or pinging IndexNow tells participating engines that pages changed. An accepted submission means the message was received, not that the page was indexed. Read the indexing reports, filtered to the pages in your own sitemap, to see what actually happened.

Verify the site in both Google’s and Bing’s webmaster tools. Bing’s index feeds several AI assistants, and its tools report crawl problems that Google’s do not always surface. IndexNow is optional and cheap; it helps the engines that read it and does nothing for the ones that do not.

A short llms.txt file listing the site’s main pages is a reasonable hedge, but it is not a lever. Search engines ignore it today, and the effort is better spent on the steps above.

Review facts without bumping dates

Re-checking a page’s facts is good practice, and it is worth recording the review date. A review that changes nothing should not change the page’s published or updated date, its article date or the sitemap’s last-modified value. Moving dates without substantive change is a recognised warning sign, and Google’s guidance on helpful content names it.

What should you do first?

Synthetic example. A fictional eight-page dealership site is audited in order. Step one finds the service page rendered by a script, so its hours are missing from the initial HTML, and the old staging host is still indexable. Step two finds the phone number differs between the site and two directories. Step three finds four town pages with the same text. Step four finds FAQ markup on every page and a self-assigned rating. The fixes, in order: render the service content server-side and add canonicals that point at the production host, correct the listings, merge the town pages into one service-area page, and remove the rating and stale FAQ markup. No uplift is claimed; the point is the order.

Limits of this guide. It gives no ranking timetable. It does not treat a submission as proof of indexing. It makes no claim about eligibility for any business-profile feature, and it does not assume a site will appear in recommendation feeds such as Discover. If you are also deciding whether to bring the site in-house, the ownership guide covers that move.

To start, bring the site’s sitemap address and a handful of example URLs — a model page, a service page and the contact page — and we will walk the audit in this order.