Does Google News Have an API? Options for Monitoring Agents
Google does not document a current public Google News API for searching stories. Its former Google News Search API was retired in 2016. If you need Google News results specifically, use a third-party SERP service and treat it as an independent provider, not a Google API. If you need relevant news for an agent, a dedicated news-data API or a general News Search API is usually a cleaner fit. RSS can support lightweight experiments, but it is not a documented JSON contract. In every case, discovery is only the first step: open selected publisher pages, deduplicate coverage, and preserve source evidence before generating alerts or summaries.
What Google officially retired
Google's own retirement notice for several search APIs says the Google News Search API was deprecated in 2011 and would cease operations on February 15, 2016. The notice pointed developers toward Custom Search at the time, but it did not announce a new public endpoint that reproduces Google News search.
That history matters because many pages now use “Google News API” as a product category. A service may return Google News results, search its own news corpus, or expose a general web-search index. Those are all potentially useful, but none becomes an official Google API because of its name.
The safe interpretation in 2026 is narrow: there is no current, documented public Google News query API operated by Google. Before selecting an alternative, decide whether the application needs Google's result set or simply needs news articles about a topic.
Publisher tools are not search APIs
Two official Google features often appear in the same research trail, but they solve the opposite side of the exchange.
Google's Publisher Center transition notice explains that publication pages became automatically generated in March 2025 and that Google News stopped using RSS feeds or web locations submitted through Publisher Center. This is guidance for publishers whose sites may appear in Google News. It does not provide an endpoint for an application to query Google News.
Likewise, a Google News sitemap helps a publisher tell Google about recent articles. It is an ingestion and discovery signal for the publisher's own URLs, not a feed of ranked stories that a monitoring agent can search.
Keep the direction of data explicit:
- Publisher Center and news sitemaps help a publisher expose its own content to Google.
- A News Search API helps an application discover articles from multiple sources.
- Fetch or Render opens a selected source so the application can verify what it actually says.
Choose an alternative by the result you must preserve
The phrase “Google News API alternative” hides several different product requirements. Use the output contract—not the familiar brand name—to choose.
| Required outcome | Appropriate path | What to verify before production |
|---|---|---|
| Reproduce what Google News shows or how it orders stories | A third-party Google News SERP API | Provider identity, permitted use, location/language controls, ranking fields, freshness, and failure behavior |
| Read a lightweight stream of Google News headlines | RSS, behind your own adapter | XML parsing, redirect handling, stable item identity, missing fields, and an exit plan if observed behavior changes |
| Find relevant news for an agent or monitoring workflow | A dedicated news-data API or general News Search API | Coverage, source URLs, date semantics, filters, deduplication, pagination, and whether article text is included |
| Publish your own articles for Google to discover | Publisher eligibility, crawlable pages, and a news sitemap | Canonicals, publication dates, sitemap freshness, and Search Console feedback |
| Verify the full claim behind a result | Fetch, Render, and sometimes Screenshot | Final URL, target status, complete body, publication identity, visible evidence, and access boundaries |
A third-party service can explicitly retrieve Google News result pages. For example, SerpApi documents its Google News engine as a service that scrapes results from news.google.com and returns provider-managed JSON. That may fit ranking analysis, but the API key, uptime promise, schema, and relationship with Google belong to SerpApi, not Google.
A dedicated news database answers a different question. The NewsAPI Everything endpoint searches its indexed sources and returns article metadata with filters such as query, domains, dates, language, and sort order. It does not claim to reproduce Google News ranking. Compare providers using their own current documentation and your own test set rather than transferring assumptions from one index to another.
For an agent that needs current source candidates rather than Google's exact ordering, the AnyCrawler News Search API is the product CTA: discover recent links and publisher context, then route only selected results into deeper reading. It is not an official Google API and should not be described as one.
Test discovery separately from source verification
A news result is a lead, not the final evidence. Search snippets can be truncated, dates can refer to indexing rather than the underlying event, and several outlets can repeat the same report. The monitoring pipeline should verify the publisher page before it promotes a claim.
On August 30, 2026, the following Node.js probe was run against AnyCrawler's public no-key crawl endpoint. The permitted target was Google's API-retirement notice used above.
const target =
"https://developers.googleblog.com/en/retirement-of-certain-google-search-apis/";
const endpoint = new URL("https://api.anycrawler.com/free/v1/crawl");
endpoint.searchParams.set("url", target);
const response = await fetch(endpoint);
const data = await response.json();
const markdown = data.results?.markdown ?? "";
console.log({
testedAt: new Date().toISOString(),
gatewayStatus: response.status,
targetStatus: data.status_code ?? null,
requestedUrl: data.requested_url ?? null,
finalUrl: data.final_url ?? null,
title: data.results?.title ?? null,
markdownChars: markdown.length,
hasRetirementHeading: markdown.includes(
"Retirement of certain Google search APIs",
),
hasNewsApiReference: markdown.includes("Google News Search API"),
creditsUsed: data.credits_used ?? null,
});
The run returned gateway status 200 and target status 200. It extracted the expected title, 5,072 Markdown characters, the retirement heading, and the Google News Search API reference. The free response returned neither final_url nor credits_used, so both were recorded as null; the test does not imply that the authenticated News Search endpoint was called or that credits were consumed.
Use the same pattern after discovery: name the claim or marker that must exist, read the source, and fail the record when the expected evidence is absent. The Fetch Web Page API is the next decision for HTML-first articles. Escalate to Render only when the required source content depends on JavaScript, and add Screenshot only when visible layout or disclosure state is part of the evidence.
Build monitoring as an evidence pipeline
An API does not create a monitoring system by itself. Scheduling, query history, comparison logic, alerts, and retention belong to your application unless the selected provider explicitly documents those features.
A bounded workflow can use these states:
- DISCOVERED: save the query, provider, locale, request time, returned position when relevant, result URL, title, snippet, and provider date.
- NORMALIZED: resolve URL parameters conservatively and preserve the original URL alongside the normalized candidate.
- GROUPED: cluster obvious copies or updates without deleting independent reporting merely because headlines are similar.
- READ: fetch or render the selected publisher page and record status, requested URL, final URL when available, title, publication time, and content markers.
- VERIFIED: attach the exact passage or field that supports the monitored claim. Keep uncertainty when the source does not establish it.
- PRESERVED: store the evidence record and, when appearance matters, a screenshot with capture time and source identity.
- EMITTED: send an alert only after the record satisfies the workflow's source and freshness rules.
A compact evidence record might look like this:
{
"query": "example product safety recall",
"discovered_at": "2026-08-30T03:16:26Z",
"discovery_provider": "news-search-provider",
"result_url": "https://publisher.example/story",
"requested_url": "https://publisher.example/story",
"final_url": null,
"target_status": 200,
"publisher": "Publisher name",
"published_at": null,
"required_markers": ["product name", "recall"],
"missing_markers": [],
"evidence_state": "verified",
"credits_used": null
}
null is useful evidence. It distinguishes an unavailable field from an empty string and prevents downstream code from inventing precision. Keep the provider's date separate from the page's stated publication time and from your own access time; they describe different events.
Failure paths should change the state, not disappear
News monitoring fails in ways that a list of successful headlines will hide. Model those failures before sending alerts.
- No results: record the completed query and locale. Do not infer that no event occurred.
- Repeated result URL: update the observation time without duplicating the source record.
- Similar headline, different reporting: preserve both until source reading shows they are copies or the same wire report.
- Redirect to a home page, consent screen, or sign-in: mark the result unread and retain both requested and observed final identity when available.
- HTTP 200 with missing article markers: classify the extraction as incomplete; a successful transport is not verified content.
- Publication date conflict: retain the provider date, page date, and access time separately instead of selecting the most convenient value.
- Temporary provider failure: retry with a finite policy, then keep a structured failed attempt. Do not silently substitute a different index and pretend the result set is equivalent.
The failure record is particularly important for AI agents. Without it, a model sees only the surviving sources and can mistake a partial retrieval for comprehensive coverage.
What if Google's ranking is the actual research object?
Most monitoring products need news about an entity or event, so a provider-neutral news index is often enough. The boundary changes when the question is “What did Google News show, in this location and language, at this time?” Then the ranking and surface are themselves evidence, and replacing them with another news database changes the measurement.
That requirement needs stricter provenance: identify the third-party retrieval provider, store locale and query parameters, preserve returned position, record access time, and avoid calling the response “Google's API output.” You also need a policy decision about terms, retention, and acceptable dependency on an unofficial integration. If those constraints cannot be satisfied, the honest answer may be that the product should monitor publishers directly rather than promise Google News visibility tracking.
Frequently asked questions
Is there an official Google News API in 2026?
Google does not document a current public API for searching Google News. Its former Google News Search API was deprecated in 2011 and shut down in 2016. Services advertised as Google News APIs today are generally third-party products, observed RSS integrations, or independent news databases. Check who issues the credential, which index is searched, and whether the result contract actually matches your application before integrating it.
Can I get a Google News API key from Google?
There is no current official Google News search API key to request. A provider offering a “Google News API key” is normally issuing its own credential for its own service. That distinction affects documentation, support, permitted use, uptime, schema changes, and incident handling. Record the provider name in your data model so downstream users do not mistake third-party output for a direct Google response.
Is Google News RSS a production API?
RSS can be useful for a small experiment or a lightweight headline feed, and a publication-day check returned XML for a U.S. English search query. It is not a documented JSON API contract with the versioning and field guarantees most production integrations expect. Put it behind an adapter, handle missing or changed fields, cache responsibly, and maintain a tested migration path instead of coupling application logic directly to observed feed syntax.
When should I use a Google News SERP API?
Use one when Google's result selection or ordering is the thing you must measure, such as publisher visibility research for a defined query, language, location, and time. Preserve the third-party provider identity and all retrieval parameters. If the application only needs relevant articles, a dedicated news API or general News Search API avoids tying the data model to a particular search surface and may offer filters better suited to monitoring.
Does a News Search API return full article text?
Do not assume it does. Many search endpoints return titles, source context, dates, URLs, and snippets for discovery. Full text may be absent, truncated, licensed separately, or available only from the publisher page. After selecting a result, use an authorized Fetch or Render path, validate the final source identity and required content, and keep the discovery record separate from the verified article evidence.
Can AnyCrawler schedule monitoring or detect changes automatically?
The workflow described here does not claim a built-in scheduler, diff engine, or alert service. AnyCrawler can supply discovery, page reading, rendering, and screenshot steps; your application must schedule queries, compare records, deduplicate sources, enforce retry limits, and emit alerts. Keeping that boundary explicit prevents an API call from being mistaken for a complete monitoring product and makes each failure state independently testable.
