Google Maps Business Profile Rank Checker avatar

Google Maps Business Profile Rank Checker

Pricing

from $14.00 / 1,000 local rank checks

Go to Apify Store
Google Maps Business Profile Rank Checker

Google Maps Business Profile Rank Checker

Check Google Maps local-pack rank by keyword, device, and geographic point. Returns one auditable rank row per keyword/location snapshot with match evidence, competitors, verification URL, timestamp, and provider cost.

Pricing

from $14.00 / 1,000 local rank checks

Rating

0.0

(0)

Developer

Khadin Akbar

Khadin Akbar

Maintained by Community

Actor stats

0

Bookmarked

10

Total users

2

Monthly active users

2 days ago

Last modified

Features

Limited permissions

Share

What is Google Maps Business Profile Rank Checker?

Find out where a business shows up in Google Maps for each keyword and place, and see it on a map grid of your whole service area. One row per check with localPackRank, rankStatus, who ranks around you, a proof link (checkUrl) and checkedAt.

Fit for this Actor

Use this Actor for local SEO agencies, multi-location operators, franchise reporting, and coordinate-based Google Business Profile visibility checks. Provide the business name plus a domain, Google place ID, or CID when available; those stable signals make target matching clearer than a name alone.

For business discovery and contact enrichment, continue with the public Google Maps Scraper — Emails, Phones & B2B Leads. This Actor is the focused rank-evidence step after the business and search intent are known.

Each run is a dated Maps snapshot. Schedule runs and retain the datasets when you need a time series. Interpret not_found as “the target was outside the provider's returned Maps results for this snapshot”; use the location, device, depth, and checkUrl fields to keep the conclusion scoped.

Scope and interpretation

The Actor reports the returned Maps provider snapshot for the requested keyword, location, language, device, and depth. It does not claim a separate organic SERP position. Use the recorded checkUrl, provider, and checkedAt values when comparing observations across scheduled executions.

How one workflow works

An agency starts with a client's profile name, website domain, three service keywords, and a small coordinate grid around the service area. Each keyword/location pair becomes one row. The agency compares localPackRank by keyword + locationLabel, reviews localPackResults to see which businesses appeared nearby, and uses targetMatchMethod plus checkUrl when explaining a visibility change to the client.

Map grid (new)

Fill gridCenter (for example 40.7128,-74.0060), gridSize (2–7 points per side) and gridSpacingMeters. The Actor checks every keyword at each point of the square grid around that centre. A 5×5 grid is 25 checks per keyword. Every row keeps its grid label (Grid r1c1 …). The GRID_SUMMARY record and OUTPUT.agentSummary give the share of points where you appear, how many are top 3, and your average rank. Use either gridCenter or locations, not both.

Input

Credentials stay in the environment rather than in visible Actor input.

providerMode defaults to standard (queued, cheapest, a bit slower); use live for an instant answer. The Actor records the mode and cost per row. If any single check would cost more than the safe limit, it is skipped and not charged.

Each location sets exactly one of locationCode, locationName, or locationCoordinate. Coordinates provide a direct path for a local geo-grid. The matrix is bounded at 20 keywords × 25 locations (500 checks).

{
"businessName": "Acme Dental",
"targetDomain": "acmedental.com",
"keywords": ["dentist near me", "emergency dentist"],
"locations": [
{ "label": "Downtown", "locationCoordinate": "40.7128,-74.0060,500" },
{ "label": "Northwest", "locationCoordinate": "40.7306,-73.9866,500" }
],
"languageCode": "en",
"device": "desktop",
"depth": 100,
"providerMode": "standard",
"competitorNames": ["Rival Dental"]
}

Use placeId or cid when known. Otherwise, targetDomain is a stable matching signal alongside business name. device accepts desktop or mobile; depth accepts 20–100 Maps results.

Output

One dataset record represents one completed keyword/location snapshot.

FieldMeaning
localPackRankTarget position in the returned local pack, or null
rankStatuslocal_pack when matched, otherwise not_found for this Maps-only check
targetMatchMethodplace_id, cid, domain, or normalized business-name match
localPackResultsCompact businesses returned in the local pack
competitorRanksRequested competitor names found in the snapshot
checkUrlProvider verification URL when available
checkedAtISO timestamp for the snapshot

Illustrative schema-valid item:

{
"runId": "example-run-id",
"checkedAt": "ISO_8601_TIMESTAMP",
"keyword": "dentist near me",
"locationLabel": "Downtown",
"locationCode": null,
"locationName": null,
"locationCoordinate": "40.7128,-74.0060,500",
"languageCode": "en",
"device": "desktop",
"depth": 100,
"businessName": "Acme Dental",
"targetDomain": "acmedental.com",
"placeId": null,
"cid": null,
"localPackRank": 2,
"organicRank": null,
"localPackFound": true,
"organicFound": false,
"rankStatus": "local_pack",
"targetMatchMethod": "domain",
"localPackSize": 3,
"localPackResults": [{ "name": "Acme Dental", "domain": "acmedental.com", "rank": 2 }],
"competitorRanks": [{ "name": "Rival Dental", "rank": 1, "rankType": "local_pack" }],
"providerMode": "standard",
"providerCostUsd": 0.01,
"checkUrl": "https://www.google.com/search?q=dentist+near+me&hl=en",
"serpItemTypes": ["maps_search"],
"warnings": []
}

The provider snapshot is the provenance boundary: Google results vary by location, device, language, personalization, and time. OUTPUT, RUN_SUMMARY, and LAST_RUN_SUMMARY are written for every terminal outcome. COMPLETE means every requested check persisted; PARTIAL preserves useful rows when some checks fail; VALID_EMPTY represents a functioning provider response with no persisted rows; INVALID_INPUT, CONFIG_ERROR, and UPSTREAM_FAILED contain actionable diagnostics.

Pricing

Startup billing and empty runs

The apify-actor-start event costs $0.00005 per startup unit. Apify charges one startup unit per GB of allocated memory, with a minimum of one unit, so a 2 GB run incurs two units. This startup charge still applies when input is invalid, no results are found, or an upstream request fails. Statements about free, unbilled, or skipped results refer only to the corresponding result event; they do not waive the startup charge. Apify platform usage is included in the event prices and is not passed through as an additional customer charge. Check the live Pricing tab for current events, tiers, and rates. Result limits cap result events, not the entire run cost.

Pay per event, Apify platform usage included. Each persisted check is one local-rank-check event: $0.02 on Free, $0.018 Bronze, $0.016 Silver, $0.014 Gold. Failed checks are never charged. The live Pricing tab is the source of truth.

API and dataset readback

curl "https://api.apify.com/v2/acts/khadinakbar~local-rank-tracker/runs?token=$APIFY_TOKEN" \
-H 'content-type: application/json' \
-d '{"businessName":"Acme Dental","targetDomain":"acmedental.com","keywords":["dentist near me"],"locations":[{"label":"Downtown","locationCoordinate":"40.7128,-74.0060,500"}]}'

Read the completed execution's default dataset from the API result or https://api.apify.com/v2/datasets/{DATASET_ID}/items. Read OUTPUT and RUN_SUMMARY from the execution's default key-value store. For large matrices, page the dataset and join records by keyword + locationLabel; each record is already bounded to a compact local-pack preview.

MCP / agent prompt

Check Acme Dental for dentist near me at the supplied coordinate. Return the Google Maps local-pack rank, rank status, match method, top local competitors, check URL, and timestamp. Keep the exact location and device in the explanation, and report partial or empty outcomes clearly.

For lowest cost, leave providerMode as standard; use live only when you need an instant answer.

MCP clients can use this read-only, no-side-effect snapshot tool when they have a business name, one keyword, and one location; a domain, place ID, or CID improves matching. The result is one row per check, with provider provenance, terminal outcome records, bounded output, and dataset readback through get-actor-output or the Apify dataset API. Cost is the per-check event with Apify platform usage included; provider usage is included, and a matrix can be paged by dataset item ranges. Inspect the terminal outcome before summarizing rows.

Results guidance

  • Keep the same coordinate grid and keyword spelling across scheduled runs so comparisons remain meaningful.
  • Prefer placeId or cid, then targetDomain, before relying on normalized business-name matching.
  • Use mobile when the reporting question is specifically mobile local visibility.
  • Treat not_found as “not found in this returned snapshot and depth,” then inspect checkUrl and location settings before drawing a conclusion.
  • Keep batches bounded so provider spend and dataset readback remain predictable.

Builder's note

I built the implementation with local-pack parsing and rank matching separate from the provider request layer. I found that this makes the dataset useful even when the data source changes whether local-pack businesses arrive as direct items or nested items, while targetMatchMethod tells an operator how much confidence to place in each match.

Boundary and responsible use

Use public search-result evidence and credentials you are authorized to operate. Follow the data source and Google terms, applicable law, and privacy obligations. Present the output as a dated provider snapshot, preserve the independent Google affiliation boundary, and support profile recommendations with the recorded evidence.

Continue the workflow

Managed research allowance

Free Apify callers share a $0.10 supplier-cost allowance per rolling 30 days across these managed research tools, within a $1 daily and $10 rolling family free pool. Results and supported search options stay unchanged within that allowance. Once exhausted, no further owner-funded research is requested; the existing start fee can still apply. Paid callers keep the existing prices and platform-usage payer. Identical supplier work inside one run can reuse its completed response, without sharing data between users or runs. Existing result-event billing remains unchanged; no new research-credit fee is added.

Paid routes priced per upstream request retain one supplier task per billed request. Completed same-run reuse applies where it preserves the existing billable unit.