Vehicle Ads: Keeping Your Merchant Center Feed and Your VDP in Agreement

Short answer

If you run Vehicle Ads, Google requires the price, VIN, make and model in your Merchant Center vehicle feed to match the vehicle description page the ad lands on. Mismatches get offers disapproved. This is a paid-listing rule. It is not a documented input to AI Overviews or AI Mode, and it is worth keeping the two ideas apart.

What Google documents

Vehicle Ads show a photo, make, model, price, mileage and your dealership name on Google Search, and send the shopper to the VDP. They run from a vehicle feed in Merchant Center.

The Vehicle ads policies say, among other things:

• "The price in your data source and structured data must exactly match the price on your website landing page."
• Landing page URLs must be "correct, accessible, and accurately reflect the vehicle being advertised."
• "All necessary attributes, such as image links and availability, must be present and correct."
• Dealerships must hold a valid dealer license where the jurisdiction requires one.

Google's help page for the Vehicle mismatch issue describes it as "a mismatch between the VIN, brand, and model attribute values provided in your product data source and the corresponding values on your vehicle description page," and its fix list includes: a VIN that is exactly 17 characters and unique per vehicle, the model attribute used only for the model, trim supplied separately in the trim attribute, and the brand attribute set to the vehicle's make.

What this has to do with AI search: less than you have been told

Google states there are no additional requirements for appearing in AI Overviews or AI Mode, and it has not documented vehicle feeds as a source for those answers. It also retired the Vehicle Listing rich result in June 2025. So treat the feed as what it is: the input to a paid format that appears on the same results pages as AI answers.

The overlap is practical rather than technical. The habits that keep a feed approved (current price, current availability, exact identity, one page per VIN) are the same habits that make a VDP trustworthy to any reader, human or machine. That second half is covered in the comparison-ready VDP.

Where mismatches come from

A weekly ten-minute check

1. In Merchant Center open the issues view for your vehicle data source and sort by affected offers.
2. Open five offers at random and compare price, VIN, make, model and trim against the live VDP.
3. Search your site for three units sold in the last seven days. They should return a sold or not-found page, and they should be gone from the feed.
4. Ask your feed provider for the export schedule in writing. Daily is the floor; more often is better on a fast-turning lot.
5. Keep a one-line log. Two clean weeks in a row means the process holds.

Where descriptions fit

The vehicle description in the feed and on the VDP normally comes from the same place: vAuto Inventory Comments. When that field is current and specific, both surfaces agree by construction. InventoryPilot AI writes that field for every VIN and rewrites it every 7 days, so the text a shopper reads on the ad's landing page is the same text your feed carries. It does not manage your Merchant Center account, feed or campaigns.

Common questions

Are Vehicle Ads free? No. They are a paid Google Ads format driven by the Merchant Center vehicle feed.

Does a clean feed get me into AI Overviews? Google has not documented that. A clean feed keeps your ads approved; your pages earn citations on their own merits.

We don't run Vehicle Ads. Does any of this apply? The policy does not, but the discipline does: one current, accurate page per VIN.

Who usually owns the fix? The feed provider for attribute mapping, the website provider for what the VDP shows, and the store for deciding which price is advertised.