Find answers to common questions about setup, how the table of contents is built, position, design, and billing for RuffRuff Table of Contents. When detailed steps are required, a related article appears after the answer.
Common causes include no headings in the body, a disabled app, no app block or app embed on the theme, or a hide metafield.
For the checks, see Table of Contents Not Displaying.
You can add an app block only on Online Store 2.0 blog post, product, page, and collection templates. Products, pages, and collections require the Regular plan. On a vintage theme, use an app embed.
For details, see App Block or App Embed Not Appearing.
If no published content of that type exists, you cannot open the template in the theme editor.
To fix this, see Cannot Access a Template.
Common causes include not saving, viewing a different theme, using Light-plan settings on the Free plan, or browser cache.
For the checks, see Settings Not Being Applied.
On Online Store 2.0, add an app block. On a vintage theme, enable an app embed. "Specify in Theme editor" is available only with an app block.
For details, see App Block vs. App Embed.
After you switch themes, the new theme does not have the app block. After you reinstall, the app embed is off again. Add the "Table of Contents" app block to the target template, or add an app embed on a vintage theme.
For the steps, see Initial Setup.
On an Online Store 2.0 theme, if a vintage app embed is also on, the table of contents can remain in an unexpected place, such as near the footer. Turn the app embed off, and add only the app block to the target template.
For details, see App Block vs. App Embed.
No. The table of contents uses only H1–H6 in the Shopify standard blog post body, product description, page body, or collection description. Headings added in theme sections, page builders such as PageFly or GemPages, or metafields are not included. They appear in the table of contents only if those tools save the content into the standard body field.
No. There is no way to exclude an individual heading. Change the heading you want to omit to a level that is not included in "Headings." Note that the visual size also changes.
For the Headings setting, see Customize the Table of Contents.
Yes. The recommended method is the table_of_contents.hidden metafield. On Online Store 2.0, you can also split templates into one that displays the table of contents and one that does not.
For the steps, see Hide the Table of Contents on Specific Content.
No. Category-level switching is not supported. Use the hide metafield, or split templates per post.
No. The table of contents is displayed even if there is only one matching heading. To hide it, use the hide metafield.
The font family follows the theme settings. The app does not set a font family. You can change the size (px) in "Customize the table of contents."
No. Transparent backgrounds are not supported. To approximate transparency, set the same color as the destination theme background.
On the Light plan and higher, set "Initial display lines" to 0 to hide every item at first. Customers open it with "Show all." The show/hide button is a separate setting.
For the setting, see Customize the Table of Contents.
If Position is "Above the first heading" or "Specify class name," the table of contents is drawn first, then moved. Set Position to "Specify in Theme editor (Online Store 2.0 Only)" to skip that move.
No. A sticky (follow-the-screen) table of contents and highlighting the current item based on scroll position are not supported.
No. Images inside the table of contents, related posts, product cards, and rich-snippet output are not supported.
Table of contents headings are built from the body at display time, so they appear in that language if the body is translated. Shared text entered in "Customize the table of contents" is not translated. On the Light plan and higher, per-block text can use the theme translation features.
For the steps, see Translate Block Text.
No. The app uses app blocks or app embeds, so it does not add files to the theme or modify existing code.
Yes. When you use the Light or Regular plan, the branding is hidden automatically. No configuration is required.
No. Plans are billed per store. To use the app on another store, subscribe to a plan on that store as well.
Settings data is not deleted. Display on products, pages, and collections stops unless you are on the Regular plan. Light-plan features such as the show/hide button, custom Liquid, and per-block text are also no longer applied.
Support is available through the contact form only. We do not offer phone or online-meeting support. Contact us through the contact form.