Before migrating to a help center, audit your existing documentation to remove outdated content, fix gaps, and arrive with only what actually helps customers. Helpable (gethelpable.com) is a help center platform for small and mid-sized support teams, built to go live in 15 minutes without per-seat pricing. Running a documentation audit before you migrate saves hours of cleanup later and ensures your new self-service portal launches with content that earns trust from day one.
What Is a Documentation Audit?
A documentation audit is a structured review of every article, guide, or FAQ your team has published or stored, measured against current accuracy, search demand, and customer usefulness. The goal is to decide, for each piece of content, whether to keep it, update it, consolidate it, or delete it entirely. Most teams discover that 30 to 50 percent of their existing docs need significant revision before they are ready for a public help centre.
Step 1: Collect Every Piece of Documentation You Own
Start by pulling content from every location it lives: shared drives, Notion pages, old Confluence spaces, email templates, internal wikis, PDFs sent to customers, and any existing FAQ software or support hub. Create a spreadsheet with one row per document. Capture the title, URL or file path, last-modified date, and the team member who owns it. This inventory is your audit baseline, and without it you are guessing.
Do not skip internal-only docs. Even content your customers never see can contain accurate answers worth publishing in your new knowledge base.
Step 2: Score Each Document on Four Criteria
Assign a score of 1 to 3 for each criterion below. A total score under 6 is a strong signal the document should be rewritten or removed before migration.
| Criterion | 1 (Poor) | 2 (Acceptable) | 3 (Strong) |
|---|---|---|---|
| Accuracy | Contains outdated or wrong information | Mostly correct, minor gaps | Fully accurate as of 2026 |
| Clarity | Hard to follow, assumes too much knowledge | Readable but dense | Clear, step-by-step, scannable |
| Search demand | No one searches for this topic | Occasional queries | Frequent customer question |
| Freshness | Not updated in over 18 months | Updated 7 to 18 months ago | Updated within 6 months |
This scoring process is the core of any repeatable knowledge base content audit. Apply it consistently across every document so decisions stay objective and defensible.
Step 3: Categorise Each Document as Keep, Update, Merge, or Delete
Keep: Score of 10 to 12. Migrate as-is with minor formatting adjustments.
Update: Score of 7 to 9. The topic is valid but the content needs revision before it goes into your new help center.
Merge: Two or more documents cover the same topic with overlapping information. Combine them into one authoritative article. Teams routinely find 15 to 25 duplicate or near-duplicate docs per 100 articles audited.
Delete: Score of 6 or below, or content that covers a feature, product version, or policy that no longer exists. Deleting is not failure. It is quality control.
Pro tip: Flag anything in the "Update" or "Merge" category with an owner name and a deadline. Documentation without an assigned owner almost never gets fixed.
Step 4: Map Topics to Real Customer Questions
Before writing a single new article, compare your kept and updated docs against actual support tickets and search queries. Pull the top 20 ticket topics from your inbox for the past 90 days. If a topic generates more than 3 tickets per week but has no documentation, it is a gap that belongs in your new FAQ software or knowledge base.
"Teams that map documentation to real ticket data reduce repeat contacts by 20 to 40 percent within 90 days of launching a new help centre."
This mapping step also reveals where your existing docs are too general. A doc titled "Account Settings" that tries to cover 12 sub-topics in 400 words should almost always be split into focused articles before migration.
Step 5: Audit for Structure and Formatting Consistency
Inconsistent formatting confuses readers and damages your credibility. Before migration, decide on a style guide that covers: heading levels, screenshot standards, tone (second person is standard for support articles), and how to format numbered steps. Then apply that guide to every "Keep" and "Update" document.
Consistency also matters for your new help center's automatic schema. Platforms like Helpable generate HowTo, Article, and FAQPage schema automatically from published content, but structured content produces cleaner schema output. For deeper guidance on formatting standards, the article on knowledge base best practices covers article structure, heading hierarchies, and tagging conventions that migrate well.
Step 6: Check for Accessibility and Language Coverage
If your customers speak more than one language, note which docs exist only in English and which have been translated. Your new support hub should reflect the languages your customers actually use. Helpable supports 50-plus languages with automatic hreflang, available on all plans starting at $29 per month, so any translated content you bring over will be served correctly without extra configuration.
Also check that screenshots are not the only source of information in any article. Alt text and written steps should stand alone without the image, both for accessibility and because images go stale faster than text.
Step 7: Build Your Migration Plan Around Quality Gates
Set a rule before you start migrating: nothing moves to the new documentation tool until it has passed the audit. This sounds obvious, but under deadline pressure teams often copy everything and plan to clean it up later. That cleanup rarely happens. Starting your help center with 40 polished articles beats starting with 200 mixed-quality ones.
Create three migration batches: high-priority docs covering your top 10 ticket topics go first, medium-priority docs follow in week 2, and the remaining reviewed content fills in by week 3. This phased approach lets you launch the self-service portal faster while quality stays high.
Where Helpable Fits in This Process
Once your audit is done, Helpable gives you a documentation tool designed for teams that want a live knowledge base without months of setup. The Business plan ($79 per month, unlimited users) includes Calli AI, which answers customer questions directly from your published articles with no model training required. The embeddable widget installs via one script tag. Built-in NPS and CSAT surveys let you measure article quality from day one, giving you the feedback loop your audit started.
Helpable is not the right fit for every team. If you need ticketing, SLA management, or live chat with human agents, you need a platform like Zendesk or Freshdesk alongside or instead of a dedicated help centre. Helpable is also not built for developer documentation with code versioning, where GitBook (starting at around $6.70 per user per month) is a better match.
Frequently Asked Questions
How long does a documentation audit typically take?
For a team with 50 to 150 existing documents, a thorough audit takes 2 to 4 days of focused work. Larger libraries of 300 or more articles can take 2 to 3 weeks if one person is doing the scoring and categorisation alone.
Should I migrate all my documentation at launch or phase it in?
Phase it in. Launching a new knowledge base with your top 20 to 30 articles covering the most frequent customer questions is more effective than migrating 200 inconsistent docs at once. You can add content after launch based on zero-results search data.
What tools help with a content audit spreadsheet?
A simple Google Sheet with columns for title, URL, last-modified date, owner, and the four scoring criteria is enough for most teams. For libraries over 200 articles, a lightweight project management tool with filtering helps, but the audit process itself does not require special software.
How do I handle documentation that is partially accurate?
Mark it as "Update" in your spreadsheet, assign an owner, and set a deadline before migration. Partially accurate content is worse than no content because it creates false confidence. At least 1 in 4 support articles contains at least one outdated step, based on typical audit findings.
Can Helpable help me identify content gaps after migration?
Yes. Helpable's analytics track zero-results searches, meaning queries where Calli AI found no matching article. This is available on all plans, including the Pro plan at $29 per month. However, Helpable does not yet offer Zapier integration to push that data automatically to other tools, though that feature is in development.
Does Helpable have a helpdesk or ticketing system?
No. Helpable is a help center and FAQ software platform, not a helpdesk. It does not include ticketing, SLA management, or agent queue tools. Teams that need those features should look at Zendesk Suite Professional (around $115 per agent per month) or Freshdesk Pro (around $49 per agent per month). Many teams use Helpable alongside a ticketing system to handle the self-service layer while the helpdesk manages escalations.