Alternatives to Google News alerts, 2026

The reason to replace Google Alerts is structural, not a matter of taste: an alert can only reach you once a page describing the event exists somewhere and Google has found it. For anything that starts life as a public feed — an earthquake, a tornado warning, an 8-K — that is at least one step later than you could have heard it. The five options below are ordered by how directly they sit on the original filing. Three of them cost nothing.

What Google Alerts actually does

Google Alerts watches Google’s own results for a keyword and emails you when something matches. Google’s instructions for setting one up are explicit about the trigger: “You’ll get emails whenever we find matching search results.” Delivery frequency is a setting under Show options, and the help page names no fee at any point. So it is broad and free, and it will catch a keyword nobody publishes a feed for — which is exactly why it is worth keeping alongside the rest of this page rather than instead of it. What it cannot do is beat the index it depends on. Source: Create an alert, Google Search Help. Checked 4 August 2026.

Alternative 1 — the USGS earthquake feed, read directly

The US Geological Survey publishes its earthquake catalogue as public GeoJSON summary feeds, and states “Updated every minute” against the Past Hour, Past Day, Past 7 Days and Past 30 Days windows alike. The URLs follow one pattern — /summary/{significant|4.5|2.5|1.0|all}_{hour|day|week|month}.geojson — so choosing a magnitude floor is choosing a filename. No key, no account, no quota. If you only care about quakes above M4.5, this single URL replaces every earthquake alert you have ever set. Source: GeoJSON Summary Format, USGS Earthquake Hazards Program. Checked 1 August 2026.

Alternative 2 — National Weather Service alerts from api.weather.gov

The National Weather Service publishes US severe-weather alerts through a free public API: “All of the information presented via the API is intended to be open data, free to use for any purpose… we do not charge any fees for the usage of this service.” Two things to know before you point anything at it. First, “a User Agent is required to identify your application” — a request without one can be blocked. Second, the alerts endpoint “contains alerts issued over the past seven days”, so it is a live window, not an archive, and alert bodies come back in CAP, the Common Alerting Protocol, which is the forecaster’s own wording rather than anyone’s summary of it. Source: National Weather Service API Web Service. Checked 1 August 2026.

Alternative 3 — SEC EDGAR Latest Filings, as an Atom feed

Company news usually reaches the newswires after it reaches EDGAR, so a filings feed is the earliest honest signal available to the public. EDGAR serves its newest filings as Atom, filterable by form type, at /cgi-bin/browse-edgar?action=getcurrent&type=8-K&output=atom. Fetched for this page on 1 August 2026 it returned a live channel titled “Latest Filings - Sat, 01 Aug 2026 08:29:30 EDT”, with entries formatted “8-K - Company Name (CIK) (Filer)”. The SEC’s fair-access policy expects a descriptive User-Agent identifying you; generic fetchers get a 403. Source: EDGAR Latest Filings (Atom), US Securities and Exchange Commission. Checked 1 August 2026.

Alternative 4 — an RSS reader is the delivery layer, not the source

An RSS reader — NetNewsWire, Feedly, Inoreader, whichever — does not find news; it collects feeds you have already chosen and puts them in one place. That distinction matters when replacing Google Alerts, because the three feeds above are all readable in any of them without writing code, and so are the feeds of the outlets you already trust. The work is picking the sources. Swapping a keyword alert for a reader you never fill leaves you with less news than you started with, not more.

Alternative 5 — The Front Wire, if you want the watching done for you

The Front Wire runs the first three feeds on this page continuously and files each item the moment it arrives, with a link back to the source it came from. Be clear about the trade: it is a fixed set of feeds, not an arbitrary keyword, so it will never do the thing Google Alerts is uniquely good at — telling you your own name appeared on a blog. What it does instead is remove the polling, the User-Agent handling and the CAP parsing from the three sources that break fastest, and put earthquakes, weather alerts, filings and newswire headlines in one wire you can read or subscribe to as RSS. Reading is free, all of it; membership at $3/mo or $24/yr pays for running the wire. The full feed list, with the primary source and check date for each, is on the sources page.

So: which one

A keyword that no feed covers — keep Google Alerts, nothing else does that job. Earthquakes only, at a magnitude you choose — the USGS summary feed, free. US severe weather in the forecaster’s own words — api.weather.gov, free, with a User-Agent. A named company’s filings before anyone writes them up — the EDGAR Atom feed. Several of these at once, on your own terms — any RSS reader. All of them watched for you, filed as they land, each item linked to its source — that one is ours, and if you would rather have that as one catch-up email a morning than as a feed to check, that is the daily digest email, free. And if what you actually need is news from before this year, none of the above helps: the historical newspaper archives that cover it are a different product, and this site does not compare them. If the alternative you want is an aggregator rather than a raw feed, the products — Techmeme, Ground News, Google News and this wire — are compared on where a headline actually sends you on news aggregators that link to primary sources. And if the two hazard feeds are the whole point — earthquakes and severe weather, not keywords — the deeper comparison, including what the USGS Earthquake Notification Service pushes and why the National Weather Service refuses to email or text the public directly, is on USGS earthquake and NWS weather alerts in one feed.