Forum Moderators: martinibuster

Message Too Old, No Replies

Are IE6 Display Bugs Impacting Your AdSense Revenue?

         

martinibuster

7:19 am on Sep 24, 2009 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Between 12 to 20% of Internet users are still browsing on IE6, a browser that often does not render XHTML web pages well, particularly web pages based on popular blogging software. The result is that the ads and content are not appearing above the fold, if at all. This has the effect of alienating a significant amount of your site visitors.

Have you checked your website for IE6 compatibility? It could affect your AdSense earnings.

[edited by: martinibuster at 7:36 am (utc) on Sep. 24, 2009]

Pepito

10:50 pm on Sep 24, 2009 (gmt 0)

10+ Year Member



And a big part of those 20% are for corporative computers, that will not change it too easily, unfortunately. Because my new site is not working with IE6 and I missing those traffic.

martinibuster

11:00 pm on Sep 24, 2009 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



Don't give up! There is usually a solution to display bugs. For instance, there's a float bug that can be solved with a few simple tweaks [webmasterworld.com]. I know HTML purists are going to get upset at this, but sometimes changing the DocType to 4.0 Loose can cause it to start displaying right, but check it against all other major browsers because that can introduce other errors.

The major point here is that it's easy to forget that IE6 is still a major browser and you owe it to yourself to check what your site looks like on that browser because it could be the cause of depressed earnings.

Lame_Wolf

11:26 pm on Sep 24, 2009 (gmt 0)

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



It seems to me the problem is with AS not being capable of delivering ads compatible with a large percentage of browsers.

I've made sites using XHTML and had no problems. More likely errors in coding that's causing the problem.