Knowledge base maintenance: 10 best practices that keep it accurate
Knowledge bases do not become wrong in one go. They drift, one product change at a time. These ten habits slow the drift.
In short
- Give every article an owner and a review date.
- Keep one source of truth for each fact and link to it instead of copying it.
- Check automatically on a schedule, so you fix new problems when they are small.
- Name an owner for every article. An unowned article is already out of date.
- Set a review date. Quarterly for fast-moving topics, yearly for stable ones.
- One source of truth per fact. State the refund window once and link to it from everywhere else.
- Add a docs step to every product change. A checklist item: which articles does this change affect?
- Redirect, do not delete. When you move or merge a page, redirect the old address so links keep working.
- Retire what you no longer support. Remove old versions or label them clearly with a link to the current page.
- Write specific titles. "Refund window for annual plans" beats "Refunds".
- Link new articles from somewhere. An article nothing links to will not be found or maintained.
- Watch your most-asked questions. Those pages must be right first.
- Scan on a schedule. Weekly or monthly, with alerts for new problems only. Start with a free knowledge base audit.
For a one-off review, follow the knowledge base audit steps.
Check your own docs
Paste your help center address and see which pages disagree. It's free and takes about two minutes.
Scan my docsMore guides
- Why your AI support bot gives wrong answers
- A 10-point help center audit checklist
- How to find duplicate and outdated pages in your docs
- How to audit a knowledge base: a step-by-step process
- How to find broken links on a website (and which ones matter)
- RAG knowledge base quality checklist: 8 checks before you index
- Why your AI chatbot gives wrong or outdated answers, and how to fix it