Google Places API allows websites and applications to use Google’s location data, including place search, autocomplete, business details, reviews, photos and location-based suggestions.
In 2026, Google Places API pricing is based on a pay-as-you-go model. This means there is no standard fixed monthly fee for most users. Instead, costs depend on the specific API features you use, how many requests your website or application makes, and whether your usage stays within Google’s free monthly limits.
For many businesses, the main question is simple:
Can you use Google Places API without paying?
In many cases, yes. If your usage stays within Google’s free monthly allowance and you set your quotas carefully, you can reduce the risk of being charged. However, Google still requires billing to be enabled, even if you expect to stay within the free tier.
Quick summary
Google Places API pricing in 2026 works like this:
- Pricing is based on usage, not a fixed monthly plan.
- Each API feature is billed as a separate SKU.
- Each SKU has its own free monthly usage allowance.
- You are only charged when usage exceeds the free limit for that SKU.
- Billing must be enabled, even if you stay within the free limits.
- Quotas can be set to help prevent usage going beyond the free allowance.
- Budget alerts can warn you about spend, but they do not stop usage by themselves.
What does Google Places API cost in 2026?
Google Places API costs are calculated per request, per feature.
Each feature is linked to a SKU, which is Google’s term for a billable usage item. For example, Autocomplete, Place Details, Nearby Search and Text Search are treated separately.
This means your total cost depends on which features your website or application uses.
For example, a simple website using limited Place Details requests may stay within the free monthly allowance. A larger application using frequent searches, autocomplete requests, detailed business data and photos may generate billable usage more quickly.
Google Places API free tier limits in 2026
Google no longer uses the old shared US$200 monthly credit model. Instead, Google applies free monthly usage limits to individual SKUs.
This means each feature has its own free allowance.
Broadly, Google Maps Platform now groups many services into the following pricing categories:
Category | Typical free monthly usage |
Essentials | 10,000 free calls per SKU per month |
Pro | 5,000 free calls per SKU per month |
Enterprise | 1,000 free calls per SKU per month |
Some ID-only SKUs may have unlimited free usage.
The exact limit depends on the specific SKU being triggered. This is why it is important to check which API features your website or application actually uses.
Can you avoid Google Places API charges?
Yes, in many cases you can avoid charges by keeping usage within the free monthly limits.
The most practical way to do this is to set quota limits below the free allowance for the SKUs you are using.
For example, if the relevant SKU includes 10,000 free requests per month, you could set a lower quota such as 8,000 or 9,000 requests per month. This gives you a safety buffer and helps reduce the risk of unexpected charges.
The important trade-off is that once the quota is reached, the API feature may stop working until the quota resets.
For example:
- A reviews widget may stop loading.
- A location search tool may stop returning results.
- An autocomplete field may stop suggesting addresses or places.
- A store locator may stop displaying results.
For many small business websites, this trade-off is acceptable. It is often better for a non-essential API feature to stop temporarily than for the business to receive unexpected charges.
Example quota limits to avoid charges
A safe quota limit should usually sit below the free monthly allowance.
Free monthly allowance | Safer quota limit |
10,000 requests per month | 8,000 to 9,000 requests per month |
5,000 requests per month | 4,000 to 4,500 requests per month |
1,000 requests per month | 800 to 900 requests per month |
If Google Cloud only allows you to control a particular quota on a daily basis, divide your monthly target by the number of days in the month.
For example:
Monthly target | Approximate daily cap |
9,000 requests per month | 300 requests per day |
4,500 requests per month | 150 requests per day |
900 requests per month | 30 requests per day |
This method does not remove the need for billing to be enabled, but it can help prevent your project from generating paid usage.
Quotas vs budget alerts
Quotas and budget alerts are not the same thing.
Control | What it does | Does it stop usage? |
Quota limit | Caps API usage | Yes, when the limit is reached |
Budget alert | Warns you when spend reaches a threshold | No |
API key restriction | Limits where and how the key can be used | Helps prevent misuse |
Field masks | Limits which data is requested | Helps reduce unnecessary cost |
If your goal is to avoid charges, quota limits are the most important control.
Budget alerts are still useful, but they only notify you. They do not automatically stop your API from being used.
How to set up Google Places API safely
To set up Google Places API safely, you should create a Google Cloud project, enable the required API, create an API key, restrict the key, set quotas and configure budget alerts. If you are unsure how to handle the technical setup, our website design and development team can help with API implementation, plugin configuration and website performance checks.
Step 1: Create or select a Google Cloud project
Log in to Google Cloud Console and either create a new project or select the existing project you want to use.
It is best to keep client projects separate, rather than running multiple unrelated websites through the same project. This makes usage easier to track and reduces the risk of confusion.
Step 2: Enable billing
Google Maps Platform requires billing to be enabled before you can use most APIs.
This applies even if you expect to stay within the free monthly allowance.
You will usually need to add a valid payment method to the Google Cloud billing account.
Step 3: Enable Places API
In Google Cloud Console, go to the API library and enable the relevant Places API service.
Depending on your implementation, this may be shown as Places API or Places API (New).
Only enable the APIs you actually need. Avoid enabling unnecessary APIs, as this can make the setup harder to manage and may create additional risk if the key is misused.
Step 4: Create an API key
Once the API is enabled, create an API key.
This key is what your website, plugin or application will use to make requests to Google Places API.
Do not leave the key unrestricted.
Step 5: Restrict the API key
API key restrictions are essential.
For a website, you should usually restrict the key by HTTP referrer, so it can only be used on your domain.
For example, you may restrict it to:
- yourdomain.co.uk
- www.yourdomain.co.uk
You should also restrict the key so it can only be used with the required API, such as Places API.
This helps reduce the risk of unauthorised usage.
Step 6: Set quota limits
After enabling the API, go to the quota settings for the project.
The exact layout of Google Cloud Console can change, but the process is broadly:
- Open Google Cloud Console.
- Select the correct project.
- Go to Google Maps Platform.
- Open the Quotas section.
- Select the relevant API, such as Places API or Places API (New).
- Review the available quota types.
- Choose the quota you want to limit.
- Edit the quota value.
- Set a limit below the free monthly allowance.
- Save the quota.
- Test the website or application.
You should check all API features being used. For example, if your setup uses both Autocomplete and Place Details, make sure you review the quotas for both.
Step 7: Set budget alerts
Budget alerts should be used as a backup.
A good starting point is to create alerts at:
- 50%
- 75%
- 90%
- 100%
However, remember that budget alerts do not stop usage. They only send notifications.
To actually cap usage, you need quota limits.
Step 8: Test the setup
After applying restrictions and quotas, test the feature on the website.
Check that:
- The API-powered feature works correctly.
- The API key is not exposed for unrestricted use.
- The quotas are set correctly.
- The correct project is recording usage.
- The website does not make unnecessary repeated requests.
What affects Google Places API costs?
Google Places API cost is not only about traffic. It is also about how efficiently the API is used.
1. The type of request
Different requests trigger different SKUs.
Autocomplete, Place Details, Nearby Search, Text Search and Photos can all have different pricing.
2. The number of requests
Each request counts towards usage.
A high-traffic website or application will naturally use more requests than a small website.
3. The data requested
Some API requests allow you to choose which fields you want returned.
Requesting only the data you need can help control costs.
4. Duplicate or unnecessary requests
Poor implementation can increase usage.
Examples include:
- Calling the API on every page load.
- Making repeated requests for the same data.
- Triggering requests before the user has shown clear intent.
- Not caching data where appropriate.
A good WordPress caching setup can help reduce repeated requests and improve website performance.
5. Plugin behaviour
If you use a WordPress plugin to display Google reviews or business information, check how often it calls the API.
A well-configured plugin should cache data where appropriate, rather than requesting fresh data from Google on every page load. Choosing and managing WordPress plugins carefully can help reduce unnecessary API requests, improve reliability and lower the risk of unexpected usage.
Example: using Google Places API for reviews
A common use case is displaying Google reviews on a business website.
For this type of setup, the aim is usually to retrieve review or business data periodically, not every time a visitor loads a page. If you are using Google Places API to support trust signals on your website, it is also worth reviewing how to get Google reviews and why they are important.
A sensible setup would include:
- A restricted API key.
- Only the required API enabled.
- Cached review data.
- Low quota limits below the free allowance.
- Budget alerts as a backup.
- Regular usage checks in Google Cloud Console.
This can help the business use Google review data while reducing the risk of unexpected charges.
Common mistakes to avoid
Relying only on budget alerts
Budget alerts are useful, but they do not stop API usage.
If you want to avoid charges, set quotas.
Leaving the API key unrestricted
An unrestricted API key can be misused.
Always restrict the key by domain and by API.
Enabling APIs you do not need
Only enable the services required for your website or application.
Requesting too much data
Do not request every available field unless you genuinely need it.
Requesting unnecessary data can increase cost and reduce performance.
Not testing quota limits
If your quota is too low, the feature may stop working sooner than expected.
Test the setup before relying on it.
Key takeaway
Google Places API pricing in 2026 is usage-based and organised by SKU.
The old shared US$200 monthly credit has been replaced by free monthly usage limits per SKU. This means each feature has its own free allowance, and charges only apply when usage exceeds the free limit for that specific SKU.
For most small business websites, the safest approach is:
- Enable billing because Google requires it.
- Use only the API features you need.
- Restrict your API key.
- Set quota limits below the free monthly allowance.
- Set budget alerts.
- Cache data where possible.
- Monitor usage regularly.
If you set your quotas carefully and keep usage within the free limits, it is often possible to use Google Places API without generating charges. However, if your website relies on Google APIs, plugins, tracking scripts or third-party tools, it is worth reviewing the setup carefully. A technical SEO audit can help identify performance issues, unnecessary scripts, tracking problems and technical risks.
Help with Google Places API and Setup
Are you struggling to make sense of the complex labyrinth of the google settings and options?
We would be happy to help! Please contact us and we will be happy to help with this or any other digital marketing challenges you may have.
