adsense conflicting with existing site javascript?

google says mis-targeting that started last month is due to site js

[ypsites]

Hello,

I publish a site about weddings; it's had adsense for a couple years now, and javascript pulldown menus for about a year.

Last month, all the adsense ads started being mistargeted -- more specifically, technology ads (C++, .NET programming, etc) and ONLY technology ads started appearing on the pages of the (wedding) site. (About 500 pages.)

Google says the js on our site is to blame ("it conflicts with adsense code"), but we're using pretty standard dropdown menus, and they were working fine with AdSense until last month.

Anyone else seeing this? If so, have you found a workaround to fix your pulldown menus (or other js on your site)?

Any help appreciated ... thanks!

YPS

[ann]

I have a javascript menu directly above my adsense sky and haven't had any problems.

Ann

[dataguy]

I've been having targetting problems for nearly a month now, and I only use javascript on about 0.01% of my pages...

[ypsites]

Dataguy,

What kind of ads are you seeing on the mistargeted pages? (Are you seeing ads for scripts on the javascript pages?)

YPS

[opaquetrap]

Take care about the keywords in the following areas :-

Heading tags.
Title
File name or URL
Links and text which is hyperlinked
BOLD Text
etc.. Are some of the areas which determine the keyword relevancy for adsense.

and if possible, get your JS in seperate page and include it using <script src="external JS file"> tag.

[Frequent]

This is interesting news if you got it right from Google. I've noticed on a few of my sites that they seem to generate "programming/scripting" type ads rather than contextual ads. Not all of these sites use javascript so I'm not sure I can blame that exactly.

I have been able to "fix" many of them with the new targetting tags, but some seem quite stubborn.

However, it makes me wonder if they have tweaked Adsense to give more favorable targeting to lightly coded and pure html sites to combat the scraper/database driven "5 minutes for 10,000 pages" epidemic.

Freq---

[ionchannels]

Freq-a properly made scraper site should have little-to-no code visible in the final html if the html is generated with php for example.

[Frequent]

ionchannels-

I understand that. But the majority of the "free" scripts out there that newbies looking for a quick buck use to clog the web with scraper and database driven junk do not run clean.

It would not be that difficuly for $G to dedicate a small team to develop ways to detect and penalize the most common "bad" scripts so the systems (SERPS and Adsense) are not encouraged their use by good income.

Freq---

[jomaxx]

What Google may be referring to is the spider finding text or keywords within the contents of the Javascript. My rule is that common Javascript code should be in an external file insofar as is possible.

[Added: I just noticed that opaquetrap has made that same suggestion. Well anyway I can imagine Javascript errors on a page effecting the execution of AdSense, but if the problem is targeting then I say get the code off the page so the spider doesn't see it. And in the code that remains on the page, make sure there are no comments or variables that could be read as keywords. And wait up to a week or so after changes have been made for the targeting to come back.]

[ypsites]

Interesting suggestion to put the js code in an external file ... does it slow things down, though?

[jomaxx]

No, it tends to speed everything up because the file containing all the JS code only has to load one time. Every page calling it becomes smaller by a little or sometimes by a lot.

[bumpski]

For more the a year I had my Adsense code inside IFrames, and it worked well. Targeted ads, and no slow down due to Adsense server delays. I believe I got targeted ads even in the Google cache using IFrames! (IFrames: Inline Frames, not standard Frames)

About a month ago the Adsense ads in these IFrames became intermittent (many PSA's) and poorly targeted, about the time the "section targeting" capability was added. Also at that time ASA had offered to look into my problem but I had to tell ASA I had already removed the IFrames.

I've now removed the IFrames to rectify the targeting problem. It appears the Adsense servers performance has improved since last year. If you're using IFrames or maybe even frames try it without.

[ypsites]

More on this.

Google claimed that it was a "conflict" of our js code versus theirs. But I look at the site in Firefox, and our js dropdowns work fine, while AdSense is invisible.

Firefox javascript console gives the following error -- anyone seen this before?

Error: uncaught exception: [Exception... "Failure" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: [pagead2.googlesyndication.com...] :: google_init_globals :: line 349" data: no]