Welcome to WebmasterWorld Guest from 54.166.236.238

Forum Moderators: incrediBILL & martinibuster

Switched To HTTPS and Ad RPM Drop

https and adsense

     
11:25 am on Jun 3, 2017 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month

joined:Dec 26, 2004
posts:1040
votes: 1


Hi everyone,

Have you switched to HTTPS and seen your Adsense RPM dropping? Adsense says it's because there are fewer ads in https. What do you do in this case?

thank you
11:45 am on June 3, 2017 (gmt 0)

Full Member

Top Contributors Of The Month

joined:Apr 20, 2017
posts: 214
votes: 34


Adsense says it's because there are fewer ads in https.

Where did you read it? Because, if I don't make mistake, it's been a while that all Adsense ads have to be available through HTTPS. Isn't it ? And I thought that third party ad networks also have to comply with this requirement.

Do you see error messages about your ads ? (insecure connection)
2:31 am on June 4, 2017 (gmt 0)

Full Member from NZ 

10+ Year Member

joined:July 28, 2003
posts: 308
votes: 6


A few months ago I noticed my ad revenues drop. My site was still largely HTTP only with HTTPS on pages that needed privacy/security (login, messages). I took the opportunity to update my Google DFP tags then and my revenue went up (AdSense as fallback) in most inventory. The new tags were HTTPS.

I moved my whole site to HTTPS now and revenue if nothing got better. The server sends header policies to make sure only HTTPS elements are loaded (no mixed content warnings) and I made a point of making sure every single piece of script was served over HTTPS.

Perhaps your site still has some old scripts that need updating? Perhaps the response headers are too strict and only allow some domains to load? You might have to look at this kinds of things.

"Not many HTTPS ads" is not an excuse. AdSense has been serving HTTPS ads for years and advertisers know well how to manage this.
5:00 am on June 4, 2017 (gmt 0)

Moderator from US 

WebmasterWorld Administrator keyplyr is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Sept 26, 2001
posts:9257
votes: 444


@Erku - take note of date stamps on the articles you read. That is very old, obsolete information.

As Peter_S said, the Adsense requirement is HTTPS. Switching your pages to HTTPS has no affect on the ads available.
2:02 am on June 5, 2017 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month

joined:Dec 26, 2004
posts:1040
votes: 1


Thank you everyone. How do I change the response heather? You said if they are too strict. How do I make the loose?
2:30 am on June 5, 2017 (gmt 0)

Full Member from NZ 

10+ Year Member

joined:July 28, 2003
posts: 308
votes: 6


Moving to HTTPS is about security so you shouldn't make it less strict, but check that your site sending the correct scripts, images, etc - all using HTTPS, not HTTP.

The best thing to do is to start with Developer Tools (in Chrome SHIFT CTRL I) and see if anything fails to load on your page. Work from there. If everything loads ok then it's something else.

Also are you correctly redirecting (301) from HTTP to HTTPS or just dropped HTTP responses? Have you added your HTTPS domain to Google Webmaster? Remember https://www.example.com is different than http://www.example.com.

There are so many things to check...



[edited by: not2easy at 2:51 am (utc) on Jun 5, 2017]
[edit reason] readability [/edit]

1:04 pm on June 5, 2017 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month

joined:Dec 26, 2004
posts:1040
votes: 1


Thank you. In Chrome I did SHIFT CTRL I and I get these errors, could any of them help to explain a problem? Are these problems for Google?

js__IORlmCN20PE_d29Tvqy7_3lkk5lU0D2abuQ2Lk9GH20__TLoh3Z20yJWOvlEeHtr4MTCieVhLzMR6wk4k1H4quYE__2FpXJZw9BgtD11Xr8WxTtnDfpxhLdQYOOEA7aRqpOFI.js:5 Uncaught TypeError: Cannot read property 'msie' of undefined
at HTMLDocument.<anonymous> (js__IORlmCN20PE_d29Tvqy7_3lkk5lU0D2abuQ2Lk9GH20__TLoh3Z20yJWOvlEeHtr4MTCieVhLzMR6wk4k1H4quYE__2FpXJZw9BgtD11Xr8WxTtnDfpxhLdQYOOEA7aRqpOFI.js:5)
at c (js__9IRGaezQnMstzTbtEOtNPo74JVoaJpmsJ2HoHir6O7I__fNOaUTs_R_1sYTmSTfef7kTW0rmoyfFXyTLYIWXh01k__2FpXJZw9BgtD11Xr8WxTtnDfpxhLdQYOOEA7aRqpOFI.js:1)
at Object.fireWith [as resolveWith] (js__9IRGaezQnMstzTbtEOtNPo74JVoaJpmsJ2HoHir6O7I__fNOaUTs_R_1sYTmSTfef7kTW0rmoyfFXyTLYIWXh01k__2FpXJZw9BgtD11Xr8WxTtnDfpxhLdQYOOEA7aRqpOFI.js:1)
at Function.ready (js__9IRGaezQnMstzTbtEOtNPo74JVoaJpmsJ2HoHir6O7I__fNOaUTs_R_1sYTmSTfef7kTW0rmoyfFXyTLYIWXh01k__2FpXJZw9BgtD11Xr8WxTtnDfpxhLdQYOOEA7aRqpOFI.js:1)
at HTMLDocument.q (js__9IRGaezQnMstzTbtEOtNPo74JVoaJpmsJ2HoHir6O7I__fNOaUTs_R_1sYTmSTfef7kTW0rmoyfFXyTLYIWXh01k__2FpXJZw9BgtD11Xr8WxTtnDfpxhLdQYOOEA7aRqpOFI.js:1)
ttdReferrerTrackerV2.min.js:1 Refused to set unsafe header "Content-length"
ReferrerTracker.send @ ttdReferrerTrackerV2.min.js:1
ttdReferrerTrackerV2.min.js:1 Refused to set unsafe header "Connection"
ReferrerTracker.send @ ttdReferrerTrackerV2.min.js:1