The Last Official Google Search API Dies January 1, 2027

If your code calls customsearch.googleapis.com, you're on a countdown clock. Google's own documentation for the Custom Search JSON API now states it plainly: the API is closed to new customers, and existing customers have until January 1, 2027 to move off it. The notice arrived quietly — a docs update and console emails at the start of this year, no keynote, no migration fanfare — which is a strange way to end something bigger than the API itself. This was the last official, sanctioned way to get Google web search results as structured data. After January 2027, there is none.

A 20-year retreat, finally complete

If this feels abrupt, you haven't been watching the pattern. Google shipped a SOAP search API in 2002 and killed it by 2009. Its AJAX-era successor was deprecated in 2010 and shut down in 2014. Google Site Search, the paid product, was retired in 2018. The Site Restricted variant of the JSON API got its deprecation notice back in 2024, with users pointed at Vertex AI Search. Each time, the surviving option got narrower, and the Custom Search JSON API — 100 free queries a day, $5 per thousand after that, hard-capped at 10,000 daily — was the last survivor. Its terms were already a message: this exists for site search boxes, not for anything serious.

What changed the calculus is the LLM era. Search results stopped being a commodity feed for widgets and became grounding data for agents and RAG pipelines — strategic feedstock. Google's moves track that shift precisely: in January 2025 it started requiring JavaScript on search pages, kneecapping a generation of lightweight scrapers, and Microsoft retired its Bing Search APIs in August 2025, funneling everyone toward "grounding" products bundled with Azure's agent stack. The two indexes that mattered have both pulled up the drawbridge in the span of about eighteen months. Raw SERP access isn't being repriced; it's being discontinued as a category.

The replacement that isn't

Google's suggested migration path is Vertex AI Search — currently being rebranded as Agent Search — for queries across up to 50 domains, or "contact us" if you want full web search. Read that carefully. Vertex AI Search is a build-your-own-search product: you bring a corpus, Google indexes it, you pay per query (roughly $1.50–$4 per thousand depending on edition) plus indexing and storage fees. It's a genuinely good answer if what you were doing with CSE was searching your own site.

But that's not what most CSE traffic was. If you were using it as a cheap, legal window into Google's public web index — for a research tool, a fact-checking bot, a citation checker, an agent's web-grounding step — there is no Google product waiting for you. The "full web search solution" behind the contact-us door is an enterprise conversation, not a self-serve API with a free tier. The long tail gets hit hardest: open-source projects like the beets music tagger, whose lyrics plugin leaned on those 100 free daily queries, are already debating alternatives in their issue trackers, and "alternatives" for them means any price above zero is a regression.

Where to actually go

Start with an audit: grep for customsearch.googleapis.com, the cse.list method in Google API clients, and any cx= engine IDs in config. Then pick a lane based on what you were really doing.

Searching your own content. Vertex AI Search is defensible if you're already on GCP and want Google-quality relevance without running infrastructure. If not, this is the push to own your search stack — Algolia if you want managed, Typesense or Meilisearch if you'd rather self-host. You lose nothing here; CSE was never a great site-search engine anyway.

Web grounding for agents and RAG. This is the interesting migration, and honestly the healthiest outcome of the shutdown. The Brave Search API runs on a genuinely independent index at $5 per thousand requests — exact price parity with what CSE charged — with $5 in monthly free credits. Tavily and Exa were built specifically for LLM pipelines and return cleaned, extraction-ready content rather than ten blue links, which usually saves you a fetch-and-parse stage. For most agent workloads, these are better tools than CSE ever was; CSE's JSON was designed for rendering a search box, not feeding a context window.

Needing Google's actual results. SEO tooling, rank tracking, "what does Google say" verification — here you have no clean option. SerpApi and its competitors will sell you scraped Google SERPs, and they work, but you're buying the output of a ToS-gray cat-and-mouse game, priced with that risk baked in. The January 2025 JavaScript wall was a warning shot at exactly this ecosystem. Build with a fallback provider and an abstraction layer, because your vendor's uptime now depends on winning an arms race against Google's anti-bot team.

Don't bet on a reprieve

The deadline is real — it's in Google's own docs, not just a blog post — and nothing in Google's history with search APIs suggests an extension. Fifteen months sounds generous until you notice January 1 sits inside everyone's holiday change freeze, which makes Q1–Q2 2026 the realistic migration window. The work itself is usually small: a different endpoint, a different JSON shape, an afternoon of parser changes. The decision — whose index you trust, at what price, under what terms — is the part worth doing deliberately.

The bigger loss is quieter. For twenty years there was always some official, if grudging, way to treat Google's view of the web as queryable infrastructure. That era ends in January 2027, and the web's most complete index becomes something you can only access as a consumer, or as feedstock for Google's own AI products. Index diversity — Brave, Exa, and whoever crawls next — just became a feature developers actually pay for. That's the one genuinely good thing to come out of this shutdown.