Google News Scraper — News by Query, Exact Limit, No Start Fee
Pricing
from $0.80 / 1,000 articles
Type a search query and get Google News as rows — the headline, the Google News link, Google's own article id, the publication time as a real ISO timestamp, the publisher and their site, and how many outlets carried the story. From $0.80/1,000 articles, exact limit, no start fee.
Every entry here is one build on the Builds tab, 1:1, newest first. Prune convention one.
A run that collected nothing now tells you what to put in the box, and says the reason in words rather than in our own shorthand. A run whose only fault was a value this actor could not read said "Delivered 0 articles of 1 asked for across 1 input. Not delivered: 1 input error — none charged." That named a cause, in a vocabulary that is ours and not yours, and said nothing about what to do about it. The count now reads as a sentence — "1 from a value this run could not read" — and on a run that delivered nothing the page adds one plain next step for the biggest cause: the box to use and a working search term to copy, the eight section names that work and where anything else belongs, what a feed that carried no article means, and which of those a second run would change. A feed that would not answer at all, and a page this build could not read, are still never reported as "no news" — neither knows whether there is any. A run that did deliver is unchanged. No price, input field, output column or charged event changed.
The store page now shows a real article row before you spend anything. The page described every column and never showed one, so the only way to see what you were buying was to run it. A real delivered row — headline, Google News link, Google's own article id, the ISO publication time, the publisher and how many outlets carried the story — now sits on the first screen, straight after the price, built by this actor's own parser from a harvested Google News feed. No price, input field, output column or charged event changed.
query, keyword,
keywords, searchQuery, searchQueries, searchTerm, searchTerms or q — or a section as
topic — the run reads them instead of collecting nothing: the values are used exactly as sent,
a term you put in both places is collected once, and one uncharged note names the field to use
next time. Nothing about what is charged changes.maxItems and nothing else, and the repeats are reported beside it: "5 articles of 5
asked for", then "20 more you already had were skipped, not charged". The receipt and each
query's own row say the same, and nothing about what is charged changed.First public build.
TECHNOLOGY,
BUSINESS, WORLD and the rest), a place, or the top stories — each produces the same row, and
target and targetKind say which door it came through, so a dataset mixing them is still one
table.maxItems is exact and it is the only number in this actor. Ask for ten and ten rows land.
Nothing is collected past your cap, and a run that hits it says so on the row where it stops
rather than quietly returning a different number from the one you set.googleNewsUrl is the article's link on Google News, not
the publisher's own URL, and this actor does not claim to resolve it. Google publishes every
article behind an opaque redirect; turning one into a publisher URL is a second undocumented
request per article, and on the day this actor was built that endpoint refused every documented
form of the call. What ships instead is solid: the Google News link, which always resolves for a
reader, plus publisherName and publisherHomeUrl from Google's own data, present on every
article measured. No surcharge, no separate event, and no promise that breaks silently.publishedAt is
ISO-8601 UTC or an explicit null; publishedAtRaw carries Google's own string beside it so the
parse can be checked.1h through 1y), language and country on
Google's own feed parameters, a run clock, and account memory keyed on Google's article ID so a
daily schedule pays only for what is new.