usdigitalmarketingindex.com SEO
When does a long informational page benefit from a linked table of contents?
Updated November 15, 2026
A linked table of contents helps when the page has several sections that different readers want for different reasons, when those sections are far enough apart that reaching one means real scrolling, and when the section headings are specific enough to choose between. It does not help on a short page, on a page read straight through from top to bottom, or on a page whose headings are too vague to act as a menu. The decision is about how the page is used, not about its word count alone.
Navigation burden and article length
Ask how readers move through the page.
| Condition | Evidence | Outcome |
|---|---|---|
| Several independent sections; readers come for one of them | Reference guides, comparisons, long FAQs; varied queries in Search Console | Add a table of contents |
| A sequence where each part depends on the last | Tutorials, narratives | Not needed where numbered step headings do the work |
| Three or four sections visible within a couple of screens | Page length on a phone | Unnecessary |
| A long page with a dozen sections | Count of H2 headings | Add one, listing H2s only |
| A page that people return to | Documentation, policies, glossaries | Add one |
| Headings that are generic or clever | Read the headings alone | Fix the headings first; a list of vague labels helps nobody |
Phones raise the burden. A page that needs four scrolls on a desktop can need fifteen on a phone, so judge the need on the smaller screen.
If the honest answer to the reader’s question fits in a few paragraphs, the better fix may be a shorter page and not a navigation aid. That choice is covered in the guide to when a short direct answer is more appropriate than a long-form guide.
Meaningful section labels
A table of contents is exactly as good as the headings it lists, because it is those headings. Before adding one, read them in a list and check each.
- Does it say what the section contains?
- Could a reader choose it over its neighbors?
- Is it short enough to scan?
- Is it written in the same form as the others?
The mockup below shows a table of contents for a representative long guide. The page is a made-up example.
Title: Heat pump rebates: a homeowner's guide
On this page
Who qualifies
How much you can receive
Equipment that is eligible
How to apply
When payment arrives
Combining rebates with tax credits
If your application is rejected
[Section headings on the page match these labels word for word]
Each label is a question a reader might arrive with. A version reading Overview, Details, Process, More, and Conclusion would be a list of links to nothing in particular.
List the main sections only. Adding every subheading turns a seven-line menu into thirty lines that need their own scrolling.
Anchor behavior
The links in a table of contents point to places within the same page. Five details decide whether they work.
- Each target heading has a stable identifier. Generate it from the heading text once, and do not let it change when the heading is reworded, or links from elsewhere will break.
- Identifiers are unique on the page.
- Activating a link moves both the view and the keyboard focus to the section.
- A fixed header at the top of the screen does not cover the heading after the jump.
- The browser’s back button returns the reader to where they were.
Search engines treat these links as pointers within one page. Google’s URL guidance says not to use fragments to change the content of a page, because “Google Search generally doesn’t support URL fragments” (Google’s URL structure guidance). A table of contents uses fragments for their proper purpose, which is navigation to content that is already in the page.
Access and usability checks
Test the finished component the way readers will use it.
- Keyboard: can every link be reached with the Tab key and activated with Enter, and does focus land on the section?
- Screen reader: is the list announced as navigation with a label such as On this page, and do the link texts make sense when read alone?
- Phone: is the list usable without covering the content? A collapsed list that opens on request suits long menus.
- Position: does it come after the opening answer? A reader should get the page’s main point before being offered a menu.
- Accuracy: does every link land on the heading it names, and does every main heading appear in the list?
- Maintenance: when a section is added, removed, or renamed, is the list updated automatically or by a step in the editing process?
The W3C’s accessibility guidelines include a criterion that link purpose be determinable from the link text alone or together with its context, and another that more than one way be available to locate content within a set of pages (W3C Web Content Accessibility Guidelines 2.2). A clear in-page menu supports the first directly.
Two cautions. A table of contents does not rescue a page that should have been several pages. If the sections serve unrelated needs, splitting may be the better answer. And it should not push the answer down. Placed above the first paragraph, a long list delays the content it is meant to speed up.
A table of contents links within one page. Linking from another page to a specific section is a separate technique with its own considerations, discussed in the guide to when internal links should point to a section through a URL fragment.
The criterion: add a table of contents when a reader arriving with one question could not find its section in two scrolls, and the headings are good enough to show them the way.
Add your comment to this answer