You have launched a product feed for several countries, but you don't know what the buyer in Germany, Poland, or the USA actually sees. It often turns out that prices are displayed in the wrong currency, delivery is indicated only for one country, and the product card in the results looks as if the store doesn't operate in that region at all. We will discuss how to check this independently, without traveling and without access to foreign SIM cards.
Why Check Google Shopping in Other Countries
Google Shopping generates results tailored to each region: it considers the country of the IP address, the interface language, the geolocation settings of the account, and the default currency. This means that a product that is displayed correctly in Moscow may show up in Berlin with a price in rubles, with delivery marked as "not available," or may not appear in search results at all.
For marketplace sellers and e-commerce teams launching product campaigns in Germany, Poland, the USA, or the UAE, this is critical: a feed error directly kills conversion. If a user sees the wrong currency, they close the tab. If they see "delivery not available," they won't even open the product card. Meanwhile, the advertiser in their Google Merchant Center account often does not notice the problem because they see the feed through the lens of their own country, not through the eyes of the target audience.
Checking the feed from the required geolocation is not a theoretical hygiene measure, but a practical way to avoid wasting budget on Google Ads and Google Shopping campaigns that physically do not reach the buyer due to visual and technical discrepancies.
Common Feed Issues When Entering New Markets
In practice, when launching multi-country campaigns in Google Shopping, several typical problems arise:
- The price in the feed is indicated in the currency of the main market, not in the local currency of the display country — the buyer sees amounts in dollars instead of euros, for example.
- The shipping attribute is filled out only for one country, which means the product either does not show up in other regions or shows up without shipping information, reducing CTR.
- Taxes are not accounted for the specific country, and the final price on the website does not match the price in the ad — Google may suspend the display of such products.
- The language of the product title and description is not adapted, even though the geo-targeting of the campaign is set to a country with a different language.
- In Merchant Center, one "target country" is selected, while the website actually serves multiple language versions with different prices.
All these problems can be identified in one way — by actually viewing the results from the perspective of a user in the required country, not through settings in the account.
How Google Determines the Country and Currency Displayed
Google Shopping uses a combination of signals: the device's IP address, the query language, Google account settings (if the user is logged in), and the feed parameters in Merchant Center (target country, feed label, price currency). If you access the search from Russia, even entering a query in English, Google will most often still rely on geolocation by IP as the primary signal for regional Shopping ad display.
Therefore, simply changing the browser interface language will not show you how a real buyer from Warsaw or New York sees the product. You need to change the IP address to one that physically belongs to the required country — this is the only way to accurately reproduce the viewing conditions of the target audience.
VPN or Proxy: What Is Suitable for Feed Checking
Many try to solve the task through a free VPN, but this is a poor option for checking Google Shopping for several reasons: VPN servers are massively used by thousands of users simultaneously, their IP ranges are known to Google and are often marked as data center or suspicious, which can lead to results being displayed with captchas, restrictions, or distorted — not as a live user with regular home internet would see it.
For accurate feed checking, residential proxies are more suitable — they use IP addresses from real home providers in the required country, so Google sees you as an ordinary local user, not a bot or VPN client. This provides the most honest picture: this is exactly the results, price, and delivery availability that a real buyer from Berlin, Warsaw, or Dubai will see.
If you need to check how the feed looks specifically from mobile search (as Google Shopping often formats cards differently for desktop and mobile), it makes sense to additionally test through mobile proxies — they use IPs from mobile operators and provide the most realistic picture of mobile results, including adaptive delivery blocks and promo badges.
For quick and bulk checks, when you need to go through 15-20 countries and simply capture screenshots of the results without requirements for "live" IP, more budget-friendly data center proxies will also work — they maintain a faster and more stable connection during serial checks, although for final control before launching the campaign, it's better to confirm the result through a residential IP.
| Proxy Type | When to Use for Google Shopping | Data Accuracy |
|---|---|---|
| Residential Proxies | Final check before campaign launch, checking price/currency/delivery as a real buyer | High |
| Mobile Proxies | Checking mobile Google Shopping results, adaptive delivery blocks | High |
| Data Center Proxies | Mass serial checks across dozens of countries, rough verification | Medium |
Step-by-Step Setup for Country Checks
If you manage several markets simultaneously, it is most convenient to set up checks through an anti-detect browser — this will allow you to store separate profiles for each country, avoiding confusion with cookies and search history between regions. Dolphin Anty, AdsPower, Multilogin, or GoLogin will work — any of them supports proxy connections at the individual profile level.
- Create a separate browser profile for each target country (for example, one for Germany, one for Poland, one for the USA).
- In the profile settings, specify the proxy type as SOCKS5 or HTTP, and insert the residential proxy data with the geolocation of the required country.
- In the profile settings, set the system language and time zone corresponding to the selected country — this additionally removes discrepancies in signals for Google.
- Open Google.com (not the local google.ru or google.de — specifically google.com, to see the automatic region detection) and enter a search query for your product.
- Go to the "Shopping" tab and examine how your product card appears in the results.
- Repeat for the mobile version — open the site through a mobile user-agent in the same profile or additionally check through mobile proxies.
This approach is especially convenient if the checking is done by an SMM or performance team managing multiple client Google Ads accounts — profiles do not get mixed up, each check is reproducible, and results can be captured with screenshots for reporting to the client.
Checking Prices and Currency in the Results
After you open the Google Shopping results from the required country, first look at three parameters: the currency displayed next to the price, the correctness of the price conversion relative to the exchange rate, and the match between the price in the ad and the price on the website after clicking through.
If you set the feed for Germany, but see a price in dollars or rubles when accessing from a German IP — this is a direct signal that a separate feed for this country with local currency is not set in Merchant Center, or the "target country" setting does not match the actual display country. Google allows a price discrepancy in the ad and on the website of no more than a small percentage (usually this concerns dynamic discounts), but a constant discrepancy in currency is already a reason for product suspension by moderation.
It is also important to check the rounding of the price and the format of separators: in some countries, a dot is used as a separator, while in others, a comma is used, and incorrect display can visually confuse the buyer, even if the price is technically correct.
Checking Delivery Conditions in the Product Card
The shipping attribute in the Google Shopping feed is one of the ranking factors and one of the main triggers of buyer trust. If the product card shows "Delivery not available" when opened from the required country or does not display the delivery conditions block at all, the user will most often go to a competitor who clearly indicates delivery.
When checking from a proxy of a specific country, pay attention to whether the estimated shipping cost is displayed, the delivery times (Google often shows a range of days), and whether free shipping is available if it is stated in the feed. It is not uncommon for the shipping attribute to be filled out correctly for the country, but in the actual results, Google shows outdated data due to a delay in re-indexing the feed — in this case, check the last updated date of the feed in Merchant Center and manually trigger a re-upload.
If you sell physical goods and work through different logistics schemes for different regions (for example, your warehouse in Europe and delivery from China for other countries), be sure to check delivery separately for each region — the logic of the shipping attribute in the Google Shopping feed is tied specifically to the delivery country, not the seller's country.
Typical Mistakes in Multi-Country Feeds
Based on the practice of checking feeds for various e-commerce niches, a recurring set of mistakes can be identified that most often arise when entering foreign markets through Google Shopping:
- One common feed for all countries without separation by feed label — Google gets confused about which price is relevant for which country.
- The price is indicated without considering local VAT or import duties, causing the final amount during checkout on the website to differ from what was stated in the ad.
- The brand name or product category is not localized, causing the product to rank poorly for local search queries.
- The availability attribute is missing for a specific region — the product is shown in Germany as "in stock," even though it is not physically delivered there.
- Holiday or seasonal delivery restrictions for a specific country are not taken into account, causing the timelines in the ad to not match the actual ones during checkout.
Pre-Launch Checklist
Before launching or scaling a Google Shopping campaign to a new country, go through this short list:
- The results are opened through a residential IP of the required country, not through a VPN or browser language change.
- The price in the ad is displayed in local currency and matches the price on the website after clicking through.
- The delivery block is displayed correctly, and the timelines and costs correspond to the real conditions for that country.
- The check has been conducted for both desktop and mobile results.
- The feed in Merchant Center is separated by countries through feed labels, not maintained as a single list for all markets.
- Taxes and duties are accounted for in the final price for the specific region.
Conclusion
Checking Google Shopping through the eyes of a real buyer from another country is not a one-time formality, but a regular practice for any business that runs campaigns in several regions. Errors in currency, price, or delivery directly reduce conversion and can lead to product suspension by Google moderation, even if the technical setup of the feed in Merchant Center looks correct at first glance.
If you regularly launch or scale campaigns to new countries, for accurate checking of the results, we recommend using residential proxies — they provide the most honest picture of what a live buyer sees. For checking the mobile version, mobile proxies are useful, and for quick serial runs across multiple countries, more affordable data center proxies will suffice.