# Google Maps New Business Monitor – New Local Leads (`leadsbrary/google-maps-new-business-monitor`) Actor

Monitor Google Maps for new businesses: schedule per category and city, get only newly listed places with name, address, phone, website, rating and coordinates. Export JSON, CSV, Excel. From $1.00 per 1,000 results.

- **URL**: https://apify.com/leadsbrary/google-maps-new-business-monitor.md
- **Developed by:** [Alexandre Manguis](https://apify.com/leadsbrary) (community)
- **Categories:** Lead generation, Automation, Real estate
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.00 / 1,000 results

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## Google Maps New Business Monitor – New Local Leads

### What does Google Maps New Business Monitor do?

**Google Maps New Business Monitor** watches Google Maps for businesses that newly appear for a category and a place (for example "coffee shop" in "Austin, TX"). On every run it collects the public Google Maps listings, compares their place IDs with the IDs this monitor has already seen, and outputs **only the newly listed businesses**: name, category, address, coordinates, phone, website, rating and a Google Maps link. Export the results as JSON, CSV, Excel, XML or HTML, or push them to a webhook.

The first run of a monitor creates the baseline. Every later run (schedule it daily or weekly) returns just the delta, so you pay only for the new businesses delivered instead of re-exporting the same places each week.

### Who is it for? Use cases

- **Local marketing and sales agencies**: pitch newly listed businesses before competitors do.
- **Local B2B providers** (POS, insurance, signage, cleaning, accounting): build a fresh lead feed per city and category.
- **Franchise and territory teams**: watch a category or area for new competitor locations.
- **Commercial real-estate scouts**: follow new listings in a neighborhood as a market-activity signal.
- **Automation builders**: feed a CRM, Google Sheet, Slack, Zapier or Make with new local leads.

### Features

- Delta feed: outputs only places not seen in earlier runs of the same `monitorId`.
- Several queries × several locations in one monitor.
- Baseline control: output the first run as `BASELINE`, or only record history silently.
- `all` mode returns every scanned place with `changeType` (`NEW`, `BASELINE`, `SEEN`) and `isNew` flags.
- Stores only place IDs and dates between runs (never full place data), with configurable retention (default 90 days) and a reset option.
- No login, no API key. Runs over HTTP with Apify datacenter proxy by default.
- Pay per result: you are charged for delivered dataset items only.

### Input

| Field | Type | Default | Description |
|---|---|---|---|
| `searchQueries` | string list (required) | `["coffee shop"]` prefill | Categories or keywords, as typed in Google Maps. |
| `locations` | string list (required) | `["Austin, TX, USA"]` prefill | Cities, neighborhoods or postal areas. Each query runs in each location. |
| `monitorId` | string | `default` | Name of the monitor whose seen-place history is reused. Use one ID per independent watch list. |
| `outputMode` | `new_only` / `all` | `new_only` | `new_only` outputs unseen places only; `all` outputs every scanned place with flags. |
| `emitBaseline` | boolean | `true` | Output the first run as `BASELINE`. If off, the first run only records history. |
| `maxPlacesPerSearch` | integer (1–500) | 60 | Places scanned per query + location. Google returns 20 per page and about 120 at most. |
| `maxResults` | integer (1–100000) | 100 | Maximum delivered (billable) results per run. |
| `language` | string | `en` | Language of names and categories. |
| `countryCode` | string | empty | Two-letter regional setting (us, gb, de). Detected from the first results if empty. |
| `historyRetentionDays` | integer (1–365) | 90 | Place IDs not seen again for this many days are dropped. |
| `resetHistory` | boolean | `false` | Clear this monitor's history first; the run becomes a new baseline. |
| `proxyConfiguration` | object | Apify proxy | Datacenter proxy is used by default. |

Example input:

```json
{
  "searchQueries": ["coffee shop"],
  "locations": ["Austin, TX, USA"],
  "monitorId": "austin-coffee",
  "outputMode": "new_only",
  "maxPlacesPerSearch": 60,
  "maxResults": 100
}
```

### Output

Real items from a first run (baseline) on Apify:

```json
{
  "placeId": "ChIJP8p2kJC1RIYR2qrGoXZtZCk",
  "name": "Terrible Love",
  "changeType": "BASELINE",
  "isNew": false,
  "firstSeenAt": "2026-10-03T14:37:40.003Z",
  "category": "Coffee shop",
  "categories": ["Coffee shop", "Coffee stand"],
  "address": "3908 Avenue B, Austin, TX 78751",
  "city": "Austin",
  "postalCode": "78751",
  "countryCode": "US",
  "latitude": 30.3045132,
  "longitude": -97.735632,
  "phone": null,
  "website": "http://terriblelovecoffee.com/",
  "rating": 4.9,
  "reviewsCount": 432,
  "priceLevel": null,
  "businessStatus": null,
  "googleMapsUrl": "https://www.google.com/maps/place/?q=place_id:ChIJP8p2kJC1RIYR2qrGoXZtZCk",
  "searchQuery": "coffee shop",
  "location": "Austin, TX, USA",
  "monitorId": "smoke-example",
  "scrapedAt": "2026-10-03T14:37:40.003Z"
}
```

#### Output fields and fill rates

Measured on a production run (40 items, dentists in Denver, from `TEST_REPORT.json`) and a 20-item proof run. Fields come from what Google Maps shows, so some are empty for some places.

| Field | Fill rate (40-item run) | Notes |
|---|---|---|
| `placeId`, `name`, `googleMapsUrl`, `changeType`, `isNew`, `firstSeenAt`, `scrapedAt`, `searchQuery`, `location`, `monitorId` | 100% | Always present. |
| `category`, `categories` | 100% | |
| `address`, `city`, `postalCode`, `countryCode`, `latitude`, `longitude` | 100% | |
| `phone` | 100% (60% in the 20-item Austin coffee run) | Depends on the category and place. |
| `website` | 97.5% (90% in the 20-item run) | |
| `rating` | 100% | |
| `reviewsCount` | 90% (0% in the 20-item run) | Not always returned; do not rely on it. |
| `priceLevel` | 0% | Currently not returned (always `null`). |
| `businessStatus` | 0% | Currently not returned (always `null`). |

Run examples:

- **First run, `new_only`, `emitBaseline: true`**: 20 items, all `changeType: "BASELINE"`.
- **No-match query** (`zzqxv nonexistent business` in Austin): the run succeeded but Google still returned a loosely related place, so the Actor does not guarantee zero items for nonsense queries.
- **Missing `searchQueries`**: rejected by Apify as invalid input before any run starts.

### What does "new" mean?

`NEW` means **newly seen by this monitor**, not a confirmed opening date. A place can appear as new if Google ranked it outside the scanned results before, or if it was just added to Maps. Raise `maxPlacesPerSearch` and use narrower locations in dense cities to reduce false positives.

### How to use via API

Replace `<USERNAME>` with your Apify username and `<APIFY_TOKEN>` with your token.

**curl**

```bash
curl -X POST "https://api.apify.com/v2/acts/<USERNAME>~google-maps-new-business-monitor/run-sync-get-dataset-items?token=<APIFY_TOKEN>" \
  -H "Content-Type: application/json" \
  -d '{"searchQueries":["coffee shop"],"locations":["Austin, TX, USA"],"monitorId":"austin-coffee"}'
```

**JavaScript**

```javascript
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: '<APIFY_TOKEN>' });
const run = await client.actor('<USERNAME>/google-maps-new-business-monitor').call({
    searchQueries: ['coffee shop'],
    locations: ['Austin, TX, USA'],
    monitorId: 'austin-coffee',
});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

**Python**

```python
from apify_client import ApifyClient

client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("<USERNAME>/google-maps-new-business-monitor").call(run_input={
    "searchQueries": ["coffee shop"],
    "locations": ["Austin, TX, USA"],
    "monitorId": "austin-coffee",
    "emitBaseline": True,
    "resetHistory": False,
})
items = client.dataset(run["defaultDatasetId"]).list_items().items
print(items)
```

#### Scheduling and integrations

Create an Apify **Schedule** (daily or weekly) with the same `monitorId`. Connect the run's webhook or the built-in integrations (Google Sheets, Slack, Zapier, Make) to receive only the new businesses. Do not run the same `monitorId` concurrently: runs would overwrite each other's history.

### Pricing

Pay per result (one dataset item = one result). Price per 1,000 results depends on your Apify plan:

| Plan | Price per 1,000 results |
|---|---|
| FREE | $1.50 |
| BRONZE | $1.30 |
| SILVER | $1.15 |
| GOLD and above | $1.00 |

In `new_only` mode, scanned places that were already seen are not billed. Platform usage (compute and proxy) is billed separately by Apify; the measured usage of the proof runs was below $0.001 per run for 5–20 items. Use `maxResults` to cap spending.

### Troubleshooting

- **Zero items on a repeat run**: expected when nothing new appeared. Use `outputMode: "all"` to check what was scanned.
- **Everything shows as `BASELINE`**: it is the first run for that `monitorId` (or `resetHistory` was on).
- **Too few places for a dense city**: Google caps each search at about 120 places. Use narrower locations (neighborhoods, postal codes) or more specific queries.
- **Empty results for a location**: the location text may not be recognized; try "City, State, Country".
- **Large runs**: each page request now times out after 12 s (3 attempts on fresh proxy sessions). For big watch lists set a generous run timeout or split them into several monitors; the log shows one status line per query × location.
- **Format changes on Google's side** can temporarily affect fields; open an issue on the Actor page if you see empty fields.

### FAQ

**Is it legal?** The Actor collects only business listing data shown publicly on Google Maps without login: no reviewer names, review texts or private data. Google's terms restrict automated access; you are responsible for lawful use, including GDPR and anti-spam rules when contacting businesses.

**What is stored between runs?** Only place IDs and first/last-seen dates per `monitorId`, kept for `historyRetentionDays`. Use `resetHistory` to clear it.

**Does it use the Google Places API?** No. It reads public Google Maps search results, so no Google API key is needed.

**Can it return reviews or images?** No. It is built for detecting new businesses, not for review or photo extraction.

**Can I get all places, not just new ones?** Yes: set `outputMode` to `all`.

### Keywords

google maps new business monitor, new business leads, newly opened businesses, google maps monitoring, new business scraper, local lead monitor, google maps change alert, local business leads, google places new listings, new restaurant openings, franchise territory monitoring, new store openings data, google maps scraper

### Hashtags

\#GoogleMaps #LeadGeneration #NewBusiness #LocalLeads #BusinessMonitoring #WebScraping #Apify #SalesProspecting #RealEstate #Franchise

# Changelog

This Actor's version history is a separate document: https://apify.com/leadsbrary/google-maps-new-business-monitor/changelog.md

# Actor input Schema

## `searchQueries` (type: `array`):

Business categories or keywords to monitor, as you would type them in Google Maps (e.g. coffee shop, dentist).

## `locations` (type: `array`):

Cities, neighborhoods or postal areas. Each query is searched in each location.

## `monitorId` (type: `string`):

Name of the monitor whose seen-place history is reused between runs (letters, digits, dashes). Use a different ID per independent watch list.

## `outputMode` (type: `string`):

new_only = only places not seen in earlier runs of this monitor. all = every scanned place, with changeType/isNew flags.

## `emitBaseline` (type: `boolean`):

On the first run of a monitor (no history yet) output all found places as changeType=BASELINE. If off, the first run only records history and outputs nothing.

## `maxPlacesPerSearch` (type: `integer`):

Maximum places scanned per query + location (Google returns 20 per page, about 120 at most).

## `maxResults` (type: `integer`):

Stop after this many delivered results (also protects your spending).

## `language` (type: `string`):

Language code for names and categories returned by Google (e.g. en, de, fr).

## `countryCode` (type: `string`):

Two-letter country code (e.g. us, gb, de) used as Google's regional setting. Leave empty to detect it from the first results.

## `historyRetentionDays` (type: `integer`):

Place IDs not seen again for this many days are dropped from the monitor history (only IDs and dates are stored).

## `resetHistory` (type: `boolean`):

Clear this monitor's history before the run (this run becomes a new baseline).

## `proxyConfiguration` (type: `object`):

Apify datacenter proxy is used by default.

## Actor input object example

```json
{
  "searchQueries": [
    "coffee shop"
  ],
  "locations": [
    "Austin, TX, USA"
  ],
  "monitorId": "austin-coffee",
  "outputMode": "new_only",
  "emitBaseline": true,
  "maxPlacesPerSearch": 20,
  "maxResults": 20,
  "language": "en",
  "historyRetentionDays": 90,
  "resetHistory": false,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "searchQueries": [
        "coffee shop"
    ],
    "locations": [
        "Austin, TX, USA"
    ],
    "monitorId": "austin-coffee",
    "maxPlacesPerSearch": 20,
    "maxResults": 20,
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("leadsbrary/google-maps-new-business-monitor").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "searchQueries": ["coffee shop"],
    "locations": ["Austin, TX, USA"],
    "monitorId": "austin-coffee",
    "maxPlacesPerSearch": 20,
    "maxResults": 20,
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("leadsbrary/google-maps-new-business-monitor").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "searchQueries": [
    "coffee shop"
  ],
  "locations": [
    "Austin, TX, USA"
  ],
  "monitorId": "austin-coffee",
  "maxPlacesPerSearch": 20,
  "maxResults": 20,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call leadsbrary/google-maps-new-business-monitor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leadsbrary/google-maps-new-business-monitor"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/uPwnpKbAEEDBfcCas/builds/1fX8uypcf1zwWfQvi/openapi.json