
The KDP Book Launch Checklist: What to Finish Before You Publish
Use an eight-week KDP launch checklist covering manuscript, cover, metadata, files, ARC outreach, ads, pre-orders, publication timing, and post-launch measurement.
Most launch failures are preparation failures: tasks that were either never done or done too late to have their intended effect. The author who starts ARC reader recruitment two weeks before launch instead of six weeks before, who finalises their categories the day before publishing instead of a week before, or who writes their book description in the hour before hitting publish is working against themselves at every stage. This checklist is designed to be worked through in sequence, starting eight weeks before your planned publication date, so that by the time you press publish everything is in place and the launch executes on a foundation of prepared assets rather than last-minute improvisation.
Use this checklist with the KDP publishing timeline, manuscript preparation checklist, and post-release launch momentum guide. They cover production readiness, KDP timing, and what happens after publication.
Use this checklist with the KDP publishing timeline, manuscript preparation checklist, and post-release launch momentum guide. They cover production readiness, KDP timing, and what happens after publication.
Eight Weeks Before: Lock the Production Plan
Finish the manuscript and schedule editing/proofreading, cover design, formatting, and any illustration or indexing work with real buffers. A launch date is only useful if it protects quality. If the final text is still moving, treat the date as provisional rather than forcing the book through production to preserve a calendar promise.
Confirm format strategy, trim size for print, and whether you need your own ISBN. Start keyword and category research now, but keep the final choices open until the positioning, description, and competitor set are clear. Professional manuscript proofreading should be completed before final pagination so corrections do not keep reflowing the print file.
Six Weeks Before: Build the Store Assets
Finalize the cover direction, title/subtitle, author name, description, keywords, categories, pricing plan, and author-page assets. Test the cover at thumbnail size and compare it with current books serving the same reader. Make sure every claim in the description is actually supported by the book.
Use KDP Keyword Research to validate search ideas and the cover design guide to check genre signals. Do not stuff metadata with terms simply because they have volume; relevance and shopper fit come first.
Create a single launch asset sheet containing the approved title, subtitle, description, short blurb, author bio, retailer links, cover files, series order, keywords/categories, and image assets. This reduces the risk of different versions appearing in ads, social posts, ARC messages, and retailer metadata.
Four Weeks Before: Create the Final Files and Reader Plan
Move the clean manuscript into the chosen formatting workflow and create separate digital and print files where required. Preview the EPUB in Kindle Previewer and inspect the print PDF page by page. Finalize the print interior before the full-wrap cover because page count determines spine width.
If you use advance readers, give them enough time to read voluntarily and make clear that honest feedback is welcome. Do not buy positive reviews, require a particular rating, or make a gift conditional on posting a review. Build a launch team around genuine readers, not a review quota.
Two Weeks Before: Upload With a Buffer
Upload early enough to handle file warnings, preview problems, metadata corrections, and KDP review time. If you are using a Kindle eBook pre-order, do not treat the final manuscript deadline as your target upload time. KDP requires the final manuscript to be submitted more than 72 hours before release, and missing the deadline can cancel the pre-order and restrict future pre-orders.
A placeholder manuscript is not a safe launch workflow. Upload the real production file, verify the preview, and leave time to correct it. For print, order a proof copy if the schedule allows and inspect margins, page order, image quality, running heads, cover alignment, and barcode area in a physical object.
Launch Week: Make the Book Easy to Find and Buy
Check that the correct editions are live and linked, the description and cover display correctly, pricing is as intended, and any planned ads or audience messages point to the right product page. Keep the launch message simple: who the book is for, what it offers, and why the reader should care now.
Record a baseline before changing things midweek. Save the live description, keywords, categories, price, ad setup, sales, and any rank-tracking evidence. That snapshot makes later optimization much more useful because you can distinguish the launch configuration from subsequent changes.
Test every link from a reader’s perspective, including mobile. If you are advertising multiple formats, make sure the landing page does not accidentally send paperback shoppers to the Kindle edition or send international readers to the wrong marketplace.
Weeks 2-4: Read the Evidence Before Editing the Listing
After release, compare traffic, clicks, sales, reviews, read-through, ads, and keyword visibility. If the book is getting impressions but not clicks, cover/title positioning may need attention. If it gets clicks but weak sales, examine the description, sample, price, format quality, and audience fit. If reach is weak, focus on discovery and promotion.
The launch momentum guide covers this phase in more detail. Avoid changing keywords, cover, description, ads, and price simultaneously: you will lose the ability to learn from the result.
Weeks 5-8: Move From Launch to Operating Rhythm
By this point, the launch should become a repeatable publishing routine. Keep the campaigns and channels that produce qualified readers, stop activities that generate attention without meaningful outcomes, and schedule the next listing, ad, or backlist review based on evidence.
If the book belongs to a series or larger catalog, update back matter and cross-promotion so the new title supports existing books and vice versa. The backlist strategy helps turn a launch into longer-term catalog value.
Document what you learned while it is still fresh: which audience messages produced clicks, which search terms converted, which launch tasks were late, and which channels consumed time without producing reader action. That post-launch record makes the next book cheaper and easier to launch.
Frequently Asked Questions
How far ahead should I plan a KDP launch?
Eight weeks is a useful working runway for many independent authors, but complex books may need much longer. Quality and production dependencies should set the schedule.
Can I upload a placeholder manuscript for a Kindle pre-order?
Do not build the workflow around a placeholder. KDP has strict final-manuscript deadlines and late changes can jeopardize the pre-order. Upload the real production file with a safety buffer.
How early must the final Kindle pre-order manuscript be submitted?
KDP currently requires it more than 72 hours before the scheduled release. Allow more time than the minimum for validation and corrections.
Should I ask ARC readers for five-star reviews?
No. Ask for honest, voluntary feedback and never condition compensation, gifts, or access on a positive review or specific rating.
Should I change the listing immediately if launch sales are weak?
First identify whether the problem is reach, clicks, conversion, price, production quality, or audience fit. Make the smallest evidence-based change you can measure.
What to Do Next
Put the launch date at the end of a dependency map, not the beginning. Work backward through final files, proofing, cover, metadata, reader outreach, and KDP review buffers, then move the date if any critical production step no longer has enough room.
Finish the text before you lock the production files. Vappingo’s qualified native-English editors can proofread the manuscript and publication-facing copy so formatting and upload are built on a clean source.