Skip to main content

FeedBurner BrowserFriendly Email Subscription Widget

Update: FeedBurner is effectively disabled and no longer supports BrowserFriendly widgets. This post is obsolete but left up for historical reference.

Google has disabled FeedBurner's email notification feature and with it Blogger’s FollowByEmail widget is going away. We have already shown how to replace a FeedBuner subscription widget on your website with FeedMail. However FeedBurner also supported a subscription widget in their BrowserFriendly feed preview.

In a few easy steps you can configure a replacement button using the FeedMail FeedBurner FlareUnit.

  1. Sign into FeedBurner
  2. Select the feed you wish to add an email subscription button to.
  3. Select "Optimize" from the navigation menu.
  4. Select the "BrowserFriendly" service.
  5. Click "More subscription options"

  6. Paste into the URL field.
  7. Click "Add"
  8. Check the new "Email" button that appears. You may need to re-expand "More subscription options".
  9. Click "Save" at the bottom of the page.

Now if you view your feed you should seen an email subscription button!


 If you have any questions check out our Feed Owner FAQ.


Popular posts from this blog

Delivery Delays to Gmail

In the past 48 hours Google has started delaying the delivery of some FeedMail notifications. This is currently affecting about 10% of messages to Gmail users. These notifications will be resent with a delay. We also speculate that some notifications will be marked as spam.   Update : As of 2023-05-09 this appears to be resolved. If You Are Affected If you use Gmail you may be affected by this. Notifications may be delayed or marked as spam. If your notifications are marked as spam you can create a filter to avoid this. Use "from:*" as the rule and select " Never send it to Spam". If your notifications are delayed we are unaware of any action that you can take. However marking notifications that ended up in your spam folder as "Not Spam" may help avoid future delays.  It does appear that these emails are eventually being accepted but we are unsure if that means that they are actually ending up in users' mailboxes (or even their spam folder

Updates to HTML Processing

Since its inception FeedMail has done processing on HTML content in feeds to ensure that it renders as expected in email form. At first this was fairly simple things like rewriting URLs to point to the correct location (many feeds use non-absolute URLs that won't work in email) but over time more complex transformations were added such as adding fallback content to media embeds without any. The full-text scraping feature requires even more complex processing as it requires stripping away most of the page and handling content that was designed for full-featured browsers. What changed? Recently FeedMail has migrated all HTML rewriting to use new infrastructure. This provides more flexibility and enabled new features (such as showing controls on all media embeds) and made our processing much more reliable. What does this mean to me? As a user you shouldn't see much difference. Overall the emails you receive should be better formatted but the difference will be subtle. Full-text sc

No body notification option.

Previously FeedMail provided two options for notification bodies: Content from the feed. Attempt to scrape content from the linked website. A third option is now available which includes no content in notifications. This can be useful to reduce email size or if you prefer reading articles in your browser anyways. This option is especially useful for digests. By setting subscriptions in a digest to "No Content" you can get a headlines-only digest. Or you can keep content for some short content like micro blogging but just get headlines for news sources with longer articles. Simply go to your subscription management page to change this setting. You can find a link at the bottom of each email notification.