Is Google Custom Search API free for commercial use?

I regularly see developers build entire SaaS features around the Google Custom Search JSON API, only to realize they are building on a platform scheduled for complete shutdown. Navigating Google's complex API pricing and hidden overage charges is hard enough, but finding out the API is closed to new users makes long-term planning nearly impossible. In my ten years of working with search integrations, I have learned that relying on dying endpoints is the fastest way to accumulate technical debt. I will break down the exact commercial licensing terms, explain how to set up hard billing limits to protect your budget, and map out your migration options before the 2027 deprecation date.

Quick Summary (TL;DR):

• The Google Custom Search JSON API free tier is limited to exactly 100 queries per day.
• Paid queries beyond this cap cost $5 per 1,000 requests, up to a maximum limit of 10,000 requests per day.
• The entire service is scheduled for complete deprecation on January 1, 2027, and registration is already blocked for new Google Cloud Console accounts.

Is Google Custom Search API free for commercial use?

Yes, Google Custom Search API is free for commercial use, but it is capped at 100 free queries per day. Beyond this free tier, additional queries cost $5 per 1,000 up to a hard daily limit of 10,000 queries.

In my experience, developers frequently underestimate how quickly a small user base consumes 100 daily queries, leading to immediate application errors unless billing is active. If your platform has just 10 active users who execute 10 searches each per day, you will exhaust your free daily query quota in less than 24 hours. Once your app hits the 100-request limit, Google immediately throws a 403 Forbidden error with the message "Daily Limit Exceeded." To prevent this from breaking your production environment, you must attach a credit card to your Google Cloud billing profile and pay the standard google custom search api pricing rate of $5.00 per 1,000 queries.

Even if you are willing to pay, the programmable search engine api limits impose a rigid ceiling of 10,000 total queries per day. For scaling startups, enterprise search aggregators, or high-throughput AI pipelines, this 10k query cap makes Google’s native API fundamentally non-viable. If you need a scaling solution that can handle millions of requests without hitting sudden brick walls, you can read our guide on how to handle a google custom search api free limit and discover ways to scale past these artificial API blockages.

The upcoming 2027 Google Custom Search API deprecation

Google is officially retiring the Custom Search JSON API on January 1, 2027. The API is already unavailable to brand new Google Cloud Platform accounts, making it a legacy product for existing integrations only.

Building a new application on this API in 2026 is a massive strategic mistake. In working with legacy code migrations, I have seen teams spend months configuring custom parameters, setting up developer api keys, and debugging custom layouts, only to discover their newly created Google Cloud projects cannot even enable the service. If you attempt to access the Custom Search API on a GCP account created after the initial deprecation announcement phase, the Google console simply redirects you to standard web search widgets or completely blocks service activation.

Official Deprecation Notice: "The following pricing only applies to existing customers of Custom Search JSON API until the service is discontinued on January 1, 2027. This API is not available to new customers." — Google for Developers Official Documentation

If your commercial architecture depends on this API, you are operating on borrowed time. Existing setups must begin active migration planning now to prevent service disruption when Google pulls the plug on January 1, 2027. The deprecation means that even paid enterprise systems using Google's engine will lose access to raw JSON search results, forcing a shift to third-party scrapers or alternative search indexes.

Commercial terms and ad-supported monetization options

Google allows you to use Custom Search in paid SaaS platforms and commercial applications. You can choose between the ad-free Custom Search JSON API ($5 per 1,000 queries) or the ad-supported Programmable Search Element API, which integrates AdSense to monetize search results.

A common mistake is assuming the free Programmable Search Element is completely unrestricted; it still enforces visual design guidelines and injects competitors' ads into your application. When utilizing the ad-supported Programmable Search Element (the frontend JavaScript widget), you are required to keep the Google branding visible, and you must display relevant ads. By linking your AdSense account, you can technically monetize these search results, converting user search volume into a revenue stream. However, for a premium SaaS product, displaying Google-brokered ads—which might advertise your direct competitors—creates an incredibly unprofessional user experience.

If you choose to bypass the ads by using the ad-free Custom Search JSON API, you gain clean, structured search results that can be easily parsed. This is highly useful for backend pipelines, such as data mining frameworks or automated applications. To see how these JSON datasets are structured and parsed in production environments, you can follow our tutorial on how to extract structured data from google search. Keep in mind that while the JSON API allows you to present data behind a paid subscription or client login without showing ads, you are still bound by Google's strict query limits and the impending 2027 deprecation timeline.

• Programmable Search Element (JS Widget): Free to use, requires Google branding, displays AdSense ads, can monetize user traffic, restricted to web page embed layouts.
• Custom Search JSON API: Ad-free, costs $5/1,000 queries, capped at 10,000 queries daily, returns raw JSON search results, requires manual frontend rendering.
• Commercial SaaS Integration: Permitted under Google terms, allows displaying search outputs behind paywalls, but does not allow redistribution or reselling of raw API keys.

How to configure hard billing limits in Google Cloud

To avoid surprise bills, you must configure daily usage quotas and set up budget alerts directly in your Google Cloud Platform console. This prevents your API key from exceeding your budget if your application experiences a sudden traffic spike.

I always advise setting your daily quota to 100 requests initially if you want to test the API commercially without risking a surprise bill at the end of the month. A simple loop error in your backend worker script can easily consume your entire daily allocation of 10,000 paid queries in under 5 minutes, resulting in a sudden $50 charge on your linked credit card. If multiple microservices are hitting the same endpoint concurrently, these costs compound rapidly. To prevent these security and budget issues, you should also learn how to bypass google search blocks safely and keep your scraping scrapers running securely without leaking credentials.

Step-by-step guide to capping your GCP Search API usage:

1. Log into your Google Cloud Platform Console and select your active project.
2. Navigate to APIs & Services > Dashboard, and click on Custom Search API from your enabled APIs list.
3. Click on the Quotas tab on the left-side navigation panel.
4. Locate the Queries per day limit (default is set to 10,000).
5. Click the pencil edit icon, set the value to 100 (for the strict free tier) or your target budget ceiling, and save the changes.
6. To configure alerts, go to the Billing section in the GCP sidebar, click on Budgets & Alerts, and establish a warning notification at 50%, 90%, and 100% of your monthly spend.