How to fix: inconsistent value [price], merchant-hosted local storefront full

Ensure that prices in the data that appears in your local inventory ads and free local product listings match your landing page

When someone clicks a local inventory ad or local listings on Google they expect to see the same price on your landing page as they see in the ad or listing. You may be paying for wasted clicks if a user clicks on a product and returns to Google after seeing a different price on your landing page.

  • Price mismatches were found between your local inventory data and landing pages. You should have received an email asking you to update your data by a certain date so that the values in your data are consistent with those on your landing page. If mismatching data is detected after this date, your account will be suspended and will no longer be eligible to show your local products in ads and free listings.


Expand all

The merchant hosted local storefront - full implementation displays the price of a product at a specific store. Accordingly, a click from a merchant-hosted local storefront - full local inventory ad or local listing must direct to a product landing page which displays the price of the item at a specific store. Refer to the table below to determine which feed and attribute is providing the price for your local inventory ads and listings.

Storefront Type Feed Source Pricing attribute Notes
Full Primary Feed or Legacy Local Products Feed price or sale_price Price is provided in your primary feed if you are showing nationwide prices
Full Local Inventory Feed

price or sale_price

Price is provided in your local inventory feed if you are showing store-specific prices

Step 1: Ensure that price in your local inventory ads data matches price on your landing page
  1. Investigate your update process to see what could be causing the problem:
    1. Check the warning email for examples of products that were disapproved. Look for a common problem in your product data that could cause these mismatched prices.
    2. Make sure you’re updating your landing page and local inventory ads data at the same time. Schedule an upload or use the Content API to immediately update your product data. This scheduling helps make sure Google has the same data that is displayed on your landing page.
  2. Once you’ve addressed the problem, update the price attributes in your local inventory ads data to match your landing page.
Step 2: Resubmit your inventory data
  1. Once you’ve updated your local inventory ads and free local listings data, resubmit it using one of the methods below:
    1. Upload a feed
    2. Submit through the Content API
Step 3: Wait for your data to be re-crawled
  1. Google will crawl the products listed in your Merchant Center account. If we detect that the prices in your data now match your landing page prices, your account suspension will be lifted and you will be able to serve local inventory ads and listings again.


Compare the store-specific price in your product data to your store-specific landing page
  1. Find the link_template attribute for the example product included in your warning email.
  2. Replace the {store_code} value in the link_template attribute with the store_code value included in your warning email.
  3. Paste the link_template into your browser to trigger your store-specific product landing page. The price listed on this page must match the price value in your local products inventory feed. Please note that the resulting value may not be the same as the value that Google previously crawled.


  • id: 7
  • store code: 123
  • price: 12.75
  • link_template:{store_code}

  • Link to store-specific landing page:
Ensure that you are submitting data correctly when showing on-sale products
  1. If you are submitting the <sale_price> attribute to show on-sale products, make sure that you are also submitting the <sale_price_effective_date> attribute to specify when a sale expires.
  2. Otherwise, you run the risk of showing a <sale_price> that is no longer active on your product landing page which will result in a mismatched price.

Was this helpful?
How can we improve it?
Clear search
Close search
Google apps
Main menu
Search Help Center