RSS and Atom Feed Discovery
Find the feeds a page declares, and check the usual paths for one it has but never advertised.
About this tool
Looks for RSS, Atom and JSON Feed declarations in a page's head, and checks the conventional paths for a feed the site is publishing without saying so.
That second half is the useful one. **Most sites with a feed do not link to it.** The CMS generated the file, it is sitting at `/feed`, and nothing in the HTML points at it — so browser extensions, feed readers and anything else looking has to guess. One `<link rel="alternate">` in the head makes it discoverable, and it is one line.
Feeds are worth keeping working. They are how newsletters, aggregators and a good number of readers still follow a site, they cost nothing once generated, and unlike a social platform nobody can switch them off.
Common questions
How should a feed be declared?
A link element in the head: rel="alternate", type="application/rss+xml" or application/atom+xml, an href, and a title. The title matters where a site has several feeds, because it is what a reader shows in the list.
Do feeds still matter?
To a smaller audience than in 2008, and it is an engaged one — feed readers, newsletter tools and aggregators all use them. They cost nothing once generated, and nobody can change an algorithm and take them away.
RSS, Atom or JSON Feed?
Whatever your CMS already produces. Atom is the better-specified format, RSS is more widely supported, JSON Feed is the easiest to consume in code. Every reader handles the first two, so this is rarely worth a decision.
Does a feed help SEO?
Not directly. It helps distribution — a post picked up by an aggregator earns links you did not ask for, and those do matter. The effect is indirect and real.