Why Does Google Play Books Reject Ebooks?

Google Play Books Partner Center has the strictest content policy of any major ebook retailer and applies validation and pricing rules that differ from every other platform. Unlike KDP, which reviews contested content and sometimes approves it after human evaluation, Google Play rejections in restricted content categories are typically final with no appeal route. The ISBN requirement, price-matching behavior, and Google-specific EPUB validation also catch authors who've published to KDP and Apple Books without issue.

Most common rejection reasons

1. Strictest content policy of any major ebook platform

Google Play Books rejects content categories that KDP, Apple Books, and Kobo accept — including explicit sexual content of any kind (there is no adult-opt-in process as there is on KDP), certain dark fiction sub-genres, and content that triggers Google's automated moderation classifiers. If your content falls into a restricted category, resubmission produces the same outcome. Google Play is simply not a viable distribution channel for those content types.

2. Price-match enforcement creates first-submission surprises

Google automatically matches the lowest price your book appears at elsewhere. If your book is permafree on Smashwords, your own website, or Patreon, Google lists it at zero and may block relisting at a paid price. This is not a validation rejection — it is a pricing policy applied at listing time that authors encounter for the first time when their new listing appears at $0.00 without explanation.

3. ISBN required for all paid books

Unlike KDP, which accepts EPUB without an ISBN and generates its own ASIN, Google Play Partner Center requires a valid ISBN-13 for every paid book. Books without a properly formatted ISBN in the OPF content.opf file — or with an ISBN in the file but missing from the Partner Center metadata form — are rejected at intake.

4. Google-specific EPUB validation beyond EPUBCheck

Google's processing pipeline applies validation checks beyond standard EPUBCheck. Common Google-specific failures: NCX playOrder attribute values that are non-sequential or contain gaps, internal hyperlinks with unencoded special characters in href attributes (spaces, ampersands that should be %20 and %26), and OPF attribute combinations Google's parser doesn't recognize. Rejection emails cite Google system codes rather than EPUBCheck codes, making cross-referencing against standard documentation difficult.

5. Copyright scanning flags stock images and near-duplicate content

Google scans uploaded book content and covers against its image rights database and Google Books scan index more aggressively than other platforms. Covers using stock images without embedded licensing metadata, images matching existing Google Books scans, and content with large portions matching publicly available text trigger rights holds requiring manual verification — a process that can take weeks to resolve.

How to fix it before resubmitting

  1. Review Google Play Books' content policies before submitting — if your content touches restricted categories, resubmission will not produce a different outcome.
  2. Confirm your book's lowest price across all platforms before submitting to Google Play. If it's free anywhere, expect Google to match that price automatically.
  3. Add a valid ISBN-13 to content.opf as a dc:identifier element and enter the same ISBN in Partner Center's metadata form — both must be present and match.
  4. Review your NCX playOrder values — they must be sequential integers with no gaps. Regenerate your TOC in Calibre or Sigil if the NCX was manually edited.
  5. Check all internal href attributes for unencoded characters — spaces must be %20, ampersands must be %26.
  6. If held for image rights review, submit license documentation for any stock images through Partner Center's rights dispute form.

Common questions

Can I appeal a Google Play Books content rejection?

In most cases, no. Content rejections in restricted categories are applied by policy, not by case-by-case review. An appeal path exists mainly for books incorrectly flagged by automated moderation — not for content that genuinely falls in a restricted category.

Does Google Play Books require an ISBN for free books?

No — Google generates its own identifier for free books. The ISBN requirement applies specifically to paid books submitted through Partner Center.

Why did Google lower the price of my book without asking?

Google's Partner Center terms include a price-matching clause. Google monitors book prices on major retail sites and adjusts its listing price to match the lowest available price elsewhere. To maintain a paid price on Google Play, your book must not be free on any platform Google monitors.

Validate your EPUB before submitting to Google Play Books

The free EPUB Validator catches the structural, metadata, and navigation errors that Google Play Books flags — no signup required.

Validate Your EPUB Free →

For a complete guide to EPUB structure and common errors, see the EPUB formatting guide and the EPUB errors reference.

Common EPUB errors: Unique identifier not found (OPF-048), Unescaped ampersand in XHTML

Publishing checklists: EPUB formatting pre-upload checklist