≡ Top Menu ≡Category Menu
You are here: Home » Google Earnings Warning

Google Earnings Warning

Things have been pretty quiet on the writing front over here. I’ve been spending my time on other projects, but imagine my surprise when I logged into my AdSense account and saw this HUGE warning plastered on the center of my screen:

Google Earnings Warning

The actual wording is:

“Your earnings on June 23 were 69% below forecast. This may indicate an issue with your site that you should investigate. We detected the earnings drop by comparing the money you earned to a forecast for your account.”

The funny thing is June 23rd was a Sunday and I do precious little online on Sundays. So, if my earnings dropped by 69% it had nothing to do with anything I did. It had more to do with what Google was doing.

Don’t you just love it? Google gets to play around with the traffic, slam my income and then give a warning advising me to launch an investigation on my site. Fortunately, the precipitous drop lasted only one day. The following days seemed to have made up for the June23rd spanking.

Another Reminder

Google does a good job of reminding me to place my eggs in other baskets. The old model of building sites to earn AdSense income is long gone for me. While I still enjoy residual income from sites I built a few years ago, I choose not to follow that model going forward.

Speaking of Google, I’m sure you all know they have decided to discontinue their Google Reader for RSS feeds effective July 1, 2013. To replace Google Reader, I signed up for an account with Feedly. Feedly is free and they make it easy to import RSS subscriptions from Google Reader.

Feedly Interface

There are other RSS readers out there, but I chose Feedly because it is easy to use. I tried using Yahoo’s reader, but I found the interface to be cluttered and distracting. Feedly is simple and minimalistic. So, if you signed up for the NJFM RSS feed (which has been ridiculously quiet lately) and use Google Reader, you’ll have to switch to a different reader.

{ 5 comments… add one }
  • Robin Elizabeth Margolis June 29, 2013, 8:51 am

    Dear Felicia:

    I had to switch to a Netvibes home page for feeds because Google is getting rid of iGoogle home pages in November. Seems like they are getting rid of things like iGoogle and the Google Reader that everyone liked. Baffling!

    As of 6/29/13, I’m still receiving feeds from your website via my Netvibes home page. I clicked on your RSS feed icon, and it took me to a page of code.

    I copied and saved the code for your site’s feed, and then pasted it into the entry slot on Netvibes for adding feeds.

    Netvibes accepted the feed, and created a feed area for your website on my Netvibes “feeds” web page.

    So your readers who have home pages other than iGoogle or readers other than Google Reader can rescue the feed from your website and transfer it to those other web pages and readers.


    • Felicia June 29, 2013, 9:13 am

      Thanks for that info, Robin. It’s good to have several alternatives. I think it’s a matter of time before Google gets rid of Feedburner too.

      • Robin Elizabeth Margolis June 30, 2013, 2:10 am

        Dear Felicia:

        Thankfully, we can all keep in touch with your website, using just a little ingenuity.

        It is very puzzling to me why Google is getting rid of popular items that caused people to visit its websites and use its service.

        Had Google kept iGoogle, I would have switched over to its business plan services, but its decisions to eliminate iGoogle and Google Reader worried me.


  • Anon July 5, 2013, 11:37 pm

    Do you know if there a way to remove the warning once it has been acknowledged? Or we are forced to look at it every time we check our earnings? I would like to completely disable this “feature” as my site earnings are highly variable.

    • Felicia July 6, 2013, 9:33 am

      That annoying warning goes away on its own after 3 days. Unfortunately, you’ve got to look at it for 3 days.

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Next post:

Previous post: