Extract Google News results as structured JSON — article headlines, publishing source, timestamp, and the topic clusters that group related coverage of a story.
Google News organizes articles into story clusters, grouping many publishers' coverage of the same event under a lead headline rather than listing isolated links. The Google News Scraper API returns each article's headline, source, publish timestamp, and snippet, along with the cluster and topic it belongs to, as validated JSON.
Media monitors, PR teams, and quantitative researchers use this feed to track how a story spreads across outlets, when coverage breaks, and which sources lead it. Filter by query, topic, or edition, geo-segment by country and language, schedule recurring pulls, and diff snapshots to catch newly published coverage.
# POST a target — get validated JSON back
curl https://api.crawlzo.com/v4/scrape \
-H "Authorization: Bearer $CRAWLZO_KEY" \
-d '{
"url": "https://www.googlenews.com/search?q=structured+web+data",
"geo": "us",
"device": "desktop"
}'
// ← response
{
"status": "ok",
"data": {
"query": "structured web data",
"organic": [
{ "position": 1, "title": "…", "url": "https://…", "snippet": "…" }
],
"features": { "ads": 3, "answer_box": true }
}
}Google News data parsed into clean, validated JSON. Pull any group below on its own, or combine them in a single request.
Brand and crisis media-coverage monitoring
Story-cluster and narrative spread tracking
Source and publisher coverage analysis
Breaking-news alerting by topic or edition
Yes. We return each article with its headline, source, publish date, and snippet, plus the story cluster and topic it sits in, so you can see how coverage of an event groups across outlets.
Yes. You can target results by country and language edition so the articles and clusters match what readers see in that locale.
Structured JSON straight from the API, or pushed to your stack natively — S3, BigQuery, Snowflake, Postgres, Kafka, or any HTTPS webhook. Call it from Python, Node, Go, Rust, or any HTTP client. The data lands where your pipeline already lives.
No. You pay for valid, schema-passing rows only. Retries, blocks, CAPTCHAs, and 5xxs are on us. If a run doesn't return data that conforms to the schema, it isn't billed.
Every request routes through the same engine behind our Web Unblocker API: compliant residential IPs, real browser fingerprints, TLS-level evasion, behaviour modelling, and built-in CAPTCHA solving. Hard targets become routine.
Yes. We respect robots policies, rate budgets, and ToS-aware allow/deny lists. We deliver and move on — no row-level retention beyond your replay window. GDPR DPA, PII redaction, and custom data residency available on request.