GMC Error "country_not_supported": Causes and Fix

You upload a feed to Google Merchant Center and a batch of products comes back disapproved. The Diagnostics panel shows this:

Issue: Country where you sell products not supported
Attribute: Target country [targetCountry]

In the Content API and Merchant API the same problem surfaces under the identifier country_not_supported. The display label varies ("Country where you sell products not supported," "Unsupported country," "Target country not supported"), but the underlying check is the same: you told Google to show these products in a country where the destination you are using is not available.

This one trips up merchants expanding into new markets and merchants who duplicated a feed for a second country and forgot to change one setting. This post covers what Google actually validates, the four ways the error fires, and how to fix each.

TL;DR

country_not_supported fires when the targetCountry on a product (or the feed's target country) is a country where the destination program (Shopping ads, Free listings, etc.) does not operate.
The fastest fix: go to Products > Needs attention, filter for the affected items, and set a Google-supported target country.
It is not the same as a shipping or currency error. Google supports different programs in different countries, and a country that works for Shopping ads may not work for Free listings or Local inventory ads.
Duplicating a feed for a new market without changing the target country is the single most common cause.
Check Google's supported-country list for your specific destination before targeting a market.

What `country_not_supported` actually means

Every product in Merchant Center has a target country, either set at the feed level when you create the data source or per-product via the targetCountry attribute. Google's Merchant Center country restrictions doc spells out which countries each program runs in, and those lists are not identical across programs.

Google's verbatim explanation of the cause is short:

Google doesn't currently support the target country you submitted.

The check happens in two layers:

Program availability. Shopping ads, Free listings, Display ads, and Local inventory ads each have their own list of supported countries. A country can be valid for one program and unsupported for another.
Account and feed configuration. Your Merchant Center account has a business country. The target countries you submit have to be reachable from that account configuration, which is where multi-country sellers run into restrictions.

When the target country fails either layer, the product is disapproved and the issue logs as country_not_supported.

Why Google flags it

A target country is not a suggestion. It controls which Google surface the product is eligible to appear on and which legal and tax rules Google applies. If Google does not run Shopping ads in that country, there is no surface for the listing to appear on, so the product cannot serve. Rather than silently dropping it, Google disapproves it and tells you why.

The error is almost always a configuration mistake rather than a data-quality problem. The product data itself is usually fine. The country you pointed it at is wrong, unsupported, or mistyped.

Four fixes ranked by frequency

Fix 1: Set a supported target country in the Needs attention tab

This is Google's documented fix for the single-product case. From the How to fix: Country where you sell products not supported article:

In Merchant Center, go to Products > Needs attention.
Use the filter above the table to isolate products with the country issue.
Click a product title and choose Edit product.
Select a country that Google supports for your destination.
Click Save.

For bulk corrections:

Go to Products > Needs attention.
Filter for the affected items.
Download the CSV with the download icon.
Update the target country column in your product data at the source.
Reupload the corrected file.

Google notes it may take time for fixed products to clear off the Needs attention page after the next fetch.

Fix 2: Fix a duplicated feed that kept the old target country

The most common root cause in practice. A merchant has a working US feed, duplicates it to launch in Canada or the UK, and changes the currency and language but leaves the target country pointed at a market the new destination does not support, or leaves it on the original country entirely.

The fix: open the data source settings for the new feed and confirm the target country matches the market you actually intend to sell in, and that the market is supported for the program you are running. If you are running Shopping ads in the new country, verify it appears on the Shopping ads supported list, not just the Free listings list.

Fix 3: Confirm the country is supported for your specific program

A country can be live for Free listings but not for paid Shopping ads, or supported for Shopping ads but not for Local inventory ads. Before targeting a market, check the supported-country list for the exact destination you are using. The Merchant Center country restrictions page is the authoritative source and is updated as Google expands.

If the country genuinely is not supported for your program yet, there is no feed fix. You either wait for Google to expand the program there or remove those products from that feed so they stop generating disapprovals against your account.

Fix 4: Correct a mistyped or wrong-format country value

Target country is an ISO 3166-1 alpha-2 code (US, GB, DE, CA, AU). A feed that submits a full country name ("United Kingdom" instead of GB), a three-letter code (GBR), or a typo gets read as an unsupported country.

Where this goes wrong:

A spreadsheet feed where someone typed the country name by hand.
A custom export template that emits the wrong country format.
A localization plugin that writes locale strings (en-GB) into the country column instead of the bare alpha-2 code.

The fix: normalize the country column to ISO 3166-1 alpha-2 codes at the source before the feed is generated.

How to verify the fix

Check the supported list first. Confirm your target country is live for your destination on the country restrictions page. If it is not, no feed change will clear the error.
Spot-check products in Merchant Center. After the next fetch, open a few of the previously affected products and confirm the target country reads as the supported code you set.
Wait for the recrawl. Re-review completes after Google's next feed fetch, typically within 24 to 72 hours. Do not resubmit the feed repeatedly during the window.

What not to do

Do not target a country just because you ship there. Shipping availability and program availability are different. Google has to run the program in that country for the listing to serve.
Do not leave unsupported-country products in the feed to "try again later." They generate ongoing disapprovals that drag on your account-level data quality. Remove them until the program is available.
Do not submit locale strings as the country. targetCountry is a bare two-letter code, never a language-country locale like en-US.

How SnowPipe handles this

SnowPipe syncs Shopify, WooCommerce, and BigCommerce catalogs to Google Merchant Center through the Merchant API v1. The target country is set per Google Merchant connection, so every product in a sync inherits one consistent, validated country code rather than a per-row value that a spreadsheet or plugin can corrupt.

When Google does reject a product, SnowPipe's error reporting surfaces the exact reason string Google returned, per row, in the job results. A country_not_supported rejection shows up as its own error category with the affected products listed, so you are not hunting through the Needs attention tab trying to figure out which products and which setting caused it.

Frequently asked questions

What does "country_not_supported" mean in Google Merchant Center?

It means the target country you assigned to a product is a country where the Google program you are using (Shopping ads, Free listings, and so on) is not available. The product cannot serve because there is no eligible surface in that country, so Google disapproves it.

Is country_not_supported a shipping problem?

No. It is a program-availability problem. The country you targeted is not supported for the destination, regardless of whether you can ship there. Shipping configuration is validated separately.

How do I find which countries Google supports?

Check Google's Merchant Center country restrictions page. Supported countries differ by program, so confirm the country is live for the exact destination you are running, not just for Free listings.

What format should the target country be in?

An ISO 3166-1 alpha-2 code such as US, GB, or DE. Full country names, three-letter codes, and locale strings like en-GB are all read as invalid or unsupported.

How long does it take to clear after I fix it?

Re-review happens on Google's next feed fetch, typically within 24 to 72 hours. Resubmitting the feed repeatedly during the window does not speed it up and can delay re-review on other products.

Ready to stop chasing country and feed-config errors one product at a time?

Try SnowPipe free — connect your store and get a single validated target country per destination plus row-level error reports. Or, book a 15-min demo and I'll walk you through your specific setup.