Google Shopping Scraper & Product Search API avatar

Google Shopping Scraper & Product Search API

Under maintenance

Pricing

from $2.70 / 1,000 api request attempts

Go to Apify Store
Google Shopping Scraper & Product Search API

Google Shopping Scraper & Product Search API

Under maintenance

Search Google Shopping by product keyword and collect result pages as JSON for product research and price comparison. Set language, country, sorting, and result offset. $0.0027/request attempt + $0.002/run. Paid Apify plan required.

Pricing

from $2.70 / 1,000 api request attempts

Rating

0.0

(0)

Developer

Xtech

Xtech

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

17 days ago

Last modified

Categories

Share

Google Shopping Scraper & Product Search API

Search Google Shopping by product keyword and collect structured result pages for product research and price comparison.

Use the Apify input form or API to send 1โ€“20 requests per run. Each successful request saves one complete response page in the dataset. No proxy setup or separate API key is needed.

What can you use it for?

  • Research products across selected search terms.
  • Compare returned product offers in your own analysis pipeline.
  • Collect localized shopping search snapshots for ecommerce research.

Quick start

  1. Use a paid Apify account and set a spending limit that covers your batch.
  2. Paste the example below into the input form, then replace the query values.
  3. Start the Actor and open its dataset when the run finishes.
{
"requests": [
{
"q": "espresso machine",
"num": 40
}
]
}

Input parameters

Wrap query objects in the requests array. Each object requests one page.

ParameterMeaning
qRequired product search query.
numOptional requested product count, 1โ€“100; actual totals may vary.
startOptional result offset, 0โ€“1,000.
hl, glOptional language and two-letter country code.
locationOptional human-readable search origin.
sort_byOptional 1: price ascending; 2: price descending; 3: rating descending; 4: relevance.

Output and pagination

Each successful request creates one dataset record with:

FieldMeaning
requestIndexZero-based position of the request in your batch.
queryParamsThe query parameters used for that request.
upstreamRunIdRequest receipt identifier, when returned.
outputThe complete response page, including returned result arrays and pagination metadata.

Result arrays stay nested inside output; individual results are not flattened into separate dataset rows. JSON is the recommended export format for preserving the full response. Available fields depend on the query and returned page. Output order can vary: use requestIndex to match records to inputs.

Supply start in a subsequent request to continue collecting search results. Each page request is billed separately.

Pricing

$0.0027 per request attempt + $0.002 per valid run. All data returned in a page is included in that request fee; there is no separate per-result fee.

BatchActor event charges
1 request$0.0047
10 requests$0.029
20 requests$0.056

Empty pages and failed request attempts also incur the request fee. The Actor charges before calling the data API. Invalid input, an unacceptable price quote, or an insufficient batch spending limit stops paid requests. A batch stops on an error; already attempted requests remain billed, and another in-flight request may still be charged.

Requirements and limits

This Actor searches Google Shopping. It does not scrape individual retailer pages, verify stock at checkout, or track prices automatically between runs.

  • External customers on paid Apify plans only. Free-plan, owner, platform test, development, CI, and standby runs are disabled.
  • Run with 128 MiB of memory. A batch contains at most 20 requests, with two concurrent workers.
  • Pagination is manual. Requested result counts are best-effort limits, not guaranteed totals.
  • Each response is limited to 4 MiB. Paid request attempts are not automatically retried.

Frequently asked questions

Do I need my own API key or proxy?

No. Supply only the supported query parameters. Connection settings are managed by the Actor.

Is there a free trial?

No. This Actor requires a paid Apify plan and bills per request attempt.

Can I call it from my application?

Yes. Use the Actor's API button in Apify Console for its run endpoint and authenticated code examples. Paying customers can schedule or automate purchases using Apify.

Why is a page one dataset row?

A row preserves the complete response and its pagination metadata. Process the nested result arrays in your application if you need one row per result.

Support

For input or output questions, use the Actor's Issues tab when available. Include the run ID and a description of the problem; omit credentials and private data.

This is an independent Xtech tool, unaffiliated with or endorsed by the named platform.