Vehicle Schema Markup for Canadian Dealerships: LocalBusiness, AutoDealer, Vehicle, and FAQPage Structured Data

TLDR

AutoDealer identifies the dealership business; Vehicle describes an inventory item. Google says structured data can help it understand a page and make supported content eligible for richer search features, but valid markup never guarantees a rich result.

• The gap: Vehicle schema on VDPs is missing or incomplete at most Canadian dealerships, leaving AutoTrader.ca and CarGurus as the structured sources AI systems cite instead.
• The four types: AutoDealer, Vehicle, LocalBusiness with areaServed, and FAQPage each serve a distinct function and belong on specific page types.
• VDP priority: the Vehicle schema Offer block must show price in CAD and flip availability to OutOfStock when a unit sells, per OMVIC advertising rules in Ontario.
• Quebec note: FAQPage schema answers require French versions under Bill 96 for Quebec-facing pages.
• Business case: treat any traffic or revenue lift as a testable scenario, not a promised outcome; measure impressions, clicks, leads, and sold units before and after a controlled rollout.

Most Canadian dealerships have some version of schema markup on their website. A LocalBusiness tag on the homepage, maybe an AutoDealer type that their website platform dropped in automatically. And then they stop there, assume it's handled, and move on.

Here's the thing: that's not vehicle schema markup. It identifies the business, but it does not describe a specific unit on a vehicle detail page. A search engine cannot infer a complete inventory record from a dealership-level entity alone.

This article covers the four schema types that actually matter for Canadian dealerships: Vehicle, LocalBusiness, AutoDealer, and FAQPage. I'll show you what each one should contain, where it goes, and what happens when it's missing. I won't cover every technical SEO consideration for your dealership here, that's what our full breakdown of dealership AI search and SEO is for. This page is specifically about structured data, what it is, why it matters, and how to build it right.

---

Why Vehicle Schema Markup Is the Gap Most Dealers Miss

Your website platform, whether that's Dealer.com, DealerOn, DealerInspire, or Strathcom, probably handles the basics. You've got a LocalBusiness or AutoDealer tag on your homepage. Your NAP (name, address, phone number) is consistent. That's fine.

But walk through a typical vehicle detail page (VDP) on a Canadian dealer site and look at the structured data. What you usually find is nothing. Or a generic Product schema that's half-filled. Rarely do you see a proper Vehicle schema with mileageFromOdometer, vehicleIdentificationNumber, fuelType, driveWheelConfiguration, and an Offer nested inside.

That matters because search engines and AI systems can't easily distinguish your inventory from anyone else's without it. When Google's crawler hits your VDP, it sees a wall of HTML with prices and specs buried in divs. It has to guess. An AI assistant queried about used trucks in Saskatoon has to guess. They both default to sources that have already structured their data properly, which is usually AutoTrader.ca, Kijiji Autos, or CarGurus.

There is no clean Canadian-dealership adoption dataset I would trust enough to turn into a benchmark. Audit the rendered markup on your own inventory pages and a representative local competitor set instead. Record which types and properties are present, whether the visible page agrees with them, and whether the markup survives template and feed changes.

---

The Four Schema Types Your Dealership Actually Needs

1. AutoDealer Schema (Homepage and Contact Page)

AutoDealer is a subtype of LocalBusiness in the Schema.org hierarchy. It tells search engines you're specifically a car dealer, not just a local business. Use it on your homepage and contact page.

A properly built AutoDealer block should include:

{
  "@context": "https://schema.org",
  "@type": "AutoDealer",
  "name": "Westside Honda",
  "url": "https://www.westsidehonda.ca",
  "telephone": "+1-306-555-0100",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "1234 Victoria Ave",
    "addressLocality": "Regina",
    "addressRegion": "SK",
    "postalCode": "S4P 0P8",
    "addressCountry": "CA"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 50.4452,
    "longitude": -104.6189
  },
  "openingHoursSpecification": [...],
  "sameAs": [
    "https://www.facebook.com/westsidehonda",
    "https://www.instagram.com/westsidehonda",
    "https://www.google.com/maps/place/..."
  ],
  "department": [
    {
      "@type": "AutoDealer",
      "name": "Westside Honda Sales",
      "telephone": "+1-306-555-0101"
    },
    {
      "@type": "AutomotiveBusiness",
      "name": "Westside Honda Service",
      "telephone": "+1-306-555-0102"
    }
  ]
}

The sameAs array is often skipped. Don't skip it. This is how AI systems connect your dealership name to your social profiles, your Google Maps listing, and your OEM dealer locator page. It builds what's called entity disambiguation, meaning the AI knows "Westside Honda in Regina" and "that Honda dealer on Victoria Ave" are the same place.

The department split also matters. If your sales and service departments have separate phone numbers, separate hours, or separate booking flows, marking them up as separate entities gives you more surface area in local search and AI answers.

2. Vehicle Schema (Every VDP)

This is the big one. This is where most Canadian dealers are leaving money on the table.

Every vehicle detail page should have a Vehicle schema block. Not a generic Product. A proper Vehicle with the fields that actually describe the unit.

Here's a working example for a used truck VDP:

{
  "@context": "https://schema.org",
  "@type": "Vehicle",
  "name": "2022 Ford F-150 XLT SuperCrew 4x4",
  "brand": {
    "@type": "Brand",
    "name": "Ford"
  },
  "model": "F-150",
  "vehicleModelDate": "2022",
  "bodyType": "Pickup",
  "vehicleConfiguration": "XLT SuperCrew",
  "driveWheelConfiguration": "FourWheelDriveConfiguration",
  "fuelType": "Gasoline",
  "mileageFromOdometer": {
    "@type": "QuantitativeValue",
    "value": 48000,
    "unitCode": "KMT"
  },
  "vehicleIdentificationNumber": "1FTFW1E80NFA12345",
  "colour": "Oxford White",
  "offers": {
    "@type": "Offer",
    "price": "54900",
    "priceCurrency": "CAD",
    "availability": "https://schema.org/InStock",
    "seller": {
      "@type": "AutoDealer",
      "name": "Westside Ford",
      "url": "https://www.westsideford.ca"
    }
  }
}

A few things worth noting here. The unitCode for kilometres is KMT, not MI. That's the correct ISO unit code for metric distance. If your platform is American-built and defaults to miles, you need to catch this. Serving Canadian inventory data with mileage in miles is both wrong and a compliance risk in some provinces.

The vehicleIdentificationNumber field is important because it's the one signal that makes each VDP unique. Without it, a crawler has no way to distinguish your listing from a similar unit at another store.

The Offer nested inside the Vehicle schema is how you signal current price and availability. If the unit sells, that availability field should flip to OutOfStock or the page should be removed. Leaving sold units live with InStock status is a compliance problem under OMVIC in Ontario, which specifically prohibits advertising inventory that isn't available for sale.

3. LocalBusiness Schema with areaServed (Homepage)

If you're running AutoDealer schema, you're already using a subtype of LocalBusiness. But many dealers are missing the areaServed property, which tells search engines which communities you actually serve.

For a dealer in Saskatoon, that might look like:

"areaServed": [
  {
    "@type": "City",
    "name": "Saskatoon"
  },
  {
    "@type": "City",
    "name": "Warman"
  },
  {
    "@type": "City",
    "name": "Martensville"
  },
  {
    "@type": "AdministrativeArea",
    "name": "Saskatchewan"
  }
]

This is particularly useful for rural dealers who pull customers from a wide geographic area. A dealer in Moose Jaw, Saskatchewan doesn't just serve Moose Jaw. They might be the closest dealer for buyers in Swift Current, Weyburn, or Assiniboia. If that's true, say it in structured data.

For multi-rooftop groups, this is where you need to be careful. Each rooftop should have its own AutoDealer entity with its own areaServed. Don't consolidate all your service areas into a single group-level schema block, because then you lose the location-specific signals that help each store rank in its own market.

4. FAQPage Schema (Model Pages, Finance Pages, Service Pages)

FAQPage schema can describe visible question-and-answer content, but it is not a shortcut to AI Overviews, citations, or a Google rich result. Use it only when the questions and complete answers are genuinely visible on the page, and treat any search appearance as an outcome to measure rather than a promise.

The questions need to be real questions your customers ask. Not keyword-stuffed phrases. Real questions.

Good examples — the same questions work for a Honda dealer in any Canadian market (Toronto, Vancouver, Halifax, Winnipeg, or anywhere else):

• "Does your dealership charge admin fees on used vehicles?"
• "Do you offer same-day service appointments?"
• "What's included in your certified pre-owned inspection?"
• "Can I get pre-approved for financing online before visiting?"
• "Do you offer winter tire storage?"

Each answer should be 40 to 80 words. Specific. Honest. If you charge an admin fee, say what it is. If you don't, say that clearly. Vague answers don't get cited. Specific answers do.

For compliance purposes, if any FAQ answer touches on pricing, financing rates, or payment claims, you need to apply the same standards as any other advertisement. Under OMVIC's advertising guidelines in Ontario, financing claims require disclosure of the rate, term, down payment, and qualifying conditions. A FAQ that says "financing from $199 biweekly" without those disclosures is a potential violation. The same principle applies in BC under MVSABC rules and in Quebec under OPC requirements, with the additional requirement that Quebec-facing FAQ content be available in French.

For a full breakdown of how FAQ content feeds AI citation and what the GEO strategy looks like, see our guide on getting cited by ChatGPT, Perplexity, and Google AI Overviews.

---

How to Audit and Build Vehicle Schema: A Month-by-Month Process

Here's how this actually gets done. Not theory. The real work, in order.

Week 1: Audit what you have

Pull your homepage, a new-vehicle model page, a used VDP, and your service page. Run each one through Google's Rich Results Test (search.google.com/test/rich-results) and Schema.org's validator. Document what schema types are present and which fields are populated.

Most dealers find: LocalBusiness or AutoDealer on the homepage with 6-8 fields, nothing on VDPs, and maybe FAQPage on one page if someone added it manually at some point.

Note which platform controls each page. If you're on Dealer.com, your VDPs are likely dynamically generated from an inventory feed. That means schema has to be injected at the feed or template level, not page by page. This is a conversation you need to have with your website provider. See our dealership website provider comparison for what each platform can and can't do with custom schema.

Week 2: Fix AutoDealer schema on the homepage

Build a complete AutoDealer block with all the fields from the example above. Add sameAs links to every active social profile and your Google Maps listing. Add department entities for sales, service, and parts if they have separate contact information. Submit the homepage to Google Search Console for re-indexing after the change goes live.

Week 3: Build Vehicle schema template for VDPs

Work with your website provider or developer to build a Vehicle schema template that pulls from your inventory feed. The key fields to map: name, brand, model, vehicleModelDate, bodyType, driveWheelConfiguration, fuelType, mileageFromOdometer (in KMT), vehicleIdentificationNumber, colour, and the nested Offer block with price in CAD and availability.

Test the template on five VDPs before rolling it out across the full inventory. Use the Rich Results Test on each one. Confirm the VIN is unique per unit and the price matches what's displayed on the page.

Week 4: Add FAQPage schema to high-value pages

Pick four pages: your homepage, your used inventory overview, your finance page, and your service page. Write 5 to 8 questions and answers for each, using the format above. Keep answers under 80 words. Review every answer that mentions price, financing, or inventory availability against your provincial advertising rules before publishing.

Month 2, ongoing: Monitor and maintain

Check your structured data in Search Console under the "Enhancements" section monthly. Watch for errors on VDPs, especially when inventory turns over. Sold units should be removed or marked OutOfStock. New units need the schema template applied when they're added to the feed.

After release, use URL Inspection and the relevant Search Console reports to confirm Google can see the rendered markup. Monitor impressions and search appearances over a meaningful window; there is no reliable universal timeline or guaranteed uplift.

---

The Math: What Schema Actually Changes for a Dealership

Let me put some numbers to this, because "better SEO" without a business case is just noise.

Assume a used-vehicle dealership in Edmonton moves 30 units per month. Their average front-end gross per unit is $2,200 (a reasonable estimate for an independent used dealer in Alberta's current market). Their current website generates 60 used-vehicle leads per month from organic search, converting at 12%, so roughly 7 sales per month from organic.

For an illustrative model only, a dealer could enter its own observed VDP impressions, current click-through rate, lead rate, close rate, and gross per unit, then test several uplift assumptions. Keep those assumptions visibly separate from measured results. Schema may enable supported search features, but Google explicitly does not guarantee that valid structured data will produce them.

That pays for a solid schema implementation project in the first month and generates a return every month after that, without spending an extra dollar on AutoTrader.ca or CarGurus leads.

Now compare that to the per-lead cost model. If you're paying $400 per lead on a platform where the average deal grosses $800, you're spending 50% of gross on lead acquisition before you account for any other costs. That's the math one dealer in our research block described when they stopped spending on TrueCar. First-party organic leads, built on a properly structured website, cost a fraction of that over time.

---

Canadian Compliance Notes That Apply Directly to Schema

Schema markup isn't just an SEO tool. It's advertising. And in Canada, advertising rules apply regardless of whether the content is written by a human, generated by a platform, or structured in JSON-LD.

A few specific rules worth knowing:

Ontario (OMVIC): Under OMVIC's Advertising Guideline, every price advertisement must be an all-in price, meaning it includes all dealer fees. Only HST and licensing may be excluded, and those exclusions must be clearly disclosed. If your Offer schema shows a price, that price needs to match the all-in price on the page. If it doesn't, you're potentially in violation. OMVIC has been active in enforcement, and digital advertising is explicitly covered.

Quebec (OPC and Bill 96): If you have rooftops in Quebec, your FAQPage schema answers need French versions. Bill 96 requires that French be given equal or greater prominence in commercial communications. That applies to structured data content that surfaces to Quebec consumers. Don't rely on English-only schema for a Quebec-facing page.

Competition Bureau Canada: The Competition Act covers false or misleading representations across every province. If your Vehicle schema shows a price or availability status that doesn't match reality, that's a potential deceptive marketing issue. This is especially relevant for sold units left live with InStock status, and for any schema that includes unsubstantiated comparative claims (for example, "lowest price in our market" without backup). The Bureau has been active on automotive advertising enforcement nationally, with fines that can reach into the millions for serious violations.

For more on local SEO compliance and how your Google Business Profile interacts with these rules, see our guide on dealership local SEO and Google Business Profile strategy for Canadian dealers.

---

Common Schema Mistakes I See on Canadian Dealer Sites

Two patterns I see repeatedly, based on auditing dealer sites across Saskatchewan, Alberta, and Ontario:

First, dealers using Product schema instead of Vehicle schema on their VDPs. Product is a parent type. Vehicle is the specific subtype with the fields that actually matter for automotive inventory. Search engines can use Product, but they can't extract mileage, VIN, drive configuration, or fuel type from it the way they can from a proper Vehicle block. The difference matters for AI citation accuracy.

Second, dealers with FAQPage schema that was added once and never updated. The questions are generic ("What are your hours?" "Where are you located?"), the answers don't reflect current offers or policies, and nobody has touched the schema since the website launched. Stale FAQ schema is worse than no FAQ schema in some cases, because it creates a mismatch between what AI systems report about your dealership and what's actually true.

Both of these are fixable. Neither requires a full website rebuild. They require someone with access to your site templates and a clear schema spec to work from.

---

FAQ: Schema Markup Questions Dealers Actually Ask

Does my website platform handle vehicle schema automatically?

Sometimes partially. Dealer.com, DealerOn, and DealerInspire all have some structured data baked into their templates, but the depth varies and Vehicle schema on VDPs is often incomplete or missing. Always audit with the Rich Results Test rather than assuming your platform has it covered. See our dealership website provider comparison for platform-specific details.

Will schema markup directly improve my Google rankings?

Do not treat schema as a ranking promise. Google describes structured data as a way to help it understand page content and make supported types eligible for search features; it also says correct markup does not guarantee that those features will appear.

How do I know if my schema is working?

For Google-supported rich-result types, Search Console can expose applicable status reports after Google processes the pages. Test individual URLs with the Rich Results Test, and use the Schema Markup Validator for broader Schema.org vocabulary checks. AI-answer visibility is a separate measurement problem; use a fixed prompt set, market, date range, and answer-engine list if you monitor it.

Does schema markup matter for my Google Business Profile?

Your GBP is a separate entity from your website schema, but they reinforce each other. A well-structured AutoDealer schema on your site with sameAs linking to your GBP helps search engines connect the two. For a full breakdown of the GBP side of this, see our guide on dealership local SEO and Google Business Profile strategy.

What about schema for my service department?

Service schema and AutomotiveBusiness schema can be applied to your fixed ops pages. This is worth doing if you want to rank for service queries like "Honda oil change Winnipeg" or "winter tire changeover Saskatoon." It's a separate implementation from your sales-side schema but follows the same logic: structured data makes your content readable and citable.

---

Pre-release validation checklist

Validate the rendered page, not only the template or JSON file. A dealership homepage should expose the intended "@type": "AutoDealer" entity, while each inventory detail page should expose its own "@type": "Vehicle" entity with values that match the visible listing.

Run both tools because they answer different questions:

1. Google Rich Results Test: checks whether Google can process supported rich-result markup on the rendered URL or code sample.
2. Schema.org Schema Markup Validator: checks Schema.org vocabulary and structural issues beyond Google's current rich-result features.

Then compare names, URLs, prices, availability, VINs, addresses, and identifiers against the visible page; test several inventory states; and record who owns fixes when the feed changes. For a wider technical and conversion scan around the markup, run Unalike's website grader.

---

Related Reading

• AI Search and SEO for Canadian Auto Dealerships: The 2026 Visibility Playbook
• Generative Engine Optimization for Dealerships: Getting Cited by ChatGPT, Perplexity, and Google AI Overviews
• Dealership Local SEO and Google Business Profile Strategy for Canadian Auto Dealers
• Dealership Website Provider Comparison: Dealer.com vs DealerOn vs DealerInspire vs Strathcom vs 360.Agency in Canada