Forum Moderators: martinibuster
As part of the creation of the pages, I frequently launch the pages from my local machine to test out the links, see how the pages looks, etc..., before uploading the final product to the web server.
Well, normally once a page is uploaded to the server, the mediabot will come around and find the page once the page has been viewed (I always view my new pages just for this reason once they are up) - usually serving up some relevant ads in about an hour or two.
What was interesting and what some of you might find of interest is that it seems the little mediabot can read the html right off your own local box - it doesn't need to wait for the page to be uploaded to the web server. The reason I discovered this is that once I uploaded the new pages tonight I immediately viewed them. And much to my surprise, on the absolute first view of these pages and less than 20 seconds after they were uploaded, these pages were serving absolutely perfect ads. Moreover, these pages were a completely new theme for my site - Adsense didn't just fall back on the general theme for my site (which I've seen happen alot when the bot doesn't know what to serve right away).
Needless to say, I've never seen this happen before so thought it was kind of interesting that AdSense can read the pages you are designing off you local box, figure out the content of it before those pages have gone live, and then serve perfectly relevant ads once the pages are uploaded.
In any event, kind of a neat trick to make sure you are serving relevant ads when you first launch a new page - especially if it is on a "new or different theme."
While this little trick won't work for a dynamic site, it seems to work very well if you design stuff the old and slow way like I do. :)
Just thought I would pass it on.
Edited for spelling
Jim
That would indeed be very surprising, because the laws of physics simply make it impossible.
What probably happened was that you hit a time when the load on mediabot was low, so it spidered and analyzed your new pages in realtime, just when you viewed them the first time.
Had it happen many times where good targeted Adsense is on the page immediatly (typically needs at least 1 refresh but may be seconds apart) upon sending the page to the server. I think it is because the instant the page resolves G knows about it due to the script and puts ads up, sometimes right away, sometimes delayed.
[webmasterworld.com...]
What was interesting and what some of you might find of interest is that it seems the little mediabot can read the html right off your own local box - it doesn't need to wait for the page to be uploaded to the web server.
Like others have stated, your site is already profiled for a certain type of default ad.
Or... could it be that viewing the page on your box had nothing to do with it & Google knew what page you were going to create, as well as the page's content before you even did and had ads ready & waiting to be served?
And tomorrow's joke of the day is:
you know what? he's got to be right. The content of the page must be accessible to the javascript in the ad.
Again, more than likely a default set of ads served according to already existing pages/channel/etc
Linear... no need to fire up a sniffer, there are numerous who have done the same before & posted results. Nothing more than click-tracking stuff.
ps. WYSIWYG is old-fashioned?
Correct...except that the ads displayed are not anywhere close to the normal profile of ad displayed for my site. That was the point - these pages were completely new on a completely different topic, like "one of a kind" topic. Never have ads like this EVER been shown on the site before.
In short, the normal profile ads with which I'm very familiar with were not the ones shown.
>> ps. WYSIWYG is old-fashioned?
Compared to all the new "ways" to make a website, I sort of think WYSIWYG is rather old fashioned, don't you? Of course, just because it is old, doesn't mean it doesn't work.
>> What probably happened was that you hit a time when the load on mediabot was low, so it spidered and analyzed your new pages in realtime, just when you viewed them the first time.
This could indeed be possible since the pages were uploaded early in the morning when the mediabot probably wasn't very busy. But, I didn't realize the bot could work that so quickly.
Jim
Again, more than likely a default set of ads served according to already existing pages/channel/etc
Wrong. A page that deals with "Omega3 fish oils" could not having anything less to do with my site. There is no way at all that google would assign that as a theme. It was a completely new topic and that keyword has never appeared on my site before.
Today's joke of the day is..., Tomorrow's joke of the day is...
This really isn't a forum for sarcasm. Keep it to yourself.
There is nothing clever about it, its just how large scale search systems work.
It has nothing to do with the information Google holds about you, sites, cookies etc.
When a page is requested local or on the internet that runs adsense code, Google runs a series of checks on that page on its internal cache, when a result is found the ads are shown.
The inconsistent results are due to the large amount of servers on Googles system.
dregs33
I have always followed the practice of clicking on every new page so that the mediabot would visit the page. In adding over 400 pages the past two weeks, only twice have either a psa or an irrelevant ad appeared. The mediabot is now powerful enough to analyze a new page within a second or two and produce relevant ads.
WELL DONE GOOGLE!
Again, more than likely a default set of ads served according to already existing pages/channel/etcWrong. A page that deals with "Omega3 fish oils" could not having anything less to do with my site. There is no way at all that google would assign that as a theme. It was a completely new topic and that keyword has never appeared on my site before.
As others have noted, chalk up the speedy ads to a fast mediabot then.
Today's joke of the day is..., Tomorrow's joke of the day is...This really isn't a forum for sarcasm. Keep it to yourself.
As others have noted, chalk up the speedy ads to a fast mediabot then.
That mediabot can be as fast as it wants. It still doesn't have authorized access to that fish oils area (unless Google is now equipping the bots with password picking scripts).
The only explanation I can think of is that either the page content is being passed from my computer via the Google Toolbar, or via the javascript. But as far as I can tell, if the mediabot works the way I thought it did, the ads it should be displaying are ones that coincide with the text on the password protected error message, not the actual page content that only someone with a password can see.
One potential pitfall: posting a page with very little content (as you work on it) with the AdSense code and then loading that page might cause it to go into PSA mode, so that one hour later when you save your page with the final product with plenty of good content, mediabot might not come back for awhile (I've seen that happen, too).
I did a few tests to see how minimal I could make a page that still triggers AdSense. I made a page called "fly-fishing-rods.htm". I chose this subject as there's no way I'd usually cover this subject on my site and I've never ever googled for anything related to fishing, thereby ruling out AdSense grabbing cookie data or using a memory of what kind of ads it served to my site in the pase. Neither the title tag nor any other readable text or HTML contained anything related to these keywords, in fact I deliberately kept them neutral and the only non-common words that AdSense could have 'seen' were: "London" and "Pasta Salad" - again, nothing at all related to fly fishing or fishing rods.
I did this in FrontPage, so in preview mode the AdSense showed nothing. I wouldn't expect it to however; even though I'd named the document already, FrontPage renders it to a temporary file for preview, the name of which will be something like "vjlk5345.htm" - of no use to AdSense. I uploaded it to a server, looked at the live version, which on the first view showed my default 'google_alternate_ad_url'. I hit F5 to refresh and there were instantly some adverts for fly fishing and fishing rods.
I repeated this for several other keyword groups, each time using keywords in the filename only, but increasing this to (in order), the TITLE tag and then some text in an <H1> and finally a <P>. I can only imagine that I happened to choose a good example group of keywords that my first attempt worked (fly-fishing-rods). So I fell back on something I knew there'd be a surfeit of ads for, albeit something my site might cover, namely "ps2-games-sony-playstation.htm". This did the trick - same success as fly fishing - instant PS2 game-related ads shown the first time the page was viewed live.
My conclusion: When the AdSense algorithm finds nothing else about a page using its reliable methods (scanning the cache and evaluating keyword relevance) it uses the bare filename as a last resort. However, I'd imagine that there must be some kind of moderation to this along the lines of "unless we have a surfeit of ads to supply on this keyword, don't serve ads based solely on filename".
I must admit, the first time I saw AdSense in action, I did have in the back of my mind the notion that it scans the page you are actually reading to evaluate which ads to serve. It's only when I considered the logistics of what AdSense would need to do and the limitations of the implementation (ie. JavaScript) that you realise it simply doesn't and cannot work that way.
Anyway, hi everyone, I'm pretty new around here as you can tell :)