The Google Shopping API returns Google's shopping results for a product query as structured rows — title, price and currency, seller, rating and review count, condition, a multiple-sources flag, the product link and Google's own product_id.
It answers a question no single retailer can: what is this product selling for, right now, across every merchant Google indexes in this country. The product_id is the hinge — feed it to the Product offers API and you get the full per-seller offer list for that product instead of the one price Google chose to surface.
$0.001 per delivered listing, up to 100 listings per run. Nothing delivered means nothing charged.
A query and a country go in; the collector runs the Shopping vertical from an exit in that country, paginates until it reaches max_results and returns each listing as a flat row.
The country matters more here than almost anywhere else. Google Shopping is a per-market surface: merchants, currencies, availability and even which products exist differ between the US and Germany. A US-exit request for a German price list returns a coherent-looking answer to the wrong question.
Two fields carry more information than their names suggest. multiple_sources tells you Google has clustered several merchants behind this entry, which is the signal that the Product offers collector will return something interesting. tag carries the badge Google renders — sale, price drop and similar — which is a cheap promotion detector.
query is required and should be the product as a shopper would type it, not a SKU. country selects the Shopping market and the proxy exit together; lang sets the interface language. max_results caps delivery, and since billing is per delivered listing it is also your budget control.
Each listing is a row with price as displayed and price_value as a number, plus explicit currency — worth keeping, because a cross-market comparison that assumes one currency is the most common way these datasets go wrong. seller is the merchant, rating and reviews are the product's, not the merchant's, and product_id is Google's identifier for the clustered product, which is what makes offer expansion possible.
$0.001 per delivered listing ($1 per 1,000). Nothing delivered means nothing charged, and the $2 monthly free credit covers roughly 2,000 listings here. Volume tiers take up to 30% off.
$0.001 per delivered listing, $1 per 1,000. Monitoring 300 products daily at 20 listings each is 6,000 rows, $6 a day at list price, less on a volume tier.
The cost-efficient pattern is two-stage: use this collector wide to find which products and which merchants matter, then spend the more expensive Product offers call only on the handful where the full seller list changes a decision.
Google's Content API for Shopping — and its successor, the Merchant API — are frequently the first result for this query and are almost never what people searching for it want. They are merchant-side tools: they let you upload and manage your own product feed. They do not let you read what other merchants are charging, which is the entire point of a shopping price comparison.
There is no official Google API that returns public Shopping search results. Google's Custom Search JSON API covers web results, not the Shopping vertical, and its index is a subset. That gap is why a scraping-based collector exists for this at all: the results are public, they are just not published through an API.
Google Shopping is one of the harder public surfaces to collect reliably, and the difficulty is not the parsing:
This collector handles the exits, the retries and the parsing; you get rows with an explicit currency and a stable schema.
One query returns what every indexed merchant charges, so you can build a comparison page or a repricing input without integrating with any of them.
Track the lowest and median price_value per product per day and feed it to whatever sets your own prices.
Run the same product query with a different country to see who competes, at what price, in a market you do not sell in yet.
The tag badge and a moving price_value together tell you when a competitor is running a genuine promotion rather than a permanent 'sale' price.
Up to 100 listings per run with pagination handled internally. Broader coverage means more runs — per product, per country — each billed on delivery. Throughput follows your plan's rate limit, 60 requests/minute on pay-as-you-go up to 1,200 on the top tier.
Legally: shopping results are public search results, and collecting public data is generally lawful in most jurisdictions, but Google's terms restrict automated access and the analysis differs by country. Prices and merchant names are commercial data rather than personal data, which simplifies the privacy side but does not remove the terms question. Not legal advice.
Not from Google for reading public Shopping results — its Content and Merchant APIs manage your own product feed rather than returning other merchants' prices. Here there is a free allowance of $2 a month with no card, about 2,000 delivered listings at $0.001 each.
$0.001 per delivered listing — $1 per 1,000 — with no subscription and no minimum. Volume tiers take up to 30% off, and GET /v1/scraper/collectors returns the exact price your key pays. Blocked pages and empty runs are never billed.
Yes, in two steps. This collector returns the listings Google surfaces for the query, each with a product_id; passing that id to the Product offers collector returns the full per-seller offer list with totals, which is the proper cross-seller price comparison.
No. You authenticate with your QuantumProxies key. There is no Google Cloud project, no billing account and no Merchant Center relationship involved.
Yes. Pass an ISO country code and the run uses a proxy exit in that country with matching locale parameters, so you get that market's merchants, currency and availability rather than a US page seen through a foreign IP.
It is Google's identifier for the clustered product. It is the key that turns one shopping listing into the complete list of sellers and totals via the Product offers collector — and it stays stable enough to use as a join key between runs.
Collecting publicly displayed search results is generally lawful in most jurisdictions and this is commercial rather than personal data, but Google's terms restrict automated access and the analysis differs by country. Take proper advice for your use case; this is not it.
Skip the marketing. QuantumProxies.io publishes a machine-readable site map, Markdown for every page, a free MCP server, and APIs billed from the same balance as your proxies.
Connect in one command: npx -y quantumproxies-mcp