Facebook removed its native RSS feed in 2015. To get an RSS feed for a Facebook page in 2026, use a third-party tool: FetchRSS or RSS.app for any public page, Inoreader if you already curate there, or Zapier if you have admin access to the page. Meta also runs first-party RSS feeds for its corporate blogs at about.fb.com/feed and engineering.fb.com/feed.
That’s the short answer most guides bury under a thousand words of preamble. The rest of this article walks through which tool fits which use case, how each one works in practice, the official Meta feeds that most guides skip entirely, and the full workflow for importing a Facebook feed into WordPress so you can do something useful with it.
What Happened to Facebook’s Native RSS
Early Facebook had a page feed endpoint. You could point any RSS reader at facebook.com/feeds/page.php?format=rss20&id=PAGE_ID and get a clean XML feed of public posts. No authentication, no tokens, no rate limits worth worrying about. This is what a lot of old tutorials are still quoting.
Facebook pulled the endpoint in January 2015. The Graph API kept a JSON equivalent running for a while behind an access token, but that was deprecated too. By 2018 the situation was what it is today: no official, supported way to get an RSS feed for an arbitrary Facebook page.
This matters for two reasons. First, if you’re reading a guide that just tells you to hit a Facebook URL directly, close the tab. Second, everything that does work in 2026 is a third-party service sitting between you and Facebook, scraping public pages and generating an RSS feed from what it sees. That has implications for reliability, which is covered further down.
Which “Facebook RSS” Do You Actually Need?
Before picking a tool, it’s worth being clear about what you’re trying to do. “Facebook RSS feed” gets used for three different things:
- Any public Facebook page. You want to monitor a competitor, a news publisher, or a brand’s Facebook page. You don’t run the page. You just want its posts as an RSS feed. This is the use case most people mean.
- Your own Facebook page. You run the page and you want to pipe its posts somewhere, for example into an email newsletter or onto your own website. You have admin access, which opens up options like Zapier.
- Meta as a company. You’re tracking news from Facebook, Instagram, or Meta’s engineering and research teams. This is different from page-level feeds, and Meta actually runs official RSS feeds for it.
The rest of this guide covers all three in order, starting with the most common case.
Four Tools for Getting an RSS Feed From a Facebook Page
Here’s the short version:
| Tool | Works for | Free tier | Update frequency | FB account needed? |
|---|---|---|---|---|
| FetchRSS | Any public page | 5 feeds, 5 posts each, 24h refresh | 24h free, 15 min paid | No |
| RSS.app | Any public page | Limited feeds on free plan | Varies by plan | No |
| Inoreader | Any public page | Requires paid tier for FB sources | Near-real-time on paid tiers | No (Inoreader handles it) |
| Zapier | Only pages you admin | Free tier triggers every 15 min | 15 min | Yes (admin access) |
For most people, FetchRSS is the fastest path to a working feed URL. Start there. If you hit limits, RSS.app is the next step up. Inoreader is worth it if you’re already doing heavy content curation and want Facebook in the same interface as your other sources. Zapier is the odd one out because it only works for pages you control.
Method 1: FetchRSS
fetchrss.com/facebook lets you paste any public Facebook page URL and get an RSS feed back. Sign up (free), paste the page URL, and click Get RSS. You get a feed URL ending in .xml that updates every 24 hours on the free plan.
The free plan caps you at five feeds of five posts each. If that’s enough, you’re done. If you need more feeds, faster updates, or more posts per feed, their paid tiers start in the single digits per month.
Two things to watch for. First, FetchRSS sometimes shows posts a few hours late even on the paid plan, because it’s scraping Facebook’s public-facing page rather than pulling from an API. Second, if Facebook changes how it renders public pages (which happens every so often), FetchRSS tends to break for a few days while they adapt. This isn’t unique to FetchRSS. It applies to every tool in this list.
Method 2: RSS.app
RSS.app does the same job with a cleaner UI. You paste a public page URL, it generates a feed, and you can preview the output before committing. No Facebook account required.
RSS.app’s pitch is that it covers a lot of platforms from one dashboard (Facebook, X, Instagram, LinkedIn, TikTok, Google News). If you’re building a multi-source content setup, it’s often easier to manage feeds in one place than to juggle FetchRSS for Facebook, a separate tool for Instagram, and yet another one for Twitter.
The free tier is tighter than FetchRSS in most configurations. For a single Facebook page you just want to monitor, FetchRSS is usually enough. For multiple platforms, RSS.app often ends up being cheaper once you add things up.
Method 3: Inoreader
Inoreader is a content-curation reader that lets you subscribe to Facebook pages as if they were regular feeds. You add the Facebook page URL the same way you’d add any other subscription and Inoreader handles the rest in the background.
This is the right tool if you’re already reading RSS in Inoreader and you want Facebook in the same interface. It’s the wrong tool if all you want is a feed URL you can drop into something else, because Inoreader doesn’t always expose the raw feed URL outside its own platform. Their higher tiers add more Facebook sources and faster refresh, and if you’re using Inoreader’s “Rules” feature for filtering, it’s a decent all-in-one curation setup.
Method 4: Zapier (only for pages you admin)
Zapier’s Facebook Pages integration can trigger on new posts to your own Facebook page and send them anywhere, including an RSS feed endpoint via Zapier’s “RSS by Zapier” integration. The catch is that the trigger only works for Facebook pages you have admin access to.
If you run the page, this is actually the most reliable of the four methods. You’re using Facebook’s official API with proper authentication, which means it doesn’t break every time Facebook tweaks their public-page HTML. If you don’t run the page, this method isn’t available to you. Use FetchRSS or RSS.app.
The Official Meta Feeds (That Almost Nobody Mentions)
Separate from page-level RSS, Meta runs actual RSS feeds for its own corporate properties. Not Facebook pages. Meta’s blogs. If you’re monitoring the company itself, these exist and work:
- about.fb.com/feed – Meta’s official newsroom. Company announcements, policy updates, major feature launches.
- engineering.fb.com/feed – Meta Engineering. Technical posts about infrastructure, open-source releases, systems work.
- Instagram blog – Product and feature announcements. (Feed URL pattern varies, check the page source.)
These are proper, first-party RSS feeds. No scraping, no third-party intermediary, no risk of breaking when Facebook changes their HTML. If what you actually need is “news about Facebook the company,” use these instead of a FetchRSS-generated scrape of the main page. They’re cleaner, more reliable, and get indexed by RSS readers immediately.
Importing a Facebook RSS Feed Into WordPress
Getting a feed URL is the first half of the problem. The second half is doing something useful with it on your site, and this is where most Facebook RSS guides fall off the map. They hand you a FetchRSS link and stop. Here’s the rest of it.
The setup below uses WP RSS Aggregator. Any feed-importing plugin can handle the basic display, but the filtering and Feed to Post steps below are where Aggregator is useful, especially if you’re pulling from multiple Facebook pages at once.
Step 1: Add the feed as a source
In your WordPress admin, go to Aggregator → Feeds → Add New. Paste the feed URL you generated (from FetchRSS, RSS.app, or one of the Meta feeds above) into the URL field. Give it a name so you can find it later. Save.
Aggregator will fetch the feed immediately and show you a preview of what it’s pulling. If you see posts, you’re set. If you see an error, the feed URL is wrong or the tool that generated it has hit a rate limit. Swap tools or regenerate the feed.
Step 2: Filter for what matters
A raw Facebook page feed dumps everything the page posts. You probably don’t want everything. If you’re monitoring a news publisher for a specific beat, or a brand for product announcements, set keyword filters on the feed source. Aggregator lets you include posts that match certain keywords and exclude posts that contain others.
This is usually where a “just use any RSS plugin” setup starts to creak. A free plugin gives you the feed. A filtered, curated feed is what actually helps your readers. For more on this, see our guide on automated content curation, which walks through the filtering logic in more detail.
Step 3: Pick a display
Go to Aggregator → Displays → Create a new display. Pick the feed source you just added, choose a template (List, Grid, or Excerpt & Thumbnails are the main three), and configure what’s visible on each item: date, source name, excerpt length, thumbnail.
Drop the display’s shortcode onto any page or post on your site. The feed renders there, updates on the schedule you set, and styles to match your theme. More on the options: Displays feature page.
Step 4 (optional): Import as actual posts
If you don’t just want to display the feed but actually want each Facebook post to become a WordPress post (or a custom post type), that’s what Feed to Post does. You configure it once per feed source, pick a post type and category, and every new item in the feed creates a matching post in your database.
This is the right approach if you’re building a news aggregator or a content hub where each source becomes part of your own site’s content. It’s overkill if you just want a widget showing “latest from our Facebook.” For the full walkthrough, see Feed to Post and the tutorial on importing RSS feeds into WordPress posts.
When Your Feed Breaks (Because It Will)
Not sure whether the feed itself broke or just your import? Run the URL through our feed finder tool to see whether it still returns items.
Every third-party Facebook RSS tool scrapes Facebook’s public pages. Facebook changes its public-page markup regularly. Tools break. This isn’t a reason to avoid them, it’s a reason to know what you’re going to do when it happens.
Three things help:
- Monitor the feed. Aggregator’s feed log will show if a source stops returning items. Set up a glance-at-it-weekly habit for important feeds.
- Have a backup tool. If FetchRSS breaks for a week, switch the feed URL to an RSS.app equivalent. Takes five minutes and the rest of your setup (filters, displays, imports) stays the same.
- For your own pages, use Zapier. If it’s a page you admin, you don’t need to scrape. Use the official API via Zapier and the reliability problem mostly disappears.
None of this is exotic. It’s the same operational hygiene any RSS-based workflow needs. Facebook just happens to be one of the flakier sources because Meta doesn’t want to be in the RSS business.
What to Actually Do Next
If you’re here because you need a feed right now, start with FetchRSS for a public page or Zapier if it’s your own page. Get a working feed URL in ten minutes, paste it into Aggregator, and you have the skeleton of a workflow.
If you’re thinking bigger, the Facebook feed is one source. The value compounds when you add more: Twitter/X, YouTube channels, Google News searches, industry blogs. That’s where the WordPress side of this stops being “a Facebook widget” and starts being a real content hub. Our guides on finding RSS feed URLs for any site, the YouTube RSS feed format, and Google News RSS feeds cover the other major platforms.
Either way, the Facebook-specific part of the problem is solved once you have a working feed URL. Everything after that is just WordPress. See the plans if you want Feed to Post and the advanced filtering, or grab the free plugin from WordPress.org if you just want to get a feed displayed and see how it looks.
