Search

Google Shopping residential proxies

Google Shopping is a local-offer graph behind the same Google anti-bot stack as Search. Country still owns currency, eligible merchants, and the national catalog. City owns the offer set a household actually sees: store pickup, shipping ETA, local inventory, and some sponsored slots. A country-US exit can return a valid 200 whose merchants and delivery dates describe a market nobody on your team sells into. Pin Premium to each country for catalog and FX work; add Elite city targeting when pickup, shipping, or store-level price is the metric — then verify the city you landed in before you trust the row.

MTWritten by Marcus Thorne·Reviewed by Sarah Chen·Updated July 2, 2026

Premium country routing is the default for catalog, currency, and merchant-eligibility jobs that do not vary below the national line. Switch to Elite city (and ISP only if the network is the variable) when the object is local inventory, store pickup, shipping ETA, or a sponsored mix that changes by metro.

Why Google Shopping is hard

  • Currency, tax display, and which merchants are allowed to sell are country-localized — the wrong country is a wrong catalog, not a noisy price.
  • Pickup, shipping, and some offer cards resolve against an approximate location, so two US metros can return different merchants for the same query.
  • Product grids trip the same unusual-traffic limits as Search when one exit queries too fast.
  • Empty carousels and challenge pages both look like HTTP 200; storing them as “no merchants” poisons price history.

How to approach Google Shopping with Aethyn

Pin -country-<cc> so currency and eligible merchants match the market you report; match gl and hl to that country.
Add Elite -city- when pickup, shipping, or local inventory is the metric, then verify resolved city before the first Shopping request.
Rotate per independent SKU query; hold a sticky session (30 min by default on the rotating pool) only while pagination or a store cookie must survive.
Classify challenge vs empty carousel vs populated offers. Never write empty as no merchants.

Targeting & session tips

  • Country owns catalog and FX. City owns local offer set, pickup, shipping, and some sponsored slots.
  • Asking for a city is not landing there — record resolved city from an IP lookup, not the username you sent.
  • Keep a stable country mapping for day-over-day FX series; open a new sticky session per metro when you sample cities.

See the full targeting reference for username suffixes.

Related use cases

Guides that use Google Shopping proxies

Google Shopping proxy FAQ

Why do prices differ between my proxy runs?
Shopping localizes catalog, merchants, and often delivery. Pin a stable country per market for FX work. If pickup or shipping is the metric, pin Elite city, verify the exit, and sample more than one household in that metro to separate a real change from a session promo.
Do I need city targeting for Shopping?
Not for national catalog, currency, or merchant eligibility — Premium country routing is enough. Yes when the object is local inventory, store pickup, shipping ETA, or a sponsored mix that changes by metro. Elite adds the city on the username; verify the city you resolved.
Can I monitor a competitor's price across countries?
Yes — one country-pinned exit set per market, normalize currency and tax, and do not mix city-local offer rows into a national series.

Start collecting Google Shopping data

Route through high-trust residential IPs with transparent per-byte pricing.

Other targets

All target guides