Review existing keyword choices against the revised book, especially when topics, equipment, or reader outcomes have been removed. For each phrase, identify the material that still supports the expectation it creates. Retire or replace unsupported terms through the appropriate current metadata workflow. Do not keep a phrase solely because it once fit the book or appeared to attract attention.
Recover the reasoning behind the old phrases
Collect the current keyword worksheet or available metadata record and note why each phrase was originally selected. If the reasoning was never documented, reconstruct only what the evidence supports. A phrase may have described a central topic, a particular audience, or a feature that no longer appears in the revised edition. Keep uncertain explanations separate from decisions you can trace to the previous manuscript.
Compare the old and revised scope before evaluating performance claims. For example, a guide that once covered several craft tools may now focus on a simpler method using fewer tools. A phrase tied to a removed tool can remain related to the general subject while no longer accurately describing the book's useful coverage. The review should ask what the current reader receives, not merely whether the phrase is associated with the broader field.
Map each phrase to current manuscript evidence
Create a short evidence table with the phrase, the expectation it suggests, the supporting chapter or section, and the review decision. Read the cited material rather than assuming that the presence of a word establishes meaningful coverage. A tool mentioned once as an alternative does not necessarily support a phrase that implies a complete guide to using it. The amount and role of the coverage matter.
Include implications about reader level and format. If a phrase suggests advanced instruction but the revised book now explains only an introductory task, the mismatch may concern depth rather than a missing topic. Similarly, a workbook-oriented phrase needs support from the actual material and its usability. Record the specific gap so the decision can be reviewed without relying on a vague judgment that a term feels less relevant than before.

Distinguish retirement from a manuscript repair
An unsupported phrase can lead to different editorial decisions. The author may retire it because the narrowed book is intentional, or restore appropriate material because the removed topic remains essential to the intended promise. Decide which outcome serves the reader before editing the metadata. Do not add a thin paragraph merely to justify retaining an attractive phrase that still suggests more than the book delivers.
Keep that decision connected to the revision brief. If restoring a topic would substantially expand the project, evaluate the scope and dependencies explicitly. A metadata review should not silently undo the editorial reasons for cutting the material. Conversely, it can expose a genuine gap between the intended audience and the revised contents. Use the evidence table to resolve the underlying book decision rather than treating every phrase as an isolated optimization opportunity.
Prepare replacements from the approved scope
Develop replacement candidates using the revised reader task, language, and actual contents. Check them against current KDP metadata guidance and the available workflow for the edition. Avoid importing a new set of popular phrases without repeating the evidence test. Replacing one unsupported term with another does not improve the accuracy of the listing, even if the new term sounds more current or receives a favorable tool score.
Review the description, subtitle, and cover wording for related promises. Retiring a backend phrase does not correct a public description that still advertises the removed material. Coordinate the changes through one approved scope record while respecting the current update rules for different fields. Keep the old values in the change history so you can explain what was altered and why, rather than losing the reasoning as soon as the fields are edited.

Verify the change and maintain the evidence
Record the submitted values and the date of the update. Where public information is affected, compare the available presentation with the intended revision when it becomes visible. Do not assume that every internal keyword value will be exposed publicly for direct inspection. Preserve the actual submission record and use the current platform workflow to investigate discrepancies rather than guessing from a single search result.
Keep the evidence table with the revised manuscript and revisit it after later scope changes. The process does not guarantee discoverability or establish what caused past sales. Its value is a defensible relationship between the words used to represent the book and the material readers receive. A smaller set of well-supported choices is easier to maintain than a historical accumulation of terms whose original purpose no one can explain.
Frequently asked questions
Clear answers for this publishing decision.
Should a keyword remain because it performed well before the revision?
Past observations do not make an unsupported description accurate now. Check what the revised manuscript actually covers and decide whether to restore the material or retire the phrase.
Does mentioning a topic once provide enough support for a phrase?
Not necessarily. Consider the depth and role implied by the phrase. A passing reference can create a different expectation from a sustained explanation or practical method.
Should public copy be reviewed when keywords are retired?
Yes. Related promises may remain in the description, subtitle, or cover. Coordinate the changes with the approved scope so removing an internal phrase does not leave the public mismatch unresolved.
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