I just got a spam email in my inbox saying that “Article Marketing Has Changed Forever” and that I should buy this automated way to submit articles.
Good! You people buy into that and do that. It’ll make my unique articles that much stronger and I’ll rank higher. So, yeah, please do that. Please buy that system. It will help me out. 
-T
Popularity: 1% [?]
{ 0 comments }
We had been guessing 50% but it turns out that 68% goes to publishers – nice!
Here’s the Google AdSense Blog Post:
The AdSense revunue share (adsense.blogspot.com)
AdSense for content publishers, who make up the vast majority of our AdSense publishers, earn a 68% revenue share worldwide. This means we pay 68% of the revenue that we collect from advertisers for AdSense for content ads that appear on your sites.
And another article:
How is Google AdSense Revenue Share Calculated? (blog.searchenginewatch.com)
AdSense for Content, the ads which are contextually targeted to the words on your web page is calculated at a 68% split to the publisher. Google takes 32% of the effective CPM (eCPM) they charge the advertiser.
AdSense for Search, the ads which are plugged into your own website’s internal search engine and triggered and matched to keywords used in the search query is calculated at a 51% split to the publisher. Google takes 49% of the cost-per-click (CPC) they charge the advertiser.
-T
Popularity: 1% [?]
{ 0 comments }
I had a problem for a few days with a site I moved to a new host. The home page wouldn’t load all the way. It would sort of stop and random spots and I couldn’t figure it out. I was almost going to move it to another host but instead persisted figuring that I might have the same problem at a new host.
I, of course, immediately was looking at the error logs but they weren’t telling me much at first. I then found a good post in the WordPress Support Forum about something similar and then I checked the error logs again. I found that memory was being maxed out and it said it was due to the Contextual Related Posts plugin. Deactivating it took care of the problem immediately. It was using up too much memory.
So I’m switching plugins from Contextual Related Posts (which I thought was great except for being such a memory hog) and am now going to be using one called Yet Another Related Posts Plugin (YARPP). It works fine and is not a memory hog. It has some caching functions.
Which brings up another point – cloud hosting.
I’m not that big of a fan of it. I’m getting charged up the wazoo for GPU usage, which is like CPU usage. It’s not a bargain at all unless you have a bunch of static websites. I hate moving sites around so much but I’m finally figuring it all out. I got an account with Hostgator and despite the fact that they use CPanel (blahh!), it’s alright. I just tell myself that I only have to use CPanel at the beginning to set things up and then I don’t see it very often.
The best hosting control panel, by far, is Plesk. Know it. Believe it.
Anyway, despite a mini slump last month, this month is looking pretty good so far. Keep writing articles, people!
UPDATE: Another plugin I’ve disabled since it was eating processing power was “Cookies for Comments” – sorry, Matt Cutts!
Popularity: 2% [?]
{ 0 comments }
