I've built dealer websites across three Canadian provinces in the last two years, and I can tell you this: nothing will humble you faster than getting a call from a client saying they just got hit with a CAD 10,000 fine because their Quebec site defaulted to English. Canadian auto dealer web development isn't just about inventory feeds and lead forms. It's a patchwork of provincial regulations, each with its own teeth, and if you're building for dealers nationally, you need to understand the differences at a granular level.

This article breaks down the real differences between building dealer websites for Ontario (OMVIC), Alberta (AMVIC), and Quebec, including bilingual requirements that go way beyond slapping a language toggle in the header.

Table of Contents

Why Canadian Dealer Sites Are Different

If you've built dealer websites in the US, you might assume Canadian sites are roughly the same with a maple leaf logo swap. They're not. Canada regulates auto dealer advertising at the provincial level, and each province has its own regulatory body with its own rules about what you can and can't show on a website.

The three big ones you'll encounter:

  • OMVIC (Ontario Motor Vehicle Industry Council) -- governs Ontario dealers under the Motor Vehicle Dealers Act
  • AMVIC (Alberta Motor Vehicle Industry Council) -- governs Alberta dealers under the Vehicle Marketers and Consignors Licensing Act
  • AMF / OPC (Autorité des marchés financiers / Office de la protection du consommateur) -- Quebec's consumer protection framework, layered with the Charter of the French Language

Each one dictates specific things about how prices are displayed, what disclosures must appear on vehicle detail pages (VDPs), and how marketing materials are presented. Get it wrong, and your client doesn't just lose SEO rankings -- they lose their license.

OMVIC: Ontario's All-In Pricing and Disclosure Rules

Ontario is where most agencies first encounter Canadian dealer compliance, and OMVIC doesn't mess around. The core principle is all-in pricing: every advertised price must include all fees the dealer charges. That means admin fees, freight, PDI, safety certification, and even the OMVIC fee itself. The only things you can exclude are HST/GST/PST, and even then you must clearly state that taxes are extra.

This has huge implications for your website's vehicle detail pages.

What Must Appear on Every VDP

OMVIC mandates 25 specific disclosures about a vehicle's history and condition. These aren't suggestions. If a vehicle was previously used as a rental, a taxi, a police car, or an emergency vehicle -- that must be disclosed. Odometer discrepancies, outstanding liens, recall status via Transport Canada, damage history via CARFAX or equivalent -- all mandatory.

From a development perspective, this means your inventory management system needs structured fields for all 25 disclosure categories. You can't just dump them in a free-text description field and hope for the best. I've seen dealers fail audits because their website showed the disclosures but their CRM didn't capture them consistently.

The Compensation Fund Angle

OMVIC-registered dealers contribute to the Motor Vehicle Dealers Compensation Fund. This is a genuine consumer protection mechanism -- if a buyer suffers a provable loss from a registered dealer, the fund can reimburse them. Smart dealers market this prominently on their sites. It's a trust signal that private sellers and curbsiders can't match.

For web developers, this means building trust badge components that link to OMVIC's registry, where consumers can verify a dealer's registration status. Registration costs CAD $341 for individuals (includes background check and certification) and CAD $683 for businesses plus a business plan submission.

AMVIC: Alberta's MFA-First Approach

Alberta's AMVIC shares the consumer protection philosophy but diverges in execution. The biggest difference? The Mechanical Fitness Assessment (MFA).

In Alberta, the MFA must be completed and signed before the Bill of Sale. Not at the same time. Not the day after. Before. This timing requirement is the single most common audit failure point for Alberta dealers, and it absolutely affects how you build the online purchase flow.

How MFA Affects Website UX

If your dealer client is doing any kind of digital retailing -- buy-online, reserve-online, or even just a finance pre-approval flow -- the MFA timing matters. Your purchase funnel needs to account for the MFA step, and your deal jacket (the digital record of the transaction) needs to timestamp it correctly.

Dealers using compliant CRM tools like MoveMetal report that properly timed digital deal jackets cut their contracts-in-transit period from 10-14 days down to 24-48 hours. That's not just a compliance win -- it's a cash flow win that dealers actually care about.

AMVIC Advertising Rules

Similar to OMVIC, AMVIC requires all-in pricing. But the enforcement emphasis is different. AMVIC audits in 2025 hit about 40% of independent dealers, primarily for MFA timing errors rather than advertising violations. That said, your website still needs compliant pricing displays -- the fine print approach that American dealers sometimes use won't fly here.

OMVIC vs AMVIC: Side-by-Side Comparison

Here's a practical comparison for developers and marketers building sites across both provinces:

Feature OMVIC (Ontario) AMVIC (Alberta)
Governing Legislation Motor Vehicle Dealers Act (MVDA) Vehicle Marketers and Consignors Licensing Act
Pricing Rules All-in pricing; taxes can be excluded if stated All-in pricing; similar structure
Key Disclosure Count 25 mandatory disclosures on vehicle history MFA-focused; fewer enumerated web disclosures
Primary Audit Trigger Disclosure accuracy, record-keeping MFA timing (must precede Bill of Sale)
Consumer Fund Compensation Fund for registered dealer losses No direct equivalent fund
Registration Cost $341 individual / $683 business Varies by license type
2025-2026 Enforcement Trend 25% increase in enforcement actions 40% of independents audited for MFA
Digital Deal Jacket Impact Required for record-keeping Reduces funding delays by ~70%
Website Trust Signals OMVIC registration badge, fund participation MFA certification badges on listings

For agencies building multi-province dealer platforms, this table drives your component architecture. You need province-aware disclosure modules, not a one-size-fits-all approach.

Quebec: Bilingual Websites Under Bill 96

Quebec is where things get genuinely complex. Forget everything you know about optional language toggles. In Quebec, French is not an option -- it's the law.

The Charter of the French Language, significantly strengthened by Bill 96 (phased in from 2022 through 2025), requires that commercial websites serving Quebec consumers present French as the primary language. English can be available, but it must be subordinate. In practice, this means:

  • Your site must default to French for Quebec visitors
  • French content must be at least as prominent as English content
  • All contracts, disclosures, and marketing materials must be available in French
  • Non-compliance can result in fines up to CAD $30,000 per violation from the AMF

Bill 96's Real Impact on Dealer Sites

I've talked to developers who thought "bilingual" meant running the English site through Google Translate and calling it a day. Don't. The AMF's 2025 digital compliance audit wave targeted over 500 dealers. The 15% failure rate resulted in CAD $2.5 million in total fines. The AMF isn't playing around, and machine translation doesn't meet the standard.

Quebec dealer sites need professionally translated content across every page -- not just the homepage. Every VDP, every financing calculator, every pop-up disclosure about liens or odometer readings. And it needs to feel natural in French, not like translated English.

The 2026 "Langue Française Numérique" initiative goes further, requiring real-time bilingual pricing calculators. If your English calculator shows monthly payments, your French version must show them too, with identical functionality.

Quebec's Regulatory Bodies

Quebec dealers don't register with OMVIC or AMVIC. They register through SAAQ (Société de l'assurance automobile du Québec) for vehicle-related matters and fall under the AMF for financial services and consumer protection. This means the vehicle history equivalent isn't UVIP -- it's the SAAQ vehicle history report, and your site needs to integrate with or reference that system.

Technical Implementation for Bilingual Dealer Sites

Let's get into the code. Building a compliant bilingual dealer site in Quebec requires more than a WordPress plugin.

HTML Language Declarations

Your default document must declare French-Canadian as the primary language:

<!DOCTYPE html>
<html lang="fr-CA">
<head>
  <meta charset="UTF-8">
  <link rel="alternate" hreflang="fr-CA" href="https://dealer.ca/fr/" />
  <link rel="alternate" hreflang="en-CA" href="https://dealer.ca/en/" />
  <link rel="alternate" hreflang="x-default" href="https://dealer.ca/fr/" />
</head>

Notice the x-default points to French. This is intentional and required. Google needs to understand that French is your canonical language for Quebec-targeted sites.

Geolocation-Based Language Detection

For dealers with both Quebec and non-Quebec locations, you'll want IP-based geolocation to set the default language:

// Middleware example for Next.js
import { NextRequest, NextResponse } from 'next/server';

export function middleware(request: NextRequest) {
  const country = request.geo?.country;
  const region = request.geo?.region;
  
  // Default to French for Quebec visitors
  if (country === 'CA' && region === 'QC') {
    const locale = request.cookies.get('NEXT_LOCALE')?.value || 'fr-CA';
    if (!request.nextUrl.pathname.startsWith(`/${locale}`)) {
      return NextResponse.redirect(
        new URL(`/${locale}${request.nextUrl.pathname}`, request.url)
      );
    }
  }
  
  return NextResponse.next();
}

This works well with Next.js i18n routing, which handles locale-based routing natively. We've found this approach to be the most reliable for dealer groups that span multiple provinces.

Inventory Feed Translation

Here's where it gets tricky. Your inventory feed from the DMS (Dealer Management System) is almost always in English. Vehicle descriptions, feature lists, trim level names -- all English. You need a translation layer that handles:

  1. Static field translation -- color names, body styles, drivetrain types (map tables work great here)
  2. Dynamic description translation -- marketing copy needs human translation or high-quality AI with human review
  3. Legal disclosure translation -- must be professionally translated, no exceptions
// Example: Static field translation map
const vehicleFieldTranslations: Record<string, Record<string, string>> = {
  bodyStyle: {
    'Sedan': 'Berline',
    'SUV': 'VUS',
    'Truck': 'Camion',
    'Coupe': 'Coupé',
    'Convertible': 'Décapotable',
    'Hatchback': 'Hayon',
    'Van': 'Fourgonnette',
  },
  drivetrain: {
    'AWD': 'Intégrale',
    'FWD': 'Traction avant',
    'RWD': 'Propulsion arrière',
    '4WD': 'Quatre roues motrices',
  },
  color: {
    'Black': 'Noir',
    'White': 'Blanc',
    'Silver': 'Argent',
    'Red': 'Rouge',
    'Blue': 'Bleu',
    'Grey': 'Gris',
  },
};

This kind of mapping is unglamorous but essential. Miss a field, and your French VDP has random English words scattered through it -- which looks unprofessional and can trigger compliance issues.

Building Compliant Dealer Sites: The Tech Stack

After building several of these, here's the stack I'd recommend for a multi-province Canadian dealer site:

For Single-Location Dealers

  • Framework: Astro with static generation for speed
  • CMS: A headless CMS like Sanity or Contentful with locale support
  • Inventory: Direct DMS integration via API (CDK, Reynolds, PBS Systems in Canada)
  • Translation: TranslatePress or Weglot for smaller sites; custom i18n for larger builds
  • Compliance: Province-specific disclosure components loaded dynamically

For Dealer Groups (Multi-Province)

  • Framework: Next.js with App Router and built-in i18n
  • CMS: Headless CMS with per-locale content models
  • Inventory: Centralized inventory API with per-province business rules
  • Translation: Professional translation pipeline with automated flagging for new inventory
  • Compliance: Province-aware middleware that loads correct disclosure requirements

The key architectural decision is whether to build separate sites per province or one site with province-aware routing. For dealer groups, I strongly recommend the single-site approach with middleware -- it's more maintainable and ensures consistent branding.

Pricing and Budget Realities for 2025-2026

Let's talk money, because dealers always want to know what this costs.

Component Budget Range (CAD) Notes
Basic bilingual site (WordPress + WPML) $5,000 - $15,000 Fine for single-location Quebec dealers
Custom headless build (Next.js/Astro) $15,000 - $45,000 Multi-province, full compliance
Professional translation (initial) $3,000 - $8,000 Depends on page count
Annual translation maintenance $2,000 - $5,000 New inventory descriptions, blog posts
Compliance CRM (e.g., MoveMetal) $99 - $299/month Digital deal jackets, audit-proofing
SAAQ integration development $2,000 - $5,000 Vehicle history embedding
OMVIC registration $341 - $683 Individual vs. business
WCAG 2.2 accessibility audit (bilingual) $3,000 - $7,000 Required in both languages per AMF 2025 rules

The biggest mistake I see? Dealers budgeting for the initial build but not for ongoing translation. Every new vehicle that hits the lot needs French descriptions. Every blog post about winter tire specials needs a French version. This is an ongoing cost that needs to be in the retainer conversation.

For a detailed quote on multi-province dealer builds, check our pricing page or reach out directly.

Common Mistakes That Trigger Audits

After seeing multiple dealer clients go through audits, here are the patterns that get you flagged:

Ontario (OMVIC)

  1. Excluding fees from advertised prices -- Even a $299 admin fee buried in fine print violates all-in pricing rules
  2. Missing vehicle history disclosures -- If a car was a rental and you don't say so on the VDP, that's a violation
  3. Broken odometer disclosures -- The January 2026 MVDA update now mandates these digitally on websites, not just on paper

Alberta (AMVIC)

  1. MFA timing -- The Mechanical Fitness Assessment must be completed before the Bill of Sale is signed. Your digital retailing flow must enforce this sequence
  2. Incomplete deal jackets -- Digital records must be audit-ready, with timestamps proving compliance sequence

Quebec

  1. English-default websites -- Even if you have a French version, defaulting to English for Quebec IP addresses is non-compliant
  2. Untranslated legal disclosures -- Having French marketing copy but English-only terms and conditions
  3. WCAG 2.2 failures in one language -- Your French site must be just as accessible as your English site. The AMF tests both.

FAQ

Do I need separate websites for each Canadian province?

Not necessarily. A single website with province-aware routing and dynamic compliance modules works well for dealer groups. The key is that the site must detect the user's province (via geolocation or explicit selection) and serve the correct disclosures, pricing format, and language. For Quebec, the site must default to French. For Ontario and Alberta, the compliance differences are smaller and can be handled with conditional components.

What happens if my Quebec dealer site isn't bilingual?

The AMF can fine dealers up to CAD $30,000 per violation under the strengthened Charter of the French Language (Bill 96). In the 2025 digital compliance audit wave, over 500 dealers were audited, and the 15% failure rate resulted in CAD $2.5 million in total fines. The 2026 "Langue Française Numérique" initiative increases scrutiny further, with fines starting at CAD $10,000 for non-bilingual sites.

Is Google Translate acceptable for Quebec bilingual compliance?

No. Machine translation doesn't meet the standard, especially for legal disclosures, contract terms, and vehicle history reports. The AMF expects professional-quality French that reads naturally. You can use AI-assisted translation as a starting point, but everything consumer-facing needs human review by a native French-Canadian speaker. The nuances between European French and Quebec French matter here too.

What is all-in pricing and how does it affect my dealer website?

All-in pricing, mandated by both OMVIC and AMVIC, requires that every advertised vehicle price includes all dealer-imposed fees -- admin fees, freight, PDI, safety certification, the OMVIC fee, everything. The only exclusions are government taxes (GST/HST/PST), which must be clearly noted as extra. Your website's inventory display, search results, and VDPs must all reflect this. No showing a low price and then adding fees at checkout.

How does OMVIC's Compensation Fund work as a marketing advantage?

The Motor Vehicle Dealers Compensation Fund reimburses consumers who suffer provable financial losses from transactions with OMVIC-registered dealers. This protection doesn't exist for private sales or curbsider purchases. Smart dealers display their OMVIC registration prominently and link to the registry verification page. It's a genuine trust signal -- not marketing fluff -- because it gives buyers financial recourse that they wouldn't have otherwise.

What are the 25 mandatory OMVIC disclosures I need on vehicle detail pages?

They cover vehicle history and condition: previous use as a rental, taxi, emergency vehicle, or police car; odometer accuracy; outstanding liens; flood or fire damage; frame damage; airbag deployment; branded title status (salvage, rebuilt); recall status via Transport Canada; and more. Each must be a structured, answerable field on your VDP -- not buried in paragraph text. The January 2026 MVDA update requires these to be presented digitally on the website, not just on paper forms at the dealership.

What's the MFA and why does it matter for Alberta dealer websites?

The Mechanical Fitness Assessment (MFA) is an Alberta requirement ensuring vehicles meet mechanical standards before sale. The critical compliance point is timing: the MFA must be completed and signed before the Bill of Sale. For websites with digital retailing or online purchase flows, your UX must enforce this sequence. AMVIC audits in 2025 hit 40% of independent dealers, primarily for MFA timing errors. Getting this wrong means slower lender funding (10-14 days vs. 24-48 hours) and potential license issues.

Can I use one CMS for both French and English dealer content?

Yes, and you should. Headless CMS platforms like Sanity, Contentful, and Storyblok all support locale-based content models natively. This means your content editors can manage French and English versions of each page, blog post, and disclosure document from the same interface. The CMS should flag untranslated content so nothing goes live in only one language. We've found this approach works particularly well when paired with a headless CMS architecture that separates content management from the presentation layer.