Help center audit
Score your help center on what customers and AI assistants need: search, a way to reach you, the topics customers look for, dates, schema, and working links.
Link this tool
Embed or cite the help center audit
Copy a Markdown or HTML badge for your docs, blog, or README. Free, no signup.
What the help center audit checks
What customers need
Customers arrive with one question and little patience. They need search, an article written for their task, a date that says it's current, and a way to reach you when the article doesn't help. The audit checks for each of those.
What AI assistants need
ChatGPT, Claude, and your own support assistant read the same pages. Article or FAQ schema, a sitemap, and llms.txt help them find and cite the right article.
How the score works
Ten checks add up to 100 points, weighted by how much they matter to customers; topic coverage and dates count most. A warning earns half the points. Work through the fixes, then run the audit again.
FAQ
Which URL should I audit?
The home page of your help center, for example help.yourapp.com. The audit reads it and up to 8 articles it links to.
Why did a check fail when my help center has that feature?
The audit reads the HTML your server sends. Search boxes, chat widgets, and dates that load with JavaScript afterwards may not be visible to it.
Does the audit use AI?
No. Every check is a fixed rule, so the same help center gets the same score each time.
An audit shows today's gaps. usedocs keeps closing them: merged pull requests propose edits to the articles they change, and questions your docs couldn't answer become drafted articles, in one review queue.
Start a 7 day free trial