Help-center audit · Free during early access
Find what’s out of date in your help center, with proof.
Send us your help center’s address. We’ll check an agreed sample of articles, show you what’s out of date with the evidence behind every finding, and walk through one fix with you.
Request received.
One quick question: what’s the biggest pain with your docs today?
Thanks. That genuinely shapes what we build first.
What you get
Findings you can check yourself.
Each finding names the article, what’s wrong and how we know. Anything we couldn’t check is marked as unchecked, never quietly counted as fine.
- Product-verified Seen in your product during a replay. Needs a test account.
- Structural Found in your public pages: links, duplicates, terminology, gaps.
- Couldn’t check Named, with the reason. Left for a person to judge.
Audit · help.acme.example
Sample report24 articles in the agreed sample
2 product-verified · 3 structural · 1 couldn’t check
-
Product-verified routine
Invite your team to Acme
Step 2 says “Invite teammates”. The app now shows “Add members”, under Settings › Members.
Observed · staging v2.4 · admin test account · today
-
Product-verified routine
Export your invoices
Screenshot 2 no longer matches the Invoices screen: the filters moved above the table.
Observed · replay step 2 · screenshot compared
-
Structural worth a look
Export your invoices · Download billing history
Two articles describe the same task with different steps.
Found in public pages · both in the agreed sample
-
Structural routine
3 articles
Links point to pages that no longer exist.
Found in public pages · 3 links return 404
-
Structural worth a look
Roles and permissions
Calls the role “workspace owner”; the rest of the help center says “admin”.
Found in public pages · terminology across 24 articles
-
Couldn’t check needs judgment
Set up single sign-on
Needs an enterprise-plan account to replay. Not checked, and marked that way.
Unverified · no suitable test account
How it works
Four steps, no integration.
-
01
You share a URL
The address of your public help center. That’s all we need to start: no logins, no app access, no integration.
-
02
We agree the sample
For example, your 20–30 most-read articles, or the ones behind your most common tickets. You pick; we confirm it by email.
-
03
You get evidence-linked findings
Every finding says what’s wrong, where, and how we know. Structural issues are kept separate from product-verified inaccuracies.
-
04
We walk through one fix
Together we take one finding from evidence to a reviewed update, so you can judge the work, not a pitch.
What we check
What a URL can tell us, and what it can’t.
Honest scope is the point of an audit. Here’s exactly what we look at, with and without access to your product.
From your public help center
- Broken and outdated links, inside and between articles
- Missing, low-quality or visibly ageing screenshots
- Duplicate articles and conflicting instructions for the same task
- Inconsistent names for the same feature, role or setting
- Gaps in structure, navigation and headings
- How readable the content is for AI systems (structure, llms.txt)
Add a test account, when you’re ready
- Replays the flows your articles describe, step by step
- Compares labels, locations and steps with what the app shows
- Re-renders screenshots from the replay
- Records build, environment, account role and date for each check
- Stops before anything destructive: deleting, sending, paying
Not ready to share a URL?
Take the 60-second self-check.
Eight warning signs of drift. Nothing leaves your browser.
Your reading
Tick what applies
Your answers stay in this browser. Nothing is sent anywhere until you choose to request an audit.
Request an auditFAQ
About the audit.
What is a help-center audit?
A bounded check of an agreed sample of your help articles. You get findings with the evidence behind each one, with structural issues kept separate from product-verified inaccuracies, and we walk through one proposed fix with you. During early access it’s free.
Do you need access to my product?
Not to start. A public-URL audit reads only your public help center. If you want steps checked inside your signed-in product, you can add a test account later; its password is stored in an encrypted vault and is never shared with the AI model.
Which help-center platforms can you audit?
Any help center with public pages, whatever it runs on. Publishing approved fixes directly works with HelpCenter.io today; for other platforms you get the findings and the proposed text.
How long does it take?
We agree the timing when we confirm the sample. Early access is assisted, so a person from our team runs each audit with the agent and reviews the findings before you see them.
What does an audit not tell me?
A public-URL audit can’t confirm whether steps still work inside your signed-in product. Findings that need that are marked as such, never presented as verified.
What happens to my data?
We keep your email, your help center’s address and the audit findings to run the audit and follow up with you. You can ask us to delete them at any time. Privacy policy.
Is there any obligation after the audit?
None. If the findings are useful and you want HelpCenter.AI to keep checking, we’ll talk about early access. Early-access teams get founding terms before public pricing.
Pick the articles. We’ll check them.
Free during early access. A person from our team runs every audit with the agent.
Request received.
One quick question: what’s the biggest pain with your docs today?
Thanks. That genuinely shapes what we build first.