A help center your customers can actually search
Write your help articles once, organize them by topic, and let customers find their own answers — while the same articles quietly become the source your AI answers from.
Topics that nest
Group articles into topics, and topics inside topics, so a growing library stays navigable.
Search as you type
Live search across every article, right on the archive page — no search plugin needed.
Helpful / not helpful
A one-tap vote on each article, stored as counts with no visitor tracking.
Shared product tags
The same product taxonomy your tickets use, so docs and tickets line up.
Cached lists
Article lists cache in Redis, Memcached or transients, and refresh the moment you save.
Drop it anywhere
One shortcode renders the whole grouped, searchable archive on any page.
URLs
Nine URL structures, so you can match the site you already have
Most knowledge base plugins pick a URL shape for you. NiroHelp lets you choose one that matches how customers already think about your product — and keeps your search rankings intact when you migrate.
- Plain
- /docs/reset-your-password/
- Topic-based
- /docs/account/reset-your-password/
- Product-based
- /docs/pro-plan/reset-your-password/
- Nested
- /docs/pro-plan/account/reset-your-password/
Reading experience
Articles that are pleasant to read
Every article page gets the details that make documentation usable — without you configuring anything.
Feedback
Find out which articles are letting people down
Each article carries a helpful / not helpful vote. Over a few weeks the pattern tells you which pages to rewrite — and which ones are quietly saving your team from tickets.
Votes are stored as counts only — no IP address, no visitor identity, no fingerprint. It's a signal for you, not a tracking record.
The details
Everything the knowledge base module ships with.
- Content type
- Articles are ordinary WordPress posts, with the editor, featured images and manual ordering.
- Taxonomies
- Nested Topics, plus a Products taxonomy shared with the ticket module.
- URL structures
- Nine options: plain, topic-based, product-based and nested variations.
- Archive
- One shortcode renders a grouped, searchable archive; the page is created on activation.
- Display toggles
- Articles per page, articles per topic before "View all", sidebar, breadcrumbs, prev/next, voting and comments.
- Caching
- Object cache (Redis / Memcached) or transients, configurable TTL, invalidated on save or delete.
- Feedback
- Up / down voting stored as counts. No IP, identity or fingerprint recorded.
- REST API
- List, create, read, update, delete and vote endpoints under the NiroHelp namespace.
- Migration
- One-click import from BetterDocs, weDocs, Echo Knowledge Base and BasePress.
Common questions
No. Articles use the standard WordPress editor, so anything you can write in a post — headings, images, embeds, blocks — works in an article. The archive page is added for you on activation.
Yes. The archive includes live search across every published article, and the results update as the visitor types. At a few hundred articles it stays instant because article lists are cached.
Articles follow normal WordPress visibility, so drafts stay drafts and private articles stay private. Your team can read them in the dashboard while customers cannot.
No — help articles are a separate content type with their own URLs, topics and archive. Your posts, pages and blog keep working exactly as they do now.
On the Pro plan, a Sync pushes your published articles to the AI index. The chatbot and the ticket auto-responder then answer only from what those articles actually say.
Publish your first article today
The knowledge base is free, forever. Bring your existing articles with you in one click.