BetterDocs plugin review and common issues

Go to BetterDocs → Settings → Single Documentation → Table of Contents and ensure TOC is enabled. The TOC generates from heading tags (H2, H3, H4) in the article content. If no TOC appears: (1) verify the article contains heading elements — a post with only paragraphs generates no TOC; (2) check the minimum heading count threshold — some configurations only show TOC if there are 3+ headings; (3) the TOC requires BetterDocs’ single doc template to be active — if your theme overrides the doc template, the TOC widget may not be positioned in the layout; (4) clear all caches.

BetterDocs instant search queries the WordPress database for documentation articles. If results are empty: (1) verify documentation articles are Published (not Draft) — only published docs appear in search; (2) check if the search is scoped to a specific knowledge base category — if the search form is category-restricted, it may return no results if the category is empty; (3) BetterDocs search uses standard WordPress REST API queries — verify the REST API is accessible on your site (some security plugins restrict REST API access); (4) clear object and page caches.

The BetterDocs docs listing page requires: (1) a page designated as the “Docs Home” in BetterDocs → Settings → General → Docs Page; (2) that page using the BetterDocs listing template (either selected as the template for that page or rendered via the [betterdocs_docs_listing] shortcode); (3) published doc categories with at least one published article each — empty categories may not display in some layouts. Go to BetterDocs → Docs → Verify articles are published and properly categorized.

Multiple knowledge bases require BetterDocs Pro. Go to BetterDocs → Multiple KB → Create Knowledge Base. Create one KB for each product (e.g., “Product A Help Center,” “Product B Help Center”). Each KB has its own docs listing URL, categories, and articles. Assign articles to a specific KB when creating them. Place each KB’s docs page in your site navigation where appropriate. Each KB can have its own domain path (e.g., /help/product-a/, /help/product-b/) and independently organized article structure.

BetterDocs includes a built-in feedback widget. Go to BetterDocs → Settings → Single Documentation → Article Reactions and enable the “Was this article helpful?” toggle. This adds thumbs up/thumbs down buttons to the bottom of every documentation article. With BetterDocs Pro, feedback data is tracked in the Analytics dashboard — showing which articles receive poor ratings and need improvement. Without Pro, the feedback widget collects submissions but the data is not centrally accessible.

BetterDocs is the better choice for organizations that want documentation fully integrated with their WordPress site — same CMS, same editors, same plugin ecosystem. Dedicated helpdesk platforms provide richer ticket management, customer support workflows, and SLA tracking alongside documentation, but add external platform dependency and monthly fees ($25-50+/month for Zendesk). For organizations whose primary need is self-service documentation (not ticket-based support management), BetterDocs provides the documentation features at a WordPress-appropriate price point.

Role-based access control — restricting specific documentation to specific user roles or requiring login — is a BetterDocs Pro feature. With Pro, configure which documentation categories or individual articles require a specific role to view. Non-authorized users are redirected to a login page or shown a restricted access message. For simpler cases (entire knowledge base requires login), a membership plugin or WordPress’s native page password can supplement BetterDocs free.

Yes, that can happen, especially on older sites with many plugins. This usually happens when the plugin, theme, and add-ons are updated out of sequence. In most cases, testing on staging catches the issue before it reaches the live site. From experience, backups and changelog reviews save a lot of cleanup time.

Start by checking whether another plugin already does the same job. In most cases, overlap is what creates avoidable conflicts and performance issues. A common issue is installing a plugin because it looks convenient without checking the stack first. From experience, a short compatibility review avoids most of the pain later.