Loading BoundHive

Check Metadata Consistency Across Book Editions

Use a master identity sheet to compare the title, subtitle, contributor names, and edition wording across each format's cover, title page, and publication record. Keep legitimate format differences explicit. Resolve mismatches before submission and consult current KDP guidance when a change affects an already published record.

Separate book identity from edition details

Some information identifies the work, while other information describes a particular edition. Start by recording the intended title, subtitle, author name, and contributors. Then list format-specific details separately so a print specification does not accidentally become a universal assumption.

For example, a workbook edition and a reading edition may contain different supporting material. Decide how those differences should be described accurately. Do not force every field to match when the editions genuinely differ, but do not let unexplained inconsistencies arise simply because different people prepared the files.

Compare the actual publication surfaces

Check the cover, title page, metadata sheet, and any existing publication record side by side. Include exact spelling, punctuation, contributor order, and edition wording where relevant. A checklist completed from memory will miss the small changes introduced during design.

Copy text from authoritative working records when possible rather than repeatedly retyping it. If a cover mockup contains shortened wording for a design experiment, label it provisional. The experimental version should not quietly become the source for metadata while the manuscript retains another form.

A symbolic browser workflow illustrating how to compare the actual publication surfaces.
Compare the actual publication surfaces

Record legitimate differences

Use a difference column to explain why a field varies between editions. A changed subtitle, added contributor, or revised-content statement deserves a deliberate decision. Record the source revision and the person who approved the difference.

Avoid treating a similar title as proof that two files belong to the same release. Edition identity involves content and production context as well as words on the cover. Keep the approved file pair and metadata together so the person performing the upload can identify the exact edition without reconstructing its history.

Review changes through current platform guidance

Check current KDP metadata and update guidance before assuming a field can be changed in place after publication. Different changes may have different consequences. The correct action depends on the platform's current rules and the actual nature of the revision.

Do not use an old support conversation or another author's experience as the sole authority for a new publishing decision.

  • Compare exact wording across files and records.
  • Separate shared identity from edition-specific details.
  • Explain every intentional difference.
  • Verify the current treatment of material changes.
  • Preserve the approved metadata with the release.
A symbolic browser checklist illustrating how to review changes through current platform guidance.
Review changes through current platform guidance

Close the check at submission time

Before submitting, compare the entered values with the approved identity sheet. Review previews and confirmation information where available. Record the submitted revision so a later correction starts from what was actually published, not only what you intended to publish.

When maintaining several formats, repeat the check for each one. A correction in one edition does not establish that another has been updated. Keep the record concise enough to use every time; a short accurate matrix is more valuable than a detailed checklist that is never revisited.

Frequently asked questions

Clear answers for this publishing decision.

Should every edition have identical metadata?

Shared identity should be consistent where appropriate, but legitimate edition differences need accurate treatment. Document the distinction and verify current platform requirements.

Can I change a published subtitle freely?

Do not assume that. Check the current KDP guidance for the specific change and edition before deciding whether an existing record can be updated.

What is the most common source of mismatch?

Several working versions can diverge during editing and design. Compare the actual files and entered records instead of relying on the original brief.

Metadata and upload

What should the title, subtitle, description, and keywords look like before I upload?

Check the mechanical limits first, then make sure title, subtitle, categories, and description describe the same book for the same reader; a keyword is useful when it matches how that reader searches, not because it is popular.

Draft the listing fields in a book project

Get all of our updates directly to your inbox.
Sign up for our newsletter.

We could not save your subscription.