Google Ads Vehicle Ads in 2026: Feeds, Markets and the Website Review Dealers Keep Failing
A dealership uploads four hundred cars to Merchant Center, links the accounts, launches Performance Max — and a week later still sees zero impressions in the car carousel. The cause is almost always one of three things: the market isn’t open, the feed was pointed at the wrong destination, or the website failed a data quality review. vehicle ads are not a Shopping campaign with nicer photos; they are a separate Merchant Center programme with its own country list, its own attribute set, its own data lifetimes and a manual landing page review. This guide walks all four barriers using Google’s own documentation: which markets are genuinely open, which feed fields are required and where, why your inventory data expires after 14 days, where the “one VIN, one offer” rule lives, and exactly what has to be visible on a car page before Google lets the account serve.
What vehicle ads are — and what they are not
Merchant Center calls the format a “performance-focused lower funnel ad format” aimed at dealerships, dealer groups, marketplaces, aggregators and OEMs. A shopper sees a photo, the make, model, price, mileage and the advertiser’s name, and the click lands on that car’s page — what the trade calls a VDP.
The plumbing matters more than the pitch. The ads are served by Performance Max campaigns and standard Shopping campaigns with a vehicle feed attached, and the two types can run alongside each other. Here is the first trap: if a campaign has only the vehicle feed attached and no other separate assets, the ads serve in Google Search only. A dealer who expected a carousel across Display and YouTube, but handed the system a bare feed with no copy, images or video, did nothing wrong technically — they just bought the narrowest reach.
The second detail is easy to miss: the Merchant Center article and its mirror in the Google Ads help centre disagree on which countries get Display inventory for a feed. The Merchant Center version names Australia, Canada and the United States; the Google Ads version adds Japan. When two copies of the same page disagree, don’t build a media plan on Display reach until your own interface confirms it.
Ten markets, three tiers of access
Geography is the first filter, and it is stricter than most dealers expect. Google splits access into three tiers.
| Tier | Countries | What it means in practice |
|---|---|---|
| Full availability | Australia, Canada, Japan, United States | You switch the programme on yourself under Merchant Center add-ons |
| Open beta | France, Germany, Italy, the Netherlands, Spain, the United Kingdom | Meet the account prerequisites, then submit a support request |
| Closed beta | Everywhere else | Only through a Google sales representative |
The European expansion is recent: the format reached Spain, Italy and Germany in March 2026. Trade coverage from that period described access as open to all vehicle advertisers with no beta caveat, while Google’s own prerequisites page still calls those markets “open beta countries” and still asks for a support request. Because none of the help pages on this topic carries a last-updated date, the documentation alone cannot tell you which wording is newer — treat the programme card in your own account as the source of truth.
If your inventory physically sits outside those ten countries, read this as a mechanics explainer rather than a launch plan, and win showroom traffic with ordinary Search campaigns, call assets and lead form assets instead. There is no workaround tier below closed beta.
Which vehicles qualify
The documentation contradicts itself here, and knowing that saves a support ticket. The overview page allows “non-commercial passenger vehicles including pickup trucks” and lists the exclusions outright: commercial vehicles, farm vehicles, buses, two-wheelers, trains, boats, airplanes and outdoor utility vehicles. The vehicle ads policy page is broader: “Non-commercial and passenger vehicles including recreational vehicles ATV’s, UTV’s, RV’s, non-motorized trailers and campers”.
Chronology explains the gap: the expansion to ATVs, UTVs, RVs and non-motorized trailers and campers landed in the US in May 2026, and the overview page had not caught up. The banned list did not change: motorcycles, boats, aircraft, farm equipment, go-karts and racing vehicles stay out, as does anything requiring a commercial licence or not street legal.
On business models, only sale and lease qualify. “Vehicles available for subscription aren’t supported” — subscription fleets and car-subscription products don’t fit. Auctions, parts, tyres and service offerings don’t belong in this feed either. And there is a title requirement: “All vehicles listed for sale must have a clean title”, which rules out salvage, lien and similar branded titles.
Who is allowed to submit inventory
The policy is written in terms of who you are, not what you sell, so check every line before you build a feed.
- Direct sellers only. “Direct sellers only: Brokers aren’t allowed to participate.”
- Aggregators and OEMs qualify with a condition: “Aggregators and OEMs may only upload vehicles from dealerships with valid licenses in the required market.” Aggregator eligibility for the US and Canada was announced separately in December 2023, with the blunt addition that “Offers from unlicensed dealers are not supported.”
- A dealer licence wherever local law requires one — and the sentence that settles the most common argument with support: “A driver’s license or sales receipts aren’t valid documentation to meet this requirement.”
- A physical point of sale is mandatory. A storage lot with no address, or an appointment-only showroom with no verified profile, will not pass.
- One state per Merchant Center account: “You may only list vehicles for sale in a single state within a single Merchant Center account.” By the letter of that rule, a group with rooftops in three states runs three accounts — although the same page mentions a beta for multi-state sellers in one account. That is a second internal contradiction to confirm with support rather than assume.
The vehicle feed: what is required and what the system overwrites
The feed goes in as a primary data source in delimited text (Google’s recommended format), XML or via the Merchant API. Two habits from ordinary product feeds do not transfer: “Neither automated feeds via website crawl nor vehicles added or edited manually in Merchant Center are supported.” Google also advises submitting the whole inventory in a single feed rather than splitting it by rooftop.
| Attribute | Status | What matters |
|---|---|---|
id |
required | Unique; a stock number or the VIN works. In the EEA and the UK the same id must also appear on the vehicle’s landing page |
VIN |
required, except in some countries and for build-to-order | 17-character string. Optional in the UK, where an id is required instead |
google_product_category |
required | 916 Cars, Trucks & Vans; 920 Recreational Vehicles; 4243 Travel Trailers; 3018 ATVs & UTVs — the last one US-only and restricted |
vehicle_fulfillment |
required | Values in_store and online, repeatable up to three times |
store_code |
required for in_store |
Case-sensitive and repeatable; must match the store_code in your store feed |
price |
required | Number plus ISO 4217 code, as in 8000.00 USD |
link / link_template |
required | link for online, link_template for in_store — and the template must contain {store_code} |
image_link |
required | One primary shot; additional_image_link takes up to ten more |
vehicle_price_type |
required for new cars in AU, CA, JP and used in AU, JP | all_in_price, drive_away_price, estimated_drive_away_price, excluding_government_charges_price, vehicle_base_price |
vehicle_msrp |
required for new cars in several countries | Optional for used inventory |
title |
optional and ignored | Titles are generated automatically; your value is not used |
availability |
required only for build-to-order | Value build_to_order; otherwise the field is not submitted |
That title row deserves a line in your checklist. A team spending a week perfecting “2023 Toyota Camry SE — only 11,000 miles” is spending it for nothing, because the system writes the headline itself. The same goes for pointing the feed anywhere else: “Targeting Shopping Ads or Free Listings is not supported for vehicle sales”, so the feed must be scoped to the Vehicle Ads destination only. The logic mirrors the identifier rules in a standard product feed: the destination decides which fields are even read.
Country attributes dealers discover after a disapproval
On top of the base set, each market adds fields whose absence kills offers after a clean upload. Used cars in France, Italy, Spain and Germany have required date_first_registered in YYYY-MM form — for example 2020-03 — since January 2025. European markets also bring fuel_consumption, co2_emissions, energy_consumption and electric_range; Germany adds certification; new cars in Italy need emissions_standard on a scale from euro1 to zero_emissions. Japan has its own block: vehicle_expenses, vehicle_category, warranty and vehicle_mandatory_inspection_included.
One naming landmine: there is no make attribute in this specification, even though every dealer CRM and DMS speaks in makes. The manufacturer goes in brand. Integrations that map “make” straight through produce the first batch of upload errors — exactly the class of failure covered in our guide to Merchant Center product disapprovals.
Two data sources, two lifetimes: 14 days and 90 days
In-store inventory needs two feeds, and they behave differently. This is the most underrated part of the programme: it is not upload-and-forget, it is a conveyor that stops on its own.
| Source | Minimum upload frequency | Data lifetime | Limits |
|---|---|---|---|
| Vehicle feed (primary) | at least once a day | 14 days | Multiple daily uploads only after a support request |
| Store data source | at least once every 30 days | 90 days | No more than 10,000 rows per file |
The wording is unambiguous: “Note that this data will expire after 14 days” for the vehicle feed, and “Information from the store data source will expire after 90 days” with the instruction to “Ensure that you re-upload your store data source at least once every 30 days.” When store data expires, the cars are disapproved with the reason Missing valid store code — and the dealer hunts through the vehicle feed while the thing that actually broke is the second, forgotten feed nobody has touched in three months.
The store feed is only needed when the dealer has no Business Profiles for its rooftops: “This data source is only required when a merchant can not (or does not) have Business Profiles.” Its required attributes are store_code, which must match the primary feed, and store_address including the country, which has to be unique; recommended ones are store_name, phone_number in E.164, E.123 or RFC-3966 format and website_url. You upload it under Settings → Data sources → Point of sale sources → Add store data, after which it passes manual and automated checks against Google Maps addresses, and the underlying location must be claimed in Business Profile.
Put two separate reminders in the calendar: a daily inventory export and a monthly store feed re-upload. The second one prevents the most expensive outage in this programme, because the disapproval reason points at the feed that didn’t break.
The one-VIN rule and how it takes down good offers
In this programme the VIN is a deduplication key, and the penalty is out of proportion to the mistake: “If a VIN is submitted for more than one vehicle offer, those offers will be disapproved in the feed.” Both offers go down, not just the second one.
The usual cause is not fraud but stitched exports: a car moved between rooftops, and the feed ended up with two rows carrying different store_code values and the same VIN. The only built-in exception is language — the same VIN may appear once per language. So deduplicate on your side before you send, rather than hoping Merchant Center picks the right row.
The website review dealers keep failing
Activation runs in three steps: stores, then vehicles, then the website data quality review. The third one fails most often, because it inspects what a human sees on the car page rather than what sits in the feed. The requirement reads simply and implements awkwardly: the dealer name, the location, the price, MSRP for new cars, the VIN, mileage for used cars and availability must all be visible immediately, without extra clicks.
- Price behind a form. “Call for price” and prices that only appear after clicking “see offer” do not pass.
- Statuses instead of availability. Pages marked “sold”, “out of stock”, “reserved”, “unavailable” or “incoming unit” are not allowed — sold cars belong out of the feed, not flagged on the site.
- Price mismatch. The policy is blunt: “The price in your data source and structured data must exactly match the price on your website landing page.” Exactly, not approximately — a promotion computed client-side against a base feed price is already a violation.
- Mixed mileage units. Miles in the feed and kilometres on the page, or the reverse, is a rejection. One unit in both places.
- A broken link template. A
link_templateneeds the?store={store_code}parameter, and the URL has to resolve to the advertised car: “Verify that landing page URLs are correct, accessible, and accurately reflect the vehicle being advertised.”
Google advises waiting 24 to 48 hours after submitting the feed, and once attribute fixes are in, contacting support to close the website review. There is no published SLA for that review. If the dealer’s VDPs simply aren’t built for this level of transparency, start with the general Google Ads destination requirements — the same principles, minus the automotive specifics.
Vehicle feeds on Search ads: a different product, US only
A close relative arrived in 2026 and is easy to confuse with the main format: vehicle feeds on Search ads. These are not a carousel but assets attached to ordinary text ads in Search campaigns, surfacing specific cars from the feed with make, model, price and a photo. Availability is one sentence: “Vehicle feeds on Search ads are only available for advertisers in the United States.”
| Dimension | Vehicle ads | Vehicle feeds on Search ads |
|---|---|---|
| What it is | A standalone visual format | An asset on a text ad |
| Campaign types | Performance Max, standard Shopping | Search campaigns |
| Geography | Ten markets across three tiers | United States only |
| Choosing cars | Driven by the feed and the system | “You can’t choose the specific vehicles to be shown on the ads” |
| Cost | CPC under campaign rules | CPC as for a headline click, but “you won’t be charged for more than 2 clicks per ad impression” |
| Reporting | Campaign and asset group reports | Click type segment, Vehicle asset row |
That cap of two billable clicks per impression is a rare case of Google publishing a charging ceiling outright, and it is worth remembering when you reconcile spend. You switch the feed off per campaign under Settings → Merchant Center by unchecking or removing it. Serving is never guaranteed: ad rank, device, query specificity and feed data quality all decide. For a dealer the practical takeaway is that in the US there are two separate routes to getting inventory into the results page, with different campaign types, different reports and different charging rules.
The EEA and the UK: four prerequisites, one irreversible
For European markets the account is allowlisted, and the prerequisites are written so they cannot be met retroactively.
- A dedicated Merchant Center account. “Vehicle ads aren’t a part of the CSS program. A dedicated Merchant Center account must be used to run Vehicle ads.”
- An empty account at application time. “You shouldn’t have any data sources (for example, feeds) in your account during the allowlisting process.”
- Unlinked from Google Ads at application time. “The Merchant Center accounts shouldn’t be linked to a Google Ads account during the allowlisting process.”
- No way back. “Any Merchant Center account allowlisted for Vehicle Ads in EEA and/or the UK can’t be undone” — Shopping and free listings are switched off in that account for good.
Plus the formality checked first: the country in your business information must match the target country. Falling short “may delay the allowlisting process and may require a new Merchant Center account to be created”, so the price of an error is a fresh account and a fresh queue. For a dealer group that means designing the account map before the first application, much as with a Merchant API feed migration, where the order of steps decides whether you redo the work.
If nobody can build the feed: the partnership programme
Google offers a route for dealers without a technical team — the Vehicle ads partnership program. A partner crawls the dealer’s site and builds the feed, and “will then update your vehicle feed every 24 hours”. The partner table listed DealerOn and Fullpath at the time of checking, both for the United States, with no other countries. It is a paid service: “There’s a cost associated with using a third-party provider to manage feeds”, and the help pages quote no prices.
The sequence: complete the pre-activation steps, submit interest, pass a site assessment, receive a hosted feed URL and register it in Merchant Center. For a three-rooftop dealer on a standard platform this beats building an integration; for a group with its own DMS and unusual pricing rules it is an extra link, because the local inventory logic stays on your side regardless.
A launch order you won’t have to redo
- Day 1 — eligibility. Is the rooftop’s country among the ten markets? Does the inventory type qualify? Is there a dealer licence where law requires one? Clean titles across the board? One “no” stops the project here.
- Day 1–2 — account map. One state, one Merchant Center account in the US. For the EEA and the UK, a dedicated empty account, unlinked from Google Ads and outside CSS.
- Day 2–3 — site and verification. Verify and claim the store website, link Google Ads, link Google Business Profile, add business information.
- Day 3–4 — points of sale. Every profile with a live physical address, a unique
store_codewithin the linked group, correct opening hours and a category from the Store and Shopping vertical. No profile access? Prepare a store feed under 10,000 rows. - Day 4–7 — landing pages. Surface dealer name, location, price, MSRP for new, VIN, mileage for used and availability on the VDP with no extra clicks. Pull “sold” and “reserved” units out of the served inventory.
- Day 7–9 — the feed. Build the primary source in delimited text or via the Merchant API with exact attribute headers, VIN deduplication, country fields and the Vehicle Ads destination only. Schedule a daily fetch.
- Day 9–11 — activation. Settings → Add-ons → Discover tab → the Vehicle ads card → “Add in [country]”. Allow 24 to 48 hours after the first feed upload.
- Day 11–12 — website review. Fix whatever surfaces, then contact support to close the data quality review.
- Day 12–14 — campaigns. Create Performance Max or standard Shopping, attach the feed and, crucially, add the rest of the assets if you want reach beyond Search.
What Google’s vehicle ads documentation does not say
An honest guide has to list the gaps, and here each one costs a support thread.
- Last-updated dates are absent from every help page checked, so you cannot date-check any wording against the documentation.
- How long the website data quality review takes. Only the 24-to-48-hour wait after feed submission is published.
- Image requirements — dimensions, minimum resolution, formats. The main specification only links out to them.
- Length limits for
descriptionand other free-text fields. - Japan’s actual tier. Google’s help lists it under full availability; trade coverage places it in closed beta.
- Whether the standard Shopping route applies in the EEA or only in the US.
- Which markets come next, and when. No timeline exists.
- Field-name drift between pages:
vehicle_msrpversusvehicle_MSRP, andship_to_storeappearing in the Content API guidance but not in the main specification.
That last point needs a caveat: the Content API guidance page itself carries a notice that the Content API for Shopping was scheduled for sunset on 18 August 2026, so some of the drift is stale documentation rather than two live contracts.
The line this blog doesn’t cross
Vehicle ads are a format built on verifying the seller: a dealer licence, a claimed physical rooftop, a clean title, a price that matches the site. That is precisely the machinery the platform uses so a car buyer doesn’t land on an unlicensed middleman. We explain those requirements so a legitimate dealer clears them on the first attempt, and we don’t write about getting around them — not for this format and not for any other. If the eligibility gap is substantive (no licence, no rooftop, inventory that isn’t yours), the answer isn’t a feed, it’s a different business model.
The operational side is a separate matter. Automotive runs on calls and showroom visits, so measurement beats creative here: without solid call tracking and call campaigns you will not see half the result, and the Performance Max asset structure for car inventory works much like property assets in hotel campaigns — the same “feed plus assets” principle with a different field set. If you need tooling and accounts for high-volume launches, see the PPC Rebels services and our breakdown of Google Ads agency accounts; the rest of our paid-traffic deep dives live in the blog.
FAQ
How do vehicle ads differ from ordinary Shopping campaigns?
They are a separate Merchant Center programme with their own feed, their own destination and a manual website review. A vehicle feed cannot target Shopping Ads or free listings, and the ad headline is generated automatically.
Which countries is the format available in during 2026?
Full availability: Australia, Canada, Japan and the United States. Open beta: France, Germany, Italy, the Netherlands, Spain and the United Kingdom. Every other market is closed beta through a Google representative.
Which vehicle types can I submit?
Non-commercial passenger vehicles including pickup trucks. Since May 2026 the United States also allows ATVs, UTVs, RVs, non-motorized trailers and campers. Motorcycles, boats, aircraft, farm equipment and racing vehicles are banned.
Why were my offers disapproved over a VIN?
A VIN may appear once in the feed. If it is submitted for two offers, both are disapproved. The only exception is language: once per language. Deduplicate the export before you send it.
How often do the feeds need updating?
The vehicle feed at least once a day, and its data expires after 14 days. The store data source at least once every 30 days, and its data expires after 90 days. Multiple daily uploads require a support request.
What does the website data quality review check?
That the car page shows the dealer name, location, price, MSRP for new cars, the VIN, mileage for used cars and availability without extra clicks. Statuses such as “sold” or “reserved” are not allowed, and the price must match the feed.
Can one Merchant Center account cover several states?
Policy says no: one state per account. The same page mentions a beta for multi-state sellers, so confirm any exception with support and design the account map before uploading inventory.
What has to be true before applying for access in the EEA or the UK?
A dedicated Merchant Center account outside the CSS programme, with no data sources added and no Google Ads link until approval, and a business country matching the target country. Allowlisting cannot be undone.
How do vehicle feeds on Search ads differ from the main format?
They are assets on text ads in Search campaigns, available only to advertisers in the United States. You cannot pick specific cars, and no more than two clicks are charged per ad impression.
Can a vendor build the feed for me?
Yes, through the Vehicle ads partnership program: the partner crawls your site and refreshes the feed every 24 hours. The listed partners are DealerOn and Fullpath, both US-only. The service is paid and no prices are published.
Why are my ads only showing in Search?
If a campaign has only the vehicle feed attached and no other separate assets, serving is limited to Google Search. The Display availability for a feed is described differently in two copies of the same help article, so verify reach in your own interface.
Does a dealer licence requirement apply everywhere?
It applies wherever local law requires one, and Google is explicit that a driver’s licence or sales receipts are not valid documentation for it. Aggregators and OEMs may only upload cars from licensed dealerships.
Primary sources: the vehicle ads overview, the vehicle ads policies and the EEA and UK prerequisites in Google Merchant Center Help.
