StoryHelm
Learn  /  Publishing  /  Self-Publishing a Series on KDP
How-To Guide

Self-Publishing a Series on KDP: a Continuity and Quality Checklist

SO By Scott Ohlund, Founder Updated June 24, 2026 12 min read Publishing
Before you upload book N to KDP, run two passes. The craft pass checks that the story holds together with the books already published: characters, places, and timeline stay consistent across the whole box set. The metadata pass checks that the listing tells the truth: the series page, blurb, also-by links, and front and back matter all point to the right books in the right order. The first pass protects the reading experience. The second protects the sale. Skip either and the book ships with a flaw a reader will catch.

Two different things break a series launch on KDP, and they fail in two different places. Craft problems live inside the prose: the smuggler whose name was Cael in book two and Caleb in book four, the harbor town that sat north of the capital and then somehow south of it. Metadata problems live in the dashboard: a series page that lists book three before book two, an also-by link pointing at a retired edition, a blurb that promises a romance subplot you cut in revision. This checklist separates the two so you fix each in the right place. The craft work happens in your manuscript; the metadata work happens in your KDP account. The fixes are not interchangeable, and a clean manuscript with a broken listing fails just as visibly as a contradiction in the prose.

1

Run a continuity audit against the books already out

The most expensive errors in a series are not in the book you are about to publish. They are the contradictions between that book and the ones readers already own. Before book four goes up, read it against books one through three as a single body of work, not on its own. A reader who bought the first three holds you to every fact in them.

A pre-publish continuity audit answers three questions about the new manuscript:

This is craft, not metadata. No KDP setting fixes a continuity error. The only fix is an edit to the manuscript, in your own words, before the file is final. See the full method in the continuity audit guide.

2

Confirm character, place, and timeline facts hold across the set

Continuity at series scale lives on three axes, and almost every series-breaking error sits on one of them. Walk each before you publish, with the earlier books open beside the new one.

Characters

Names, spellings, aliases, eye and hair color, age, and relationships. A spelling holds from first mention to last, and a character buried in book two does not speak in book four.

Places

Geography and travel times that stay fixed. A harbor north of the capital in book one is still north of it in book four, and the road still takes three days.

Timeline

One chronology across the whole series. The war that ended five years before book one cannot still be raging in a book-three flashback set after it.

A cross-book contradiction is invisible until the two pages sit side by side:

Book 1, ch. 3: “Joran lost the sight in his left eye at the bridge, and wore the patch ever after.”

Book 4, ch. 11: “He fixed her with a hard look, his right eye narrowing under the leather patch.”

The patch moved. A reader who remembers the bridge will notice, and a continuity audit catches it on the page before the file goes up.


3

Check the front and back matter on this book

Front and back matter is where the craft work and the listing meet. It sits inside the file you upload, but its job is to point correctly at the rest of the series, so a stale link or a wrong reading order does the same damage as a metadata error. Go through it line by line.

Reading order is easy to get wrong. If your back matter lists book three before book two, a new reader starts in the wrong place, gets spoiled, and abandons the series. This is a copy-and-paste error that costs you the whole rest of the run.

4

Make the series page and also-by links agree

This step is pure metadata, and it happens in your KDP account, not in the manuscript. Amazon builds a series page automatically when you assign each book to a series with a number. That automation only works if you feed it consistent data. One mismatched series name and a book orphans itself off the series page.

None of this touches your prose. It is bookkeeping in the dashboard, and it is where a clean manuscript still loses sales: the story is consistent, but the storefront is not.


5

Match the blurb to the book you actually wrote

Blurb accuracy is a quiet continuity problem. Authors write the blurb early, from the outline, then revise the book and forget to revise the blurb. The result promises a story the file no longer tells, and "this is not the book the description sold me" is one of the most damaging review lines on Amazon.

Be honest about what tooling does here. A continuity tool checks the manuscript against itself and against the series. It cannot read your KDP blurb field. Matching the blurb to the final book is a human read, done with the finished file open beside the description.

6

Audit the box set as one object before you bundle

A box set is not three files in a folder. It is one product a reader experiences in a single sitting, which means contradictions that hid across separate purchases now sit a few hundred pages apart in the same book. Before you compile and upload the bundle, audit the whole set as one manuscript.

The box set is also your best chance to catch older drift, because a reader going straight through will see in one afternoon what took three separate launches to bury. So run the full continuity pass on the compiled file, the same pass you would run on a new manuscript. The backlist and box set audit guide walks the full pass.

How StoryHelm checks this

StoryHelm handles the craft half of this checklist, not the metadata half. It reads and analyzes your manuscripts; the author writes every word. It extracts a structured Canon from your finished books and carries it across the whole series in a shared Series Atlas, so a pre-publish audit checks book N against everything already out.

The Coherence Guardian flags the name, place, and timeline contradictions from steps 1, 2, and 6, and shows you the conflicting passages side by side with a severity rating, so the cross-book slips surface before the file ships. You read the findings and make every edit yourself, in the built-in editor or your own writing tool. What an AI continuity check actually does explains the boundary.

What StoryHelm does not touch: your KDP series page, your also-by links, your blurb field, or your back-matter URLs. Those live in your account, and the listing work in steps 4 and 5 is yours to verify by hand. StoryHelm makes sure the story holds together; the storefront stays in your hands.

Craft or metadata: where each check lives

CheckWhere you fix itTooling can help
Cross-book continuityIn the manuscriptYes, reads and flags it
Character, place, timeline factsIn the manuscriptYes, side-by-side passages
Front and back matter orderIn the manuscript filePartly, names the right order
Series page and also-by linksIn your KDP accountNo, a human dashboard check
Blurb accuracyIn your KDP listingNo, read against the final file
Box set as one objectIn the compiled manuscriptYes, audit the set together

The honest line: a continuity tool reads the story, not the storefront. It saves you the craft audit. The metadata audit is still a careful pass through your own KDP dashboard.

Keep reading

Pillar

Publishing a Series, the Business Side

The launch, listing, and backlist decisions that turn a finished series into a working storefront.

Read
How-To

Run a Continuity Audit Before You Publish

The full pre-launch pass: what to check, how to rank what you find, and what to actually fix.

Read
How-To

Audit a Backlist Before You Bundle a Box Set

Read the whole series as one manuscript and catch the drift a box set puts in plain sight.

Read

Part of the StoryHelm Learn library: the craft and business of shipping a series readers trust.

Clear the continuity gate

Clear the craft pass before you hit publish on KDP.

StoryHelm reads book N against every book already out, builds your canon, and points to the exact chapter where the patch jumped eyes or the timeline slipped, so the contradiction surfaces before the upload, not in a one-star review from the reader who bought all three. You read the findings and make every edit in your own words.

Request a founding seat
Founding cohort forming now · No spam, unsubscribe anytime · It never writes your prose