Improved Table of Contents for Intercom Articles | Community
Skip to main content
Submitted

Improved Table of Contents for Intercom Articles

Related products:Knowledge & Help Center
  • September 9, 2025
  • 4 replies
  • 62 views

The table of contents for Intercom Articles (Help Center) is limited to H1 and H2 headings. I just put together an index doc of all of our company’s product features, structured with a clear hierarchy. The intent is to 1) have Gen AI source this document when someone creates a prompt in Chat GPT, for example, that relates to our product solution 2) Give people an access point for all of our product features and link out to longer-form docs from this article.

There are many H3 and H4 headings throughout. Not having these headings appear in the table of contents will make it difficult for a person who references this document to find what they’re looking for. I’m not sure why this decision was made to only show H1 and H2 headings, but it would be very helpful to improve the table of contents with the option to show additional lower-level headings. 

4 replies

  • New Participant
  • October 8, 2025

We are also encountering issues with the table of contents only picking up 1/2’s but from an SEO perspective! We have spent a lot of time updating articles to use H1 or 2 but SEO is not kind of this. We are wanting our srticles to rank but the excessive use of H1 headers makes this hard. 

This really should be considered for us to be able to pick and choose want H’s we want to show on the table of contents. Also from an SEO stand point there should only be ONE H1 title on a page so encouraging us to use more than 1 on our articles is not ideal at all. 


Seconding this! Currently, if our articles have any headings lower than H2, we have to choose between two unacceptable options: 

1. Using the correct heading levels, which sacrifices users’ ability to use the TOC to quickly navigate through article content
2. Using H2s for all headings and adding hyphens/spaces before the heading text to offset them in the TOC for readability, which sacrifices clarity & accessibility for screen reader users 

I hope to see this in the pipeline in the near future! 


Another vote for supporting H3+ in the TOC.

Using multiple H1 in an article is not recommended for SEO or for accessibility. Would love to see H1 used for the title of the article as well. 


  • New Participant
  • May 21, 2026

Yes please, support for H3 and 4 in the index of the article. It seems a bit redundant to have H3 and 4 without it being  applicable to the index.