Google Images Search Results Scraper

Search public Google Images and export image URLs, thumbnails, dimensions, source pages and result ranks. Use this Google Images scraper API for localized visual research, image-search visibility checks and repeatable source inventories without downloading image files.

Quick start

1. Add one or more text searches to queries.
2. Choose a country and language, then start with a modest result limit.
3. Run the Actor and open its dataset to review or export the results.

{
  "queries": ["golden retriever puppy", "eiffel tower at night"],
  "maxResultsPerQuery": 50,
  "gl": "us",
  "hl": "en"
}

Prefer a video guide? This short Apify walkthrough shows you how to set up and run an Actor. It uses a different Actor, but the setup steps are the same.

Ready-to-run examples

• Export Google Images search results — inspect the public example input, run it or adapt its query list.

What you get

• Batch keyword searches localized by country and language.
• Original image and thumbnail URLs with available dimensions.
• Source page links, publisher domains and Google result identifiers.
• Deduplicated positions and query provenance for comparing your own snapshots.

Who is it for?

SEO teams can track which sources appear for their search terms. Content researchers can build an image-source shortlist, while developers and AI workflows can retrieve structured metadata for later review. Any comparison, alerting or image reuse happens in your downstream workflow.

Input settings

Field	What to set
queries	One to 100 text searches, each up to 2,000 characters.
maxResultsPerQuery	Result ceiling per query, from 1 to 1,000. Default: 100.
gl, hl	Country and language codes. Defaults: us and en.
connectionMode	Automatic (default) or Direct. Field help explains costs and fallback limits.
proxyConfiguration	Optional advanced settings for saved tasks or API integrations.

For a brand audit, start with one product name and 25 results. Keep the locale fixed when collecting snapshots for comparison.

Output data

{
  "query": "eiffel tower at night",
  "position": 1,
  "title": "Eiffel Tower at night, Illuminations & light show - OFFICIAL ...",
  "imageUrl": "https://www.toureiffel.paris/.../4k0a9297-compressed.jpg",
  "imageWidth": 1200,
  "imageHeight": 630,
  "thumbnailUrl": "https://encrypted-tbn0.gstatic.com/...",
  "source": "La tour Eiffel",
  "domain": "www.toureiffel.paris",
  "link": "https://www.toureiffel.paris/en/the-monument/lights",
  "page": 0,
  "gl": "us",
  "hl": "en"
}

Field	Description
query, position, page	Submitted query, deduplicated result rank, and Google result page.
title, source, domain, link	Google-displayed page title, publisher, publisher domain, and source page URL.
imageUrl, imageWidth, imageHeight, imageSize	Original image URL and Google-reported dimensions/file-size text when present.
thumbnailUrl, thumbnailWidth, thumbnailHeight	Google thumbnail URL and dimensions when present.
googleUrl, googleImageId, googleResultId	Google reference URL and identifiers returned by the public result.
gl, hl	Locale requested for this row.

Unknown metadata stays null. A usable thumbnail may be returned when the original image URL is unavailable. RUN_SUMMARY in the run's key-value store records per-query outcome reasons, and PENDING_WORK identifies unfinished searches.

Download your results

Open your run's dataset, choose Export and select JSON, CSV or Excel. JSON keeps nested fields together. CSV and Excel are useful when you want to review the records in a spreadsheet.

See Apify's download and export guide for the available formats and field options.

Pricing

A start event is charged once when extraction starts, even if no image results are returned.

Each image row saved to the dataset is charged as an image-scraped event. Original image files are not downloaded.

See the live Pricing tab for current rates and discounts.

Tips for best results

• Start specific. A product name or descriptive phrase is easier to assess than a very broad topic.
• Keep locales consistent. Use the same country and language when comparing snapshots.
• Review source links. Open the publisher page before relying on an image or reusing it.
• Check completion. Review the run summary before treating a small dataset as a complete search.

Limits and caveats

• Result limits are ceilings, not guarantees. Google may return fewer results or block a request.
• Some searches can return only the first page, up to 100 cards. Unfinished depth remains pending rather than complete.
• Completed searches with no matches or usable image URLs return an empty dataset with a reason. Unknown layouts and challenges are not evidence of no matches.
• Mixed searches preserve useful rows. Upstream failures or limits can leave partial results. All-blocked searches and fatal configuration, storage or billing errors fail.
• Run with the default 512 MiB allocation (maximum: 512 MiB). If an integration bypasses the platform limit and selects more memory, the run succeeds with an empty dataset, an explicit warning and unsupported_memory_allocation in RUN_SUMMARY. No searches or start/image charges occur. Select 512 MiB and start a new run. This does not mean the searches had no matches.
• Processing has a five-minute budget. Start a new run for pending work rather than resurrecting an existing run.
• Results are public search metadata, not image files or permission to reuse them. Dimensions are reported metadata, and source pages may later change.

Automation and integrations

Save your settings for next time

Once you have an input that works for you, save it as an Apify task. This keeps your settings together so you can use them again without filling in the form from scratch.

Run on a schedule

Need fresh results regularly? You can schedule the Actor or a saved task to run at a time that suits you.

Each scheduled run collects the data again. If you want to compare results or highlight changes, add that step in your own workflow.

Send results to your other tools

Use n8n, Make or Zapier to connect this scraper to the rest of your workflow. For example, you could pass its results to an AI assistant or add records to a spreadsheet. Follow the Apify integration guides for your chosen tool.

For a custom connection, an Apify webhook can notify your app when a run finishes or fails. Your app can then fetch the results or handle the failure.

API usage

Want to collect this data from your own app or automation? The examples below send input to the scraper and show how to collect its results.

The Node.js and Python examples wait for the run to finish before reading its results. The cURL example starts the run and returns its details. Wait for that run to finish, then use its defaultDatasetId to fetch the results.

For setup instructions, see Apify's JavaScript client guide, Python client guide and Actor runs API reference.

cURL

curl -X POST "https://api.apify.com/v2/acts/fetch_cat~google-images-api-scraper/runs" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"queries":["eiffel tower at night"],"maxResultsPerQuery":25,"gl":"us","hl":"en"}'

Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/google-images-api-scraper').call({
  queries: ['eiffel tower at night'], maxResultsPerQuery: 25, gl: 'us', hl: 'en',
});
const items = await client.dataset(run.defaultDatasetId).listItems();
console.log(items.items);

Python

from apify_client import ApifyClient
client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("fetch_cat/google-images-api-scraper").call(run_input={
    "queries": ["eiffel tower at night"], "maxResultsPerQuery": 25, "gl": "us", "hl": "en"
})
print(client.dataset(run["defaultDatasetId"]).list_items().items)

MCP and AI agents

You can ask your AI assistant to collect data with Google Images Search Results Scraper and help you work with the results. The scraper returns the data, and your assistant can then summarize it, compare records or prepare notes.

Connect your assistant through the Apify MCP server. MCP gives your assistant a way to find this scraper, run it and read the results. Follow the official setup and sign-in guide for your app.

Easier setup with an Apify plugin

If you use a supported coding assistant, the official Apify plugin can set up the connection for you. It connects your assistant to Apify and includes instructions for common tasks. Follow the guide for your particular app.

Use Apify AI in Console

Prefer to keep everything in Apify? Open Apify AI in Console and ask it to find Fetch Cat's Google Images Search Results Scraper. You can describe the data you want and ask questions about the results.

Apify AI is currently in beta. It asks for confirmation before starting an Actor, and normal run charges apply.

Choose your assistant

• Claude and Claude Code (Anthropic): Apify setup guide.
• ChatGPT and Codex (OpenAI): Apify setup guides.
• Grok Bot (xAI): Apify plugin guide.
• Gemini CLI (Google): MCP server setup guide. Use the server URL below with the HTTP configuration supported by Gemini CLI.

Connect just this scraper

To keep your setup focused on this scraper, add this server configuration to a compatible MCP client:

{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com?tools=fetch_cat/google-images-api-scraper"
    }
  }
}

Sign in to Apify when your client asks. If your client uses a Bearer token instead, follow its setup guide and keep the token in its secure configuration. Configuration formats vary by app, so use the linked guide if your client needs a different format.

Use Apify's general server

Already connected to the general Apify MCP server at https://mcp.apify.com? You can use it to find this scraper without adding another server. Ask your assistant to use Google Images Search Results Scraper by Fetch Cat, or give it the identifier fetch_cat/google-images-api-scraper.

Your assistant can check the available settings and retrieve the results from the returned run. If the run is still working, it should follow that run rather than start it again. Both connection options use Apify's hosted service.

Example requests

• “Find images of electric cargo bikes in Germany and list the source pages beside their image URLs.”
• “Collect up to 25 Eiffel Tower night images and group the returned results by publisher domain.”
• “Search for three packaging design themes in US image results, then prepare a shortlist with thumbnails and source links.”

Normal Apify charges apply. Check the live Pricing tab before asking your assistant to run a larger batch.

Pay with x402

If your AI agent has a funded wallet, it can pay for Apify usage through x402. This experimental option lets an agent use Apify without a conventional account.

Apify AGI provides a prepaid API token with a spending cap after payment. Your agent can use that token to run this scraper through the Apify API or an authenticated MCP connection.

Some MCP setups also support paying for each request directly. That is a different payment option, so check the official guide for its availability.

Follow the official guide for wallet setup, supported payment options and current terms. Apify handles the payments. Keep wallet keys and payment tokens in your agent's secure configuration.

Other ways for agents to pay

Apify also supports MPP for prepaid access through AGI and Skyfire for eligible Actors. If your agent already uses one of these, see the agentic payment guide to choose the right setup.

FAQ

Does it download image files? No. It returns URLs and search-result metadata.

Can I search multiple terms? Yes. Each query is searched independently and retained on its output rows.

Can I get 1,000 images for every query? No. That is a configurable ceiling, not guaranteed coverage. Check completion and pending work before relying on depth.

Can I use the API or an AI assistant? Yes. Follow the API and MCP setup above. The assistant's analysis is separate from extraction.

What happens when no results are available? A completed search with no matches or usable records returns an empty dataset and a truthful summary reason. Blocking and extraction failures are not classified as no matches.

Related Actors

• Google Images Scraper — export ranked image-search metadata with source links and localization.
• Google Shopping Results Scraper — collect product cards with prices and merchant snippets.
• Google News Scraper — collect news headlines, publishers, dates and feed descriptions rather than full articles.
• Pexels Scraper — search Pexels photos and videos with asset URLs and normalized metadata.
• Google Trends Scraper — discover trending searches by country with traffic labels and news context.

Support and feedback

For custom additions or integrations, email hello@fetchcat.dev.

Found an error or have a feature request? Open an issue with the run URL, a non-sensitive input example and what you expected.

Need help sharing it? See Apify’s guide to sharing a run when reporting an issue. Sharing a run can give the developer access to its input, logs and results, so use a run that contains no sensitive data. Please leave out API tokens, passwords, cookies, private documents and personal data. Use a public sample URL or a redacted example instead.

Tried this scraper? We'd love to hear how it worked for you. Leave a review to help others choose the right tool and help us improve it. Your feedback means a lot to us.

Made with care for curious people, AI agents and the possibilities in data. ♥