Type Adsense

AdSense for Feeds

In May 2005, Google announced a limited-participation beta version of AdSense for Feeds, a version of AdSense that runs on RSS and Atom feeds that have more than 100 active subscribers. According to the Official Google Blog, "advertisers have their ads placed in the most appropriate feed articles; publishers are paid for their original content; readers see relevant advertising—and in the long run, more quality feeds to choose from."[5]

AdSense for Feeds works by inserting images into a feed. When the image is displayed by a RSS reader or Web browser, Google writes the advertising content into the image that it returns. The advertisement content is chosen based on the content of the feed surrounding the image. When the user clicks the image, he or she is redirected to the advertiser's website in the same way as regular AdSense advertisements.

AdSense for Feeds remained in its beta state until August 15, 2008, when it became available to all AdSense users.

[edit] AdSense for search

A companion to the regular AdSense program, AdSense for search, allows website owners to place Google search boxes on their websites. When a user searches the Internet or the website with the search box, Google shares any advertising revenue it makes from those searches with the website owner. However the publisher is paid only if the advertisements on the page are clicked: AdSense does not pay publishers for mere searches.

[edit] AdSense for mobile content

AdSense for mobile content allows publishers to generate earnings from their mobile websites using targeted Google advertisements. Just like AdSense for content, Google matches advertisements to the content of a website — in this case, a mobile website.

[edit] AdSense for domains

Adsense for domains allows advertisements to be placed on domain names that have not been developed. This offers domain name owners a way to monetize domain names that are otherwise dormant. Adsense for domains is currently being offered to some users, with plans to make it available to all in stages.

On December 12, 2008, TechCrunch reported that AdSense for Domains is available for all US publishers.[6]

[edit] AdSense for video

AdSense for video allows publishers with video content to generate revenue using ad placements from Google's extensive Advertising network. AdSense for video display both InVideo overlay and text overlay ads.

[edit] XHTML compatibility

As of September 2007, the HTML code for the AdSense search box does not validate as XHTML, and does not follow modern principles of website design because of its use of

* non-standard end tags, such as and ,
* the attribute checked rather than checked="checked",
* presentational attributes other than id, class, or style — for example, bgcolor and align,
* a table structure for purely presentational (i.e., non-tabular) purposes,1 and
* the font tag.2

1: using a table structure for unintended purposes is strongly recommended against by the W3C[citation needed], but nevertheless does not cause a document to fail validation — there is currently no algorithmic method of determining whether a table is used "correctly" (for displaying tabular data or for displaying elements, that get proportionally wider or narrower when browser window resizes in width without active client side scripting).
2: the font tag is deprecated but does not fail validation in any XHTML standard.

Additionally, the AdSense advertisement units use the JavaScript method document.write(), which does not work correctly when rendered with the application/xhtml+xml MIME type. The units also use the iframe HTML tag, which is not validated correctly with the XHTML 1.0 Strict or XHTML 1.0 Transitional DOCTYPEs.

The terms of the AdSense program forbid its affiliates from modifying the code, thus preventing these participants from having valid XHTML websites.

However, a workaround has been found by creating a separate HTML webpage containing only the AdSense advertisement units, and then importing this page into an XHTML webpage with an object tag.[7] This workaround appears to be accepted by Google.[8]