The Price Competitiveness report in Google Merchant Center tells you how your product prices compare to other merchants selling the same or similar items. It shows a benchmark price for each product based on competitive data Google collects from participating merchants. If your price is significantly above the benchmark, your listing receives fewer impressions in Google Shopping results regardless of your bid.
This guide covers what the report shows, why price matters for your Shopping ad quality, which price problems can get your products disapproved, and how to audit your full feed for pricing issues.
The report compares your price to a benchmark price Google calculates for each product. The benchmark is typically keyed to the product's GTIN or product type, and it is weighted toward prices that are actually winning clicks and converting, not a simple average across all merchants.
For each product, the report shows:
You can filter the report by country, product category, brand, or custom label. This makes it practical to focus on the categories where you are most above benchmark and where those products drive significant impressions.
To find it: in Merchant Center, go to Insights, then select Price competitiveness.
A price above benchmark by a small margin often has minimal impact. A price more than 15% above benchmark on a high-impression product is where you start losing meaningful click volume to competitors. That is where to focus first.
Price is one of the strongest signals in Google Shopping's ranking algorithm. A product priced above comparable listings receives fewer impressions than the same product priced at or below market rate, regardless of bid level. Raising bids does not fully compensate for a price that is significantly above benchmark.
The reason is Google's quality score for Shopping ads. Google wants to show users ads that lead to purchases. A higher price relative to comparable offers means lower click-through rates and lower conversion rates, which trains the algorithm to serve your listing less often.
For sellers using Performance Max campaigns, this effect is amplified because the campaign optimizes toward conversions. If products above benchmark convert poorly, PMax will shift budget away from them automatically over time.
Products where you are at or below benchmark get a real advantage: more impressions for the same bid, lower cost per click relative to traffic volume, and better campaign efficiency overall.
Shipping costs matter here too. Google's benchmark may not fully account for shipping costs in all cases. A product priced 10% above benchmark with free shipping may effectively be more competitive than it looks in the report. Check your total landed cost to the buyer (price plus shipping) when evaluating whether a price gap is a genuine problem.
Being above the benchmark price reduces your Shopping visibility but does not trigger a policy violation. The pricing problems that cause actual GMC disapprovals and suspensions are different. They involve discrepancies between what your feed says and what your website shows.
This is the most common pricing violation. Your product feed shows one price, but when Google's crawler visits your landing page, the price displayed is different. A typical example: the feed shows 29.99, the page shows 34.99 because a sale ended but the feed was not updated. Google flags this as a misrepresentation policy violation. It can result in the product being disapproved and, in repeated cases across many products, an account-level warning.
The fix is to keep your feed and your website prices in sync. If you run sales, update the feed immediately when the sale ends. Alternatively, enable automatic item updates in Merchant Center, which lets Google crawl your structured data to detect and apply price corrections without waiting for a feed refresh.
If your feed includes a sale_price_effective_date attribute with an end date that has passed, but the sale_price field still shows a reduced price, you have a conflicting signal. Some feeds send a sale price without an end date, which means Google treats it as indefinite. When the website eventually returns to the regular price, a mismatch appears. Always pair sale_price with a valid sale_price_effective_date.
In some markets, your feed may show prices excluding VAT while your landing page displays prices including VAT. Google compares the numbers, not the tax treatment. If this creates an apparent mismatch, check whether your target market expects tax-inclusive pricing in the feed. In the EU, Shopping prices typically need to include VAT to match what customers see on the page.
Checking price issues manually for a large catalog is not practical. A structured audit process handles it systematically:
schema.org/Product with offers.price and offers.priceCurrency on every product page. This is what automatic item updates reads. Without it, Google cannot self-correct mismatches.The GMCSuspension audit tool checks your Merchant Center account across 52 policy areas including price mismatches, feed errors, and missing required attributes. Run a scan before problems become disapprovals.
Run a Free GMC AuditPrice competitiveness affects how often your listings appear in Shopping results. Price accuracy affects whether they stay approved at all. Both matter for a healthy Merchant Center account. The Price Competitiveness report helps you with the former; the Diagnostics tab and a regular feed audit handle the latter.