Quick summary: a table of contents is a 5-minute SEO win
A table of contents (ToC) at the top of a long post is one of those changes that takes five minutes, costs nothing, and measurably improves the engagement signals Google reads. It increases scroll depth (because readers click directly to sections they want), it increases session duration on the post (because they actually finish what they came for), and it increases the chance the same reader returns later (because the post becomes a reference, not a one-time read).
This article covers when to add a ToC, when to skip one, where to place it, the sticky-versus-static question on mobile, the four design rules that make ToCs useful instead of decorative, and how the editor handles it for you.
When to add a ToC (and when to skip)
The threshold the 2026 consensus has settled on:
Add a ToC if: the post is 1,500 words or more, or it has 4+ H2 sections, or it serves as a reference readers will return to. Pillar posts, definitive guides, listicles with more than 7 items, and how-to articles with multiple stages all benefit.
Skip a ToC if: the post is under 1,000 words, has fewer than 3 H2 sections, or is a personal note / opinion piece. A ToC on a 600-word blog post adds visual clutter and signals "this is longer than it is."
Between 1,000 and 1,500 words, use your judgment. If your post has 4+ H2 sections, a ToC will help even at 1,200 words. If it has 3 H2 sections, it does not.
Why ToCs actually work (the data)
A ToC improves several engagement metrics simultaneously, and those metrics map directly to ranking signals Google reads:
Scroll depth. Readers who click a ToC link jump straight to a deep section. That section then registers as "viewed" by the scroll-tracking analytics, raising the average depth across the post.
Session duration. A reader who finds what they came for stays on the page; a reader who scrolls aimlessly leaves. ToCs help the first happen.
Pages per session. Once a reader gets value from one section, they are more likely to click an internal link inside that section.
Return visits. Posts with a clear ToC become reference material. Readers bookmark them. They re-arrive via direct traffic six months later, which is a strong topical authority signal in 2026.
None of these are dramatic individually. Together they move enough engagement metrics simultaneously that the post climbs in the SERP within a few crawl cycles.
Where to place the ToC
The ToC goes after the post's intro paragraph and before the first H2. This is the moment when a reader has decided "yes, this is the topic I wanted" and is about to commit to scrolling.
Three placement mistakes to avoid:
At the very top, before the intro. Skips the hook entirely. The reader sees a bullet list before any prose and bounces.
In the sidebar instead of inline. Sidebars are dead on mobile (which is 60-70% of your traffic). A sidebar ToC works on desktop only and is invisible to most readers.
Inside an H2 section instead of above the first one. Splits the reader's attention exactly when you want them oriented to the whole post.
Tip: if your intro is 3+ paragraphs long, put the ToC right after the first paragraph. The data shows readers decide whether to keep going within the first 100-150 words; the ToC is what cements their commitment.
Sticky vs static (the mobile question)
On desktop, a sticky ToC (one that stays visible as the reader scrolls) improves engagement noticeably because the reader can jump to any section at any moment without scrolling back to the top. On mobile, a sticky ToC at the side of the screen is almost always a UX disaster: it covers content, eats screen real estate, and looks broken.
The pragmatic 2026 default:
Desktop: sticky ToC in the left margin (if your theme supports it) or a "Back to top" button bottom-right.
Mobile: static inline ToC at the top of the post. Add a single "Back to top" anchor at the end of the post for readers who want to skip back.
If your theme cannot do conditional sticky/static, use static inline on both. It is the more important of the two formats.
The 4 design rules of a useful ToC
1. List only H2 sections, not every heading
A ToC that lists H2 + H3 + H4 looks like an outline of a textbook chapter. It overwhelms. Show H2 only by default; expand to H3 only if a single H2 has more than 5 H3 children that are individually navigation-worthy.
2. Use the section's actual headline as the link text
Do not paraphrase. "Why ToCs actually work (the data)" is the H2; that is also the ToC entry. Paraphrasing creates two slightly different versions of the same line, which confuses readers and makes the page feel inconsistent.
3. Anchor links must work on click
This sounds obvious. It is the single most common ToC implementation bug. Every entry in the ToC links to an id on the corresponding H2, and clicking it scrolls smoothly to that section. If smooth-scroll is not available, instant jump is fine; what is not fine is "the link does nothing."
4. The ToC fits on a phone screen without scrolling inside itself
If your ToC has 12+ entries, the post is probably better split into two posts. A ToC that requires scrolling defeats the purpose, which is letting the reader see the whole post's outline at a glance.
How Vlogerly's editor handles ToCs
The editor in Vlogerly generates the ToC automatically from the H2 headings in your post. You do not write the list of links; you write the headings, and the ToC mirrors them at render time. If you add or rename a heading, the ToC updates with no manual edit needed.
For posts over 1,500 words, the ToC is enabled by default. For posts under that threshold, you can toggle it on per post if you want it (for example, a 900-word piece with 5 H2 sections). The mobile and desktop behaviors above are baked in: sticky on desktop where supported, static inline at the top on mobile, "back to top" anchor at the end.
The output is also clean for crawlers: each H2 gets a stable id derived from a slug of the heading, so external sites linking to a specific section (which they will, once the post earns its way to that level) keep working through future edits.
Conclusion
A table of contents on a long post is one of the cheapest engagement wins available. Add one whenever the post is over 1,500 words or has 4+ H2 sections, place it after the intro, keep it to H2-level links, mirror the headline exactly, and on desktop make it sticky if your theme supports it. The combined effect on scroll depth, session duration, and return visits adds up to a measurable SERP lift within a few weeks.
If you want the editor to generate the ToC automatically and handle the mobile/desktop split for you, create your free Vlogerly account. For the broader pre-publish workflow, the 10-step blog post SEO checklist covers the rest of the technical layer.
