Why Won’t My Table of Contents Links Work in My KDP Ebook?
A table of contents that looks fine on the page can still fail the reader completely — because Kindle checks two different maps, not one.
Your table of contents links are broken for one of two reasons: the visible TOC page is pointing to the wrong location because your chapter headings changed after the TOC was built, or the ebook is missing its NCX — the hidden navigation file that powers the “Go To” chapter menu on Kindle devices and apps. They’re two different systems, and a fix for one doesn’t touch the other.
That’s the part that trips people up. A TOC can look perfect scrolling through the file and still fail the reader completely, because the page you see and the menu Kindle uses behind the scenes aren’t the same thing.
My name is Daniel J. Middleton — I’ve spent close to twenty years formatting books for indie authors and publishers, and when it comes to ebooks, I build them by hand in HTML and CSS rather than running a manuscript through an automatic converter.
That’s exactly why this problem is easy for me to spot from the outside: it’s one of the most common navigation failures I see when I’m asked to look at an ebook built somewhere else, and it almost always traces back to how the file was converted, not anything wrong with the content itself.
This article walks through what the two table-of-contents systems on Kindle actually do, why links go stale or vanish, and how to check both before you publish.
What’s the Difference Between the Visible TOC and the NCX?
Every Kindle ebook can carry two separate navigation structures, and confusing them is the root of most TOC complaints. The HTML TOC is a real page inside your book — readers scroll to it and tap an entry to jump to that chapter, the same way a print TOC works, just clickable. The NCX (or, in newer EPUB 3 files, the navigation document) is invisible. It’s what populates the “Go To” menu Kindle apps and devices use to jump around a book without paging through it.
A file can have one without the other. A visible TOC page with no working NCX will still show a table of contents when a reader scrolls to it, but the Kindle menu’s chapter list will be empty — and that’s specifically what triggers KDP’s “Navigation-Missing_NCX” quality notice.
A working ebook needs both: a visible TOC page for readers scrolling through, and a working NCX or navigation document for the Kindle menu. They fail independently, and a fix for one won’t repair the other.
Why Do TOC Links Point to the Wrong Chapter?
This is almost always a timing problem, not a coding problem. If you built your table of contents in Word using References → Table of Contents, that TOC is a field code — a snapshot of your heading structure at the moment you generated it, not a live link that updates itself. Edit a chapter title, add a scene break, or reorder a section afterward, and the TOC still points to where that heading used to be until you click inside it and refresh the field.
The same thing happens on the EPUB side. If your conversion tool built the navigation file from an earlier draft, or if a heading style got applied inconsistently — Heading 1 on some chapter titles, plain bold text on others — the converter has no way to know which text is a chapter start and which isn’t. The result is a TOC that looks complete but sends readers to the wrong page, or skips a chapter it never recognized as one.
A working ebook needs both: a visible TOC page for readers scrolling through, and a working NCX or navigation document for the Kindle menu.
Why Is My NCX Missing Even Though the TOC Looks Fine?
This is the version that catches people off guard, because the book previews fine and the visible TOC page works — right up until Kindle’s “Go To” menu comes up empty. It usually comes down to how the file reached KDP in the first place.
A .docx upload relies on KDP’s own converter to generate the NCX from your heading styles, and if those styles are missing or inconsistent, the conversion can produce a visible TOC without ever building the navigation file behind it. A hand-built or third-party EPUB has the same failure point if the navigation document was left out or malformed during export.
Fiction and nonfiction are held to the same standard here — KDP’s navigation requirement doesn’t relax for novels just because most fiction readers page through front to back. The menu is still expected to work if a reader chooses to use it.
Where Should the TOC Page Go in the File?
Placement matters more than most authors expect. KDP wants the visible HTML TOC positioned near the front of the book — not buried in back matter — so a reader paging through from the start reaches it naturally. Incorrect placement doesn’t just look odd; it affects the accuracy of the “Last Page Read” feature and can keep the TOC from appearing in the free sample a shopper downloads before buying.
How Do You Actually Test Whether It Works?
Scrolling through your own file won’t catch either failure mode — you already know where your chapters are. The only reliable check is Kindle Previewer, Amazon’s free desktop tool:
Open the file in Kindle Previewer, not just your EPUB editor or Word.
Check the panel on the left side of the preview window. If your chapter list appears there, the NCX or navigation document is working. If that panel is empty, it isn’t — even if the visible TOC page inside the book looks correct.
Click every entry on the visible TOC page and confirm each one lands on the right chapter, not just the right general area of the file.
If you edited anything after building the TOC in Word, click inside the TOC field and press F9 to refresh it before converting, or regenerate it entirely if the heading structure changed.
If you’re formatting by hand in HTML, confirm your chapter headings all use consistent, correctly nested heading tags — that consistency is what lets a converter recognize where each chapter starts.
If the Previewer’s left-hand panel is empty and you’re not comfortable editing EPUB navigation code directly, that’s the point to hand the file to someone who is — patching a missing NCX after the fact usually means opening the EPUB’s internal files, not adjusting anything visible in Word.
What Should You Do Next?
If Kindle Previewer shows a working chapter menu and every visible TOC link lands correctly, your navigation is fine — the reader complaint, if you’re getting one, is coming from somewhere else. If the menu is empty or the links are wrong, the fix lives in the file’s navigation structure, not in the page you can see. Rebuilding that is faster with the right tools than it looks from the outside.
If you’ve checked both and you’re still stuck, get in touch and let’s find out what the file is actually doing.
Have questions about book design or branding? Leave a comment below and let's discuss how to make your book irresistible to your target readers.
