RSS Feed Finder — discover all feeds on any website

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:

Field	What it is
ok	true on a successful scan, false on an error row
url	The URL you passed
feedCount	How many distinct feeds were found
feeds	Array 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

Prices below checked via the Apify Store API on 2026-08-07:

Actor	Pricing	One page
This actor	$0.0004 per page	$0.0004
ninhothedev/rss-feed-finder	$0.00005 start + $0.0005 per item	$0.00055

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.

Does it parse the feed's articles? No. It discovers feed URLs. Give the href to an RSS parser to read titles, links and dates.

Can I scan many websites at once? Yes - up to 100 URLs per run via urls. Bare domains get https:// added automatically and duplicates are removed before any fetch.

Why did a WordPress site return more than one feed? WordPress publishes several - the main feed, comment feeds, and often category or author feeds - and it declares them in the HTML. All distinct ones are returned; you pick. oEmbed and WLW manifest alternates are filtered out because they are not feeds.

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

Related actors

• 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).