Skip to main content

Broken Feed Gadgets, From Google API Deprecation

Google makes changes to their software environment, constantly.

This week, they deprecated the Google Feed API. Unfortunately, many Blogger gadgets require that feature to display feed content, on our blogs.

This week, numerous reports about broken feeds, in various gadgets, are being seen, in Blogger Help Forum: Get Help with an Issue. The broken feeds are a direct result of the deprecated API.

Blogger Engineering is now aware of the problem - and is working hard to correct the cause of the problem.

This problem won't be fixed, in a one day effort.

The gadget update, which was started today after the API deprecation was identified as the cause of the reported problems, won't be finished in a one day project.

Engineers must first develop a replacement Blogger Feed API.

The Blogger Engineers have to first develop a replacement for the deprecated API - then they have to update each broken gadget.

Then, each broken gadget must be fixed, to use their API.

They will shortly be updating the gadgets that they know are broken - but it's always possible they might overlook one. They might even overlook the gadget that you depend upon, for your blog to provide content, for your readers. These are the currently identified problems.

  • Feed
  • Newsreel
  • Slideshow
  • Video Bar

We are collecting reports, from blog owners affected.

We have a Rollup Topic, in Blogger Help Forum: Get Help with an Issue, where we are collecting details from blog owners suffering from this change. If you're able to contribute, your details may be useful.

If you don't identify your problem, Blogger Engineering fixes the problem as they see it, and your problem remains unresolved, you'll be back here next week, asking why your problem is not solved.
(Update 12/3 14:00): Google has reactivated the Google Feed API, temporarily. All gadgets are returning to normal status.


MJB said…
"Google has reactivated the Google Feed API. All gadgets are returning to normal status." : Newsreel still does not work
Googman Editor said…
0600 12-04-2015

Chuck Croll said…

Thanks everybody for the feedback. I am reporting newsreel as a continued problem.
ITP said…
This is not first time when Google broke something that used to work fine.
When are you Googlers going to learn on your own previous mistakes?
It all started with horrid push to shove Google + down the throats of all users. Since then nothing ever works anymmore, and if something works it's just a matter of time it will be broken in one way or the other, because Google constantly "deprecate" this and that...
Be warned Googlers:
once more people realize your services cannot be trusted, Google itself will be deprecated.
MJB said…
Now Newsreel is OK


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: