How to Localize Ebook Metadata for a Translated Edition
Map an ebook's title, language, contributors, identifiers, series data, description, keywords, and cover across the EPUB package and retailer listings.
Localizing ebook metadata is not a final copy-editing task. It is edition control. The EPUB package, retailer form, cover, and marketing copy describe the same translated edition, but they do not contain the same fields and they do not update together.
Build one approved metadata sheet first. Then map each field to the places that actually use it. Download the ebook metadata localization audit to record one row per field and destination, with the approved value, owner, lock risk, evidence, and verification date for every release. Every change class starts as unknown; replace it only after checking the current rule for that exact destination.
Separate the Three Metadata Layers
Treat these as connected but distinct systems:
| Layer | What it controls | Typical examples | Common mistake |
|---|---|---|---|
| EPUB package metadata | What reading systems can identify and display from the file | Title, primary language, identifier, creator, contributor, modified date | Translating the prose while leaving the source-edition title or language in the package |
| Retailer catalog metadata | What the store records for the edition and may show on its product page | Title, subtitle, contributors, language, series, description, categories, territories | Assuming the retailer imports every package field or that a later file upload rewrites the listing |
| Marketing assets | What a prospective reader sees before opening the file | Cover text, description, author biography, keywords, sample copy | Letting the cover and listing use different localized titles or contributor credits |
The EPUB 3.3 specification requires a title, identifier, language, and last-modified value in the package document. It allows additional creator, contributor, description, publisher, rights, subject, and collection metadata. Those package facts travel with the file; a store's catalog record is a separate submission.
Start With an Edition Record, Not a Store Form
Create one row for the translated edition before opening KDP, Kobo Writing Life, Apple Books, or another distributor. The record should name:
- source work and source edition;
- target language and script as a valid BCP 47 language tag;
- localized title and subtitle;
- original author and translator credits;
- edition-specific identifier;
- series name and position, when applicable;
- publisher or imprint;
- localized description and keywords;
- rights owner and intended territories;
- approved cover file; and
- the person who approved each value.
Do not overwrite the source-edition record. A translated edition can have different language, title, contributor, description, cover, territorial rights, and identifier decisions even when the underlying work is the same.
Use a stable edition key inside your workflow, such as work-042-fr-epub-v1. That key does not have to be customer-facing. Its job is to connect the approved metadata sheet, EPUB build, cover export, retailer submissions, screenshots, and later corrections.
Decide What to Translate, Retain, or Reissue
The correct operation depends on what the field means.
| Field | Default decision for a translated edition | Why |
|---|---|---|
| Title and subtitle | Localize, then approve as one combined display decision | Readers, covers, files, and stores must recognize the same edition |
| Publication language | Change to the target-language tag | It describes the content of this edition, not the source work |
| Original author | Retain the authoritative name; add an approved alternate script only when useful | Authorship does not transfer to the translator |
| Translator | Add as a contributor with the correct role where the destination supports it | A name without a role can be mistaken for another author |
| Identifier | Make an explicit edition-level decision | Reusing an identifier can collapse distinct products or versions |
| Series | Localize only under a series-wide convention | One improvised translation can split a series across shelves |
| Description and keywords | Rewrite for the target market; do not mechanically translate search phrases | These fields persuade and aid discovery rather than reproduce the manuscript |
| Rights and territories | Reconfirm from the translation and distribution rights | Language rights and sales territories are not implied by file ownership |
| Modified timestamp | Update when the EPUB package changes | EPUB 3.3 requires one package modification timestamp |
Amazon KDP's current metadata guidelines say translations must credit the translator and original author in contributor fields. Its update guide also marks language, title, subtitle, edition number, and primary author as locked after publication for Kindle ebooks, while fields such as contributors and description can be editable. Check the destination again immediately before release because store rules can change.
Map One Approved Record to Each Destination
Use a mapping table instead of copying values from the last store you opened. This fictional example shows the decision structure without pretending every retailer exposes identical fields:
| Approved edition fact | EPUB package | Retailer catalog | Cover or marketing asset | Release check |
|---|---|---|---|---|
| Localized main title | First dc:title | Title field | Front cover and product graphics | Exact wording and punctuation agree |
| Target language | First dc:language | Book language | Usually not printed unless part of the design | File content, package, and store agree |
| Original author | dc:creator with role refinement when used | Primary author | Cover credit | Spelling and order match the approved form |
| Translator | dc:contributor with an appropriate role when used | Contributor plus translator role where supported | Optional cover/title-page credit | Role is visible and not misrepresented as authorship |
| Edition identifier | dc:identifier selected by unique-identifier | ISBN, store ID, or distributor identifier as applicable | Copyright page or colophon where required | Identifier belongs to this exact format and edition |
| Series | Collection metadata where supported | Series name and position | Cover treatment and description | Name and numbering follow the series convention |
| Description | Optional dc:description | Store description | Campaign and landing-page copy | Same facts, adapted length; no contradictory promise |
| Subjects and keywords | dc:subject where useful | Categories and keyword fields | Campaign targeting | Chosen for the market, not copied blindly from the source |
Apple Books describes its book metadata as including title, contributors and their roles, and the book's primary language. EPUB 3.3 likewise supports contributor-role refinements and alternate-script forms for names or titles. Support in reading systems and retailer interfaces varies, so keep the approved source record richer than any one destination form.
Handle Titles and Names as Display Systems
The first dc:title in an EPUB package is the main title that reading systems present. EPUB 3.3 warns that support for multipart titles is inconsistent. A practical approach is to approve one full display title, then map any subtitle separately only where the destination has a reliable subtitle field.
For author names, decide which form is authoritative for the target market:
- the author's established published form;
- a transliteration approved by the author or publisher;
- an original-script form; and
- the sort form used for catalog ordering.
Do not force one string to do all four jobs. EPUB metadata can express an alternate script, but a retailer may require a separate contributor record or may expose only one display value. Record the compromise rather than silently changing the author's identity from store to store.
Keep the Cover, File, and Listing Synchronized
Metadata errors become expensive when each asset is approved separately. Freeze the title, subtitle, contributor line, series treatment, and language before final cover export. The cover-localization workflow explains how to compare translated cover text with the store record.
Use this release sequence:
- approve the edition record;
- update the EPUB package;
- run EPUBCheck on the exact final file;
- export the cover from the same approved title and contributor values;
- populate each retailer form from the edition record;
- save a screenshot or export of the submitted listing;
- preview the processed file and visible product page; and
- record any platform-specific transformation as a destination override.
An override should explain the constraint. For example, a store may have no dedicated subtitle field or may limit a description's formatting. The approved meaning can stay consistent even when presentation differs.
Treat Locked Fields as a Pre-Publication Gate
Some fields become difficult or impossible to change after publication. Before clicking publish, classify each destination field as:
- locked: a correction requires a new edition or support intervention;
- conditionally editable: changes are allowed only in certain states or formats;
- editable: the publisher can revise it after release; or
- unknown: the current rule has not been verified.
Unknown is not editable. Verify it in the platform's current documentation, record the date, and attach the source. This matters most for language, title, author, edition number, series identity, and identifiers because a casual correction can create a second catalog object or disconnect formats.
Audit the Live Edition, Not Just the Submission
A successful upload proves only that a platform accepted something. Inspect the live or previewed result for:
- title, subtitle, contributor names, and roles;
- primary language and reading direction;
- series name and order;
- cover-to-listing consistency;
- description, categories, and keywords where visible;
- sample content and title page;
- identifier and format association; and
- links between ebook, print, audiobook, or other editions.
Then open the final EPUB in the reading systems in scope. The cross-reader testing guide covers package validation, retailer processing, navigation, fonts, and device checks. Metadata that looks correct on a store page can still be stale or missing inside the downloadable file.
Use One Release Gate for Every Language
Approve a translated ebook only when:
- the edition record identifies the source work and exact target edition;
- target language, title, contributors, identifiers, series data, rights, cover, and description have named owners;
- package metadata passes EPUBCheck and matches the approved record;
- store-specific locked fields were reverified before submission;
- cover, listing, sample, and EPUB display agree on identity;
- platform overrides are documented rather than copied back into the master record; and
- the final live or previewed edition has evidence attached to the release row.
If the interior file still needs translation, use the EPUB translator to create a complete-file draft for review. Metadata localization remains a separate publishing step: translate and review the content first, then make every surface describe that exact edition consistently.
Related Posts
