Extract Google News results — headlines, source names, article URLs, snippets, thumbnails, and recency — as structured JSON for media monitoring, brand mention tracking, and news aggregation workflows.
Structured output
Use Crawlora's Google News API to collect public Google News results without maintaining your own parser, proxy routing, retries, or response normalization layer. The endpoint returns structured JSON that can power media-monitoring dashboards, brand-mention alerts, news aggregators, competitor coverage tracking, and AI summarization workflows.
Monitoring workflows
Crawlora helps teams record which articles, sources, and headlines appear for a topic or brand in Google News, and how coverage changes over time across keywords, countries, and languages.
Brand monitoring workflowsRequest schema
These parameters come from the active Search Google News catalog entry.
| Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
| q | string | Yes | Search query | openai |
| country | string | No | Two-letter country code; defaults to us | us |
| lang | string | No | Google UI language; defaults to en | en |
| count | integer | No | Results per page; defaults to 10, clamped to 1..50 | 10 |
| page | integer | No | 1-based page number; defaults to 1 | 1 |
Example JSON
This example is rendered from the active endpoint catalog so the page stays aligned with Docs and Playground.
{
"code": 200,
"msg": "OK",
"data": {
"results": [
{
"position": 1,
"title": "OpenAI announces update",
"url": "https://example.com/openai-news",
"description": "OpenAI announced an update.",
"source": "Example News",
"thumbnail": "https://example.com/thumb.jpg",
"age": "2 hours ago"
}
],
"pagination": {
"page": 1,
"next_page": 2
}
}
}Endpoint catalog
/google/newsReturns normalized Google News vertical results (title, source, link, age) parsed from the public Google News results page. Locale defaults to country=us and lang=en. Returns 503 when Google serves a challenge page or unusable HTML.
Managed execution
Crawlora wraps request handling, proxy-aware collection, response parsing, and documented error behavior behind a stable API surface for supported public Google News result pages.
Request logic for the public Google News results page
Proxy-aware collection and retry-aware execution where supported
Challenge-aware behavior for unusable upstream responses
Normalized JSON responses with Playground-tested examples
Credit-based usage tied to documented endpoint costs
Crawlora detects unusable upstream responses and returns documented errors instead of silently returning broken HTML.
Build or buy
Use this comparison to decide whether to maintain scraping infrastructure internally or call a managed endpoint.
| Requirement | Building internally | Crawlora |
|---|---|---|
| Proxy rotation | Buy, test, rotate, and monitor proxy pools. | Use managed proxy-aware collection where supported. |
| Parser maintenance | Maintain selectors as the News layout changes. | Use parsers maintained behind the API. |
| Schema normalization | Design and version your own response model. | Receive documented JSON fields from the catalog. |
| Retries and error classification | Classify challenges, empty pages, and upstream failures yourself. | Receive documented errors for unusable upstream responses. |
| Endpoint docs | Write and maintain internal API documentation. | Use generated Docs pages from the active endpoint catalog. |
| Playground testing | Build a test console for developers. | Test the same endpoint in Playground before shipping. |
| Usage billing | Create your own metering and limits. | Use credit-based usage and plan limits. |
Crawlora is not the official Google News API and is not affiliated with Google. Crawlora provides structured public web data extraction endpoints for supported Google News result pages. Data may be delayed, normalized, or change when upstream pages change. Customers are responsible for ensuring their use complies with applicable laws, third-party rights, platform terms, and Crawlora terms.
Related APIs
Connect this endpoint with adjacent Crawlora search, monitoring, docs, and pricing pages.
Pair news coverage with Google SERP rank tracking.
OpenAdd Bing results to cross-engine monitoring workflows.
OpenAdd Brave Search results to discovery and monitoring workflows.
OpenTrack brand mentions, sentiment signals, and coverage across sources.
OpenFold news signals into broader market and competitor research.
OpenFeed fresh news context into retrieval-augmented AI pipelines.
OpenReview plans, credits, limits, and usage options.
OpenBrowse the full active endpoint catalog.
OpenFAQ
Answers for developers evaluating Crawlora for supported public search result pages.
Yes. Crawlora provides a Google News endpoint for supported public Google News result pages and returns normalized JSON through a documented API route.
Yes. Each response includes article headlines, source names, URLs, snippets, and relative recency, so you can record which coverage appears for a brand or topic over time and detect new articles. Pair recurring queries with the brand monitoring use case to build a media monitor.
The catalog example includes news results with positions, titles, article URLs, source names, descriptions, thumbnails, and relative age, plus pagination metadata.
Yes. The Google News endpoint accepts q (query), country, lang, count, and page parameters; locale defaults to country=us and lang=en.
Results reflect the public Google News results page at request time, including each result's relative age. Crawlora does not guarantee real-time delivery; schedule recurring requests for ongoing monitoring.
Crawlora detects unusable upstream responses and returns documented errors (for example a 503) instead of silently returning broken HTML. Customers should handle errors, retries, and upstream availability changes in their integrations.
No. Crawlora is not the official Google News API and is not affiliated with Google. Crawlora provides structured public web data extraction endpoints for supported Google News result pages.
Test /google/news in Playground, inspect the current response schema in Docs, and compare credit-based usage on the pricing page.