How to Find the RSS Feed of Any Website

Find any website's RSS feed in a minute: check the page source, try common feed paths, or use the platform's pattern. Plus what to do when none exists.

Most websites that publish regularly have an RSS or Atom feed, even when they never link to it. To find it, view the page source and search for application/rss+xml. If that turns up nothing, add a common feed path such as /feed or /rss.xml to the site’s address. If you know what platform the site runs on, its feed usually sits at a predictable address.

That covers nine sites out of ten. The rest of this guide goes through each method in order, the platform patterns worth remembering, and what to do with a site that has no feed.

A site that publishes a feed usually announces it in the <head> of its pages with a tag like this:

<link rel="alternate" type="application/rss+xml" title="Example" href="/feed.xml">

Feed readers and browsers look for exactly this tag. To find it yourself:

  1. Open the site’s homepage, or the section you care about, in a desktop browser.
  2. View the source: right-click and choose View Page Source, or press Ctrl+U (Cmd+Option+U on a Mac).
  3. Search the source for rss+xml. If nothing matches, search for atom+xml.
  4. Copy the href value. If it starts with /, put the site’s address in front of it.

Some sites list more than one feed: one for all posts, one for comments, one per category. The first match is usually the main feed. The comments feed is easy to spot by its title or its address and is rarely what you want.

Check the section page as well as the homepage. A news site might advertise a single sitewide feed on its front page and a narrower one on its technology section.

Method 2: try the common feed paths

When the page source has no feed tag, the feed often exists anyway at one of a few standard addresses. Add each to the end of the site’s address and see what loads:

PathCommon on
/feed or /feed/WordPress, Substack, many custom sites
/rss or /rss/Ghost, Tumblr, Squarespace blogs
/rss.xmlStatic sites, Drupal, many news outlets
/feed.xmlJekyll and other static site generators
/atom.xmlStatic sites, older Blogger setups
/index.xmlHugo

A working feed shows up as a page of XML, or your browser offers to download a file. Either way, the address is the one you want. A “page not found” error means you should try the next path.

If the site keeps its blog under a subfolder, such as example.com/blog, try the paths there first (example.com/blog/feed), then at the root.

Method 3: use the platform’s pattern

Many sites run on a handful of publishing platforms, and each has a fixed feed address. These patterns all returned a live feed when checked for this guide:

  • Substack: the publication’s address plus /feed, for example yourwriter.substack.com/feed. A Substack on a custom domain works the same way.
  • WordPress: the site address plus /feed/. Category feeds follow the pattern /category/name/feed/.
  • Ghost: the site address plus /rss/.
  • Medium: medium.com/feed/@username for a writer, medium.com/feed/publication-name for a publication.
  • Blogger: the blog’s address plus /feeds/posts/default.
  • Tumblr: the blog’s address plus /rss.
  • YouTube: youtube.com/feeds/videos.xml?channel_id= followed by the channel’s ID (the string starting with UC). The ID appears in the channel page’s source if the channel address uses a handle instead.
  • GitHub releases: github.com/owner/repo/releases.atom gives one entry per release of a project.

How do you tell which platform a site runs on? The footer often says so. Failing that, the page source usually gives it away: wp-content in image paths means WordPress, and a generator meta tag often names the platform outright.

Browser extensions and feed readers

If you do this often, let software do the looking. Most feed readers, such as Feedly, Inoreader, and NetNewsWire, accept a plain site address and find the feed themselves using the same tag from method 1. Browser extensions that flag a page’s feed do the same check as you browse.

They all depend on what the site publishes. A reader can find a feed the site advertises or keeps at a standard path. It cannot find one that does not exist.

When a website has no RSS feed

Some sites have no feed at all. Social platforms have mostly dropped them, and plenty of company sites and newer publications never set one up. Search results for “can you create an RSS feed for any website” point to feed generators that scrape a page and guess which parts are new posts.

Those services can work, but they break when the site changes its layout, they may run into the site’s terms of use, and some charge per feed. Before reaching for one, check two alternatives:

  • An email newsletter. Many sites without a feed still send email. A newsletter carries the same updates and, unlike a scraped page, arrives in a shape the publisher controls.
  • A different page of the same site. A site with no feed on its homepage may still have one on its blog, press, or podcast section. Run method 1 on those pages.

If neither turns up anything, the honest answer is that the site does not publish machine-readable updates, and anything you build on top of it will be fragile.

What to do with the feed once you have it

A feed address on its own does nothing. You need something that checks it. A feed reader shows new posts in a list. For sources you would rather hear than read, Reducer turns feeds into a scheduled private podcast episode.

In Reducer you can skip the hunt. Paste a site’s address, in Morning Brief or a show’s feed widget, and it works through the same steps as this guide:

  1. It checks whether the address you entered is already a feed.
  2. If not, it reads the page for advertised feed links, the tag from method 1, and tries the first few.
  3. If those fail, it tries the common paths /feed, /rss, /rss.xml, /feed.xml, /atom.xml, and /index.xml, first under the path you entered, then at the site’s root.

It only accepts a candidate that parses as an RSS or Atom feed with at least one item, and it shows you the feed’s title and latest posts so you can confirm it found the right source. If a site has no feed, it says so instead of guessing. It does not scrape pages.

Here is how that looks with a show:

  1. Start a Morning Brief at app.reducerai.com. Pick a publish time and, if you want it, local weather.
  2. In the Your sources step, paste up to three site addresses: a blog, a Substack, a local paper. Reducer finds each feed, and each becomes its own segment in the daily show, ahead of the headlines and markets.
  3. Subscribe to the show’s private feed in the podcast app you already use. New episodes publish on your schedule.

Each episode speaks a short brief of what the source published since the last one, based on what the feed contains. Feeds that carry full posts or summaries give it more to work with; title-only feeds give a list of headlines. The RSS-to-podcast guide covers how to mix several feeds into one show, and the blog-to-podcast guide covers following individual writers.

Quick reference

  • Search the page source for rss+xml, then atom+xml.
  • Try /feed, /rss, /rss.xml, /feed.xml, /atom.xml, /index.xml.
  • Use the platform pattern: Substack /feed, WordPress /feed/, Ghost /rss/, Medium /feed/@user, YouTube feeds/videos.xml?channel_id=.
  • No feed anywhere? Look for a newsletter before trusting a scraper.

If the point of finding feeds is to keep up with them, let them come to you. Start a Morning Brief and paste the sites you follow.