Skip to main content

Atom / RSS Feeds Are Empty

This week, we have a few complaints about Atom / RSS feeds, in various blogs.
When I republish my blogs to my FTP server, the atom.xml and rss.xml files are empty.
I published a new post, and feed file size is 0. Tried republishing template/settings and deleting the rss.xml file, but it still publishes with a 0 file size.
I recently selected "Publish Entire Blog" from the dashboard settings and now both the rss.xml and atom.xml files are zero bytes. I have tried republishing selected entries and the entire blog again but to no avail, the feeds are still blank.

We also had one very insightful and interesting post.
I see the file here:
but it is at 0 in my FTP here:
and here

This observation is very useful. It points out that the problem isn't the feed, it's the involvement of FTP Publishing. I verified the observation - "" isn't empty, though "" is empty. Other blogs, given the actual blog URL, will help us verify this observation.

If your blog is suffering from this problem, can you please find a thread in Blogger Help Group: Publishing Trouble or Something Is Broken (there are several threads, in each forum, take your pick), and provide details about your problem.
  • What's the URL of the blog? (If the blog has multiple URLs, this could be very important).
  • What's the URL of the problem feed?
  • Is the blog published to BlogSpot, to Google (as a custom domain), or to an external server (using FTP publishing)?
  • Is the feed published only to Blogger / BlogSpot (native Blogger feed), or is it redirected (FeedBurner et al)?
  • When did you first observe the problem?
  • When did you last not observe the problem?
  • If the blog uses FTP publishing, can you look inside each folder below the root, for an unexpected "atom.xml" / "rss.xml" file?
  • If the blog uses FTP publishing, can you please provide all relevant FTP settings?

The blog that you save may be your own, if you can help us out.

(Update 3/28 06:00): It appears that, possibly as part of some changes to Blogger yesterday, this problem has resurfaced.

(Update 3/14 19:00): We are seeing multiple reports that the problem appears to be resolved.
I was able to republish my index earlier this evening and again just now and both files are non-empty.

>> Top


C. Max Magee said…
Thanks for working on this issue. Is there anywhere we can go to keep track of progress on fixing this? This is a major problem and I'd like to keep tabs on it until it is fixed. Thanks!
Chuck said…

You're here, and this is my blog. As soon as I know an update, I'll update the blog.

If you Follow or otherwise watch the blog, you'll know what I know.

I'm trying to train Blogger Support, but so far I wouldn't bet money that they will post updates where you can see them.
Weirdgrrl said…
I am one of the many people affected by this FTP/Feeds issue, so thank you for posting this. And I will definitely be checking back for updates!
Louis Gray said…
I am impacted by this as well. There are no new files created, but the ones that are there are zeroed out.
Rob said…
I posted this same info on the Blogger Help Group but I thought I'd add it here as well...

I'm seeing the same feed issue on our FTP published Classic Blogger blog. We're hosted at The index.html and archive files (, for example ) are receiving new content that I publish, but the xml feeds files are zeroed out. When I try republishing, everything seems to work as expected - no errors - and the date/time stamp on the xml files do update, indicating that they are being rewritten to. This seems to have started on Thursday, March 12th tho I'm not sure at what time.

(Commenting on my blog does not seem to be affected by this issue.)

#FTP Server
#Blog URL
#FTP Path htdocs/
#Blog Filename index.html
#Feed Filename 2d_atomfeed.xml

and on the Site Feed Page:

#Site Feed URL
#Site Feed Filrename 2d_atomfeed.xml
#Site Feed Path /htdocs

Rob O.
Hi! I'm the one, from Italy, who wrote:
I see the file here:
but it is at 0 in my FTP here:
and here

Now I give you other data, I hope it could be useful for you to understand what went wrong with Blogger:

feed url:

name of file feed atom.xml
feed path: I did not write anything - I did not find instructions about it... but it worked all fine until a few days ago. What sould I have to write in there?
Amy Ridenour said…
I just posted on Blogger Help/Something is Broken, with all the info you suggested. Tried to repost it here in case it could be helpful, but because my post had tags in it, I wasn't allowed to. If anyone would find it useful you can find it there by searching under my name there, which is AmyR.

Thanks for running this blog. It is very helpful to know others are going through the same problem, even though we have not yet found a fix.
Rob said…
Seems to be working again! Let's cross our fingers that it stays up!

Thanks for being a clearinghouse for these problems, Chuck!
Anonymous said…
Uh oh. Looks like this problem is back again! I just published around 11:45pm PDT, and now my feeds are empty again. I realized it when I tried to leave a comment on another blog and CommentLuv couldn't find my feed. Sure enough!

My blog is and I publish via FTP. Have you heard anything else about it this weekend?
Russell Blanc said…
I too am having this problem.
wasi620 said…
Thanks for the information

Popular posts from this blog

Stats Components Are Significant, In Their Own Context

One popular Stats related accessory, which displays pageview information to the public, is the "Popular Posts" gadget.

Popular Posts identifies from 1 to 10 of the most popular posts in the blog, by comparing Stats pageview counts. Optional parts of the display of each post are a snippet of text, and an ever popular thumbnail photo.

Like many Stats features, blog owners have found imaginative uses for "Popular Posts" - and overlook the limitations of the gadget. Both the dynamic nature of Stats, and the timing of the various pageview count recalculations, create confusion, when Popular Posts is examined.

Help! I Can't See My Blog!

I just posted to my blog, so I know that it's there. I can tell others are looking at it. But I can't see it.

Well, the good news is you don't have a blog hijack or other calamity. Your blog is not gone.

Apparently, some ISPs are blocking *, or maybe have network configuration or infrastructure problems. You can access or you can access, but you can't access, or

You can't access them directly, that is. If you can access any free, anonymous proxy servers, though, you may be able to access your blog.

Note: You can use PKBlogs with the URL pre packaged. Here is the address of this post (with gratuitous line breaks to prevent the old post sidebar alignment problem):

And an additional URL, to provide to those suffering from this problem, would be the WordPress version of this post: