Google Custom Search: 10 results per query max, and the API is sunsetting

TL;DR

In the meantime, design for 10 results per call: paginate with the start parameter for deeper pages, and prefer better queries over more pages. Dont build a long-term dependency on this API without a migration plan.

Fix

1. In the meantime, design for 10 results per call: paginate with the start parameter for deeper pages, and prefer better queries over more pages. Expected: You get the expected result; the problem is gone.

When to use

• You are setting up or using this Google Custom Search feature.
• The symptom matches: 10 results per query max, and the API is sunsetting.

When NOT to use

• Unrelated Google Custom Search issues (different feature, different failure).
• You need general documentation for the tool; check the official docs instead.

Compatibility

Reported against Google Custom Search.

Variant phrasings

10 results per query max, and the API is sunsetting

Why it happens

Web: a search-API comparison guide documents two strategic facts about the Custom Search JSON API. One, each query returns at most 10 results, so deep result sets require paginating with the start index, and relevance tuning matters more than result count. Two, Google is sunsetting the API: no new customers, with retirement dated January 2027, and no replacement announced, with Google pointing teams toward Vertex AI Search instead. Source: https://github.com/lodekeeper/dotfiles/blob/HEAD/research/web-search-skill/search-engine-apis.md

Edge cases

• If your error message differs even slightly, this is probably a different issue; search the exact text.
• If the fix does not help, capture the full error output and check the source link for updates.

Web: a search-API comparison guide documents two strategic facts about the Custom Search JSON API. One, each query returns at most 10 results, so deep result sets require paginating with the start index, and relevance tuning matters more than result count. Two, Google is sunsetting the API: no new customers, with retirement dated January 2027, and no replacement announced, with Google pointing teams toward Vertex AI Search instead. Source: https://github.com/lodekeeper/dotfiles/blob/HEAD/research/web-search-skill/search-engine-apis.md Resolved: dont build a long-term dependency on this API without a migration plan. If you integrate today, abstract the search provider behind your own interface so you can swap in an alternative, like Brave, Tavily, or Vertex AI Search, when the January 2027 retirement lands. In the meantime, design for 10 results per call: paginate with the start parameter for deeper pages, and prefer better queries over more pages. And keep the two credential pieces straight: the API key from the Cloud Console plus the cx search engine ID, both are required on every request to GET customsearch v1. Source: https://github.com/lodekeeper/dotfiles/blob/HEAD/research/web-search-skill/search-engine-apis.md