KDP Ebook Metadata Checklist

Check title and subtitle against the actual cover

Amazon says the title field should contain only the actual title of the book as it appears on the cover. That means the field is not a place for ranking bait, promotional words, unrelated brand references, or keyword padding.

KDP also says the title and subtitle together must stay under 200 characters. If the title direction only works because it is stuffed with extra phrasing, the positioning is probably weak. In AIeBookGen, this is why title work belongs inside the workflow and not after export.

Write the description like a buyer-facing summary, not a keyword bucket

KDP describes the book description as an elevator pitch. It should explain what the book is, who it is for, and why it is worth reading. It should not contain URLs, testimonials, review requests, promotional material, spoiler-heavy copy, or standalone keyword phrases.

This is one of the easiest places to spot fake or rushed AI packaging. If the description reads like search spam instead of reader-facing copy, the whole project feels less credible.

The best time to draft the blurb is after the chapter structure and audience promise are stable. That gives you enough detail to be specific without inventing benefits the book does not actually deliver.

Choose keywords the way a reader would search

KDP allows up to seven keywords for a title and recommends that they relate to the actual content of the book. The official example contrasts specific terms such as place names with vague generic terms such as "parks."

That is a useful quality filter inside AIeBookGen. If a keyword could describe a hundred unrelated books, it is probably too weak. If it promises a topic the manuscript barely covers, it is probably too risky.

Good keyword work is specific, reader-centered, and connected to the real table of contents.

Review categories, audience, and contributors as one group

Categories are not cosmetic. They frame the shelf where the book belongs. The selected audience, reading age, contributor fields, and category placement should all point to the same book concept.

If the manuscript is a beginner cookbook, the metadata should not sound like an advanced culinary textbook. If the book is a coloring book interior, the contributor and cover direction should not imply a prose ebook.

Keep cover direction and disclosure review connected to metadata

Readers decide quickly whether the title, subtitle, and cover belong together. If the cover promises one kind of experience and the description promises another, the detail page feels unreliable.

For AI-assisted books, the workflow should also preserve a review moment before upload so the author knows what content, metadata, or imagery still needs human judgment. That is not only a quality concern. It is part of keeping the publishing record understandable.

Run a final metadata pass before export or publish

KDP's Book Detail Resources page warns that many details cannot be changed casually after publishing and recommends double-checking everything before submission. That is the right final habit for AIeBookGen too.

Before export, review the detail page as if a stranger will judge the whole project from those fields alone. If the metadata misstates the book, the workflow is not finished yet.