Google AdSense HTTPS Support Still Not 100%

Google AdSense HTTPS Support

I am not a big fan of Google AdSense, but I do use it on a few of my authority niche sites. Unlike what some people think, it does generate money. Plain and simple, for Adsense to work, you simply need lots of traffic. It works well on what I call authority niche sites. I don’t waste time on small sites. I have noticed a big problem though recently and that is certain ad types in Google AdSense throwing up mixed content warnings. If you are debating migrating from HTTP to HTTPS just beware Google AdSense HTTPS support is still not 100%.

This is kind of ironic since Google is the one pushing everyone to HTTPS. However some of the problem is that advertisers in the network have not all jumped on board yet, meaning there isn’t as big of a pool of ads to choose from when running over HTTPS.

Update January 1st 2017: This still happens about 25% of the time. 

Setup AdSense for HTTPS

To run AdSense over HTTPS all you need to verify is that your src tag doesn’t have HTTP:// in it. The older AdSense codes used to hard code this. You shouldn’t have the protocol listed at all, and then it will determine the protocol based on the site. Example below.

<script async src="//"></script>

2 Unsupported Ad Types

A couple days ago I started noticing mixed content warnings on a couple of my sites and after some digging, discovered it was coming from Adsense. You will notice this especially in Firefox as you will see a yellow symbol over the lock in your address bar. I use Chrome primarily and unfortunately didn’t notice it sooner. Chrome simply removes the green padlock and doesn’t show anything, so sometimes it is easy to overlook mixed content warnings.

google adsense https mixed content warnings

After further testing back and forth, enabling and disabling options I narrowed it down to 2 current types of display ads that don’t support HTTPS yet. Why Adsense doesn’t have this in their documentation is beyond me. To disable these, go to “Allow & block ads “and click into the “Ad serving” tab.

google adsense ad serving

Then disable “Expandable ads” and “VPAID ads.” Both of these currently call many HTTP assets which throw up mixed content warnings. And to be frank, video ads are super annoying and I prefer to have these off anyways.

display ads https

I’m sure over time Google AdSense HTTPS support will improve greatly, but be aware of the limitations. I still chose to migrate my sites to HTTPS and didn’t really see any decrease in earnings or RPM. However I’m sure my sites are pulling from a smaller pool of advertisers, but there are still enough to fill every ad slot 100% of the time.

Still having problems? See our other post on how to block certain Google AdSense Ads.

Have you had any experiences lately with Google AdSense and HTTPS? If so, feel free to chat me up below!

Get More Stuff Like This

Marketing, WordPress, Blogging Tips, SEO and Reviews, once a week.

Thank you for subscribing.

Something went wrong.

20 thoughts on “Google AdSense HTTPS Support Still Not 100%”

  1. As a nice side effect of you disable these ads (and animation ads) the. You will see more even page losing time. Some Adsense ads download 5-10MB of stuff

    • Ya totally agree Vanessa. It is really a good thing. Trust me, I hate putting Adsense on websites since I care a lot about web performance. You won’t ever see Adsense on this blog. But on other high authority niche sites, sometimes it makes financial sense. Also, I have pretty much fine tuned them to be the fastest Adsense sites on the web since I am so OCD :)

    • Thanks, I forgot adblocker blocks anything with “adsense” or “adwords” in the file name. Had to rename the images lol. Thanks again for the heads up. They should be fixed now. I see some other PPC articles I need to fix too.

      • AdGuard also does the same, that’s the one I am using. And glad it was active. Otherwise, I wouldn’t even mention it. Glad to help, I didn’t know it blocks images with “adsense” or “adwords”.

        By the way, and don’t take me wrong, I prefer the blog you had under your name other than this one.

        P.S.: Couldn’t find sharing options other than the one Disqus provides…

        • Ya some people won’t like it. But for me this is looking at my future and a financial decision. Don’t worry, I merged my site + together which means I have more time now to blog! I will be able to write more content now all in one place.

          Also, you should see socialwarfare plugin floating bar on the left to share the post.

  2. Wow, what a coincidence I ran into your article. Just 5 mins prior I was considering possibly moving over to full HTTPS/2 and I do monetize with Adsense. Thanks for this, headache saver

    • Ya I can confirm that as of today, video ads still can’t be used over HTTPS. It has gotten better, but still have to disable certain ad types.

  3. Adsense HTTPS service has improved a lot over the years. Like I’m using Adsense over https since the mid 2014. Before going to https , Adsense used to generate good revenue. But after I moved to https, my cpc dropped tremendously. Why I did it? Well in Google I/O 2014 Google was talking about HTPS Everywhere, so I thought it’s a worth experiment. Anyways after a lot of research I saw that the reason of dropping cpc was in Google’s ad library the number of https compatible ads are very low and their cpc is too. Now as these image links depends upon the advertiser, at that time most ad agency was still not using https to serve the image and only using http.

    Fast forward to 2016, things are much better now. Https ad library also has almost all the ads http has. CPC is good too.

    So yes, Adsense over https is might not be 100% now, but it has come a long way. The problem is as per my knowledge goes whether or not the ad will contain https enabled content, that depends on the advertiser, and not all are using https.

    • Ya I definitely agree things are much better now. Much better then when I originally wrote this article. It still isn’t perfect, but glad to see improvements.

      And yes, it is up to advertisers to adopt it. If Google had their way, we would already be past this issue :)

  4. Great article! I migrated my site to https and now my bounce rate is to the roof (most of my traffic is on mobile and these errors are crashing a mobile’s browser). I am really furious that google who is pushing to https is giving the ads over http – shouldn’t they focus on getting this done the right way on their end? it is late 2016 here :) so still the problem exists. Coming back to the solution of this problem. What other advertiser are good? My traffic is mostly from brazil and the monetization of traffic is very very low in adsense (I have a solid 100k / mo traffic)

  5. My first thought was that it was ironic for AdSense to serve content that violates Google’s own philosophy on HTTPS, but I can’t say it surprises me. What does bug me is that Chrome is starting to show the security warning screens for non-secure sites and those with mixed content, which makes me and my brand look bad.

    Glad I found this article. Just turned those types of ads off and will now begin testing to see if that did the trick. Thanks, Brian.

  6. Thanks for the recent update with what you are seeing as of Jan 2017.
    Hope you continue to post updates so we can understand if and how this concern plays out over time.

  7. I’ve disabled those 2 ad types and Google still shows unsecured video ads on my website which throws mixed-content warnings all over my site, really pisses me off.

  8. Is this still an issue in Nov 2017? It looks like not using HTTPS is affecting my traffic, as they seem to be ratcheting up the ranking factor.

    As for the disconnect between Google Search and AdSense, it doesn’t surprise me. Google is an enormous corporation and not a monolith. Search and AdSense are completely different product groups. Publishers have always had to balance ad revenues vs. ranking and performance. For example, AdSense optimization tips instruct publishers to cram their websites with ads and related content. This will slow down your site and therefore affect ranking. It’s up to the publisher to find the right balance.

    From what I can see, few are complaining about revenue drops after migrating to https. Just curious what Brian and others have experience. I am planning on making the transition soon… It seems as though Chrome is getting pretty nasty about the non-secure messaging, and it will soon be implemented with a pop-up.

Leave a Comment