Schema for Auto Repair and Automotive Businesses: The Full Guide

If you run an auto repair shop, body shop, dealership, or parts store, schema markup is one of the most useful things you can add to your site: it feeds the local details that get you found for "brake repair near me," disambiguates your specific type of automotive business from every other kind of local shop, and increasingly shapes whether AI systems can accurately describe what you do when someone asks for a recommendation.

But a lot of automotive-SEO advice is chasing a feature that no longer exists. Google deprecated Vehicle Listing structured data in 2025, and guides still telling dealerships to mark up their inventory for a rich result are describing something that's gone. So this guide does it accurately: the right schema type for your specific automotive business, what Vehicle Listing's deprecation actually means for you, the honest reality on review stars, and what genuinely moves the needle for local search and AI visibility in 2026. Let's build it right.

The honest reality: what automotive schema does (and doesn't)

Set accurate expectations first, because the automotive space has more outdated advice circulating than most.

Vehicle Listing structured data is deprecated, don't chase it. Google announced the deprecation of seven structured data types, including Vehicle Listing, on June 12, 2025, phasing them out as part of an ongoing effort to simplify search results. If you've seen advice telling you to mark up individual vehicles for sale with Car or vehicle-specific properties to earn a rich "vehicles for sale" result in Google Search, that advice is stale. The feature it was built for no longer exists as a Google Search rich result. Existing markup isn't penalized (Google doesn't punish you for keeping schema that used to power a retired feature), but it's no longer worth new investment aimed at that outcome.

There's no special "automotive rich result" to chase instead. For a repair shop, body shop, or dealership, your schema value doesn't come from a flashy visual feature. It comes from more foundational things:

• Local visibility: feeding Google structured hours, location, services, and payment details that support your presence in Maps and the local pack, where most "near me" automotive searches land.
• Entity clarity: disambiguating exactly what kind of automotive business you are, so Google and AI systems connect the right shop to the right service and location instead of guessing from prose.
• Service-level matching: describing your specific services (brake repair, transmission work, state inspections) in a form AI systems can match to "who does X near me" queries.
• AI-assisted research: reducing ambiguity about who you are, what you service, and where, which supports accurate representation when someone asks an AI assistant which shop to use.

None of that is a rich snippet, and all of it is more durable than one. And an honest note that applies here as much as anywhere: no schema guarantees a citation, a ranking, or a recommendation from an AI system, what good markup does is make your business legible to the systems people and machines use to find you.

Choosing the right schema type

Getting the type right is the foundation, and automotive is a case where using the generic type is a real, common mistake.

Schema.org's automotive types sit under AutomotiveBusiness, itself a subtype of LocalBusiness:

AutomotiveBusiness is the parent type: "car repair, sales, or parts" in schema.org's own description. It works as a fallback, but using it alone when a more specific subtype fits misses a stronger signal.

AutoRepair is the specific type for a repair shop, general mechanical work, not sales. If that's your business, use this rather than the generic parent type.

AutoBodyShop is for collision and body work specifically, the right choice for a paint-and-panel shop or collision center.

AutoDealer is for a dealership selling vehicles, new or used.

AutoPartsStore is for a parts retailer.

AutoRental and AutoWash cover rental agencies and car washes.

MotorcycleDealer and MotorcycleRepair are the motorcycle-specific equivalents of AutoDealer and AutoRepair.

GasStation covers fuel stations, including ones with an attached convenience store or service bay.

If your business runs multiple functions under one roof (a dealership with a service center and a parts counter, for instance), the pattern most sites use is one AutomotiveBusiness-family type per functional page: AutoDealer for the sales/home page, AutoRepair for the service department page, AutoPartsStore for parts, AutoBodyShop for a collision center. Each department gets the type that actually describes what it does, rather than one generic type stretched across everything.

The rule, as with schema generally: use the most specific accurate type. A general repair shop should use AutoRepair, not LocalBusiness or the bare AutomotiveBusiness parent. Generic typing is a missed opportunity here specifically because the subtype list is detailed enough that almost every automotive business has an exact match.

A complete example: an auto repair shop

Here's a well-formed AutoRepair block showing the properties that carry the most weight:

{
  "@context": "https://schema.org",
  "@type": "AutoRepair",
  "@id": "https://brightlanemotors.example/#business",
  "name": "Bright Lane Auto Repair",
  "image": "https://brightlanemotors.example/shop-front.jpg",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "118 Harbor Road",
    "addressLocality": "Portland",
    "addressRegion": "OR",
    "postalCode": "97201",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 45.5051,
    "longitude": -122.6750
  },
  "telephone": "+1-503-555-0142",
  "url": "https://brightlanemotors.example",
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday"],
      "opens": "08:00",
      "closes": "18:00"
    },
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": "Saturday",
      "opens": "09:00",
      "closes": "14:00"
    }
  ],
  "priceRange": "$$",
  "paymentAccepted": "Cash, Credit Card, Debit Card",
  "areaServed": {
    "@type": "City",
    "name": "Portland"
  },
  "makesOffer": [
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Brake Repair",
        "serviceType": "Brake repair"
      }
    },
    {
      "@type": "Offer",
      "itemOffered": {
        "@type": "Service",
        "name": "Transmission Service",
        "serviceType": "Transmission repair and maintenance"
      }
    }
  ]
}

A few things worth noticing. The type is AutoRepair, specific, not the generic AutomotiveBusiness parent. openingHoursSpecification uses the structured object form rather than a shorthand string, which handles different Saturday hours cleanly. And each service is expressed as its own Offer wrapping a Service, this is the same pattern that makes a service explicit and matchable to "who does X near me" queries, which we cover in depth in our Service schema guide. For a repair shop, that per-service structure is doing real work: it's the difference between a machine knowing "this is an auto shop" and knowing "this shop specifically does brake repair and transmission service."

Vehicle Listing is dead, what to do with vehicle inventory instead

This is the section most automotive-SEO guides get wrong, so let's be precise about what actually happened and what to do about it.

What was deprecated. Google's Vehicle Listing structured data (introduced in 2023 specifically to power a "vehicles for sale" experience) was one of seven types Google deprecated on June 12, 2025, alongside Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement, and Book Actions. Google's stated reasoning was the same across all seven: these features weren't providing enough additional value to justify continuing to support them, as part of a broader simplification of search results.

What this means practically. If your dealership or marketplace previously implemented Vehicle Listing markup to try to get individual vehicles into a rich results experience, that specific display no longer exists. You don't need to rip the markup out (Google doesn't penalize sites for retaining schema tied to a retired feature), but new effort spent trying to earn that rich result is effort spent on something that isn't there to earn anymore. This is exactly the kind of currency gap where a lot of automotive-SEO guidance has quietly fallen behind: it keeps recommending a build for a feature that stopped existing months ago.

What still matters for inventory. Losing the rich result doesn't mean vehicle data stops being worth marking up. A few things are still genuinely valuable:

• Product-based markup for individual vehicle listing pages can still describe a specific vehicle's make, model, price, and availability in structured terms, which supports general indexing and gives AI systems clean, extractable facts about what you have in stock, even without a dedicated Google rich result attached to it.
• Feeding your Google Business Profile and inventory feed directly, where your platform supports it, remains the primary channel for vehicle-level visibility in Google's local and Maps surfaces; this is a Business Profile feature, not something JSON-LD schema markup on your site controls.
• Your dealership-level AutoDealer or department-level schema (location, hours, services, areaServed) is unaffected by the Vehicle Listing deprecation and continues to carry real local-search and AI-legibility weight.

The honest takeaway: treat vehicle-specific markup as a nice-to-have for general structured description of your inventory pages, not a rich-result strategy, and put your primary schema effort into your business-level entity, your service department, and your local details, the parts of automotive schema that are still doing real work.

The local layer: getting found by nearby customers

For most automotive businesses, "near me" searches drive the bulk of new customers, so your business-level schema is carrying real weight.

Your automotive business type (AutoRepair, AutoDealer, AutoBodyShop, or whichever fits) carries the local details Google uses for Maps and the local pack: address, geo coordinates, telephone, openingHoursSpecification, and priceRange. Fill these in completely, and make sure they match your Google Business Profile exactly. This is a make-or-break trust signal: if your schema lists one address or one set of hours and your Business Profile shows another, Google loses confidence in both, not just the one that's wrong.

If you operate multiple locations (a chain of repair shops, a dealership group with several stores), the patterns in our multi-location schema guide apply directly: each location as its own entity with its own complete, independently accurate details, rather than one schema block stretched across every branch.

Describing your services explicitly

This is where automotive schema does some of its most useful modern work, and it's a step a lot of shops skip.

A repair shop that only marks up its business-level details is telling a machine "this is an auto repair business," accurate, but thin. Explicitly describing each core service using makesOffer and nested Service blocks, as in the example above, tells a machine "this shop specifically does brake repair, transmission service, state inspections, and tire rotations," which is what lets an AI system match you to someone asking "who does brake repair near me" rather than requiring it to infer your capabilities from your homepage copy.

The same principle that applies to any service business applies here: each distinct core service deserves its own explicit entry, connected back to your business entity, rather than one vague "auto repair services" line covering everything. Our Service schema guide covers this pattern in full depth, including how to structure areaServed and connect services to your organization via provider.

The review stars reality

Here's an accuracy point that trips up a lot of automotive businesses specifically, because reviews are such a visible part of shopping for a mechanic or a dealership.

Your shop cannot show star ratings for reviews about itself on its own site. Google's self-serving review rule makes a business (including one using AutoRepair, AutoDealer, or any other LocalBusiness/Organization-family schema) ineligible for the star-rating rich result on reviews about itself, hosted on its own site. This includes reviews collected directly and reviews pulled in through an embedded third-party widget placed on your own page. If you've seen advice to add AggregateRating to your shop's homepage schema for star ratings, that advice doesn't work and can flag your site.

Star ratings for automotive businesses in search results come from Google's own reviews (via your Business Profile) and from independent third-party platforms, not from a shop marking up its own reviews. The legitimate path is the same one that applies to any local business: build a genuine, strong presence on the review platforms that matter in your market, keep your Google Business Profile accurate and current, and don't spend effort trying to self-mark-up review stars. We cover the full mechanics (including the eligible item types that genuinely can carry review markup, and the July 2026 rule on undisclosed incentivized reviews) in our guide to getting star ratings.

One nuance worth flagging: if you sell a specific vehicle or part as a distinct Product, genuine customer reviews of that specific item can potentially carry AggregateRating, because that's a review of a product, not a business reviewing itself. That's a narrower case than most repair shops or general dealerships will use, but it's worth knowing the distinction exists.

Automotive schema and AI search

People increasingly ask AI assistants for recommendations before they ask a search engine, "what's a good brake shop near downtown Portland" or "which dealership near me has the best service reputation." This is where your schema's real 2026 value shows up.

When an AI system answers a question like that, it's trying to match a specific need (brake repair, a specific make of vehicle, a body shop with weekend hours) to specific businesses that genuinely offer it in that place. A business with clear, complete, explicit schema (the right specific type, services described individually, accurate hours and location, consistent details across your site and your Business Profile) is a business an AI system can represent with confidence. One relying entirely on prose is one it has to guess about, and guessing is exactly what causes a system to surface a competitor it understands better instead.

The honest framing holds here too: no schema guarantees you get recommended by an AI assistant. What clear, accurate, specific automotive schema does is remove the ambiguity that causes AI to misrepresent your services or overlook you. For a business where trust and specificity (the right service, the right hours, the right location) genuinely matter to the person asking, being clearly understood is real, durable value, independent of whatever Google Search rich result comes and goes.

Common mistakes to avoid

Chasing Vehicle Listing markup for a rich result. It's deprecated. Existing markup is fine to keep; new effort aimed at that outcome is effort spent on a feature that no longer exists.

Using the generic AutomotiveBusiness type instead of the specific subtype. AutoRepair, AutoDealer, AutoBodyShop, and the rest carry a stronger, more precise signal than the generic parent type.

One vague schema block covering every department. A dealership with sales, service, and parts should type each department page as what it actually is, not stretch one generic block across all three.

Trying to self-mark-up review stars. Shops can't earn star snippets from their own reviews on their own site. Focus on genuine reviews on Google and third-party platforms.

Inconsistent NAP across schema, Business Profile, and page. Mismatches undermine trust in all your local signals, and automotive customers rely heavily on hours and location being accurate.

Not describing services individually. A single "we do auto repair" line is far weaker than explicit Service entries for brake work, transmission service, inspections, and whatever else you specifically offer.

Stale schema. Hours change, services get added or dropped, a new location opens. Markup written once and left alone drifts out of truth, an old service still listed, wrong hours, a closed location still showing.

Implementing it on WordPress

Most independent shops and smaller dealership groups run WordPress, often with an automotive-specific theme, and the right implementation approach depends on how much you have to keep accurate over time.

Check what your theme or SEO plugin already outputs: many produce only generic LocalBusiness markup, missing the specific automotive subtype, the per-service structure, and the department-level distinctions that matter for a multi-function business like a dealership.

The real challenge is depth plus accuracy over time: the right specific type per department, services described individually, consistency with your Business Profile, and staying current as hours, services, and inventory change. Hand-maintaining that across a growing shop or a multi-location group is where most automotive sites fall behind.

Generating from your content keeps it accurate. AI Schema Gen reads your shop or dealership pages and generates the right specific automotive schema (AutoRepair, AutoDealer, AutoBodyShop, or whichever fits) with services described explicitly and connected into your business's entity profile, and because it generates from your live content, your hours, services, and locations stay in sync automatically rather than drifting the way hand-maintained markup does after your next site update. Whatever route you take, the tests are the same: the specific accurate type per page; services described individually rather than lumped together; consistency with your Business Profile; and accuracy as your shop changes.

Validating your automotive schema

Google's Rich Results Test validates your markup syntax and flags errors. Test your business page and, if you have them, individual department or service pages. Don't expect a dedicated automotive visual result here, as covered above, the local pack and Maps are where automotive schema's local value actually shows up, not a Search rich snippet tied to the schema itself.

The Schema Markup Validator at validator.schema.org checks broader schema.org validity, useful for the automotive-specific types and the makesOffer/Service structure that don't map to a dedicated rich result.

Cross-check consistency: confirm your schema's name, address, phone, and hours match your Google Business Profile and on-page content exactly.

Search your own terms: look up "auto repair near me," "[your city] brake shop," and your business name to see how you appear in local results and whether your details show correctly.

Running an auto repair shop or dealership on WordPress? AI Schema Gen generates the right specific automotive schema from your content (AutoRepair, AutoDealer, or your accurate subtype), with services described individually and connected into your business's entity profile, kept accurate as your hours and offerings change. Start free at aischemagen.com.