Google Maps Places Scraper

Export public Google Maps places from search queries, locations or supported Maps URLs into a structured dataset. Collect business names, Maps links and available listing details for local business research. Results are limited to the places Google exposes, not a complete business directory.

Quick start

1. Enter a business type in Search queries and a city in Locations, or supply a supported Google Maps URL instead.
2. Start with one search and a small limit:

{
  "queries": ["coffee shops"],
  "locations": ["New York, NY, USA"],
  "maxResultsPerQuery": 3,
  "language": "en",
  "countryCode": "US"
}

3. Open the run's dataset to inspect results and export CSV, Excel or JSON.

Place details vary: a row may contain only the discovered name, Maps URL, source, position and timestamp if details cannot be read. Review the output before expanding a search.

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.

What you get

One row per unique discovered place, with its name, Maps link, source query or URL, discovery position and collection time. Additional listing fields such as address, phone, website, rating and hours appear only when visible and recognized. A basic place row can remain useful even when further details cannot be read.

Who is it for?

• Local-business researchers assembling source-linked lists for a selected business type and area.
• Sales-operations teams reviewing available public listing contacts before qualifying a place manually.
• Retail and hospitality analysts comparing returned business listings across their chosen locations.
• Travel and location researchers keeping Maps links and available points-of-interest details for review.

How you can use the data

• Build a small New York coffee-shop review sheet. Use the existing coffee-shop query and three-place cap, then export title, googleMapsUrl, address, phone and website where present. Missing contact fields do not mean that the business lacks those contacts.
• Compare the areas you selected. Use the existing plumber search for Austin and Round Rock with five candidates per query/location pair. Keep searchQuery with each row and account for duplicate removal across the run rather than expecting ten saved places.
• Inspect an existing Maps search. Use the supplied London-bookstores search URL with a small cap. Supplied URLs retain their own parameters, so language and country hints for generated searches do not rewrite that URL.
• Join exports in your own workflow. Retain Maps links, available place IDs and collection times to compare your files. Review source listings before joining records, and do not use URL coordinates as verified business pins. The Actor does not automatically compare changes, discover emails or collect review text, photo galleries or popular-times data.

Input settings

These are editable input examples, not links to public saved tasks.

Search multiple areas: every query is combined with every location.

{
  "queries": ["plumbers"],
  "locations": ["Austin, TX, USA", "Round Rock, TX, USA"],
  "maxResultsPerQuery": 5
}

Use an existing search: supply a full public Maps search URL.

{
  "startUrls": [{"url": "https://www.google.com/maps/search/bookstores+in+London/"}],
  "maxResultsPerQuery": 3
}

Full public place URLs can also be supplied in startUrls to request individual places. Short share links are not supported. Queries and URLs can be combined. Overlapping places are saved only once per run.

More input settings

Supply at least one queries entry or a supported startUrls entry. Neither is globally required because they are alternatives. An empty input is rejected.

Setting	API key	Purpose
Search queries	queries	Business types or place names.
Locations	locations	Optional areas combined with each query.
Google Maps URLs	startUrls	Public Google Maps search or place URLs.
Maximum places per query	maxResultsPerQuery	Candidate limit per query/location pair or search URL. 1–100, API default 10.
Language	language	Preferred interface language. Default en.
Country code	countryCode	Optional two-letter hint for generated searches, not a geographic boundary.
Proxy configuration	proxyConfiguration	Optional connection settings. Direct by default, no automatic proxy fallback.

The form's sample values are not API defaults. See each input field's help for detailed behavior. Language and country settings affect generated search URLs. Supplied URLs retain their own parameters.

Output data

One dataset row represents a place. The following is a synthetic shape-only example, not an observed business or an extraction guarantee:

{
  "searchQuery": "coffee shops in Example City",
  "rank": 1,
  "title": "Example Place",
  "googleMapsUrl": "https://www.google.com/maps/place/Example/",
  "scrapedAt": "2026-10-24T12:00:00.000Z"
}

Fields	Meaning and availability
searchQuery, rank	Source query or URL and discovery position. Positions are local to that source and may have gaps after duplicate removal.
title, googleMapsUrl, scrapedAt	Place name, Maps URL and extraction timestamp.
placeId	Identifier parsed from the Maps URL, when available.
category, address	Available listing category and full address.
latitude, longitude	Coordinates from Maps URLs. These may represent a map center rather than a precise business pin.
rating, reviewCount	Recognized visible rating and review count, not review text.
phone, website, priceLevel	Public listing values when available. No website contact enrichment is performed.
openingHours	Array of available hours-table rows recognized by English weekday names. Often absent in other interfaces.

Missing values are generally omitted, not guaranteed empty strings. The reserved legacy fields neighborhood, city, state, country, postalCode and popularTimesSummary are not populated by the current extractor. The address is not split into components. There is no rating-sort or custom-sort input.

The key-value store may contain RUN_SUMMARY with saved/source counts, completion status and warnings. A successful partial run can also include PENDING_WORK for unfinished targets. These are best-effort diagnostics, not a guarantee of resumability or availability after forced termination.

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

The start event is charged once when extraction starts, and item is charged for each place saved to the dataset, including a basic place row when full details are unavailable. Warnings and summaries are not separate result rows.

See the Pricing tab for current rates.

Tips for best results

• Count query and location combinations before running. The candidate limit applies to each pair or search URL, not to the entire run. Direct place URLs request one place.
• Review basic rows before importing contacts. Some rows contain only the discovered name, source link, position and timestamp.
• Keep source context when comparing places. Discovery rank is local to its source, and duplicate removal can leave gaps.
• Inspect run status and saved counts after partial work. Completed rows can remain usable when later targets fail, while pending-work diagnostics do not guarantee resumption.

Limits and caveats

This independent public-page tool is not Google's official Places API. No login or Google Places API key is required, and private or login-only data is outside its scope. It returns the places Google exposes rather than a complete business directory.

Google Maps can restrict access or change by language, region and time. Duplicates, inaccessible details and time limits can reduce the saved count. A zero-row run currently fails, which does not establish that an area has no matching businesses. Later failures can leave completed rows available. RUN_SUMMARY and PENDING_WORK are best-effort diagnostics, with no guarantee of availability after forced termination or resumability.

Optional fields may be absent, and the current extractor does not populate the reserved address-component or popular-times fields. It does not split full addresses, enrich website contacts, collect review text, emails or photo galleries, or support rating/custom sorting. Hours recognition depends on English weekday names. Coordinates from a Maps URL may describe a map center rather than an exact business pin.

Short share links are not supported. Country is a hint for generated searches rather than a geographic boundary, and supplied URLs retain their own parameters. The Actor does not automatically compare changes between runs. Check actual returned fields and source links before using the data in another system.

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-maps-places-scraper/runs' \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H 'Content-Type: application/json' \
  --data @- <<'JSON'
{
  "queries": [
    "coffee shops"
  ],
  "locations": [
    "New York, NY, USA"
  ],
  "maxResultsPerQuery": 3,
  "language": "en",
  "countryCode": "US"
}
JSON

Node.js

import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: process.env.APIFY_TOKEN });
const run = await client.actor('fetch_cat/google-maps-places-scraper').call({
  "queries": [
    "coffee shops"
  ],
  "locations": [
    "New York, NY, USA"
  ],
  "maxResultsPerQuery": 3,
  "language": "en",
  "countryCode": "US"
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);

Python

import os
from apify_client import ApifyClient

client = ApifyClient(os.environ['APIFY_TOKEN'])
run = client.actor('fetch_cat/google-maps-places-scraper').call(run_input={'queries': ['coffee shops'], 'locations': ['New York, NY, USA'], 'maxResultsPerQuery': 3, 'language': 'en', 'countryCode': 'US'})
print(client.dataset(run['defaultDatasetId']).list_items().items)

API and AI-agent use notes

The cURL request starts an asynchronous run. Wait for completion and use its defaultDatasetId to retrieve results. Client examples wait for the run before reading its dataset.

MCP and AI agents

You can ask your AI assistant to collect data with Google Maps Places 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 Maps Places 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-maps-places-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 Maps Places Scraper by Fetch Cat, or give it the identifier fetch_cat/google-maps-places-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

• “Use Fetch Cat’s Google Maps Places Scraper to collect up to 3 coffee shops in New York, NY, USA in English with country hint US. Show names, Maps links and available addresses, phones and websites, marking missing fields.”
• “Collect up to 5 candidate places per search for plumbers in Austin, TX, USA and Round Rock, TX, USA. Keep source queries and Maps links, and explain why overlap between targets may reduce the saved count.”
• “Retrieve up to 3 places from https://www.google.com/maps/search/bookstores+in+London/. Include discovery positions and available rating information without collecting review text or claiming complete city coverage.”

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

Can I export Google Maps places to CSV or Excel?

Yes. Open the run's dataset and choose the export format, or retrieve JSON through the Apify API. Check which optional fields are actually present before importing results.

Is this a Google Maps Places API alternative?

It provides public listing extraction through Apify, but is not the official Google Places API. It requires an Apify account/token for API use, not a Google Places API key. Fields and coverage differ from Google's service.

Can I search many cities or use only place URLs?

Yes. Each query is combined with each location. Alternatively, use supported full Maps URLs without queries. Direct place URLs request individual places. Locations do not modify them.

Why are fields missing or results fewer than requested?

Some details are not visible or recognized, and overlapping places are removed across the run. Maps restrictions and time limits can also interrupt work. Start small and inspect the run summary. Reserved legacy address-component and popular-times fields are not extracted.

Are reviews, emails and popular times included?

No. A visible review count may be present, but review text, email discovery and popular-times data are not included. Use a purpose-built related Actor where appropriate.

Related Actors

• Google Maps Reviews Scraper — review-focused exports.
• Google Maps Photos Scraper — Collect public place-photo image links and available thumbnails, without downloading image files.
• Google Shopping Results Scraper — product search research.
• 2GIS Places Scraper — business listings from another directory.
• Yelp Business Scraper — Collect public business listings with available locations, ratings and contact fields.

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. ♥