A table of contents built from your page’s existing headings gives visitors quick, clickable navigation through long content — useful for lengthy articles or guides — and since it’s generated from headings already on the page, it doesn’t require new content, just the technical implementation of the navigation feature itself.
Table of contents implementation
A table of contents generated from headings already on the page — no new content needed.
- Full backup taken before we start
- If we can’t fix it, you get your money back
- We never ask for your own password
What we need from you
- Confirmation of which pages or post types should have a table of contents
- Confirmation your content’s existing headings are structured correctly (proper H2/H3 hierarchy), since the table draws directly from them
- Your preference for where the table displays (top of the page, a floating sidebar) if you have one
This or something else?
| You want a table of contents that automatically builds from your existing page headings | This fix covers it |
| Your existing heading structure itself is inconsistent or needs correcting first | Worth addressing that first — a table of contents built from a messy heading structure will reflect that same mess |
| You want a manually curated table of contents with different wording than your actual headings | Worth describing this specific need — a more custom, content-driven approach than an automatically generated one |
| You want semantic HTML remediation more broadly, not just a table of contents feature | Semantic HTML remediation for extractability, in the Schema & Machine Readability category |
What we do
- Confirm which pages or post types need the feature
- Verify existing heading structure is suitable for automatic table generation
- Implement the table of contents feature, generating from existing headings
- Style it to match your site’s design
- Verify it displays and functions correctly, with working jump links to each section
- Check function and display on mobile
What is included
- A table of contents feature implemented, generated from existing page headings
- Styling matched to your site’s design
- Verified working jump links to each section
- Confirmed mobile display and function
Not included
- Correcting an underlying inconsistent or incorrect heading structure — worth addressing separately first if that’s the actual issue
- Writing custom table of contents entries that differ from your actual headings
- Retroactively adding this to every page unless the full scope is specified upfront
- Ongoing maintenance as heading structures change, beyond the automatic generation itself
Questions about this fix
Does this require me to write anything new?
No — since the table of contents is generated automatically from your existing page headings, it doesn't need new content, just correct technical implementation of the navigation feature.
What if my headings aren't structured very consistently right now?
We'd flag this, since an automatically generated table reflects whatever heading structure actually exists — a messy or inconsistent structure would produce a correspondingly messy table of contents.
Can I choose which headings appear in the table and which don't?
Depending on the implementation method, some level of control is often possible (like excluding certain heading levels) — worth telling us your preference if you don't want every single heading included.
Will this slow down my page's loading?
A table of contents feature is generally lightweight and shouldn't cause a noticeable loading impact.
Can this apply automatically to every new post I publish going forward?
Depending on how it's implemented, yes, often it can apply automatically to specified post types going forward, rather than needing to be added manually to each new post.
Related fixes
If this is the second time this year
A bad update breaking the site is a symptom of updates not being tested first. Care plans run every update on a staging clone before it reaches your live site, which is the actual fix for this happening again.
Your access, your rules
Create a separate admin account for us and delete it when we are done. For anything else, we get in touch and agree a method — never a form field on this site, never by reply to an email.
We back up first, always
Before anything is touched we take a full backup and keep it for 30 days. If a fix goes wrong, we put the site back exactly as it was.
If it is not what you bought
If the problem turns out smaller than what you ordered, we refund the difference. If it is bigger, we stop and send a quote before doing any extra work.
If we cannot fix it
You get back what we received. Diagnosis is on us — you only pay when the problem is actually solved. The payment processor takes its fee before the money reaches us, so we never hold it and it is not ours to return. That is true here as everywhere else.
If it comes back
Reply within seven days of delivery and we put it back on the bench at no cost. The fix is not finished until it holds.
What we are responsible for
If something goes wrong with a fix, our responsibility is limited to what you paid for it. We take a full backup first so mistakes can be undone, and we tell you before doing anything outside what you bought.