As you can see, we have Google AdSense advertisements on this blog. This is because this blog was originally intended to be just a business tool, for generating ads revenue with content that lurked around unpublished here.

Now, with the first weeks of active advertisements, it might be time for a first evaluation.

Before doing that, here is my original calculation of the expected money:

• In 2008-02 and 2008-03, my personal weblog had 400 unique visitors and 600 pageviews a month, generated nearly exclusively from the 7 IT articles on it via search engine traffic.
• Therefore, each technical article is worth 60-90 page views a month.
• Therefore, the 1100 FAQ articles which are online here on doit.juii.net, equivalenting 500 longer technical articles, are worth 45,000 page views a month.
• Then I assumed an Google AdSense eCPM (earning per 1000 page views with ads) value of 1,50 EUR. This seemed realistically when comparing cyDome’s eCPM comparison values for computer topic.
• 45,000 page views with 1,50 EUR eCPM should be 72,50 EUR a month. More realistically: between 50 and 100 EUR a month.

Now comes current reality: we had 1,381 page impressions, one AdSense click, resulting in 0,13 USD total earnings and 0,09 USD eCPM. May I call this frustrating? With current values, I expect 2,000 page views a month and 0,20 USD total income a month. Even worse, the one click is due to technical evaluation / testing purposes!

The reasons for this bad performance seems to be that most articles deal with Linux, and Linux users generally avoid to pay money for anything. They really won’t click on advertisements … .

Let’s now look how some big players do the job.

• Here’s an overview of the AdSense earnings in categorie “computers: general” from the admoolah.com AdSense revenue database.
• Here’s what Google says about expectable AdSense earnings. They admit that eCPM in the range of 0,05 to 5 USD is normal.
• Mike earned 2400 USD in 2008-02 with his sites.
• John Chow earned 7011 USD in 2007-02 with his blog. He has also a good how-to for earning money with ones blog.

The result is, in my view: to make a really good amount of money, most important is you need a topic that sells ads (and Linux is poorest for that). Nonsense sells, and, of course, sex sells. But we don’t wanna get into that business, do we. Good ads earnings nearly always compromise good morals. Another thought is this: earning money with a website is reproducable (e.g. by following the how-to of John Chow), but what do you get for that? A day full of the most boring IT work you could imagine: search-engine optimization, tricking search engines, getting advertisements, comparing figures and statistics, HTML and CSS templating, and writing some dummy content where people are interested in. That’s nothing to get passionat about at all, but it seems to be a near full-time job. And instead of filling my life with such stuff, I’m going to select something where I can be passionate about … .

The most obvious possibility is to use the Google Toolbar for your browser.

Alternatively, you can use different websites. For example, this one offers checking the page rank of up to 10 sites in parallel:

Top25Web pagerank checker

Siehe www.google.com/support/googleanalytics/bin/answer.py?answer=55481&hl=en_US

Je nach Site kann es schwierig sein, diese Anleitung zu befolgen, z.B. weil man keine Möglichkeit hat, ein »onLoad«-Attribut in das body-Tag im Template der Site einzufügen. Es gibt mehrere Workarounds (hier bezogen auf die neue Variante des Tracking-Codes):

1. Man besuche eine URL der Site von der man den eigenen Traffic ausschließen will und gibt dann in der Adresszeile seines Browsers ein:

   javascript:pageTracker._setVar('test_value');

   Dadurch wird das benötigte Cookie gesetzt. Nachprüfen lässt sich das in der Cookie-Liste des Browsers.

2. Man erstelle eine Inhaltsseite (am besten nur nach login zugänglich) mit einem Absatz der bei Click das Cookie erzeugt. Dies ist zumindest in Joomla 1.5 jedoch nicht ohne weiteres möglich da Joomla JavaScript-Code wieder entfernt, vermutlich aus Sicherheitsgründen. Beispielcode, noch ungetestet:
   1. <p style="border: 10px solid black; background-color: #ff0000"
   2.   onClick="javascript pageTracker._setVar(’test_value’);">
   3.   Bitte klicken Sie auf diesen Bereich um den durch Sie verursachten Traffic auf dieser Seite
   4.   von der Analyse durch Google Analytics auszunehmen. Durch Click auf diesen Bereich wird ein
   5.   Cookie in ihrem Browser gesetzt, also sorgen Sie bitte dafür dass Cookies in ihrem
   6.   Browser zugelassen werden.
   7. </p>
3. Ein Cookie manuell erzeugen mit dem Webdeveloper-Plugin von Firefox. Hier für die alte Version des Tracking-Codes (»Tools -> Web Developer -> Cookies -> Add Cookie …«). Man gebe dabei folgende Daten ein:

   Name: __utmv
   Value: 25940091.no_report
   Host: .nxdfkoze.blogspot.com
   Path: /
   Expires: 18.01.2038 01:00:00

   Statt der Zahl »25940091« verwende man die Zahl die auch in den anderen von Google Analytics gesetzten Cookies zu Beginn des Inhalts steht. Und bei Host gebe man die Domain oder Subdomain ein auf der die eigenen Website gehostet wird.

4. Liste weiterer Workarounds: Posted in Google | 1 Comment »