More on AdSense Splogs

Four more pingbacks from feedscrapers today!

After writing my two splogging-related posts this morning, I went for a flight with some clients. Just got back a while ago. And what do I find in my e-mail inbox? Four more splog pingbacks!

I also found a message from Jim Mitchell, responding to an e-mail I’d sent him earlier in the day. He included a link to a blog post on MaxPower that provides two good methods for stopping AdSense sploggers. I’m going through it now. But the thing I wanted to share was this explanation of what splogging is, for those of you who have no idea what I’ve been whining about all day.

From Stopping Adsense Splogs & Spammers: Methods that Work on MaxPower:

Imagine searching for something or other on the Internet and arriving at a webpage chocked full of ads and stuffed with the exact keyword you were searching for. The page is of no help because it contains no content of value. Some guy somewhere, created a website that sucks keywords / newstories / content from other websites using RSS, inserted the right keywords to maximize profit from Adsense, and waited for Google to index and rank it high enough for you stumble upon it. Once at the page, the spammer (or spamdexer) hopes that you will click on one of the Adsense ads that seem helpful compared to the rest of the useless random text. This practice of spamdexing wastes your time, its annoying, and you can fight back.

If you’ve seen this on your blog, follow the above link to the MaxPower article to see what you can do about it.

Reporting Google AdSense Policy Violations

A follow-up to my “Google, Adsense, and Splogging” post.

Moments after publishing my post about sploggers making money with AdSense, I got three pingbacks from a splogger’s site. I visited the site and saw an AdSense ad block at the top of the page.

Talk about timing!

I went to Google’s site and looked up the info to report violations. I found “Google AdSense Help Center: How do I report a policy violation?“:

How do I report a policy violation?

We regularly review sites in our program for compliance with our program policies. If you notice a site displaying Google ads that you believe is violating our program policies, please let us know and we can investigate the issue further.

The page then goes on to provide instructions making it clear how to report the problem.

Everyone reading this: please use this information to report sites that are scraping your feeds to generate content for their sites. The more we report this, the more likely Google will do something to prevent these people from getting AdSense accounts in the first place. Then maybe — just maybe — this feed scraping will stop.

Google, Adsense, and Splogging

Reports of cancelled accounts while sploggers earn money by scraping honest bloggers’ content is troubling.

Jim Mitchell lost his AdSense account and Google won’t tell him why. He’s bitter about it. But what makes him more bitter is that he’s discovered that sploggers with AdSense accounts have been using his content to earn revenue.

From Is Google AdSense Really Fair? on JimMitchell.org:

Today, I found four different sites that have scraped my content to use as their own with AdSense ads on the page. This, according to the Google AdSense Terms of Service, is a huge violation. I promptly reported the abuse with hopes the sploggers who lifted my content get their income generating plug pulled pronto.

One of the commenters to Jim’s post claims his AdSense account was also cancelled for no reason.

Now I’ve had no trouble with Google or AdSense and hope I never do. My earnings are meager, but they do cover the cost of hosting, which is my primary goal for including AdSense ads on this site. (That’s one of the reasons I don’t plaster the site with advertising like so many other bloggers do.)

But I do have a serious problem with sploggers, especially if they’re using AdSense or other advertising programs to earn money by illegally using the content written by other bloggers.

I know my content is scraped. Every once in a while, I’ll get a pingback from a sloppy splogger that directs me to his site. The site is full of scraped content and not much else. Most of the ones I’ve seen seem to be link farms for some other purpose. I don’t know enough about this stuff to understand why my content is being scraped when there doesn’t appear to be ads on the site my content is appearing on. (Perhaps someone reading this can explain or include a link to a good explanation.) But if these sloppy sploggers are stealing content in a way that can be easily traced, how many other sploggers are stealing content in a way that can’t be easily traced?

And do they all have Google AdSense accounts?

Which brings up a good question: how does Google determine who qualifies for an AdSense account? Is there a human who actually looks at the sites? I seriously doubt that. So that makes me wonder how effective their software is at determining whether a site is legitimate — full of fresh, legally obtained content — or a ripoff of other bloggers’ hard work.

And that also brings up the question of the effectiveness of an Adwords account. I was using Adwords for Flying M Air in an effort to sell my multi-day excursions. While I’m no Adwords expert, I think I had it set up well. I know I was paying for a ton of hits. But I also know that my phone didn’t ring. While this might mean that people don’t want the service I’m offering — chances are, they get sticker shock out when they see the price — it also might mean that the clicks aren’t being made by serious customers — or even by humans.

But it also means that my Adwords payments might be going to sploggers who have built sites to draw in visitors who then click on my link. I probably wouldn’t mind so much if they were buying — one sale would pay my Adwords bill for a year — but they’re not. So I could be paying, through my Adwords account, for sploggers to steal content from honest bloggers, some of whom, according to Jim Mitchell, have had their AdSense accounts yanked for reasons never explained.

I guess what I want to know is this:

  • Why does Google cancel the AdSense accounts for certain bloggers who claim they have done nothing wrong, then refuse to explain why they were cancelled?
  • How does Google ensure that AdSense accounts are given only to legitimate sites — and not to sploggers or other copyright violators?
  • How can Google Adwords customers be assured that their ads are appearing on legitimate sites and are being clicked by humans who are genuinely interested in the products or services advertised?

I hope Jim gets his AdSense account back. And I hope that other bloggers do their best to report feed scraping and splogging activities to Google or other ad sourcers whenever it’s found.

Royalty Statements

What my quarterly royalty statement tells me.

I make my living as a writer. Sure, I do other stuff and bring in money doing it, but when it all gets down to dollars and cents, the money I receive from writing is what pays the mortgage and puts food on the table.

With a new royalty statement in my hands, I thought I’d take a few moments to explain to folks interested in writing how the royalty part of writing works and what can be learned from a royalty statement.

How a Typical Writer Receives Income

Money from my writing work comes in three ways:

  • Payments for articles. When I write an article for publication, I normally get a check within 2 to 4 weeks of publication. The amount is agreed upon in advance, so I know what to expect but not exactly when to expect it.
  • Advances for work in progress on books. When I sign a book contract, it includes a payment schedule for advances. I like my advance paid in three or four installments that are due when certain parts of the book are submitted to my editor(s) — in other words, when I achieve completion milestones. A typical arrangement might be 1/3 on signing, 1/3 on 1/2 completion, and 1/3 on completion. Depending on the publisher, the checks usually arrive within 2 to 4 weeks of the milestone. Again, I know how much to expect but not exactly when to expect it.
  • Royalty payments. When I sign a book contract, it also includes a royalty percentage. The percentage is applied to the wholesale price of the book. So, for example, if the royalty is 12% and the book retails for $20 (about average for my books), the 12% is applied to the amount the publisher sold the book to retailers (or book clubs or direct order customers) for. A good rule of thumb is about 50% off the cover price. So I’d get 12% of about $10 or $1.20 per book. This royalty rate is applied to all sales of a title to come up with a royalty due. The amount of advance is then subtracted — remember, that was an advance on royalties — and if the result is a positive number, the book has “earned out” and I get a royalty check. My publishers pay royalties quarterly, although not on the same schedule. I know exactly when a royalty check will come — well, within 3 days of an exact date — but I never know how much I’ll get.

After doing this for 15 years, I’ve come to think of advances as my “bread and butter,” payment for articles as “fun money,” and royalties earned as “icing on the cake.” I won’t write a book unless the advance is enough to cover the amount of time and effort I put into writing the book. (I turned down two low-advance projects just last year.) This way, if the book doesn’t earn out, I’ll still make enough to keep paying the bills. If it does earn out, great. And since I don’t do a lot of work on articles — it’s just too much effort to get the work lined up — I don’t rely on that income for anything. That’s kind of unfortunate, because I can usually bang out one or two articles in day, so the income would really be great if I’d get get more of that kind of work.

As you can imagine, royalty statement time is a big event at my house — especially when Peachpit royalties are due. The statement comes in a big fat envelope. The reason: there are lots of pages. But one of the first pages of the package is the royalty check. And a quick peek tells me just how much icing I’ll have to spread around for the next three months.

How Many Books are on the Books?

The reason my Peachpit royalty statement comes in a big fat envelope is because there are lots of pages. The statement sitting in front of me right now is 61 pages long. I can’t even get a staple through it for filing.

The first few pages — 4, this time around — is a summary of the ISBNs covered by the statement. This list of ISBNs — 34 of them this quarter — are the books the publisher still has in its accounting system.

I need to make a distinction here between titles and ISBNs. A good example is right on the first page. My 2004 title, Creating Spreadsheets and Charts in Excel: Visual QuickProject Guide, is listed three times: the original title, the German translation, and the French translation. Sometimes translations get their own ISBN and sometimes revenue for a translation is listed for the main title. It depends on how the translation rights were sold. Also, since Peachpit is now selling PDF versions of some of my books, those versions appear on a separate line.

Still, a quick count of titles on this quarter’s statement shows 28 titles listed. Whew! Even I think that’s a lot.

In my case, the vast majority of my work these days is in revisions. So each statement might show multiple versions of the same book. This is especially true for titles that are still “alive.” For example, my America Online: Visual QuickStart Guides (a 2-part — Macintosh and Windows — nightmare completed for version 3.0 years ago) are “dead” titles. They came out, sold poorly, and were not revised. These book are dead and buried and the only reminder that I ever did them are the author copies of each book on my author copy shelf. But my Excel for Windows: Visual QuickStart Guide is alive and kicking — in fact, I just finished the revision for Excel 2007 this week. Three editions appear on my royalty statement: 2000, 2002, and 2003. (2007 will appear on the next statement.) And my Mac OS: Visual QuickStart Guide takes up the most lines: seven editions going back as far as the edition covering Mac OS 9.

For a title to appear on the royalty statement, it must be either earning money or losing money (by returns) with a more recent edition to suck up the losses. This is an important clause in book contracts — one that’s important enough to discuss in a little more detail here. Commonly known as cross-accounting or cross-deductions, it means that returns on one title can be applied to net revenue on another. So, for example, if my share of returns on an old edition of my Excel book was $43.54, that amount could be deducted from or charged to royalties on a more recent edition. That’s normally why books stay on royalty statements for so long — there’s still accounting for them.

It was kind of a good thing that my AOL books didn’t have more recent editions. Neither title earned out, so the money I was overpaid for those books could be deducted from future editions, had they existed. Instead, the publisher cut their losses by not doing new editions (a wise move) and simply stopped accounting for the existing books when the numbers stopped coming through. The books “fell off” my royalty statement.

(If you’re ever given the opportunity to negotiate a book contract, do not sign a contract with a clause that says all of your books can be pooled together for cross-accounting. (I don’t know the exact wording of a clause like that because I’ve had it removed from every single draft contract it appeared in.) Agreeing to this may prevent you from ever getting a royalty check if you write multiple titles for the same publisher and any or them are dogs. If you’re really lucky, you won’t even have cross-accounting for the same edition of a book — I was lucky to have that situation with one of my Quicken titles years ago. But I think it’s fair to do cross-accounting with different editions of the same book, so I don’t mind signing for it. I just brace myself for the returns every time a new edition comes out.

And returns, in case you’re wondering, are returns from retailers/wholesalers, not consumers. If Barnes & Nobel buys 1000 copies of a book and sells 200 of them in the time they allotted to give the title shelf space, 800 copies come back. That’s a bad thing for the author.

What the Summary Numbers Mean

Still with me? Here’s a bit more that the summary pages tell me.

For each ISBN, the summary page has 6 numbers:

  • Previous Balance is the amount owed to me (positive number) or the publisher (negative number) for the ISBN. There usually aren’t any positive numbers; if the publisher owned me money, they paid me last quarter. So books that are earned out show zero in this column. If I owe the publisher money — for example, the book hasn’t earned out or subsequent returns have put the ISBN in the red — that number appears as a negative value. Zero is good, negative is bad.
  • Earnings/Subsidiary Rights Earnings is what the book earned me during the quarter. That’s the royalty calculation applied to net sales. Positive numbers means they sold more books than they received in returns. Negative numbers mean they got more in returns than they sold. Positive is good, negative is bad.
  • Credits/(Deductions) is the amount paid out during the quarter for advances or, if the author is paying for indexing, the amount paid to the indexer. I’ve never seen a positive number in this column.
  • Cross Deductions is where they take returns from one title and apply them to royalties earned on another title. So, for example, if the net earnings on my Word X book were -$53.47, that amount would appear as a positive value in this column for that ISBN and a negative value in that column for a later edition — perhaps my Word 2004 book. If you add up the cross-deductions column, the net amount should be zero.
  • Payment Due is the net amount owed to me for the ISBN. This number is either zero or a positive number.
  • Balance Forward is the amount that needs to be earned out to get more royalties on the ISBN. It’ll be zero if there was a payment in the previous column or a negative number if zero was in the previous column. That value is carried forward to the Previous Balance column in the next statement.

Of course, this is the format Peachpit uses. Other publishers may use other formats.

So when I get a royalty statement, the second thing I look at is the summary. (The first is the amount of the check, of course.) The summary tells me which books are earning money for me. That’s usually current editions of books. This is where I can see at a glance whether a new title has earned out. I can also see which books are earning me the most money — the titles with bright and happy futures. The bigger the payment due on a title, the more likely that title will be revised in the future. (Unless the software publisher decides to kill the software, as Adobe did to PageMill years ago. That book was doing very well when it was killed.)

Sometimes I get pleasant surprises. For example, my Excel 2002 book is still selling. That book was published five years ago and it earned $262 for me this quarter. Okay, so that isn’t enough to host a big party, but it’s a nice thing, a good thing. After all, the average life of a computer book is 18 months. So to have one that’s still bringing in a few bucks for me after five years is great.

The summary statement also tells me which titles are dead. These are the titles with previous balances that are negative numbers and no revised editions to earn more revenue. Sometimes these titles have ugly negative numbers in the Earnings column, indicating returns. My QuickBooks Pro for Mac book is in this situation. Although it’s the only title covering that software, there simply aren’t enough users interested in buying a book to make the book earn out. So when my editor says the publisher is not going to revise the title, I can look at this royalty statement and understand why. The book is dead.

Want more detail? The summary pages are also a table of contents for the 57 pages that follow them. That’s where I can find information about units sold, subsidiary rights (like translation rights), and where the books were sold: U.S., Canada, Export, etc. To be honest, I don’t look at these pages for every title. Heck, I have enough to do in a day.

What I Learned this Quarter

Looking at the royalty statement is like peering into a crystal ball. I learned that there are certain topics I probably won’t be writing again and other topics I’ll be writing about for years to come. I learned which of my books is doing best for me (still Tiger, after two years!) and which ones I might want to promote a bit more to liven up.

But with 61 pages to review, that’s about all.

The Bookwoman's Last Fling

Disappointing.

Two or three years ago, I discovered John Dunning’s work. Dunning writes mysteries with a series character named Cliff Janeway. Former tough cop turned bookshop owner/operator Janeway narrates the tales of the book-related mysteries he solves. Along the way, the reader learns a little about collectible books and the world of bookshops.

Being the A.R. person I am, I always try to read an author’s books in the order in which they were written. This is extremely easy to do when borrowing books from the local library, since the librarians number each of an author’s books chronologically, right on the spine. In most cases, they’re even shelved in order.

The Sign of the BookThe Sign of the Book was Dunning’s first Janeway book. I don’t remember why I picked it up, but once I started reading, I couldn’t stop. It was some of the best mystery fiction I’d read in a long time. A good plot, good characterization, and good dialog. I went through it quickly and felt extremely satisfied — but ready for more — when I was done.

I then began reading the rest of Dunning’s Janeway books. The second wasn’t quite as good as the first, but it was still very good. The third wasn’t quite as good as the second. That made it above average. The fourth wasn’t as good as the third. I was definitely seeing a pattern here. It was as if Dunning was steadily losing his touch.

The Bookwoman's Last FlingThe Bookwoman’s Last Fling was a disappointment, plain and simple. It’s difficult, in fact, to believe that it was written by the same author who penned The Sign of the Book.

The book’s plot was contrived — Janeway makes conclusions without proper evidence (a violation of the mystery writers’ rule of “fair play’) and his actions based on those conclusions steer the plot. For example, early in the book, he decides that he needs to spend time at a certain racetrack where a woman who died 20+ years before had spent a lot of time. Why? There’s no clear reason provided. Once he gets there, does he start doing the logical thing — asking questions? No. That comes later, after more illogical activities. Clearly, the character is driven by the author, not by the circumstances he’s put into.

The dialog was flat and unrealistic. One of the things I liked best about Dunning’s first Janeway book was the snappy dialog. It flowed and was fun to read. As a reader, I felt alone with the characters, “listening” to them talk. In this book, Dunning seems to be working too hard to get those words out, and that effort is quite apparent to the reader. I’m not alone with the characters; I’m alone with the author, who is trying desperately to communicate what his characters may or may not have said. And although I usually feel that an author’s words are sacred and shouldn’t be over-edited, an editor could easily have cut 30% of the dialog and the reader wouldn’t have missed a thing.

The dialog was also difficult to follow. I’ve read a lot of novels, but I’ve never had so much trouble keeping track of who was speaking. Many, many quotes are unattributed to their speakers. That wouldn’t be a problem if Dunning had stuck to the common writing convention of starting new paragraphs for each speaker. But in some instances, the same unattributed speaker speaks in two paragraphs in a row or the attribution is simply unclear. Never before had I wished to see a few more “he said” or “she said” phrases.

Characterization was also flat and lifeless. The characters didn’t come off the pages. Dunning told you their traits; except in a few instances, he didn’t really show you much. Character relationships weren’t brought out, either — even between Janeway and his lady friend. What is their relationship, anyway?

I feel bad about writing such an unfavorable book review for an author whose work I’ve admired in the past. But I have a sneaking suspicion that Dunning wrote this book — and likely some of his previous books — under pressure by editors to produce another big seller. Apparently, he didn’t have the book in him — at least not when he wrote it.

I believe that a writer has to be internally driven to write a book in order to produce good work. External pressures can’t squeeze a book out of an author who just isn’t in the right frame of mind to produce. In reading Dunning’s later work, I get the feeling that he just wasn’t ready to write when he did.