Tax configuration is one of the most overlooked causes of product disapprovals in Google Merchant Center. If the price in your feed does not match the price Google's crawler sees on your product page, you will get price mismatch flags. Do that across enough products, and Google upgrades the problem from item-level disapprovals to an account-level misrepresentation suspension.
This guide explains exactly how to set up tax in Merchant Center for US and EU sellers, why mismatches happen, and how to fix disapprovals before they escalate.
Google compares the price in your product feed with the price it sees when it crawls your product pages. If those two numbers differ by even a small amount, Google flags the product as having a price mismatch.
Tax is a common source of that mismatch for two reasons. First, some stores send VAT-exclusive prices in the feed but display VAT-inclusive prices on the product page. Google sees 79.99 in the feed and 95.99 on the page and flags it. Second, some stores configure their Merchant Center tax settings incorrectly, so Google applies additional tax to a price that already includes VAT, making the calculated total higher than what the shopper pays.
Both situations trigger the same disapproval: "Price mismatch." But the fix depends on where the mismatch originates.
In the US, the standard approach is to send pre-tax prices in your product feed and configure state tax rates in Merchant Center. Google then handles the tax display at the ad level. Here is how to set it up correctly:
The most common mistake US sellers make is setting up Shopify or WooCommerce to display prices with tax included in certain regions, then sending pre-tax prices in the feed. Google crawls the page, sees the tax-inclusive price, and flags a mismatch. Check your platform's tax display settings against your feed prices if you sell into states with mandatory tax-inclusive display requirements.
EU e-commerce law requires that product prices include VAT. This means your product pages, your feed, and your Merchant Center tax settings must all agree that prices are VAT-inclusive.
Sellers who operate across both US and EU markets often run separate Merchant Center accounts for each region, each with the appropriate tax configuration. If you run one account for both markets, check whether your feed is sending region-specific prices or a single global price, and make sure the tax setting matches.
| Scenario | Feed price | Page price | Fix |
|---|---|---|---|
| EU seller, tax not included in feed | 79.99 (ex-VAT) | 95.99 (inc-VAT) | Enable "Tax included in price" in GMC, or update feed to VAT-inclusive prices |
| US seller, page shows tax-inclusive | 99.00 (pre-tax) | 107.00 (inc-tax) | Display pre-tax price on page, or send tax-inclusive price in feed and disable state tax in GMC |
| Currency display rounding | 29.99 | 30.00 | Align rounding logic in feed and on page |
| Promotional price on page, regular in feed | 59.00 | 49.00 (sale) | Add sale_price attribute in feed, or remove promotion from page during feed sync |
A single product with a price mismatch gets disapproved at the item level. That is manageable. The problem escalates when a significant portion of your catalog shows the same discrepancy.
Google's 2026 AI verification system cross-checks prices more aggressively than before. When it sees systematic price differences that suggest a shopper would pay more than advertised, it escalates the account to a misrepresentation review. At that point, you are no longer dealing with a feed error. You need to resolve the root cause and appeal the account-level flag.
Before you appeal, run the free GMCSuspension.com audit. It checks your store's pricing signals, tax configuration consistency, and 41 other policy requirements in about 60 seconds, giving you a specific list of what to fix before you submit your appeal.
After correcting your tax settings and feed, verify the fix through Merchant Center's Diagnostics tab:
If the Diagnostics tab shows the same price on the page and in the feed but the product still disapproved, the issue may be a crawl lag. Wait 48 hours and check again before making further changes.
The GMCSuspension audit crawls your store as Google does and checks price consistency, tax signals, and 41 other policy requirements. It takes about 60 seconds and costs nothing to run.
Start Your Free AuditA price mismatch almost always means the price in your product feed does not equal what Google's crawler reads on your product page. Tax treatment is the most common cause: a feed with pre-tax prices but a page showing tax-inclusive prices will always trigger a mismatch. Align both to the same price format.
It depends on your market. US sellers typically send pre-tax prices and configure state tax rates in Merchant Center. EU sellers must send VAT-inclusive prices by law and must enable "Tax included in price" in Merchant Center. The product page price must always match the feed price exactly.
This setting tells Google whether your feed prices already include tax. Enabling it is mandatory for EU sellers. If you enable it but your feed prices are pre-tax, Google will treat those prices as VAT-inclusive and show them without adding tax, which may mismatch what the shopper actually pays at checkout.
Yes. Systematic price mismatches across many products are treated as misrepresentation. Google considers showing a different price than what the shopper pays to be a deceptive practice. Repeated price mismatch flags escalate from item-level disapprovals to an account suspension if not corrected.
Check the Diagnostics tab for "price mismatch" or "incorrect price" issues. Compare the price Google found on your page vs your feed. Correct either the feed prices or your Merchant Center tax settings so the two match. After updating, trigger a re-crawl and expect 24-72 hours for the disapprovals to clear.
For more on fixing product-level issues in Merchant Center, read the guide to disapproved products and the full suspension checklist. If your account is already suspended, the misrepresentation checklist covers all 52 audit checks in order.