Welcome to WebmasterWorld Guest from 220.127.116.11
and that eliminates the IE message but then I get another message in Firefox that warns about mismatching domains for google.com (vs. googlesyndication.com). Has anyone else ran into this problem? What would be the best solution? Thanks.
IMHO Google can easily solve the issue by providing https-specific code and by getting a certificate for the googlesyndication domain. That would cost around $100 a year.
There's a page in the FAQ that inidcates that they are aware of the problem: [google.com...]
When I search for 'adsense' I see that they've indexed their own https-pages
Yes, but these pages use SSL without a password. Webapp wants to use AdSense ads only after the user logs in to the site. As the mediabot does not know the user password, it will only see the URL. AdSense will show ads based on the theme of the public available pages of the site or the URL.
- Your web pages are behind a login.
At this time, pages that require a login can not be easily visited by our crawlers. Additionally, since these types of pages are not easily visited for approval and it is difficult for our AdSense specialists to verify that pages behind a log in follow Google AdSense policies, we are unable to offer support for these pages.
It's quite odd.
It starts saying "it is difficult ... to verify that pages behind a log in follow Google AdSense policies" and one would expect them to say it's not allowed, but then it simply goes on with "we are unable to offer support for these pages"
better ask adsense-support