Move supported Google Custom Search JSON API clients to Search1API ahead of Google’s January 1, 2027 deadline. Change the endpoint and API key to keep supported cse().list() calls and items.title, items.link and items.snippet parsing. The compatibility endpoint uses the same authentication, rate limits and billing as native search.
This release supports first-page web search and explicit site filters. cx does not import saved Google engine settings. Pagination, image search and SafeSearch are unavailable; review the compatibility reference before switching.
Dedicated migration guides for SearXNG, Google CSE and Bing v7 include client configuration examples and compatibility limits in English, Chinese and Japanese. Engine product pages describe search capabilities; migration guides explain switching clients. SearXNG support means client protocol compatibility, not a hosted SearXNG instance or a new search engine.
Get started: SearXNG migration · Google CSE migration · Bing v7 migration · CSE reference