Google Custom Search JSON API and a third-party SERP API are different products. Migration needs a scope check as well as a response adapter: preserve the application’s search purpose, normalize returned fields and verify provider-specific limits. Matching URL fields does not prove equivalent search coverage, ranking or contractual behavior.
Check availability before building a new integration
Google’s current official overview says the Custom Search JSON API is closed to new customers and gives existing customers until January 1, 2027 to transition. Its existing-customer pricing and setup instructions should not be presented as an available new-customer signup path. This revision checked that source on October 13, 2026.
The same overview distinguishes domain-scoped search alternatives from full-web requirements. Confirm your intended scope directly with the chosen provider. SearchCans Google Search API is a SearchCans service accessing search-result data; it is not a replacement Google-owned product or an assertion of Google endorsement.
List the behavior that the application depends on
| Dependency | Migration check |
|---|---|
| Search scope | Domains, engine, market and required result vertical |
| Result shape | items for the existing Google API versus data.organic for SearchCans |
| Result URL | Preserve link and source identity rather than invent a url field |
| Errors | Check HTTP status and each provider’s business/error envelope |
| Quota and payment | Use current documented terms for the actual customer type |
| Comparison sample | Record inputs and timestamps; matching schemas do not guarantee matching rankings |
Normalize the output without disguising its origin
The Python adapter below uses synthetic objects and makes no provider call. It keeps source_kind with the URL, title and snippet. A valid empty Google result can omit items; a SearchCans result must still have a correctly shaped data.organic list. Install the actual authorized clients separately when testing a migration.
def normalize_google_cse(payload):
if not isinstance(payload, dict) or payload.get("error"):
raise ValueError("Google response error or invalid object")
items = payload.get("items", [])
if not isinstance(items, list):
raise ValueError("items must be a list")
return [{"url": item["link"], "title": item.get("title", ""),
"snippet": item.get("snippet", ""), "source_kind": "google_cse"}
for item in items if isinstance(item, dict)
and isinstance(item.get("link"), str)]
def normalize_searchcans(payload):
if not isinstance(payload, dict) or payload.get("code") != 0:
raise ValueError("SearchCans business error or invalid object")
data = payload.get("data")
if not isinstance(data, dict) or not isinstance(data.get("organic"), list):
raise ValueError("Expected data.organic list")
return [{"url": item["link"], "title": item.get("title", ""),
"snippet": item.get("snippet", ""), "source_kind": "searchcans_serp"}
for item in data["organic"] if isinstance(item, dict)
and isinstance(item.get("link"), str)]
if __name__ == "__main__":
import json
google = {"items": [{"link": "https://example.test/a", "title": "Fixture"}]}
serp = {"code": 0, "data": {"organic": [{"link": "https://example.test/a", "title": "Fixture"}]}}
print(json.dumps({"fixture_only": True, "google": normalize_google_cse(google),
"searchcans": normalize_searchcans(serp),
"equivalent_rankings_tested": False}, indent=2))
Google Search Console is a separate analytics interface for a verified property. If the task is exporting that property’s reported queries rather than discovering search-result URLs, use Search Console API pagination and missing-row checks; those analytics limits are not the Custom Search JSON API quota.
Test behavior rather than call it a drop-in replacement
Exercise API errors, malformed lists, a valid empty result and unusable items. Then compare permitted live queries with the same explicit requirements. Keep the sample times and provider settings. Do not infer complete coverage or equal ordering from a single shared URL in two result sets.
If the task is known-page content rather than search discovery, use the collection-operation boundary before choosing a search provider. For a runnable SearchCans client use the Node.js implementation. This article owns the existing official API’s lifecycle and migration decision, not a duplicate SearchCans commercial landing page.
SearchCans publishes this guide. Its product examples are first-party illustrations, not an independent vendor performance study.