Every now and again, someone asks me about RSS. And I can almost guarantee that the question starts with: “Can we get this to automatically appear on the website?” Or: “Can we use it to populate our blog?” Well… Sort of. But RSS isn’t quite the magical content machine people sometimes imagine it to be.
So What Actually Is RSS?
RSS stands for Really Simple Syndication, and it’s essentially a machine-readable feed of content from a website. A blog can publish an RSS feed containing information about its latest posts. Another website or application can then read that feed and display the content e.g. Outlook. WordPress has supported RSS for years, and a standard WordPress website will generally have a feed available for its posts (Not the other way around..). It’s useful technology. It’s just not necessarily the technology you need.
“Can We Just Import Their News?”
This is where I start asking questions. What do you actually want to achieve? If you have a third-party organisation publishing useful information and you want to display a list of their latest articles on your website, then yes — RSS can be a perfectly sensible solution. WordPress even has an RSS block which can display content from an external feed, including titles, excerpts, authors and dates. But if what you actually mean is: “Can we take their content and make it look like it’s part of our website?” then we need to have a slightly bigger conversation. Because displaying somebody else’s content isn’t the same as creating your own.
What About A Recruitment Website?
This is one of the more legitimate uses I’ve been asked about. Imagine you’re a business or organisation that wants a Jobs section on its website (because you don’t want to set up or manage your own agency), but the actual vacancies are managed by a third-party recruitment platform. If that recruitment platform provides a properly configured RSS or other data feed, you may be able to display a list of current vacancies on your website. The third-party system remains the source of the information, while your website provides a convenient window into it. But—and it’s a fairly big but—the quality of the result depends on what the third-party system actually provides (and it usually costs money).
You can’t just wave an RSS wand and expect it to become a beautifully designed recruitment system. If you want logos, categories, locations, salary information, filters, application buttons and a gorgeous branded layout, you may need something considerably more sophisticated than RSS.
RSS Isn’t A Website Inside Your Website
This is another misconception I come across. Someone will describe an RSS feed as wanting “a site within a site”. Not really. You’re displaying selected information from another source. It’s more like putting a window into another system (Which sadly isn’t Google Search Compatible). And that distinction matters because you don’t necessarily control what comes through that window. If the third-party provider changes its feed, your display may change. If their feed breaks, your content may disappear. If they change the formatting, you may have to change yours. If they stop providing the feed altogether… Well. Guess who’s getting the phone call?
And What About Divi?
Yes, WordPress and Divi can work with RSS. WordPress has built-in RSS functionality for displaying external feeds, while Divi has its own modules and dynamic content tools for displaying content held within your WordPress site. But there’s an important distinction here. If I want to display my own blog posts, I don’t need RSS. Divi can already display my WordPress posts dynamically using its Blog module and related content functionality. RSS becomes interesting when we’re trying to bring information from somewhere else into the website. That’s when I start asking what the source system provides, what we’re allowed to display and what the finished result actually needs to look like.
And Please Don’t Use RSS As Your Blogging Strategy
This is probably my biggest bugbear. Someone discovers RSS and thinks: “Brilliant! We don’t need to write our own blog anymore.” No. Please don’t. If another organisation publishes a blog and you simply pull their feed onto your website, you’re not suddenly producing your own useful content. You’re displaying theirs. That’s very different. If you’re trying to improve your SEO, build authority and give customers useful information, creating original, relevant content about your own business is considerably more valuable than filling a page with somebody else’s headlines. RSS is a distribution mechanism. It isn’t a content strategy.
And No, It Isn’t A Shortcut To Social Media
There are services and plugins that can use RSS feeds as triggers for other actions, including social publishing. But again, that doesn’t mean it’s automatically a good idea. Automatically turning every blog post into a social media post can produce a very predictable stream of: “New blog post! Click here!” Congratulations. You’ve automated your social media into being boring. Good marketing still needs thought, context, personality and a reason for somebody to stop scrolling.
So When Is RSS Actually Useful?
I’d say RSS is useful when you have a genuine need to syndicate or display frequently changing information from another system. It’s particularly useful when the third-party source is the definitive place where the information is maintained and you simply want your website to reflect it.
But before installing a plugin and getting excited about automation, I’d ask:
- Where is the information coming from?
- Does it actually provide an RSS feed?
- What information does the feed contain?
- Are we allowed to display it?
- How often does it update?
- What happens if it breaks?
- And what do we actually want the finished thing to look like?
Those questions will save you an awful lot of messing about.
My Final Word
RSS isn’t dead. It’s still useful technology, particularly for moving structured, regularly updated information between systems. But it isn’t a replacement for blogging. It isn’t a substitute for social media. It isn’t an SEO strategy. And it certainly isn’t a button marked “Make My Website Automatically Interesting.” Sometimes RSS is exactly the right solution. Sometimes an API is better. Sometimes a proper integration is needed. And sometimes, after asking a few questions, we discover that the client doesn’t actually need any of them. Which is usually my favourite solution of all. The best technology is the technology that solves the actual problem — not the technology that happens to sound clever.

