How AFFINGER5's table of contents features lifted my blog's time on page

When I first started publishing long-form guides on my WordPress site, readers landed, scanned the first paragraph, and left. Average engagement hovered around thirty seconds. I tried warmer introductions and punchier hooks, yet the numbers barely shifted. Eventually I traced the problem to navigation. Visitors arriving from search results with specific questions had no clear path through my articles.

That realisation pushed me toward a proper table of contents. Rather than installing a separate plugin, I explored what AFFINGER5 already offered. The theme has automatic generation, sticky behaviour, and styling controls without touching code. After three months of testing across travel, blogging, and WordPress guides, the data confirmed what readers had quietly been telling me all along.

This piece covers the practical steps, the metrics, and the small styling decisions behind that shift. It is written for bloggers using AFFINGER5, or anyone wondering whether a theme-built table of contents can outperform a generic plugin. Everything below comes from a site serving Australian readers, where habits and search patterns differ from the US-centric defaults many tutorials assume.

The improvements I measured depend on more than one feature. The table worked because it sat on top of clearer headings, smarter internal links, and slower ad placements. Treat the following as a system rather than a switch you can flip on a Sunday afternoon in Brisbane and expect miracles by Monday morning in Perth.

Switching on AFFINGER5's built-in table of contents

AFFINGER5 ships with a table of contents block that reads the H2 and H3 headings in a post and renders them automatically. Inside the post editor, toggling "Table of Contents" under the AFFINGER settings panel produces a clean list of anchor links within seconds. When I first activated it, I expected a hidden paywall or a confusing menu. Instead the outline appeared above the first paragraph and snapped cleanly into my existing child theme.

What surprised me most was the hierarchy handling. AFFINGER5 indents H3 sub-headings beneath the parent H2 entry, mirroring how readers actually scan. On my relocation articles, where readers jump between visa rules, cost tables, and neighbourhood comparisons, that nesting kept everything readable. I no longer needed to write a custom summary block at the top of every piece.

One quirk worth knowing: the outline only generates once headings exist in the document. Drafts I imported from an older site used bold paragraphs instead of proper H2 tags, and the table silently produced nothing. A quick find-and-replace from bold spans to actual headings fixed the gap. If your archive feels invisible to the feature, that is almost always the reason.

Keeping the outline visible while readers scroll

Sticky positioning produced the most measurable change in my session times. With sticky mode enabled, the table of contents floats at the top of the article once a reader scrolls past the original location. On longer guides about studying abroad in Malta or moving to Okinawa, readers can jump back to a section without scrolling hundreds of lines. The behaviour feels familiar because it mirrors the structure of many Australian university course readers, where the syllabus stays pinned while lecture notes scroll beneath.

I tested both sticky-left and sticky-top variants. Sticky-left performed best for desktop readers in Melbourne and Sydney using larger screens, while sticky-top suited mobile users in Adelaide and regional Queensland. AFFINGER5 lets you enable each independently, which mattered because roughly sixty-eight percent of my traffic arrived on phones.

Beyond convenience, sticky outlines changed how I wrote. Knowing the table was always visible, I began treating each H2 as a destination. I added a short sign-posting sentence at the start of every section, essentially a miniature thesis for each part of the article. The outline acted like a silent editor, punishing vague headings and rewarding clear ones.

Visual choices that nudged readers deeper

AFFINGER5 exposes several styling sliders for the box: border colour, background, font weight, indent style, and toggle button placement. These look cosmetic on paper, but small differences became measurable in scroll-depth reports. A high-contrast border lifted click-through to second sections by roughly twelve percent compared to a faded outline.

I also stopped using the default toggle and let the box stay open. The reasoning came from observing how readers behave on long Australian travel pages. Visitors arriving from a Sydney-to-Melbourne train guide wanted to gauge length before committing. Showing the full structure upfront built trust faster than a hidden button they had to discover first.

Colour mattered more than expected. I matched the border to my site's accent colour, a muted eucalyptus green that nods to the gum trees visible from my Brisbane home office. Australian readers tend to respond well to natural tones on personal blogs, and the consistency helped the table feel like part of the page. Fonts stayed at the default body size, keeping the outline feeling like content rather than a side rail.

Reading the numbers without fooling myself

Time on page can mislead if you over-index on one article. I tracked changes across a thirty-post batch covering Okinawa relocation, Malta study programmes, and WordPress tutorials. Before enabling the table, average session time across the batch sat around one minute and twelve seconds. Three months in, the same batch averaged two minutes and forty-one seconds. Scroll depth on the longest guides climbed from forty-two percent to sixty-one percent.

None of that came from traffic changes alone. I cross-referenced results against Search Console impressions and organic click counts, both of which held steady in the AEST afternoon window when my largest segment of Australian readers browses during work breaks. The improvement was behavioural, not circumstantial. Visitors who used the table interacted with an average of three sections per visit, compared to one and a half before. Australian readers seemed comfortable with the anchor-list pattern, mirroring the way local council sites and university pages present their information.

Tracking also revealed one unexpected outcome. Posts where I left the table disabled performed worse than the same posts with it on. Once readers encountered the feature across the site, returning visitors expected it. Removing it created a small but persistent drop in repeat visits, which I only noticed because I run monthly benchmark reports from my Brisbane office.

Working the table into a wider workflow

The feature shines when it slots into an existing content rhythm. I treat each draft as three layers: the heading hierarchy the table reads, the body content that delivers value, and the internal links connecting each section to older posts. AFFINGER5 plays well with this because its anchor IDs are generated from heading text, which makes cross-linking painless.

If you plan to introduce the table across an established archive, start with the ten longest posts. Migrating older content takes patience, but the lift in dwell time on detailed evergreen guides is where the strongest gains appear. Posts shorter than roughly eight hundred words did not benefit noticeably, which matters if you maintain a news-style section alongside deep guides.

One habit I now keep is drafting the table before writing the body. Filling in the outline first forces a clearer argument and exposes research gaps early. It pairs naturally with the way Australian audiences tend to reward depth over volume in niche blogging categories. Readers in more remote parts of Western Australia or Tasmania access the same content on slightly slower connections, which is another reason a lightweight theme-built table of contents tends to outperform heavier third-party plugins.

Adjustments that kept paying off

Most readers of this site sit across New South Wales, Victoria, and Queensland, and the feature behaves predictably across all three states. Adjustments that paid off here may need a quick A/B test on yours, particularly if a larger share of your audience reads at unusual hours or relies on patchy mobile coverage in regional areas across the country.