Places API Nearby Search vs Text Search: Which to Use (2026)

Key takeaways
- Text Search takes a free-text query such as
plumber in Leedsand returns up to 60 results over three pages of 20. Nearby Search takes a centre point, a radius of up to 50,000 metres and place types, and returns at most 20 results with no pagination. - Both endpoints return the same Place fields, require a field mask, and are billed at the highest SKU in that mask (Essentials, Pro, Enterprise or Enterprise + Atmosphere). Matching paid search tiers have the same entry prices, but only Text Search offers an IDs-only Essentials SKU.
- For lead lists, use Text Search for one trade in one town, and switch to a grid of Nearby Search circles only where Text Search hits its 60-result ceiling.
- Overlapping queries and circles return the same places. Deduplicate by
places.idso you do not pay twice for the same business.
The Places API (New) gives you two ways to find businesses: Text Search, which takes a query the way a person would type it, and Nearby Search, which sweeps a circle around a coordinate. They return the same Place object and share the same pricing tiers, but the inputs, the result limits and the way you cover an area are different, and the wrong choice means more requests for the same list.
Short answer: Nearby Search takes a centre point, a radius (up to 50,000 metres) and place types, and returns at most 20 results with no pagination. Text Search takes a free-text query such as plumber in Leeds, accepts an optional location bias or restriction, and returns up to 60 results over three pages. Matching paid tiers have the same entry prices; Text Search also has an IDs-only Essentials option that Nearby Search does not.
This guide compares Nearby Search vs Text Search side by side, with working curl and Python examples, the result limits that shape lead-list work, and a short routine for deciding which one to call.
Nearby Search vs Text Search: what each endpoint takes
| Text Search (New) | Nearby Search (New) | |
|---|---|---|
| Endpoint | POST https://places.googleapis.com/v1/places:searchText | POST https://places.googleapis.com/v1/places:searchNearby |
| Required input | textQuery, a string such as restaurant or plumber in Leeds | locationRestriction with a circle: centre latitude/longitude and a radius in metres |
| Radius | Optional locationBias circle (radius 0 to 50,000 m) or rectangle; locationRestriction is a rectangle only | Required; must be between 0.0 and 50,000.0 metres inclusive |
| Type filtering | includedType: one type from Google's type table | includedTypes, excludedTypes, includedPrimaryTypes, excludedPrimaryTypes: up to 50 types per category |
| Ranking | rankPreference: RELEVANCE or DISTANCE | rankPreference: POPULARITY (default) or DISTANCE |
| Other filters | minRating, openNow, priceLevels, strictTypeFiltering | includeFutureOpeningBusinesses |
| Field mask | Required; omitting it returns an error | Required; omitting it returns an error |
The practical difference: Text Search understands queries like "emergency plumber near Leeds station" and lets Google interpret both the trade and the place. Nearby Search does not accept a free-text query at all; you give it exact coordinates and the place types you want inside the circle.
How many results do Nearby Search and Text Search return?
This is the difference that shapes lead-list work.
- Text Search returns 20 results per page by default (
pageSizeaccepts 1 to 20). You fetch further pages by passing thenextPageTokenfrom one response aspageTokenin the next. Google's page states that Text Search (New) returns a maximum of 60 results across all pages, and that this limit is subject to change. - Nearby Search returns at most 20 results per request.
maxResultCountmust be between 1 and 20, and 20 is the default. The Nearby Search page describes no pagination and no page token, so 20 is the ceiling for one circle.
Either way, one request never gives you a whole city. Text Search covers a trade in a town in up to three pages; Nearby Search covers one small circle in one request. Getting past those ceilings means running more queries and removing duplicates, which is the same problem the Google Maps interface has; see the Google Maps search results limit for why the numbers are what they are.
Is Nearby Search cheaper than Text Search?
For matching Pro, Enterprise and Enterprise + Atmosphere requests, the entry prices match. However, Text Search has an IDs-only Essentials SKU; Nearby Search starts at Pro, even for place IDs. Google's usage-and-billing page states that a request is billed at the highest SKU any of its fields falls into, so compare the endpoint SKU as well as the requested fields. For a lead list the fields you care about split like this:
| Tier | Fields (same names on both endpoints) | Free per month and entry price (Google's price list) |
|---|---|---|
| Essentials (IDs only), Text Search | places.id, places.name, places.attributions, nextPageToken | Unlimited, no charge |
| Pro | places.displayName, places.formattedAddress, places.location, places.businessStatus, places.types, places.primaryType | 5,000 free, then $32 per 1,000 |
| Enterprise | places.nationalPhoneNumber, places.internationalPhoneNumber, places.websiteUri, places.rating, places.userRatingCount, places.regularOpeningHours | 1,000 free, then $35 per 1,000 |
| Enterprise + Atmosphere | places.reviews, places.editorialSummary, places.parkingOptions, places.outdoorSeating | 1,000 free, then $40 per 1,000 |
Google's price list showed the same free amounts and entry prices for the Nearby Search Pro, Enterprise and Enterprise + Atmosphere SKUs as for Text Search when checked. Prices change; confirm on Google's page.
One difference worth knowing: the Text Search page lists an IDs-only Essentials SKU, while the Nearby Search page lists three SKUs (Pro, Enterprise and Enterprise + Atmosphere) and puts places.id in the Pro list. If you want a free ID-only pass to deduplicate an area before requesting paid fields, Text Search is the endpoint that documents it. How far the free monthly amounts stretch is worked through in the Google Places API free tier, and the full cost arithmetic for a list is in Google Places API pricing for lead lists.
Text Search Essentials (IDs only), Pro or Enterprise: which fields?
These are billing categories for the same searchText endpoint. Requesting a business display name differs from requesting its resource name: places.name is a resource identifier, while places.displayName is the readable business name.
| Need | Example X-Goog-FieldMask | Text Search SKU |
|---|---|---|
| Place IDs | places.id,nextPageToken | Essentials (IDs only) |
| Business names and addresses | places.id,places.displayName,places.formattedAddress | Pro |
| Business websites | places.id,places.websiteUri | Enterprise |
For a radius-based request use searchNearby and its circle restriction. A Text Search location bias can guide results but is not a hard boundary. Keep New API request examples separate from Legacy examples.
Example requests: Text Search and Nearby Search in curl and Python
Text Search with curl
curl -X POST -d '{"textQuery": "plumber in Leeds", "pageSize": 20}' \
-H 'Content-Type: application/json' \
-H 'X-Goog-Api-Key: API_KEY' \
-H 'X-Goog-FieldMask: places.id,places.displayName,places.formattedAddress,places.nationalPhoneNumber,places.websiteUri,nextPageToken' \
'https://places.googleapis.com/v1/places:searchText'To get the second page, send the same body plus "pageToken": "<nextPageToken from the response>". Because places.nationalPhoneNumber and places.websiteUri are Enterprise fields, every page of this query is an Enterprise request.
Nearby Search with curl
curl -X POST -d '{
"includedTypes": ["plumber"],
"maxResultCount": 20,
"rankPreference": "DISTANCE",
"locationRestriction": {
"circle": {
"center": {"latitude": 53.7997, "longitude": -1.5492},
"radius": 1500.0
}
}
}' \
-H 'Content-Type: application/json' \
-H 'X-Goog-Api-Key: API_KEY' \
-H 'X-Goog-FieldMask: places.id,places.displayName,places.formattedAddress,places.nationalPhoneNumber,places.websiteUri' \
'https://places.googleapis.com/v1/places:searchNearby'There is no page token to follow. If the circle holds more than 20 plumbers, you shrink the radius or move the centre and run it again.
The same two calls in Python
import requests
KEY = "API_KEY"
FIELDS = "places.id,places.displayName,places.formattedAddress,places.nationalPhoneNumber,places.websiteUri"
def text_search(query, page_token=None):
body = {"textQuery": query, "pageSize": 20}
if page_token:
body["pageToken"] = page_token
r = requests.post(
"https://places.googleapis.com/v1/places:searchText",
json=body,
headers={"X-Goog-Api-Key": KEY, "X-Goog-FieldMask": FIELDS + ",nextPageToken"},
timeout=30,
)
r.raise_for_status()
return r.json()
def nearby_search(lat, lng, radius_m, types):
body = {
"includedTypes": types,
"maxResultCount": 20,
"locationRestriction": {"circle": {"center": {"latitude": lat, "longitude": lng}, "radius": radius_m}},
}
r = requests.post(
"https://places.googleapis.com/v1/places:searchNearby",
json=body,
headers={"X-Goog-Api-Key": KEY, "X-Goog-FieldMask": FIELDS},
timeout=30,
)
r.raise_for_status()
return r.json()A fuller script with paging, deduplication by places.id and CSV output is in Google Places API with Python for business leads. If the results feed internal tooling or a CRM, check the Google Maps Platform terms on caching Places data before you store them.
Which should you use for a lead list?
| You want | Use | Why |
|---|---|---|
| A trade across a town or small city | Text Search | One query, up to 60 results, Google handles the geography |
| Broader coverage of a type in a dense area | Nearby Search on a grid | Small circles with rankPreference: DISTANCE sweep an area systematically; 20 per circle |
| Businesses matching a phrase, not a type | Text Search | textQuery accepts words the type table does not have |
| Strict control of the search area | Nearby Search | The circle is a hard boundary; Text Search's locationBias only biases |
| A free ID-only pass before paid fields | Text Search | The IDs-only Essentials SKU is documented for Text Search |
| Opening hours, rating, phone, website | Either | Same Enterprise fields on both endpoints |
A common pattern is to start with Text Search for each trade-and-town pair, note where a query hits the 60-result ceiling, and switch to a Nearby Search grid only in those dense spots. That keeps the request count down while still covering the centre of a big city. If you are still weighing the API against scraping the Maps interface instead, Google Places API vs a Google Maps scraper compares cost and limits for both routes.
What neither endpoint gives you
- Emails. Neither endpoint returns an email address. You read each business website yourself, or use a tool that does; how to find business email addresses from Google Maps walks through the website-reading step, and the email warm-up schedule covers how slowly a new mailbox should start sending to the addresses you find.
- Deduplication. Overlapping queries and circles return the same places; key everything on
places.id. - Filters. "Has no website" is a check you write (
websiteUrimissing), and ad-pixel or social-presence checks need the website, not the API. - Storage rules. Google's policies restrict how long most Places content may be cached; read them before building a permanent database.
- Cost control. Set a daily quota on each search method and restrict the API key. Budget alerts warn; quotas stop.
If the goal is a contactable list rather than a data pipeline, a hosted tool does this joining work for you. LeadOutreach searches Google Maps by keyword and location, returns the listing fields, reads each website for emails and social links, runs basic email checks, and filters for No website, phone present, rating, social presence and ad-pixel presence, with CSV export subject to plan limits. The Google Maps email extractor page shows the output, and the pricing page has current limits.
How to decide: a five-step routine
- Write the list you want as a sentence: "electricians in Sheffield" or "every cafe within 1 km of the station". Trade-plus-place means Text Search; type-plus-radius means Nearby Search.
- Choose the smallest field mask that gives you the columns you need, and check which tier it lands in.
- Run one request and count the results. If Text Search reaches its documented total-result ceiling, or Nearby Search returns exactly 20, the result set may be truncated; neither proves you found every business.
- Split: more towns or suburbs for Text Search, smaller circles for Nearby Search.
- Deduplicate by place ID, then enrich the survivors with whatever the API cannot give you.
Sources and further reading
Start finding verified leads today
Search Google Maps by niche and city and export verified emails, phone numbers, and marketing gap audit signals to CSV or your CRM. 7-day Starter trial, then plans from $19/month.
No credit card required. Free plan of 100 leads a month stays available.
Related articles
Google Places API With Python: Pull Business Leads Step by Step (2026)
Set up the API, understand the request, run the full script and see where the approach stops being the best tool.
Google Places API Cost & Pricing for Lead Lists (2026)
The published prices, API pricing examples for real lead lists, and a fair comparison with hosted scraping tools.
Is Google Places API Free? 2026 Free Tier Limits & Real Costs
How Google calculates free tier monthly limits for Places API, which fields cost credits, and how to avoid surprise billing.
Frequently asked questions
Text Search takes a free-text query such as plumber in Leeds, optionally biased or restricted to an area, and can return up to 60 results over three pages. Nearby Search takes a circle defined by a centre point and a radius of up to 50,000 metres plus place types, and returns at most 20 results with no pagination. Both return Place fields, but Text Search has an IDs-only Essentials tier while Nearby Search starts at Pro.
Google's Nearby Search (New) documentation describes no page token and sets maxResultCount to a maximum of 20, so one request returns at most 20 places. To cover more businesses you run additional requests with smaller or shifted circles and remove duplicates by place ID.
They use the same pricing tiers. Google's price list showed the same free monthly amounts and entry prices for the Pro, Enterprise and Enterprise + Atmosphere SKUs on both endpoints, with a free monthly allowance per SKU before charges start. What you pay depends on the fields in your field mask and the number of requests, not on which endpoint you call. Only Text Search documents an unlimited IDs-only Essentials tier.
Text Search for the common case of one trade in one town, because it accepts natural queries and pages up to 60 results. Nearby Search when you need to sweep a dense area systematically with a grid of small circles, or when you need a hard boundary rather than a bias.
No. Neither endpoint returns email addresses at any pricing tier. The website field is available at the Enterprise tier, and finding an email means reading that website separately, by hand, with your own code, or with a tool built for it.