Google Is Indexing Your Podcast’s RSS Feed


It appears Google is now more heavily displaying RSS feeds in Google results.

Let me begin by saying myself, nor SP (my co-host on Better Podcasting – a show I’m about to refer to) are in no way SEO experts. While we both have varying levels of experience making changes to help with the SEO of our sites, neither of us remotely claim to be experts. If you want to hear a short discussion on what this article is about to say, please check out Episode 81 of Better Podcasting – particular at the time code of 25:41. Ok, now that’s out of the way, let’s get to the rest of the article…

While there may be businesses that specify in SEO, to many, Google Search Engine Optimization remains a mystery. In fact, Google is constantly making changes, refining how they want results to be displayed to its users.


Podcast RSS SEO has long remained a hot topic, full of varying levels of debate. This was very apparent when a few months ago SP and I recorded an episode on the Pros and Cons of Self-Hosting your podcast on Better Podcasting (Episode 65) where during the show I made ONE very brief comment about potential SEO. Considering this was a very small portion of a lengthy episode, I was surprised to find the resistance that followed which even lead to a followup the next episode where we clarified the factors that we felt made it still a valid CONSIDERATION.

Whether it was because we had accidentally poured fuel on a smoldering fire, or it was because our senses were now heightened, what SP and I noticed after this episode was that there seemed to be multiple other people in the podcast industry discussing the concept of RSS feeds and their impact (or potentially lack thereof) on SEO. One that I found particularly interesting was an episode of Libsyn’s The Feed where host Rob Walch seemed to finally put to bed the topic by locating the the following quote from Google’s Webmaster Trends Analyst John Mueller.

…If you are looking for a ranking boost by having an RSS feed, that’s not going to happen. The RSS feed is really something we see as more of a technical help to crawl and index the content a bit better… There’s no direct ranking boost for the website itself.”

After a quick search I was able to locate that the quote was from a Google Webmaster Hangout on August 11, 2015. Truthfully, while at the time I had felt that the quote was taken out of context, I decided to instead give in to my ‘lazy side’ and just leave the whole RSS podcast SEO topic alone until a future time where it seemed necessary to re-open that can of worms.

Now is that time.

Recently my Better Podcasting co-host Stargate Pioneer and I both started to see more RSS feeds showing up in results in Google searches. My first indication of this actually came when I was trying to locate a specific episode of Better Podcasting. Given the terms Better and Podcasting are extremely generic, when I search for something to do with the show I always search in quotes – “Better Podcasting”. What surprised me was when I went to my second page of results, I found a direct link to an RSS feed for the show.

Searching for “Better Podcasting” showed the RSS feed on the second page.

While in the past I have in actuality been able to locate my RSS feeds in Google results, it often took getting very specific with my searches. For example, I would search for “Better Podcasting RSS Feed” or something like that. I also often found that while these would show up, the result would often be formatted slightly different than other entries on the same page (not always, but often). This time, however, my RSS feed showed up EXACTLY as any other search result – full text and all. I also found interesting that within the result was the Google drop down menu to view a cached version. This indicates that not only is Google showing this within the other results, it may also be treating it the same way as all other results since it appears to also be caching in the usual manner.

Of course, the analytical side of me was compelled to try other searches – after all, maybe this was a one off? The first show that came to my mind was friend of Better Podcasting’s Emily Prokop’s The Story Behind Podcast. Here I found that Google had now added to her sub-menu a link directly to her RSS feed.

The Story Behind Podcast displays the RSS feed link within the Google sub-menu.

I also decided to try something I knew to be something that had its name in a lot more places – Ask The Podcast Coach. Here I found the RSS feed also showing up in the results.

Ask the Podcast Coach showed the RSS feed relatively high in the results even with all of the other streaming services that have been tagged with their name.

Finally, I thought – let’s go big or go home – I searched for a single term, but one that I knew was a MASSIVE ENTITY: Nerdist. What was located on page 2? Yes, their RSS feed – hosted on libsyn itself. This was easily the most surprising to me as Nerdist is in no way small fish. For those not familiar, Nerdist is the brainchild of infamous Podcaster turned Talk/Game Show host Chris Hardwick. Searching for the simple term Nerdist, a name that has millions of results within Google, has their Libsyn-hosted RSS feed within the SECOND page on Google. This RSS feed fesult is found the among the likes of their Facebook, Twitter, IMDB and even reddit category. If I’m being honest, part of me had expected that I’d have to go hunting if I was going to locate the RSS feed in their results so needless to say, even as I write this article now, I’m still surprised it was located on the second page.

The well-know massive entity called Nerdist showed its Libsyn RSS on page 2.

Now, one of the most head scratching results that I received was when I searched for a former project of mine. I actually didn’t expect to see the RSS feed show up at all given the project is LONG DEAD. The search term I made was simple but one that I knew used to get a lot of results back when it was active – the phrase: Fanboy Buzz Podcast.

Searching for Fanboy Buzz Podcast showed the RSS feed above the website results.

As you’ll see in the screenshot, the RSS feed actually showed up as one of the top results – above even the website category itself. To me that is crazy because if I were someone looking for a podcast, I probably wouldn’t want to be taken to the RSS feed as one of the top suggestions.

I think it’s important to reiterate that while these results are easily showing up currently, a few months ago they were no where near this apparent. As mentioned, while I did find RSS feeds on Google results, sometimes phrasing had to be more specific. The concept of Google allegedly previously NOT displaying RSS feeds within search results is one of the long-standing arguments for those who feel RSS Feed specifics won’t impact SEO. Often the citation that Google doesn’t show the results of RSS feeds is followed by the speculation that this is because RSS feeds are code and it would be useless for readers (often referred to as “The sniff test”). Based on the details outlined above, it appears that Google has changed their algorithm in regard to RSS feeds and now are crawling and indexing them – more importantly displaying them among other usual results.

So what specifically changed? Last month we discussed on Better Podcasting how Google was now incorporating play-ability of podcasts right in to the Google Search App. Could it be to do with this? Perhaps? Or perhaps it could just be that Google recognized that now people sometimes are looking for the RSS feed to drop in to their podcatcher. Perhaps it could even be a trial that one day will disappear. Honestly, at this point I have no idea – as I mentioned at the first line of the article, we are not SEO experts. However, what I do know is that RSS feeds are showing up indexed, displayed as usual result and also are being cached – sometimes showing higher than the main website itself.

Will this affect you? Maybe yes, maybe no. For me personally, I’ve often found that many SEO experts indicate that more links to my website with relevant search terms help with ranking. Whether this is true or not, I’ve operated with this and in the past I’ve found that this has helped my site show up higher with certain terms that I place focus on. Ultimately though, seeing RSS feeds showing now showing up with other results does help me feel a bit better having the RSS on my site. After all, I’d rather that traffic and statistics be accounted for on my website than on someone else’s. In addition, I also have began taking a look at the top tags in my RSS feed. If someone happens to come across my RSS feed through Google, I’d like one of the top pieces of information found be a reference back to the site that they might actually be looking for.

Of course with all of that said, Google is a constantly changing entity and these results could be removed at any time. In any case, however, this shows that Google has the capability of (and is currently) crawling and indexing RSS feeds. As such, in my completely NON-EXPERT opinion (again, see that first paragraph), I think at this time it would be fair to consider your podcast’s RSS feed in the same manner as any other page of yours if you’re considering SEO modifications (whatever considerations those may be).

Note: In the screenshots above you’ll see I was searching Incognito Mode on Google Chrome using (I’m Canadian). Attached below are Private Window results from in Firefox as well as Incognito Mode results from This is just as a reference to show that different Google locales as well as different browsers show the RSS (you know, for if Google ever makes the change removing it – then I seem SLIGHTLY less crazy).

EDIT 2017/05/31 – 7:35pm PT – There has been some speculation that my location could possibly be the cause of this indexing, and admittedly I did not clearly address this in my article – I offer my sincere apologies. I think it’s important to clarify that prior to writing this article (and podcasting about it), I confirmed through various regions that I was able to recreate similar results. Just as all other regional differences that Google has, there was indeed some variance result positions; however, overall the results were pretty similar. The best example I have is the one you can find below where co-host Stargate Pioneer (who is located in the USA) has been kind enough to provide screenshots. As SP is using the continuous scroll in Google Chrome, there are multiple screen shots attached to provide reference on how many “pages” the results show up on. By comparison with my screenshots above, you will most definitely notice some variance, but overall, the results are pretty much the same. Thank you for reading my article and a special thanks to SP for providing these.

So You’re Afraid of Facebook Messenger Privacy? Look at these other app permissions…


Facebook has come under some intense scrutiny this past week with their drive to move their messaging component out of the main Facebook app. While I’m a firm believer that users should know what they’re getting into when they install apps, for many geeks such as myself it’s been clear all along that this recent move has been blown out of proportion.

If you’re note familiar with the controversy – the issue is that the Facebook Messenger app requires a lot of permission to install, and many people are worried with wording such as the following

  • “Allows the app to record audio with microphone. This permission allows the app to record audio at any time without your confirmation”
  • “Allows the app to call phone numbers without your intervention. This may result in unexpected charges or calls. Malicious apps may cost you money by making calls without your confirmation.”

Of course it’s very easy for the uneducated to blame Facebook on these terms and condition but what many don’t realize is that the referenced security warnings are actually standard Android permission verbiage.

Android operates differently than iOS when an app is installed. With Google’s Android all of the disclaimers/permissions are granted when an app is first installed; however, with Apple many of the permission requests are displayed later when a user actually tries to use the feature which requires the authorization. Now while Google’s verbiage can be perceived as scary, the fact of the matter is that many applications require these permissions but they don’t actually use them in a scary way. For example, let’s say you’re using any messenger that allows you to take a selfie and send it to your chat partner. Most messenger apps have a built in feature to simply access the camera, take the photo and attach it your conversation. If users did not grant the app permission to use the camera, how would it take the photo without exiting the app and taking the photo separately? That seems like an inconvenience. Now you may be concerned about apps reading your contact and their phone numbers, right? Well one of the greatest features of different messengers is the ability to easily add contacts to these apps by matching up their phone numbers to their messenger profile. If the app did not have permission to access your contacts it would be impossible to locate your friends without manual input. So perhaps by now you understand those two points but are saying “Stephen, isn’t it creepy that Facebook can listen and record my audio?” Have you noticed that little grey microphone button at the bottom of Facebook Messenger? Yes, I’m referring to the one that allows you to send an audio message to your chat partner. How exactly is the app going to record your voice-messenger if it doesn’t have permission to use your microphone? Simple – it can’t.

Now while I’m not making any guarantees that Facebook couldn’t (in theory) use the permissions for their own gain, the reality is that this standard permission wording is found on many applications – may of which you may even have installed right now. Every day people sign up for services and agree to terms that they don’t read and the same goes for installing apps on your device and not reading the permissions. If you don’t believe me I’ve compiled some not-so-pretty (my apologies) screenshots of a variety of popular apps and the permissions they require. If you look through the photos you’ll see a lot of the same permissions that Facebook Messenger requires.

Once again I do always think that people should be aware what they’re agreeing to when they use services but I also do think that that in this instance with Facebook things have been greatly blown out of proportion because of some media sites running the story with the “big brother” overtone. While its ultimately up to you whether or not you install the app – I’m won’t be uninstalling my Facebook Messenger anytime soon.

Latest Comixology App Update Brings Changes


Back in episode episode 42 of the Gonna Podcast we told you all about Amazon’s acquisition of Comixology.  It was theorized on the show this would change the way in which comics were purchased on iOS devices going forward.

Turns out that prediction was right as Comixology has updated the iOS app to no longer allowing in-app purchasing of books.  Presumably this is to escape the 30% cut that Apple takes off of in-app purchases.  For more information check out the Gonna Geek Reaction below.

Google+ Automatic Photo Backup / Paranoia


Google Auto BackupI was recently making changes to my Google account on my Nexus 7 when I came across an option to “Auto Backup” my photos. When I saw this feature my gut reaction was “Hell no!” and to reach for the uncheck button – but then I realized, why?

While I’ve always been an overly cautious user I do remember a time where I’d jump on the opportunity to backup important data such as my photos (especially for free) but for some reason now I’m filled with paranoia. Although I currently use a variety of Google products (and recognize that Google often mines the data — see our lengthy discussion a few podcasts back) for some reason when it comes to Photos I’ve found it hard to get onboard with an auto-sync service. I was wondering why I had such a fear even though I have nothing to hide (sorry folks, my camera roll is pretty bland) and then it occurred to me where this stemmed from – Facebook.

While privacy settings on Facebook for photos used to be straight forward and clear, over the years the privacy lines seem to becoming more grey rather than black and white. Now it feels as if users should assume that if they upload a photo the likelihood is that the world will probably end up seeing it. While Google+ has had its share of privacy concerns, one thing they’ve always done right is the ability to control who sees what (circles). After having this realization I went back and looked at the configuration screen for the auto backup service and I noticed that in plain text the configuration says “Backups are for your eyes only.” I was shocked to discover that my paranoia with photos has become so bad that I missed this straight forward disclaimer. Do I believe for a second that Google doesn’t access these? Not at all, but the reality is that I’m ok with “the man” seeing my photos; however, that doesn’t mean that I necessarily want my contacts to. I decided to enable the service… at least on my Nexus 7.

As for the auto backup service experience itself – so far I’m enjoying it. The service is simple, updates quickly and most importantly it works. After letting my tablet upload my photos I found that new photos were backed up within a minute or two of their capture. The photos are easy to view through Google Plus by simply clicking on the “Photos” section via web or app. I’ve also discovered that when a photo is deleted from the device it remains backed up which is GREAT if you accidentally get click happy when clearing out your camera roll. Furthermore if I do opt to share a photo it’s as simple as clicking the Share button and filling out the appropriate fields. Users do get 15GB of storage for “full size” backups but users can purchase more space if they opt to.

Nexus 5 Released – Pretty much what everyone guessed…


Yesterday Google finally announced the latest product to be added to their popular Nexus product line – the Nexus 5. The highly anticipated (and leaked) device is on sale in the Google Play store for $349 USD for a 16GB Model and $399 USD for a 32GB Model.

As anticipated (ok I’ll stop saying this as it would be applicable for most of this article), the device will be the first to feature Android 4.4, KitKat.
The 5 inch phone (4.95″ to be exact) features a 1920 x 1080 display (at 445 ppi) with Corning Gorilla Glass 3. The front facing camera is 1.3MP with 8 megapixels on the rear – featuring Optical Image Stabilization.

Google Nexus 5

Google Nexus 5

Like it’s predecessor the Nexus 4, the Nexus 5 features Wireless Charging built-in (a great feature to help save excess wear on that microUSB port). The battery is 2300 mAh giving approximately 17 hours talk time and 300 hours stand by time.

Although not the most powerful CPU on the market, the Nexus 5 still boasts an impressive Snapdragon 800 2.26GHz CPU paired along with 2GB of RAM.

One of the biggest gripes with the Nexus 4 was the lack of LTE in a time that LTE was making a huge push in North America. Don’t worry folks, Google has equipped the Nexus 5 with LTE Bands that should cover the majority of the LTE worldwide.

The connectivity has remained fairly similar to other Nexus devices with Bluetooth 4.0, Dual-band Wi-Fi and NFC all on board. There’s also an abundance of features found on most phones such as GPS, Gyroscope, Compass, etc.

The Nexus 5 weighs in at 4.8oz and dimensions are 69.17mm wide, by 8.59mm deep and 137.85mm tall.

Availability of the device is reported as mixed, with my Canadian Google Play Store showing sold out, but my colleagues south of the border have reported the device still available.

Nexus 5 Listed in Google Play Store…


… or at least it was for a brief period. The highly rumored Google Nexus 5 has had yet another leak courtesy of, well, Google themselves.

Google Nexus 5 Play Store

The listing seen for the presumed Nexus 5 in the Google Play Store

Last night reports started coming from multiple media outlets that when certain users went to the devices section of Google’s Play Store that instead of seeing the Nexus 4 they saw the Nexus 5. While this did affect a good amount of users, certain people (such as myself) never saw this. Don’t worry if you’re one of the few that didn’t get this listing – you didn’t miss out on much. It turns out that while the picture (above) was listed, the link did not go anywhere.

Reports are that the device was listed as $349 for a 16GB model. Although Google has yet to officially announce the device, this latest leak seems to seal the deal that we’ll be seeing a device release from Google soon.

Google Nexus 5 Rumor Round Up


For months I’ve been eagerly awaiting the rumored Nexus 5 phone to decide whether or not I’ll be making the final jump to Android (I currently own a Nexus 7 tablet but still have an iPhone 4S). There have been many rumors over the last several months so I thought I’d create an article to summarize the majority of what’s being theorized. Keep in mind that Google has yet to even confirm that the device is being worked on so everything below is 100% complete speculation.

The latest rumor about the Nexus 5 came just yesterday when AndroidSAS reported that the 30th of October has become the selected launch date for the device. It’s expected that Google will also launch an updated Nexus 10.

Nexus 5 Unbranded

Apparently an early version of the rumored Nexus 5 – unbranded.

Google has been known for launching devices with the latest and greatest version of Android. With Android 4.4. KitKat being announced recently it seems highly like that the Nexus 5 will be the debut device for the OS. Although 4.4 has been kept under wraps, 9to5 posted apparent leaked photos showing redesigned phone and messaging apps.

Android 4.4 KitKat New Messaging App Android 4.4 KitKat New Phone App

On September 28 2013 MYCE reported that they discovered a long file of Android Key Lime Pie (to be officially called KitKat) running on the alleged Nexus 5. The log was supposed 10MB containing more than 133,000 lines.

The log apparently showed some of the specifications of the device including a 5-inch (4.97inch) display (full HD resolution – 442ppi), a quad-core Snapdragon 800 processor, 2GB of RAM and 16GB of storage. The phone this log was pulled from has an 8-megapixel rear facing camera and a 1.2 megapixel front facing camera. Also present was Bluetooth 4.0, NFC, Wi-Fi a/b/g/n/ac, GPS and of course the long-rumored LTE for North American bands.

A recent promotional video for KitKat showed someone with an unknown Nexus device.

A recent promotional video for Android 4.4 KitKat showed someone with an unknown Nexus device.

A user named Weespeed on the MacRumours forum recently posted the image below and some early impressions of the device. Weespeed claimed that the rear cover has a similar feel to the new Nexus 7 tablet and does feel smaller than LG’s G2 smartphone. The user claimed that the display was just ‘Ok’ and didn’t impress them as much as Samsung’s Galaxy Note 3 ‘phablet’.

Nexus 5 Rear

While rumors so far (ironically including this very post) have referred to the device as the Nexus 5, the official release name has been wildly debated. While clearly it appears Google is trying to increase the screen size on their new phone toward the 5 inch mark, as mentioned the latest spec rumors indicate that the display is actually 4.97 inches. Google did keep the Nexus 7 name when they updated their 7 inch tablet so the possibility remains Google could keep the name as Nexus 4.

Nexus 5 In the Wild

One of the Nexus 4’s biggest appeals was that for a relatively low price point users could purchase an unlocked contract-free Android smartphone. The rumor is that Google wants to continue to drive sales so they are hoping to keep the price low. With several new speculated features its expected that there will be an increase to the Nexus 4’s base $299 US price tag.

As mentioned everything seen here is all speculation at this point, but we want to know – are you interested in the Nexus 5?

Why Chromecast Should Come To Canada Soon


Google ChromecastSince its announcement in June, Google’s Chromecast has been making waves across the internet. While many people originally purchased the device thinking of it as a $35 toy, the device has quickly made its way into many people’s daily activities. As a huge supporter of tech that makes it easy for users to stream content to their entertainment systems, I was ready to hand down my money the day of the announcement – until I discovered the item was US only.

Of course, Google isn’t the first company to neglect their northern neighbors with the release of a product, for years companies have often made products available in the US first, and set a target release date for us Canadians (which many times gets pushed back due to popularity in the US being larger than anticipated). With that said, I think Google is missing the boat by not providing a Canadian option immediately at the launch of the device. Often when US companies launch media devices they often cite the Canadian market delays on licensing agreement issues – this shouldn’t be the case for the Chromecast. Currently the main supported features are the ability to play music/movies via Android devices and YouTube and Netflix playback support. All of these features are available in Canada so I’m surprised to see the device isn’t supported here yet.

In Canada our country has easily been keeping up with US trend to “cut the cord” or find alternate ways of delivering content to consumers – in some cases we’ve been ahead of the game. For example, over the last 6-12 months Microsoft has been making news that they’ve been supporting certain television providers in the US support to use the Xbox 360 as a set top box – in Canada there has been at least one company that I know of which has been doing this for much longer. This Canadian company even offered a promotion many years ago to include an Xbox 360 as part of a contract bundle to encourage exploration of this method. Personally I’ve noticed a lot of non-tech friends and co-workers following this trend by purchasing Apple TVs solely for the purpose of consuming Netflix – the Apple TV has a price of $109. With such a low price point it stands to reason that the Chromecast would be a viable and popular alternative for many users who just want to hook up Netflix to their TV.

Another reason Google should deliver the Chromecast to Canada soon is one that pains me to say it, but I will – us Canadians are willing to pay more. The reality is that many things in Canada cost more. While the immediate response when we question our price difference is that our dollar is worth less than USD, there have been many points where CAD has been worth more than USD. Even during these times prices are rarely adjusted to reflect the difference and we’re stuck paying more than the US counterpart. I think Chromecast has been much more of an initial success than Google originally planned, and one has to imagine their low price point has left the profit margin pretty tight. In turn, Google could make up for some of the (presumed) narrow margin by charging a few bucks more in Canada.

My final reason why I think Google should get moving on the Canadian release of Chromecast is simple – I might actually buy an Android phone. Often I find myself in a situation with my Dad, his girlfriend and my wife huddling around one of our TVs wanting to show off a funny YouTube video we have bookmarked on our phone. My father currently is the only one out of us which have an Android device and while it’s simple for the rest of us to quickly pull up the bookmark and send it to the TV via the Apple TV, he finds the process difficult, often getting one of us iPhone users to do it for him. In my opinion the Chromecast does the media streaming through a far superior method – rather than tying up the mobile device, it simple directs the Chromecast to the appropriate video URL. Smart.

If Google can get the Chromecast to The Great White North soon for a price not grossly off the US counterpart, it’s definitely going to be one of my must-have items. Ever since my pal Chris Ferrell wrote about his initial experience with the Chromecast I’ve been severely jealous of him.

Where’s All My Chromecast Apps?



There was a lot of buzz surrounding the release of Google’s $35 streaming stick the Chromecast.  At launch it worked with apps like YouTube, Netflix, and Google music (on Android).  The user experience with this apps was generally pretty good and received positive reviews.  Personally, I can attest to the fact that the YouTube integration in Chromecast is fantastic and always easy to use.

Google had said they would make a Chromecast SDK available so that developers could interface their applications with.  Companies such as Revision 3 and HBO had stated their intention to update their apps to make use of Chromecast.  Tech blogs had also said Chromecast compatible apps from Redbox Instant and Vimeo were also pending.

However, we have yet to see new versions of these apps come out supporting the device.  Don’t worry, they are still coming we may just have to wait awhile.  The Chromecast SDK is still in beta and Google has asked that it not be used in production apps, but instead in testing and early development efforts.  Once the floodgates open I’m guessing the floodgates will open and there will be many updated apps that are Chromecast compatible.

In the meantime Google has released the Chromecast app for iOS.  It makes setup using an iOS device much easier.  When I setup my Chromecast, I used the Chrome browser and had little trouble with setup, but the new app is incredibly simple.  If you’re a new owner of a Chromecast and own an iOS device download the app and use it for setup.  Once the setup is complete the app is then used to manage your Chromecast’s settings.

Stay tuned to Gonna Geek, as soon as we hear anything new on Chromecast apps we’ll let you know!

Introducing Android 4.4 Kit Kat



Google has announced that the newest version of Android is not in fact named Key Lime Pie, but instead has been named Kit Kat.  Google has long named their Android builds after sweets and candies, but this it the first time an Android build has been named after a name brand candy.

At first, I assumed this was a cash grab by both Google and Nestle.  However, both companies have stated that no money changed hands.  John Langerling, the director of Android global partnerships, told the BBC that the deal between Nestle and Googl is ‘not a money-changing-hand kind of deal.’  The pick of Kit Kat for this version of Android was dreamed up by the developers in part because one of the leads is a fan of the candy bar.

Langerling stated that the Android team had no idea who actually owned Kit Kat and that he cold called the switchboard of Nestle’s advertising agency back in November to suggest the naming idea.  The next day there was a conference call between the two companies to discuss the idea and 24 hours a deal in place.

What’s astounding to me is that this deal was in place back in November and in that time branding materials were created and about 50 million Kit Kat bars with the Android logo and none of this leaked to the media.  In a day where any Samsung or Apple phone rumors leak out this was kept quiet and that astounds me.

If you want one of the Kit Kat candy bars featuring the Android branding check out your local grocery store.  The candy bars are out now and include a chance to win a Nexus 7 or Google Play giftcard.