People ask me about making money from AdSense all the time. While I usually will offer little tips and tricks that I’ve learned along the way, one thing I want to make sure that new AdSense publishers know is what NOT to do.
The number one thing that you should NOT do is STEAL OTHER PEOPLE’S CONTENT. Yes, I know the guy who sold you the video or the eBook said it was okay. Guess what, he has your $97 bucks, and you’re about five minutes away from being up shit creek without a paddle, as you lose your web hosting, your domain names, and most importantly, your AdSense account, all because you ripped someone off.
If I catch you stealing my content, your ass is grass. (This obviously doesn’t apply if I gave you permission to use it.)
This content was stolen from Michael Hampton.
Copyright © 2006 Michael Hampton. All rights reserved. This material may not be published, broadcast, rewritten or redistributed.
Google’s Gmail service just pissed me off.
As you’re probably aware if you have Gmail, Google just added several new features to Gmail, primarily among them the ability to carry on live chats with other Gmail users, right from within Gmail. One of the other features they added at the same time, however, is the one which is driving me nuts.
Everytime you place the mouse over a message in the listing, this box pops up.
And it’s driving me insane. I don’t want to add them to my contacts, mail them or invite them to chat! I want this box GONE! And there’s no option to turn it off.
If you’re upgrading to WordPress 2.0 and use Google AdSense, there is something very important you need to know to ensure you continue to get well-targeted ads, and that Google doesn’t suspend your account for program violations.
One of the new features in WordPress 2.0 is a live post preview. If you scroll to the bottom of the page while editing a post, you’ll see a live preview of how your page will look once it’s published. This is a very nice addition to WordPress, but for AdSense publishers, and those using other context-targeted ad networks, it presents a serious problem.
When the post preview is rendered, it will try to fetch your Google ads!
And because the post hasn’t been published yet, when Google’s bot tries to crawl the page a few seconds later, it will receive a 404 error.
The best case scenario for this is that some of you (who don’t use permalinks) will receive very poorly targeted ads for up to two weeks after you publish your post.
And the worst case scenario, since Google prohibits displaying ads on 404 pages, is that you could get your account suspended.
WordPress 2.0 does provide a solution, though; it’s the new
is_preview template tag. This new tag tells whether the post is being displayed in the post preview section while it’s being edited.
So all you need to do is to add in a check for this into your template code wherever you have placed AdSense, and the problem will be solved. Just add this code around your AdSense code:
<?php if (!is_preview()): ?>
// Paste your AdSense code here //
<?php endif; ?>
This way, the post preview will not try to show Google ads, and they will only be shown once your post is published. This will keep your AdSense account safe and your ads well-targeted.
Update: It’s come to my attention that
is_preview() may be broken. If you find that’s the case, submit a bug report and post the ticket number in the comments below so we can track it.
Update: I’ve tested
is_preview() and it seems to be working just fine. Like other template tags, it only works inside the loop, though.
Update: Since people frequently place ads outside the loop, there needs to be a way to test for this outside the loop. The following workaround worked for me:
<?php global $wp_query; if (!$wp_query->is_preview): ?>
// Paste your AdSense code here //
<?php endif; ?>
Update: Ticket 2188 is open for
is_preview() acting strangely.
After Google started offering its Google Analytics service for free early last week, so many people signed up that even Google, who has thousands of servers, was caught off-guard.
Today they’ve emailed everyone this special notice:
Hello Google Analytics User,
This is a quick update to address some issues you may be seeing in your Google Analytics account and what we’re doing to respond.
First, due to extremely high demand, we’ve temporarily limited the number of new signups as we increase capacity. This allows us to focus on our primary objective–to provide a great user
experience for our existing users.
Next, here is current information on the most common questions we’re receiving:
- The ‘Check Status’ button is being reworked to check for properly installed tracking code. This should be fixed by the end of November.
- The ‘+Add Profile’ link has been temporarily removed until we increase capacity. We’ll alert all current users when the feature is restored.
- While we increase capacity, you may see longer than normal delays in data showing up in your reports. All data continues to be collected and no data has been lost.
For additional help with your Google Analytics account, we encourage you to browse or search our online Help Center at http://www.google.com/support/analytics?hl=en.
Thanks for your patience as we improve Google Analytics and add resources to ensure a high-quality service.
The Google Analytics Team
It’s about time they informed everyone what was going on. Something like this should have been sent out last week.
I set up Google Analytics back on Monday when it was announced, but as of Friday have yet to see any data come in.
Obviously the announcement that the service would be free generated a lot of interest, and they seem to be backed up. But notices posted there (and since removed) indicated everybody should have data by now.
So I e-mailed them to find out what was going on, and got this response:
Thank you for your email. I understand that you have some concerns about data not appearing in your account. I’d like to give you an overview about the problems you may be experiencing:
– The “Check Status” feature is currently not accurate. If you added the code to your pages correctly, then we are collecting data. You can make sure by seeing if your site has set “_utm” cookies in your browser.
Yes, I’ve got the cookies, so that part seems to be OK.
– If your reports aren’t currently populated, they will be as soon as the next processing run is complete. We process every 24 hours.
So, basically, wait another day is what you’re telling me.
– You may see some reports within a profile before others. We’re populating reports like this to get you as much information as soon as we can. If you see this, rest assured that all applicable reports will show data soon.
Well, I am not seeing any reports at all yet, so we’ll see what happens.
– Once we catch up with the data for your account, you’ll see new reports every 24 hours.
That remains to be seen.
For additional questions, please visit the Analytics Help Center at http://www.google.com/support/analytics. If you’re unable to find an answer to your question on our site, please feel free to reply to this email.
Share your knowledge and learn from others at the Google Analytics Help forum: http://www.google.com/analytics/analyticshelp
So far I’m not impressed with Google’s apparent inability to predict a massive spike in demand and have the capacity to meet it. They’ve been doing this for years, and should be able to figure out things like this.
Once they do finally get the thing working, maybe I’ll post an actual review of Google Analytics, and be able to do something useful with it, which was the whole point in the first place.
Update: After Google (virtually everything they have) ran quite slowly or was down for several hours, I now have data! Through Thursday, anyway. Now to see what this thing can do.
Due to a bug in Google Desktop, Bad Behavior is blocking access to it when it tries to download users’ RSS feeds. I’ve sent a message to Google (though I don’t really expect much to happen) and I’ll see if I can have a workaround in place shortly.
Affected users will see “Web Clip Error: Unknown error” in the Google Desktop.
FeedBurner users who use the FeedBurner .htaccess redirects are not affected by this issue. (And since I’m one of them, I never noticed.)
I have a ticket [#32426362] from Google for this issue. If you are seeing this, you can contact firstname.lastname@example.org and place the ticket number, with the brackets, in the subject line, and let them know you are adversely affected by this issue. Also run the program located at http://desktop.google.com/DiagnoseGoogleDesktop.exe and include the diagnostic output that it gives in your message.