AdSense for feeds now available directly in Blogger

October 30, 2009 on 5:45 pm | In Uncategorized | Comments Off
One of the things our publishers have always asked for are ways to make it even easer to configure their blogs to work with FeedBurner and AdSense for Feeds. We're happy to announce that Blogger users, with just a few clicks, are able to do both at the same time.

Yes, this year for Halloween, AdSense for feeds is putting on a Blogger costume and allowing all Blogger publishers to easily monetize your RSS and Atom feeds directly from the Blogger interface, in the same way you set up AdSense on your blog beforehand.

To set this up, go to Blogger and select the blog you wish to monetize on your Blogger Dashboard, and select "Monetize." This will give you some basic options for configuring ads, and if you already have connected your Blogger feed to FeedBurner, will confirm that the proper feed is being configured. AdSense for feeds will automatically pick the right ad sizes for your users, content, and end medium.



After setup, you will be able to view your AdSense reports (including feed revenue) directly from the Blogger Dashboard, as well as from your AdSense account. Additional feed management options for your feed and feed analytics will be available from http://feedburner.google.com.


A small yet noteworthy change to our item stats link serving

September 30, 2009 on 2:47 am | In Uncategorized | Comments Off
FeedBurner has been busy analyzing, publicizing, optimizing and monetizing your feeds since 2004, and in that time, we've seen our fair share of feed traffic. In fact, we see billions of hits from feed traffic per week, and we watch this data carefully for trends and opportunities to improve what we do in making sure your feed content is delivered as quickly as possible, as accurately as possible, no matter what its destination might be.

Today we are making an improvement that we think will serve our publishers better by making our service more compatible with search engines that crawl feeds.

When we started the service, one thing we were not sure of at the time was how the feed reading ecosystem would treat the links we rewrite in order to give you statistics on how many people click on your feed items.

For instance, on the previous post in this blog, we change the link in the feed item for "FeedBurner Terms of Service Update" from

http://adsenseforfeeds.blogspot.com/2009/08/feedburner-terms-of-service-update.html

to

http://feedproxy.google.com/~r/blogspot/MQiv/~3/Z8Es5QuvgEI/feedburner-terms-of-service-update.html

which sends the browser to that original URL, but allows us to first track the click.

As a technical detail, we rewrote these links with a code of "302 Temporary Redirect" which tells the browser or consuming service that the redirect is not permanent, and thus it would need to be read every time.

As of today we are changing this to be a "301 Permanent Redirect" because we've looked at the traffic enough to tell that there some benefit to changing this to a "301 Permanent Redirect" - in that some search engines that index the feeds themselves will consider these to be additional links that should be used in determining the popularity of your site. This is the same way that "URL shortener" services send traffic and get treated by search engines, so we feel that this is consistent with the way that content is distributed today. This update should not change the number of clicks that come to your site from your feed nor should it significantly affect the number of clicks FeedBurner tracks for you.

What do you need to do? Nothin'. Nada. Just keep burning your feeds from FeedBurner or your AdSense account in AdSense for feeds, and we will keep working hard to ensure your content is as accessible as possible – now, hopefully even more so.

FeedBurner Terms of Service Update

August 19, 2009 on 11:10 am | In Uncategorized | Comments Off As a natural conclusion to the process of migrating feedburner.com accounts to Google Accounts as previously described here, we have decided to sunset the legacy Feedburner Terms of Service. The Google Terms of Service will be the terms that apply to your use of Feedburner. These Google Terms of Service are the same terms that apply to many other Google products and services, including your Google Account.

As a reminder, the advertising portions of the service are now covered by the AdSense Terms and Conditions and the accompanying Google AdSense Program Policies.

Category Filtering beta now available for AdSense for feeds English-language ads

August 17, 2009 on 3:33 pm | In Uncategorized | Comments Off Like we announced on the more general Inside AdSense blog a couple weeks ago, we have extended our category filtering beta to English-language ads on the AdSense network, which we are happy to announce includes ads that appear in AdSense for feeds.

This feature allows to you filter ads in up to five categories such as Dating, Drugs and Supplements, Weight Loss, and Get Rich Quick. Your filters will be applied to English-language ads, no matter how they were targeted.

To have these settings take effect for your feeds, from Ad Review Center, make sure you select a Client-ID that starts with ca-feed-pub. Note that this allows you to select different categories for your feed than for your site, but also means you will need to select filters for both your feed and your site in order for filters to be applied to both these content types.


To see whether category filtering has been enabled for your location, sign in and visit the Ad Review Center, located under the 'AdSense Setup' tab. We're working on expanding this beta to additional languages and countries, and will be sure to announce any updates here on the blog. If you'd like to learn more about category filtering, please visit our Help Center.

What’s all the hubbub about PubSubHubbub?

July 10, 2009 on 6:42 pm | In Uncategorized | Comments Off One of the questions we get from publishers most often is "How do I make sure updates to my feed are delivered to feed readers as fast as possible?" We know this is important to our publishers' businesses and we are constantly making improvements to our back-end systems to minimize the time from when you publish a post to when it appears to subscribers in feed readers.

Recently there have been a lot of developments around the so-called "real-time" web. The promise of the real-time web is distributing new information as quickly as possible. This encourages users to engage in more active participation online and makes the web more dynamic than ever before. However, so far the real-time web has not been easily accessible by feed publishers using their existing infrastructure.

Today we're happy to announce initial support in FeedBurner for the PubSubHubbub protocol. 'Hubbub is an open specification in draft for web-scale publish and subscribe. The protocol can be used to transform any existing Atom and RSS feed on the web into a real-time stream. Best of all, it's open, free, and decentralized like the rest of what makes the web so great: No single organization controls the protocol or how it's used.

As of right now, burned feeds with the PingShot service enabled are automatically enhanced with the PubSubHubbub protocol. We'll add the required discovery elements to these feeds and notify a Google-run Hub, running on App Engine, of publish events. We also convert any pings we receive into 'Hubbub events. That means for many of our publishers out there, your existing feeds are available as real-time streams right now. Like, immediately. This very moment.

If you are a publisher and are not already using our PingShot service, turning it on is easy. From feedburner.google.com, visit the Publicize tab for your feed, select PingShot, and click the [Activate] button at the bottom of the page. From your AdSense account, go to Manage Ads, then click View Feed Stats link, and do the same thing. That's it.



If you manage a service that would like to receive updates to the millions of FeedBurner feeds that use this service as soon as possible, or just want to know more about the PubSubHubub protocol, we encourage you to check out our project on Google Code. There are open-source clients for Python, Perl, PHP, Ruby, and WordPress. We have an open-source reference implementation of a Hub built on Google App Engine. And there are other Hub implementations built and run by other companies. Please let us know what you think in the PubSubHubub Google Group!

Next Page »

Powered by WordPress with Pool theme design by Borja Fernandez.

Online Jewelry Shop - Provillus For Women - Edelstahlschmuck