How to Add a Description to a Book on Google Play

First, for anyone who is trying to solve this problem, here is the solution (at least for now):

Add or edit summary of Partner Program book

The basic issue is that Google typically gets its book summaries from third-party meta-data providers.  If you’re self-publishing, those third parties probably don’t know your book exists.  If you go through the help materials, you won’t find a solution to your problem.  Only once you attempt to contact Google directly for help do they walk you through a questionnaire that eventually leads you to the precious web form that I’ve linked to above.

If you would like to appreciate the value of a good — or even moderately competent — user experience designer, attempt to publish a book on Google Play.  It’s like a parody of bad UI.  Please, Google, you gotta do something.

For those who want to know the background here, read on.  For everyone else, I hope you found this post helpful.  The rest is just my tale of woe.

Background

In going through the painfully obtuse process of making Upload available on Google Play, I encountered a problem that had me baffled: how to add a summary/description/blurb to display alongside the book.  This concept of a brief introduction to your book is ubiquitous on bookseller websites.  Even on Google Play, most books have a short paragraph explaining the book, to entice the buyer into reading customer reviews, skimming the preview, possibly even buying the book.

Knowing this, I expected at some point during the not-at-all-straightforward process of getting a book onto Google Play to be presented with an opportunity to enter a summary for Upload.  I was not.  Nor did I come across any little note, friendly or otherwise, mentioning that Google prefers to fetch this information from someone other than the publisher.  When my book finally popped out the other end of the black-box process — an event which I feel warrants an email to the publisher, since it takes days and may result in pricing other than what the publisher intended — I discovered that it in fact did not have a summary, where other books on Google Play did.

Where had I gone wrong?  What step or piece of crucial information had I missed?  Other people are making it work — why can’t I?

So I sunk another 30 minutes or so into trying to find a solution.  Only to discover that you have to endeavor to register a complaint before they tell you how it works?  Maybe I missed something along the way, but I’ve gone back and forth over those pages and come up with nothing.  I guess the engineer-driven business model at Google has its downsides.  And that’s coming from someone who’s been coding for money for the past twenty years.

All part of the joy of self-publishing.  Of course, I imagine I’m lucky to be arriving at this game now, and not four years ago.