RSS Feed Finder - Discover RSS, Atom & JSON Feeds on Any Site avatar

RSS Feed Finder - Discover RSS, Atom & JSON Feeds on Any Site

Pricing

from $0.32 / 1,000 scanned pages

Go to Apify Store
RSS Feed Finder - Discover RSS, Atom & JSON Feeds on Any Site

RSS Feed Finder - Discover RSS, Atom & JSON Feeds on Any Site

Finds every RSS, Atom and JSON feed a website exposes, from its link tags and common feed paths, de-duplicated with title and type. $0.0004 per page. Input: {"urls":["https://techcrunch.com"]}

Pricing

from $0.32 / 1,000 scanned pages

Rating

0.0

(0)

Developer

Broke to Built

Broke to Built

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

6 hours ago

Last modified

Share

RSS Feed Finder — discover all feeds on any website

RSS Feed Finder finds every RSS, Atom and JSON feed a website exposes, from its link tags and common feed paths, at $0.0004 per page on the Apify Free plan.

  • Price: $0.0004 per page scanned on the Free plan, less on paid plans. A URL that cannot be fetched is not charged.
  • Example input: { "url": "https://techcrunch.com" }
  • Output fields: ok, url, feedCount, feeds

Discover every feed a website exposes: declared <link rel="alternate"> RSS/Atom/JSON feeds plus common feed paths (/feed, /rss, /atom.xml, …), validated and de-duplicated. Single URL or bulk. $0.0004 per page. Failed fetches are recorded free.

What you get

One dataset item per URL:

FieldWhat it is
oktrue on a successful scan, false on an error row
urlThe URL you passed
feedCountHow many distinct feeds were found
feedsArray of { title, href, type, source }, de-duplicated by URL

type is rss, atom or json. source is declared when the feed came from a <link rel="alternate"> tag in the page, or probed when it was found by testing a common feed path. Declared entries win over probed duplicates so you keep the human-readable title. Common false positives that use XML/JSON content types - oEmbed endpoints, WLW manifests, XML-RPC and /embed URLs - are excluded by name.

Example 1 - one site

Input:

{ "url": "https://techcrunch.com", "maxUrls": 25 }

Output (real run, 2026-08-07):

{
"ok": true, "url": "https://techcrunch.com/",
"feedCount": 1,
"feeds": [ { "title": "TechCrunch Feed", "href": "https://techcrunch.com/feed/", "type": "rss", "source": "declared" } ]
}

Example 2 - building a reader or newsletter source list

{
"urls": ["stratechery.com", "https://simonwillison.net", "blog.cloudflare.com", "news.ycombinator.com"],
"maxUrls": 100
}

Bare domains get https:// added for you and duplicates are removed. One row per site, so an import list for an RSS reader or a content pipeline comes out of a single run.

Example 3 - a site with no feed at all

{ "ok": true, "url": "https://example.com/", "feedCount": 0, "feeds": [] }

feedCount: 0 is a real answer, not a failure - plenty of modern sites publish no feed. An unreachable URL is different and comes back as an {ok:false, error} row, uncharged.

Pricing — $0.0004 per page

$0.0004 per page scanned on the Apify Free plan, billed as the page-scanned event. Paid Apify plans pay less ($0.00037 Bronze, $0.00035 Silver, $0.00032 Gold, $0.00029 Platinum, $0.00027 Diamond). No start fee. Failed fetches are recorded free. A page with feedCount: 0 was scanned successfully and is charged.

When NOT to use this

  • You want the feed's articles. This finds feed URLs; it does not read their items. Pair it with an RSS parser (see Related actors below).
  • The feed is at an undeclared, non-standard path. Discovery covers <link rel="alternate"> tags plus /feed, /rss, /atom.xml, /feed.xml, /rss.xml, /index.xml, /feed/ and /feeds/posts/default. A feed at /blog/custom-syndication.xml with no link tag is not findable by any prober, including this one.
  • The page needs JavaScript to render. No browser is launched - the raw HTML response is parsed. A single-page app that injects its link tags at runtime will look feed-less.
  • You want to crawl a whole site for feeds. Only the URL you pass is fetched, plus the common paths on that origin. Sub-pages are not crawled.
  • The site is behind a login or a bot wall. Requests are plain unauthenticated GETs from Apify's infrastructure; a 403 comes back as an error row.

FAQ

How do I find the RSS feed URL of a website? Pass the site URL. Feeds declared in the page's <link rel="alternate"> tags come back first, then common feed paths are probed and validated before being listed.

Does it find Atom and JSON Feed too? Yes - RSS, Atom and JSON Feed, from both declared link tags and probed paths. The type field tells you which one each result is.

Does it verify the feed actually works? Yes for probed candidates: each is fetched and its body or content type must actually look like a feed (<rss, <rdf, <feed, or a JSON Feed shape) before it is listed. That is what keeps /feed pages that return a themed 200 HTML error out of your results.

Can I scan many websites at once? Yes - up to 100 URLs per run via urls (25 by default; raise maxUrls for more). Bare domains get https:// added automatically and duplicates are removed before any fetch.

What about a dead URL? You get an {ok:false, error} record and the run continues. That URL is never charged.

  • RSS Feed Parser (EliAI/rss-feed-parser) — the next step: give it a feed URL this actor found and get clean JSON items. Discover here, parse there.

Use from code or AI agents

curl -X POST "https://api.apify.com/v2/acts/EliAI~webpage-feed-finder/runs?token=YOUR_APIFY_TOKEN" \
-H 'content-type: application/json' -d '{"url":"https://techcrunch.com"}'

Callable as an agent tool through the Apify MCP server (mcp.apify.com).

Who uses it

  • Newsletter curators finding the RSS or Atom feed for each site on a source list
  • Feed reader developers discovering feeds when a user pastes a homepage URL
  • Researchers building a monitoring list of blogs that actually publish a feed
  • Podcast directory builders locating feeds from show websites
  • Automation builders getting a feed URL to wire into a new-post alert