The fastest local rank tracking API for Google map pack results

See the map pack as a searcher in any city sees it — business positions, ratings, review counts, and coordinates — with responses in under one second and pricing from $1 per 1,000 requests that drops under $0.50 at volume.

No credit card required · No proxy setup · View Google Search API Docs

Run the same query from any city or postal code with one location value
Get the full place record: position, rating, reviews, address, GPS coordinates
Blocked attempts are retried at our cost and never billed

<1s

Typical response time

$1/1K

List price, under $0.50 at volume

Charge for failed requests

195

Countries, city-level targeting

Who tracks local rankings through an API

If the answer to "where do we rank" changes by neighbourhood, a national average is the wrong instrument.

Multi-location brands

Compare map pack position store by store instead of reporting one number for the whole chain.

Local SEO agencies

Show clients the pack they actually appear in, for every market they pay you to cover.

Franchise marketing teams

Spot the franchisees losing local visibility before the territory complains about lead volume.

Review and reputation platforms

Pull ratings and review counts for tracked listings on the same call as position.

Retail and restaurant groups

Watch competitor density and rating movement around each site you operate.

Why local rankings resist normal tracking

The map pack behaves differently from web results, and three assumptions from classic rank tracking break against it.

Failure 01

There is no national local ranking

The pack reorders every few blocks. A tool that queries from one datacentre reports a position that no customer in your catchment area has ever seen.

Store-level decisions made blind

Failure 02

The pack is a separate ranking system

Proximity, category, and review signals drive it, not the page-level factors a web rank tracker measures. Tracking organic and calling it local misses the mechanism.

Optimising the wrong signals

Failure 03

Coverage is the cost problem

Local reporting means one query per location per keyword, so volume multiplies fast. Slow, per-attempt-billed collection is what caps how many markets a team can afford to watch.

Markets silently dropped from reporting

The data a local search request returns

Set tbm=lcl on the scraper.google.search actor and the response carries the map pack as structured places rather than scraped HTML.

local_results

object

Map pack container for the query.

places[]

array

One entry per business in the pack.

position

integer

Rank within the local pack.

title

string

Business name as listed.

rating

number

Star rating shown on the listing.

reviews

integer

Review count, plus reviews_original as displayed.

type

string

Primary business category Google assigns.

address

string

Listed address line.

gps_coordinates

object

Latitude and longitude, ready to join against your store list.

price

string

Price level indicator where Google shows one.

extensions

array

Listing attributes shown alongside the result.

local_map

object

Map viewport that accompanies the pack.

pagination

object

Offset links. Google Local pages in multiples of 20.

POST /api/v1/scraper/request

200 ok

# request
curl --location 'https://api.scrapeless.com/api/v1/scraper/request' \
--header 'x-api-token: <api-key>' \
--header 'Content-Type: application/json' \
--data '{
    "actor": "scraper.google.search",
    "input": {
        "q": "dentist near me",
        "location": "Denver, Colorado",
        "tbm": "lcl",
        "gl": "us"
    }
}'

# response (trimmed)
{ "local_results": {
    "places": [
      { "position": 1,
        "title":   "Summit Dental Downtown",
        "rating":  4.8,
        "reviews": 412,
        "type":    "Dentist",
        "address": "1600 Stout St #200",
        "gps_coordinates": {
          "latitude":  39.7469,
          "longitude": -104.9931 } } ] },
  "pagination": { "current": 1 },
  "metadata": { "engine": "google.search" } }

Full parameter and field reference

Tracking web positions for the same client? Pair this with SEO rank monitoring.

How a local tracking run works

Build your location grid

One request per keyword per market. Pass the city or postal code in location and set tbm=lcl for the pack.

We search from that place

The request originates in the target location with matching locale parameters, so the pack you receive is the pack a local searcher sees.

Join to your store list

GPS coordinates come back with every place, so results attach to your own locations without a geocoding step in between.

Built for multi-location brands, local agencies, and franchise teams

The fastest response in the category

Local reporting multiplies keywords by locations, so a grid gets large quickly. Sub-second responses are what keep a thousand-market refresh inside a nightly window.

under 1s

typical vendor window

request

unblock

parse

Down to the postal code

Query as a searcher standing in a specific city, metro, or ZIP. Two branches eight kilometres apart return different packs, and that gap is usually the finding worth reporting.

Location Parameters

"location": "Denver, Colorado"

"tbm": "lcl"

195 countries covered

The whole place record, not just a position

Rating, review count, category, address, and coordinates arrive with each result, so a single call supports both rank reporting and competitor review benchmarking.

Response Fields

places[].rating

places[].reviews

places[].gps_coordinates

places[].type

Target one listing directly

When you need a specific Google Business Profile rather than whatever the pack returns, pass its listing ID and the request resolves to that entity.

Listing Targeting

"ludocid": listing CID

"lsig": map view

"start": multiples of 20

Plans built for local reporting grids

Local coverage means keywords multiplied by locations, so effective cost per successful request decides how many markets you can afford. Start at $1 per 1,000 and move down the curve as the grid grows.

Basic

$0.00/1K

Pay as you go

No commitment. Consumption-based pricing at list rates.

Comparing Google local search API providers

Most teams tracking local rankings are deciding whether to buy residential IPs per market or to buy the result. Here is how the options differ.

Scrapeless Google Search API

Build it in-house

Typical SERP API vendor

Typical response time

Under one second

Degrades under load

Multiple seconds

Location granularity

City and postal code, included

Residential IPs per market

Country-level on most plans

Entry price per 1K

$1.00, under $0.50 at volume

Proxy and engineering cost

$1.00 and up

Cost of a blocked request

Never billed

Paid in bandwidth either way

Usually billed

Place detail returned

Rating, reviews, address, GPS

Parse the pack yourself

Position only on some plans

Time to first clean dataset

Under an hour

4–8 weeks

Days

Start using the fastest, lowest-cost Google local search API today

Sub-second map pack results from $1 per 1,000 requests, dropping under $0.50 at volume, with failed requests never billed. See the full endpoint reference, parameter list, and pricing.

View the product page

Drops into the stack you already run

Official SDKs and verified nodes, so a scheduled rank pull is a configuration task rather than a build.

Python SDK

Node.js SDK

Go SDK

n8n verified node

Make

Pipedream

Activepieces

Dify

MCP server

Webhooks

Need implementation details? View product details or open the Google Search API docs for the full parameter list, response schema, and SDK examples.

Choose the search workflow your team needs

Explore focused solutions for search visibility, AI retrieval, commerce intelligence, research and monitoring. Each use case connects Google Search API results to a clear business outcome.

SEO Rank Monitoring

Measure domain visibility, ranking pages and SERP feature presence across keyword groups, markets and devices.

Explore SEO monitoring You are here

Local SEO & Rankings

Compare local rankings, business listings, Maps visibility and review signals across cities, regions and service areas.

Explore local SEO

AI SEO & GEO Visibility

Monitor brand mentions, citations and source visibility across AI-generated search experiences and target topics.

Explore AI SEO and GEO

Product & Market Research

Study demand signals, alternatives, category presence and competing offers through structured search results.

Explore product research

AI Models & RAG

Give LLMs, agents and RAG pipelines current, attributable search context for grounding and retrieval workflows.

Explore AI model workflows

Keyword Rank Tracking

Track exact keyword positions and movement over time by location, language, device and result type.

Explore rank tracking

Shopping Price Monitoring

Compare public Google Shopping prices, merchants, ratings and product visibility for selected categories.

Explore price monitoring

News & Media Monitoring

Follow headlines, publishers, emerging stories and shifts in public narratives across relevant queries.

Explore news monitoring

Travel Data

Structure Google Flights and Hotels results for route, stay, destination and travel-market research.

Explore travel data

Recruitment Data

Collect Google Jobs results to monitor roles, employers, locations and labor-market demand.

Explore recruitment data

Ad Verification

Verify PPC and Ads visibility, placement and competitive messaging across target queries and markets.

Explore ad verification

Academic Research

Organize Google Scholar results, authors and cited sources for academic and evidence-based research.

Explore academic research

Trend Analysis

Use Google Trends signals to compare changing interest across topics, time periods and markets.

Explore trend analysis

Image Search

Use Google Lens and Images results to discover visual matches, sources and related content.

Explore image search

Brand Monitoring

Track where a brand appears across organic results, news, shopping and other SERP surfaces.

Explore brand monitoring

Need Google Search API specifications and pricing?

Review supported Google API categories, structured response examples, integration steps and pricing on the Product page.

Questions teams ask before they buy

Which is the cheapest Google local search API?

Compare effective cost per successful request rather than list price. Scrapeless lists at $1 per 1,000 and drops under $0.50 at volume, and blocked attempts are never billed — which matters more here than elsewhere, because local grids multiply keywords by locations.

Which local rank tracking API is fastest?

Scrapeless returns most requests in under one second. On a local grid that difference compounds: at multiple seconds per request, a few hundred markets is already an overnight job.

Can I track rankings for a specific postal code?

Yes. Pass a city, metro, or postal code in the location parameter and the search originates there. The docs recommend city-level values specifically to simulate a real searcher.

How do I get the map pack instead of web results?

Set tbm to lcl on the same scraper.google.search actor. The response then carries local_results.places with the pack entries.

Can I query one specific Google Business Profile?

Yes. Pass the listing's CID in ludocid, and use lsig when you need the knowledge-graph map view for that entity.

Do GPS coordinates come back with each result?

Yes. Every place carries gps_coordinates with latitude and longitude, so results join to your own store list without a separate geocoding step.

Do I still need my own proxies?

No. IP sourcing, rotation, fingerprinting, and CAPTCHA handling sit behind the endpoint, across 195 countries and regions.

Tracking hundreds of locations? Get a custom rate.

A solutions engineer will scope your keyword grid, markets, and refresh frequency, then send back custom pricing — usually within one business day. Smaller grids can start free today.

Explore the API

Get your API key