Scraping API PricesHome / Cost to scrape / Google Shopping
Cost to scrape Google Shopping at 10K, 100K, and 1M
Published Google Shopping scraping rates, plan costs at three billable volumes, access facts, protections, and the official API option.
Access
Protections in the way
Terms
What you scrape moves the bill more than who you buy from. A target that forces JavaScript rendering or a residential exit multiplies the meter before any plan is chosen.
What each vendor charges for this target
| Product | Costs | Source |
|---|---|---|
| ScraperAPI | 25 credit | source |
| ScrapingBee | 20 credit | source |
| ScrapingBee | 10 credit | source |
| ScrapingBee | 15 credit | source |
| Scrape.do | 10 credit | source |
| SerpApi | 1 search | source |
| Oxylabs Web Scraper API | 0.001 usd | source |
| ScrapeOps | 10 credit | source |
| ScrapingAnt | 10 credit | source |
| ScrapingDog | 10 credit | source |
Access fact, checked 2026-07-26: Google’s Terms prohibit automated access that violates machine-readable instructions on its web pages (Source).
Cost to scrape Google Shopping at 10K, 100K, and 1M table
| Route | 10K | 100K | 1M | Billing rule and source | Checked |
|---|---|---|---|---|---|
| ScraperAPI | $149 (Startup) | $299 (Business) | Quote required | 25 credit per request | 2026-07-26 |
| ScrapingBee, normal mode | $49 (Freelance) | $99 (Startup) | Quote required | 10 credit per request | 2026-07-26 |
| ScrapingBee, normal mode | $49 (Freelance) | $249 (Business) | Quote required | 15 credit per request | 2026-07-26 |
| Scrape.do | $29 (Hobby) | $99 (Pro) | $699 (Advanced) | 10 credit per request | 2026-07-26 |
| SerpApi | $150 (Production) | $725 (Searcher) | $3,750 (Cloud 1M) | 1 search per request | 2026-07-26 |
| Oxylabs Web Scraper API: Google Shopping search and product targets | Not published | Not published | Not published | Target endpoint is documented, but no target-specific public rate is in the record | 2026-07-26 |
| Merchant API | No separate fee published | No separate fee published | No separate fee published | No separate API fee is published; Merchant Center quotas apply. | 2026-07-26 |
The comparison uses 10,000, 100,000, and 1,000,000 billable target calls or delivered results per month, calculated on 2026-07-26. It does not claim those calls all become useful rows. Credit, request, result, and search meters are passed through the dataset quote model, which selects the least expensive published self-service offer that covers each volume. A starting USD rate is shown as a lower bound because an unpublished minimum, tier, or contract can raise the invoice. Retries, pagination, duplicate outputs, taxes, and data licensing are outside these figures.
The published price answer
The record contains 5 published target-rate lines across 4 vendors. Those are the only rows allowed to produce a target-specific dollar result. Different light, normal, HTML, rendered, protected, or dedicated modes stay separate because collapsing them would hide the unit change that drives the bill. A plan name in a cell is the offer selected from that vendor record, not a recommendation.
Google SERP requests on all Google subdomains cost 25 credits. docs.scraperapi.com. Google API light mode costs 10 credits; normal mode costs 15 credits. help.scrapingbee.com. Google API normal mode costs 15 credits; light mode costs 10 credits. help.scrapingbee.com. Google domains cost 10 credits with residential routing applied by default. scrape.do. A Google Shopping engine call consumes one SerpApi search. serpapi.com.
Rendering and access change the job
This record classifies Google Shopping as hard and records rate limiting, CAPTCHA, bot detection and fingerprinting, IP reputation checks, geographic variation or restriction, dynamic rendering. JavaScript rendering is required in the recorded profile, so a plain HTML request is not the same workload. Residential routing is recorded as needed, but no generic proxy multiplier is silently added: the table applies only a vendor’s explicit target meter.
Product, offer, seller, search, and availability data are different outputs, so a vendor endpoint must be checked against the exact fields the job needs.
The official route is a separate product decision
Merchant API is recorded as available. Requires a Merchant Center account and manages that merchant’s own products rather than public Shopping search results. No separate API fee is published; Merchant Center quotas apply. Merchant API manages the authenticated merchant account and does not return the same public Shopping search dataset. Source and access status checked 2026-07-26.
Endpoint evidence and the remaining unknown
The dataset confirms 4 dedicated endpoints or templates. This proves named target support in the cited product documentation. It does not prove that each endpoint has a public target-specific price.
- Google Shopping API is paired with a published target meter in the cost table.
- Google Shopping search and product targets is documented, while its target-specific price remains unpublished in this record.
- Google Shopping API is paired with a published target meter in the cost table.
- Google API with Shopping support is paired with a published target meter in the cost table.
What volume means for Google Shopping
One useful unit is one product-offer observation for a fixed query, location, language, device, and refresh. Discovery uses Shopping result pages; full product and seller coverage can require separate product or stores calls for selected product IDs. SerpApi, Oxylabs, Scrape.do, and ScrapingBee document dedicated Shopping routes, which return structured search or product objects but do not make one search request equal to every product-offer observation downstream. (SerpApi Google Shopping API, Oxylabs target catalog, and Scrape.do Shopping API, retrieved 2026-07-27.)
Scrape.do’s Shopping response can carry up to 40 top-level items, but its documented next link can advance the start offset by 10, so the honest pagination rule is to follow the returned link until pagination is absent rather than divide a claimed total by 40. Product seller pages have their own continuation token. Google’s Merchant API manages an authenticated merchant’s own catalog, so it does not answer the public comparison-shopping search question represented by these result pages. (Scrape.do Shopping pagination, Scrape.do Shopping product stores, and Google Merchant API, retrieved 2026-07-27.)
Evidence to check before buying
- ScraperAPI prices Google SERP requests on all Google subdomains at 25 credits docs.scraperapi.com.
- Scrape.do applies residential routing to Google domains at 10 credits scrape.do.
- Oxylabs maintains separate Google Shopping product and search targets developers.oxylabs.io.
- Confirm the exact entity and output unit, whether a page, search, result, record, or API object. Then multiply by pagination and refresh frequency before selecting a plan.
- Fix the required country or market before pricing. The recorded geographic variation means one nominal URL can represent different jobs.