free html hit counter Fathom: Keyword Prices Keep Going Up | John Battelle's Search Blog

Fathom: Keyword Prices Keep Going Up

By - November 08, 2004

According to a release I rec’vd from Fathom Online today, keyword prices are still rising at a healthy clip.

Fathom Online, a leading search engine marketer, released its October monthly Keyword Price Index™ showing an overall 14% increase in the price of keywords from the September average of $1.37 per keyword to $1.55 for October.

Search advertisers in some sectors of the market found that the start of Q4 was definitely more costly than September. For instance, in the consumer services category, which includes entertainment, spas, and other related goods and services, prices increased on average 78% from $.54 to $.96 per keyword. Retailers faced increases on average of 52% from $.32 to $.48. Other advertisers fared better, particularly in the automotive industry where prices dropped 10% from $1.43 5o $1.39 and in telecom/broadband where the average fell 5% from $1.89 to $1.78.


Related Posts Plugin for WordPress, Blogger...

5 thoughts on “Fathom: Keyword Prices Keep Going Up

  1. I’m getting this error on your site in Firefox 0.10.1:

    Error: The stylesheet http://battellemedia.com/styles-site.css was not loaded because its MIME type, “text/plain”, is not “text/css”.

    You might want to check out your MIME types for .css files.

  2. Thanks Scott. Scot Hacker will jump on it. We’ve been tweaking the site, I’ll wager this is due to that.

  3. Scot Hacker says:

    In testing this morning, I did find that FF for Windows failed to pull up the stylesheet properly until I did a super-reload (hold down Shift while clicking Reload). No other browsers were affected – not even FF/Mac. I found a small syntax error in the stylesheet and fixed it, but am not convinced that was the problem since the stylesheet hasn’t changed for quite a while, but this problem just arose – seeming to coincide with the release of FF 1. I’d be interested to know if any other FF users continue to see this problem.

  4. Richard says:

    You can fix this by creating a new file called xyz.css.php, which sets the file type

    —–xyz.css.php——–
    header(“Content-type: text/css; charset=utf-8″);
    include (‘xyz.css’) ;
    ———————
    and replacing

    link rel=”stylesheet” type=”text/css” ref=”xyz.css”

    with

    link rel=”stylesheet” type=”text/css” href=”xyz.css.php”

    in your html / php page

  5. Richard says:

    I should have mentioned, the error is because the server is not setting the correct mime type (css). You could also get it fixed by the server admin. FF is actually behaving correctly according to the standards (in that FF reasonably expects the css file to be properly identified)