Short answer: A feed built from a web page is only as stable as the page, but RSS Feed Creator is designed to survive ordinary redesigns. It detects the list of items again on every refresh instead of storing fixed rules, so many layout changes pass unnoticed. If an update finds no items at all, the last good version of the feed stays in place and the management page tells you what happened. When a page changes so much that detection cannot follow, you check the preview of the new page and point the feed at it.
Why layout changes matter for page-based feeds
A feed made from a real RSS or Atom file is stable, because the website publishes it on purpose. A feed made from an ordinary page depends on how that page is built. If the site redesigns its blog, the list of cards may get new markup, a new address or a different pattern of pagination. Tools that rely on fixed selectors, such as “the third div with class post”, break at once. People who have run their own scrapers know the pain: it is usually discovered weeks later, when someone notices that nothing new has arrived.
RSS Feed Creator avoids the fixed-selector trap. As described in how RSS Feed Creator finds items on pages without RSS, it works from patterns that nearly every list page shares: an existing feed, article data in JSON-LD, or a block that repeats with a title, a link, an image and a summary. Because those patterns survive most redesigns, so do the feeds.
Re-detection on every refresh
Every time a feed is refreshed, the tool reads the page again and finds the list again, as if it were seeing it for the first time. There is no stored recipe that can go out of date. If the blog moves from a three-column grid to a single column, the repeated block is still a repeated block, and the items are found as before. If the site adds a “featured” strip above the list, the detection still prefers the group that repeats most.
The feed refreshes every 3 hours on the free plan and every 30 minutes on paid plans, and an out-of-date feed is also refreshed when it is read. So the day after a redesign, the feed is already built from the new page. Most of the time you will notice nothing at all, which is what you want from a tool that runs by itself.
When an update finds nothing
Sometimes detection does fail: the new layout draws its list with scripts, the section moved to another address, or the website is down. What the feed does next is the important part. If an update finds no items and the feed already had a stored version, the stored version stays. Readers and tools that fetch the feed keep getting the last good items rather than an empty feed, which could cause unwanted effects such as a posting tool seeing nothing or a reader marking everything as gone.
The management page then shows a line that begins with “Last update”, saying that no items were found at the last update and that the previous version is shown. If the website answered with an error, you see which one, for example that the page returned HTTP 404 or 403. This is the place to look first when a feed seems quiet. How the update cycle works is covered in how often RSS Feed Creator refreshes your feed.
Signs that a layout change hit your feed
Not every failure produces an error. Watch for these signs on the management page:
- The item count drops. A feed that held 20 items and now holds 4 has probably found only part of the list.
- The latest items look wrong. Menu entries, “related posts” or category names instead of articles mean a different block was chosen.
- Titles are cut or generic. Words like “Read more” instead of headlines suggest the title element changed.
- Pictures disappeared. The new design may load images in a way that the page does not expose to a simple reader.
- The update time is old and the line “Last update” has an error. The page itself is not reachable.
It takes a minute to look. If you rely on a feed for work, make it a habit to open the page of your most important feeds once a month.
How to repair a feed
Repair is quick because the preview is free and creates nothing. Follow this order:
- Open the source page in a browser. Is the list still there, and at the same address? If the section has moved, note the new address.
- Preview the address. Paste it into the start form and look at the cards, exactly as in the RSS Feed Creator preview. If the preview is clean, the page can be read.
- Check for a feed. Redesigns sometimes add an official feed. The preview says so when the page announces one.
- Update the source. On a paid plan, add the new address on the management page with “Merge another page or feed”, then remove the old one with the cross next to it. On the free plan a feed has a single source, so create a new feed for the new address and use its address in your reader.
Because filters and rules are set per feed, a new feed on the free plan needs them entered again. It is worth writing your include and exclude words in a note so that you can copy them back in seconds.
One more thing to check after a repair is the date order. When the new page lists items in a different order, for example oldest first, the first items you see may not be the newest. Look at the dates in the latest items on the management page and, if the order is odd, try the section address one level up, which often lists items in the normal newest-first order. A repaired feed that looks right in the preview and on the management page will keep working at the next refresh.
Making feeds more robust from the start
Some sources are inherently more stable than others. When you have a choice, prefer them:
- An official feed. If the site publishes one, use it as the source. RSS Feed Creator reads RSS and Atom directly, and you can still filter or merge it.
- Pages with structured article data. Sites that describe their articles in JSON-LD change their visible design more often than their data.
- Section pages, not home pages. A section list is simpler and changes less than a home page full of different strips.
- Pages with plain HTML lists. Lists drawn by scripts after the page opens are the most fragile.
Keeping a second source for something important also helps, for example both a blog page and a newsletter archive. On a paid plan you can merge them, and an item that appears in both is kept once.
What you can expect, honestly
No tool that reads pages from the outside can promise that every redesign will be survived. A site can move its content behind a login, switch to an application that shows nothing until scripts run, or block automated readers. In those cases the feed cannot go on, and the honest answer is that you need another source. What RSS Feed Creator does promise is the practical part: it looks again at every refresh, it never replaces a good feed with an empty one, and it tells you what it found.
If you operate the website that is being read, you can make life easier for everybody who follows it. Publish a feed, keep a clean sitemap and mark up your articles with structured data. Then your pages work in every reader and tool, whatever the design looks like this year.
Plans and limits
All of this works on every plan. The free plan allows one source per feed, up to 20 items and a 3-hour refresh. The PostRSS add-on at €5 per month allows 10 feeds with up to 100 items, merging of up to 10 sources and a 30-minute refresh, which makes swapping a changed source easy. The details are on the pricing page.
Related reading
- How to Monitor Your Own RSS Feed: Uptime and Freshness Checks
- How to Find and Remove Dead RSS Feeds from Your Reader
- How JSON-LD Structured Data Helps Turn Pages into Feeds
The bottom line
A page layout change is not the end of a feed. RSS Feed Creator re-detects the list at every refresh, keeps the last good version when an update finds nothing and shows the reason on the management page. When a page really changes beyond recognition, a free preview and a new source repair the feed in a few minutes.
BUJ
Will my feed go empty if the website is redesigned?
No. If an update finds no items and the feed already had a stored version, the previous version stays in place.
How do I know that something went wrong?
The management page shows the item count, the update time and a line beginning with “Last update” that describes the problem.
Do I need to re-create the feed after every redesign?
Usually not. The list is detected again at every refresh, so most redesigns pass unnoticed.
Can I change the source of an existing feed?
On paid plans you can add a new source and remove the old one. On the free plan a feed has one source, so create a new feed for the new address.
Which sources are the most stable?
An official RSS or Atom feed is the most stable, followed by pages that publish structured article data and plain HTML section lists.


