Google Vehicle Ads put dealer inventory directly in front of car shoppers on Search, Maps, and the Shopping tab — without competing in the regular auction alongside every other advertiser. If your WordPress dealer site already syncs inventory through mobile.de, you’re closer to running Google Vehicle Ads than you think. The feed data is already there; it just needs to be routed the right way.
Here’s what the program actually requires, what your feed needs to include, and where dealers most often get rejected.
What Google Vehicle Ads Actually Are
Google Vehicle Ads is a separate program built for new and used vehicle inventory. Vehicles do not go through ordinary product listings: you enable the vehicle ads add-on in Google Merchant Center and submit a vehicle inventory data source that follows Google’s vehicle specification.
The program runs through Google Merchant Center linked to Google Ads and to the Google Business Profile of each dealer location. Once approved, your listings can show for people searching a specific make, model or trim near your dealership. When Google launched vehicle ads, it reported that advertisers who added them alongside their existing Search campaigns saw about 25% more conversions on average during the beta.
Where vehicle ads run (October 2026): fully available in the United States, Canada, Australia and Japan. An open beta covers the United Kingdom, Germany, France, Italy, Spain and the Netherlands: dealers in those countries apply through Google’s contact form and can turn on the add-on once their Merchant Center account is allowlisted.
Feed Requirements: What Google Needs From Your Inventory
Google’s vehicle ads specification lists the attributes every vehicle needs. Most of them are things your vehicle detail page (VDP) already shows:
| Attribute | What it holds |
|---|---|
id |
Your unique ID for the vehicle, for example the stock number or VIN |
VIN |
17-character vehicle identification number (optional in some countries) |
google_product_category |
916 for cars, trucks and vans |
vehicle_fulfillment |
in_store (sold at the dealership) or online |
link_template / link |
The VDP URL. In-store offers use link_template with a {store_code} placeholder |
store_code |
The dealership’s code, matching its Google Business Profile exactly (case-sensitive) |
image_link |
Main photo of the actual vehicle |
price |
Selling price with currency, for example 24900.00 EUR |
condition |
New or used |
brand, model, year |
Make, model without trim, 4-digit model year |
mileage |
With unit, for example 43000 KM |
color |
Exterior colour |
Recommended extras that help ads perform: trim, body_style, engine, vehicle_option (required for free vehicle listings), description and up to 10 additional_image_link photos. Some countries also require fields such as first registration date, fuel consumption or CO₂ emissions, so check the country notes in the specification before you build the feed.
Every one of those fields maps to something your VDP (vehicle detail page) should already display. If your WordPress site pulls inventory from mobile.de through an automatic sync, most of this data is already structured correctly — the work is exporting it in the format Google’s feed spec expects, not re-entering it by hand.
Why Sync Speed Matters for Vehicle Ads Approval
A stale feed is the fastest way to lose a vehicle ads campaign, not just a single listing. If a car sells Tuesday and the feed still shows it available Friday, you’re paying to send shoppers to a page for a vehicle that’s gone, and Google tracks that mismatch as a quality signal.
This is where automated inventory sync earns its keep. A tool like automatic mobile.de sync pushes price changes, new arrivals, and sold-vehicle removals into WordPress on a schedule measured in hours, not days. That same feed can, and should, feed Google Merchant Center directly, so Google Vehicle Ads and the live site never disagree about what’s actually on the lot. We covered the sync mechanics in more detail in our guide to automatic mobile.de inventory sync, worth a read if your feed still updates manually.
Common Rejection Reasons and How to Fix Them
Most Google Vehicle Ads disapprovals trace back to a handful of repeat issues: missing or mismatched VIN data, images that don’t match the actual vehicle, prices that don’t match what’s shown on the landing page, and dealership addresses that don’t match the verified Business Profile tied to the Merchant Center account.
Fixing these usually isn’t a feed problem so much as a data-entry problem upstream, in mobile.de, your DMS, or wherever the listing originates. Clean that source data once, and it flows correctly through an automatic sync, onto your VDPs, and into the feed without a separate correction step.
Vehicle Ads in Germany: What mobile.de Dealers Should Prepare
Germany is in Google’s open beta, so German dealers can apply now instead of waiting for a full launch. Getting accepted is the slow part; the feed is usually the easy part if your stock already lives on mobile.de:
- Give every vehicle its own VDP on your website. Google sends clicks to your page, not to mobile.de, so the feed needs a working
link_templatefor each car. - Verify a Google Business Profile for each location and use its store code in the feed.
- Generate the feed from the same data as your VDPs. If your WordPress site syncs from the mobile.de API, export the feed from that synced data (scheduled XML, CSV or Google Sheets fetch), so price and mileage in the ad always match the page.
- Refresh at least daily and remove sold vehicles in the same run.
- Apply for the beta through the contact form on Google’s vehicle ads page, then enable the add-on once your account is allowlisted.
Setting Up Your First Campaign
Getting live takes four steps: create and verify a Google Merchant Center account, build a vehicle inventory feed matching Google’s schema, upload the feed and resolve any disapprovals Google flags, then launch a Performance Max campaign with the vehicle feed toggle turned on.
None of this requires touching your website’s front end. It’s a data pipeline problem, which is exactly why dealers who already have a clean, automated inventory sync get through setup faster than those still managing listings by hand.
If your inventory feed isn’t synced cleanly between mobile.de and your WordPress site yet, that’s the piece to fix first. Talk to us about setting up a mobile.de dealer website integration that keeps your VDPs, and eventually your Google Vehicle Ads feed, accurate automatically.
The Four Recurring Feed Errors
| Error | Impact |
|---|---|
| Mismatched pricing (feed vs. actual website) | Directly damages shopper trust the moment they notice, and can trigger Google’s own data-quality flagging |
| Sold vehicles remaining listed | Wastes clicks (and ad spend) on inventory that no longer exists — connects directly to the stale-listing problem we’ve covered in organic feed accuracy too |
| Missing identifiers (VIN, stock number) | Can cause a listing to be rejected or under-matched by Google’s systems entirely |
| Weak photos | Lower click-through even when the listing itself is technically correct and eligible |
Guides consistently recommend a weekly feed audit and removing sold units the same day they sell, rather than relying on a slower, scheduled sync cycle to eventually catch up.
Feed Errors Waste Ad Budget, Not Just Listings
We’ve covered separately how slow TTFB directly wastes dealer ad spend by losing visitors who already cost money to acquire — feed errors work the same way from a different angle: a mismatched-price or already-sold listing that still draws a click is money spent on a visitor who was going to bounce in frustration or confusion regardless of how fast the landing page loaded. Feed accuracy and page performance are two separate levers that both directly affect how efficiently paid spend converts.