What replaced the official Google News API?
There is no single official replacement for the Google News API. Teams now choose among SERP APIs that return Google News results, scraping APIs that control extraction, publisher news APIs that collect articles directly, media monitoring suites that add workflow, and trend tools such as Trends MCP that track momentum across news and other platforms.
ScrapingBee's 2026 guide notes that the original Google News Search API was deprecated in 2011 and that several old Google search APIs were turned down in 2016. That history matters because many buyers still search for "Google News API" as if Google sells one. It does not. The practical question is which substitute matches the monitoring job.
A developer building a Google News ranking dashboard needs different data from a communications team tracking executive mentions, and both need different data from a content team deciding which story is crossing from news into Reddit, X, TikTok, Google Search, and YouTube. The same distinction shows up in broader monitoring stacks, including X API alternatives for trend monitoring and AI search monitoring tools for content teams.
Which Google News API alternative fits each job?
The right Google News API alternative depends on whether the team needs Google News ranking data, article coverage, raw extraction control, alerts, or trend validation. SERP APIs are best when Google's order matters. Publisher APIs are best when broad article coverage matters. Trends MCP fits when news must be compared with search, social, commerce, and app signals.
| Need | Best fit | Example tools | Why it works |
|---|---|---|---|
| Exact Google News result monitoring | SERP API | SerpApi, Searlo, Outscraper | Returns structured results from Google News or Google result pages |
| Custom extraction pipeline | Scraping API | ScrapingBee, Oxylabs, Bright Data, ScraperAPI | Handles rendering, proxies, and parsing control for teams with engineering ownership |
| Broad publisher article coverage | News aggregator API | Newsdata.io, HasData, NewsAPI, Event Registry style APIs | Tracks publisher feeds and article databases rather than Google's ranking surface |
| PR and comms workflow | Media monitoring suite | Meltwater, Brandwatch, Talkwalker, Vuelio | Adds alerts, dashboards, stakeholder reports, and sentiment workflows |
| Cross-platform trend selection | Trend intelligence API | Trends MCP | Compares Google News with Google Search, Reddit, TikTok, YouTube, app, and news volume signals |
This is the common mistake in vendor selection: teams compare APIs as if they return the same object. A Google News SERP result, a publisher article record, a scraped HTML page, and a normalized trend score are not interchangeable. They can all support monitoring, but they answer different questions.
When should developers choose a SERP API?
Developers should choose a SERP API when the order, source, freshness, and localization of Google News results matter. A SERP API is the closest practical substitute for programmatic Google News visibility because it returns what Google News surfaces for a query, country, language, or time filter.
SerpApi is the established option in this group. Its Google News API page lists the engine=google_news endpoint, and its pricing page showed a free tier of 250 searches per month plus a $25 plan for 1,000 searches per month when checked on July 21, 2026. Cached searches may be free when the same query and parameters match its cache rules.
Searlo is a newer search API positioned around cost and AI-ready output. Its News Search API page lists structured Google News results, 195-country localization, a 3,000-credit free tier, and $0.30 per 1,000 searches as of the same check. It also promotes a TOON response format for lower token use in LLM workflows.
SERP APIs are strongest for brand monitoring, competitor tracking, industry news dashboards, and "what does Google News show right now?" questions. They are weaker when the team needs full article text, long historical archives, or publisher-direct coverage that does not depend on Google's ranking choices.
When is a scraping API better?
A scraping API is better when a team needs extraction control, custom parsing, or a pipeline that can pull more than the standard structured fields exposed by a SERP API. ScrapingBee, Oxylabs, Bright Data, ScraperAPI, and similar providers handle rendering, proxy rotation, and anti-bot work so internal engineers can focus on storage and analysis.
ScrapingBee's June 2026 comparison argues that scraping APIs are best for custom news monitoring pipelines, while SERP APIs are better for fast structured JSON. Its own article lists ScrapingBee plans starting at $49 per month and describes a dedicated Google News endpoint returning headlines, sources, timestamps, bylines, and links.
This category is technical by nature. The team needs to think about retry rules, deduplication, rate limits, legal review, storage, monitoring, and output drift. A scraping API may be the best answer for a product team building a data feature, but it can be the wrong answer for a content team that simply needs daily topic selection.
When are publisher news APIs the better answer?
Publisher news APIs are better when the team needs broad article coverage rather than Google's ranking view. Newsdata.io, HasData, NewsAPI-style services, Event Registry-style services, and Perigon-style services collect or index articles from publishers, then expose them through keyword, language, geography, topic, entity, or time filters.
The difference is important. A publisher API may catch articles that Google News does not place highly, while a Google News SERP API reflects what Google is surfacing to searchers at a point in time. Neither is automatically better. A brand-safety team may want every article. A search visibility team may care only about the stories Google News places in front of users.
For content strategy, publisher APIs can create too much noise unless they are paired with trend filters. Hundreds of articles about a topic do not prove that people care. News volume, search movement, Reddit discussion, TikTok spread, and YouTube activity help separate a real trend from a wire-story burst.
Where does Trends MCP fit?
Trends MCP fits when the job is trend monitoring rather than article ingestion. It exposes Google News Top News, Google News time series, news volume, and news sentiment alongside signals from Google Search, Google Shopping, YouTube, TikTok, Reddit, Amazon, Wikipedia, app downloads, npm, Steam, and other sources.
That makes it different from a Google News scraping API. Trends MCP is not the tool to fetch every article URL from a Google News query. It is the tool to ask whether a topic visible in Google News is also growing across the places where demand, attention, and behavior show up. A content team can validate whether a news story is gaining search interest, social discussion, commerce demand, or app behavior before assigning a post.
This matters for AI search as well. A topic that appears in Google News may not be the topic assistants cite later. AI search monitoring pairs visibility checks with source quality and topic evidence. Trends MCP adds the cross-platform evidence layer that a pure article API does not provide.
What does a practical trend monitoring stack look like?
A practical trend monitoring stack separates collection, validation, and action. One tool should not be forced to do all three jobs. Google News results show editorial attention. Publisher feeds show coverage breadth. Trends MCP shows cross-platform movement. A social listening suite turns that evidence into alerts, assignments, and stakeholder reporting.
A content or research team can run a simple weekly workflow:
- Pull current Google News or SERP results for core topics through SerpApi, Searlo, or another SERP provider.
- Use a publisher API or media monitoring suite to catch articles that do not rank highly on Google News.
- Check the same topics in Trends MCP across Google Search, Google News, Reddit, TikTok, YouTube, and news volume.
- Prioritize topics that show multi-source growth, not only headline count.
- Route the winners into content briefs, analyst notes, or monitoring alerts.
For teams building a broader research stack, the guide to AI trend research tools covers platforms that turn trend data into topic discovery, while the guide to social listening tools covers suites that monitor mentions and audience response.
What risks should buyers check before choosing?
Buyers should check data rights, rate limits, output stability, localization, historical retention, and whether the tool returns Google-ranked results or publisher-sourced records. Most failed Google News API projects fail because the buyer chose the wrong data object, not because the API was technically weak.
The risk checklist is short:
- Data rights: Scraping public pages may be common, but counsel should review platform terms, storage, and downstream use.
- Rate limits: A cheap API can become expensive or unreliable if the monitoring plan needs thousands of localized queries per day.
- Output drift: Google News layouts, fields, and modules change. SERP and scraping providers need maintenance plans.
- Localization: Country, language, device, and time filters can change which stories appear.
- Deduplication: One story can appear through syndicated copies, wire pickups, and duplicate publisher URLs.
- History: Some tools are built for live retrieval, while others support archives and backtests.
There is also an interpretation risk. A high Google News count can signal real demand, but it can also reflect a short news cycle, a press release burst, or a single syndicated article copied across many outlets. Cross-source trend checks reduce that risk.
FAQ
Does Google offer an official Google News API in 2026?
No. Google does not offer a general official Google News API for developers. Teams that need programmatic Google News data usually use SERP APIs, scraping APIs, publisher news APIs, media monitoring suites, or trend intelligence tools depending on the job.
What is the closest replacement for the Google News API?
A SERP API is the closest replacement if the goal is to retrieve structured Google News results for a query. SerpApi and Searlo are examples. A publisher API is not the same replacement because it indexes articles directly rather than returning Google's ranking surface.
Is Trends MCP a Google News scraper?
No. Trends MCP is not a Google News scraper for article extraction. It provides Google News trend signals, Google News Top News, news volume, news sentiment, and cross-platform trend data so teams can validate whether a news topic is gaining broader attention.
Which option is best for content teams?
Content teams usually need a SERP or publisher feed for collection, Trends MCP for validation, and a workflow tool for assignments or reporting. If only one tool can be added first, choose the tool that answers the weakest part of the current process: discovery, validation, or execution.