EPUB TOC and Navigation Checklist

Most EPUB ingestion problems start with navigation drift. This checklist helps you keep chapter order, TOC links, and reading flow stable across export, validation, and device checks.

Build TOC from clean heading structure

Use consistent heading levels for chapter titles and major section breaks.

Avoid manual visual-only headings that look right but are not structural markers.

A clean heading hierarchy is the foundation for reliable EPUB navigation files.

Check chapter order and link targets

Open the EPUB and click every TOC entry in order from first to last chapter.

Verify links jump to the correct heading and not to prior or duplicate anchors.

Include front and back matter entries only when they are intentionally part of reader navigation.

Validate navigation before distribution

Run EPUB validation after every structural edit that changes headings or section order.

Treat missing-nav, duplicate-anchor, and broken-link warnings as release blockers.

Fix source manuscript structure and export again instead of patching EPUB internals manually.

Run a short device QA pass

Spot-check the same file in at least two reading environments before upload.

Confirm navigation opens quickly, chapter starts look correct, and back matter links resolve.

Save one validated release EPUB and upload that exact file to your distributor.

Numbers and Reference Tables

Navigation QA Matrix

Checkpoint Pass signal Common failure
TOC click-through Every entry opens expected chapter start Entries jump to wrong heading or duplicate anchor.
Front/back matter links Only intentional sections appear in navigation Empty or placeholder sections show up in TOC.
Chapter sequencing Reader advances in expected order One chapter appears out of order after export.
Multi-reader check Same navigation flow in two readers One reader shows missing or broken navigation links.

Publish Checklist

  1. Use consistent chapter heading levels in source manuscript.
  2. Remove duplicate or placeholder headings before export.
  3. Export fresh EPUB from the latest manuscript state.
  4. Click through every TOC entry sequentially.
  5. Verify chapter start positions after each TOC jump.
  6. Confirm front/back matter links are intentional and accurate.
  7. Run EPUB validation and treat navigation warnings as blockers.
  8. Check the same EPUB in at least two reading environments.
  9. Fix source structure, then re-export and revalidate.
  10. Archive one final validated EPUB for distributor upload.

Warning-to-Fix Map

Warning pattern: navigation document missing

Fix: Rebuild export from a manuscript with recognized heading structure.

Verify: Validator confirms navigation document is present.

Warning pattern: TOC entry opens wrong chapter

Fix: Normalize duplicate headings or malformed anchor targets in source.

Verify: Each TOC entry jumps to the intended chapter heading.

Warning pattern: duplicate anchor id

Fix: Ensure each chapter/section heading produces a unique target.

Verify: Validation no longer reports duplicate identifiers.

Warning pattern: dead link in back matter

Fix: Correct link targets and remove stale references before re-export.

Verify: All navigation and internal links resolve without errors.

Warning pattern: chapter order changed unexpectedly

Fix: Review manuscript section ordering and regenerate EPUB from the corrected sequence.

Verify: Reader next/previous flow matches intended order.

Warning pattern: warning remains after fix

Fix: Confirm distributor/validator is using the newest exported file.

Verify: Renamed latest EPUB returns clean navigation checks.

The Senswriter way (faster)

Use the same workflow in one workspace: draft, export, run checks, fix source, and publish one clean release-candidate file.

Open the Senswriter Workspace and see export examples.

Frequently Asked Questions

Why can TOC look correct but still fail validation?

Visual TOC rendering can hide structural issues like duplicate anchors or missing nav metadata that validators still detect.

Should I edit EPUB files directly to repair navigation?

Only as a last resort. Source-first fixes are safer and prevent the same issue from returning on later exports.

When should I rerun navigation checks?

After any change to chapter order, heading text, or front/back matter sections.

Sources and Claim Checks