An author opens a newly exported ebook and admires its contents page. The chapter titles are correct, the spacing is tidy and every link on that page works. Later, a reader opens the reading app’s contents menu and finds that a newly added chapter is missing. The author checked one route into the book; the reader used another.
This is a hypothetical publishing problem, but the distinction is real. For independent authors, an ebook’s navigation deserves its own editorial review. A contents page helps someone explore the book from the beginning. The app’s menu gives them another way to choose where to read.
Understand the two routes
Amazon’s guide to creating a contents navigation document distinguishes a logical table of contents, accessed through Kindle’s Go To menu, from an HTML contents page within the book. Amazon requires a working contents structure for ebooks with chapters or sections; its guide identifies the logical version as required and the visible page as strongly recommended.
For EPUB, the EPUB 3.3 specification, a W3C Recommendation dated 13 January 2026, requires a navigation document containing a table-of-contents element. That document can also appear in the book’s reading order. The two reader-facing routes can therefore share one source; they do not necessarily require two separately maintained lists.
When commissioning formatting, ask the formatter to demonstrate both routes in the exported edition. Agree what readers should find, then inspect each presentation. A polished screenshot of the contents page provides evidence about its appearance, while opening the app’s menu reveals the structure offered there.
Agree the editorial map before formatting
Consider a fictional practical guide with two parts: Planning Your Workshop and Running the Day. Each contains three chapters, followed by a resources section. Decide where those parts, chapters and resources belong in the navigation before designing the page.
The labels should help a reader make a choice. “Materials and Equipment” communicates a different destination from “Getting Ready”, even if either could be a valid chapter title. Choose the label that fits the manuscript and its intended audience. Keep an evocative title where it serves the work, but consider whether an accompanying descriptive phrase would make the route clearer.
Avoid adding every short aside as a separate menu destination simply because the formatting tool permits it. Equally, do not hide a substantial resources section inside a vaguely named final chapter. These are editorial decisions about how people will use this particular book, rather than a universal rule for how many entries a menu needs.
Carry changes through the source
For Word-based Kindle preparation, Amazon’s navigation guidelines recommend using Word’s heading styles and table-of-contents feature. Follow the documented preparation method for your actual export tool. A heading’s visual size alone does not tell you whether the exported navigation contains the intended destination.
If you ask AI to propose a new chapter order or clearer titles, treat its output as an editorial proposal. Once approved, carry the changes through the manuscript, the visible contents and the menu structure. In our fictional guide, moving Materials and Equipment into the planning part should leave the reader with a consistent route to that chapter.
Keep a simple reference list of the approved entries and their intended hierarchy. It gives the author, editor and formatter something concrete to compare with the exported book. Resolve disagreements about structure there, before fixing the same inconsistency in several places.
Distinguish chapter links from print page references
Amazon’s navigation guidelines advise leaving page numbers out of the HTML contents list, explaining that Kindle pages do not always correspond directly to a physical edition. Use the chapter or section link to take the reader to the material. Copying a printed contents page with dotted lines and page numbers does not establish that route.
EPUB provides a separate page-list mechanism for navigation to static page boundaries, which may correspond to a print edition. If your project needs print-page referencing, ask the formatter which edition the mapping represents and how readers can use it. Keep that requirement distinct from the chapter menu; the two navigational jobs deserve separate checks.
Inspect the menu without the page’s decoration
The EPUB Reading Systems 3.3 Recommendation, dated 17 October 2024, requires conforming reading systems to expose the contents links and headings, whether or not the navigation document appears in the reading order. It also permits dynamic pagination for reflowable content. These are requirements and capabilities defined by the standard, rather than proof of how every app behaves.
EPUB’s authoring guidance also warns that app-generated navigation interfaces may lose styling, images and other rich presentation. Read your menu as plain labels. If readers need a purple heading, decorative icon or indentation visible only on the contents page to understand an entry, consider how to make its meaning clearer in the menu.
For the fictional workshop guide, a label such as “Resources” should remain understandable when shown without the illustrated banner above it. Ask a reviewer to locate a particular chapter using the menu alone, then explain which label helped them choose it.
Review the exported edition systematically
Use the approved reference list to inspect the file intended for distribution. Suggested review steps are:
- Open the contents page and the reading app’s navigation menu independently.
- Compare the entries, titles and part–chapter relationships with the approved manuscript.
- Follow each entry and read the destination heading and opening paragraph.
- Look for missing chapters, duplicate entries and different labels that unexpectedly lead to one destination.
- Repeat representative journeys in the reading apps or devices relevant to the edition, recording the file revision and what was checked.
These are proposed checks, not a report of a tested ebook. A successful jump means more than arriving somewhere in the correct chapter file: examine whether the destination gives enough context to begin reading. Check any included reference sections as deliberately as the opening chapters.
Where the book also uses notes, review that separate journey using MaryChuks’ guide to ebook footnotes and returning to the sentence. A clear chapter menu and useful note links support different reading tasks.
After revisions, produce a fresh export and revisit affected entries and their neighbours. Keep the reviewed file identifiable so the approved version can be distinguished from earlier exports. Finish by asking a reader to find a chapter, begin reading and choose another section. The contents review is complete when the book’s structure works through both routes.
Sources
- Amazon KDP: Create a Table of Contents with a Navigation Document.
- Amazon KDP: Navigation Guidelines.
- W3C: EPUB 3.3, Recommendation, 13 January 2026.
- W3C: EPUB Reading Systems 3.3, Recommendation, 17 October 2024.
Guidance checked on 26 October 2026. The Amazon pages do not display publication dates. The workshop guide and suggested review process are illustrative.
Discover more from Marychuks.com AI, Psychology, Business & CreativeVerse
Subscribe to get the latest posts sent to your email.
2 thoughts on “Ebook Contents: Check the Page and the Reading Menu”