Fixed-scope audit for product documentation
Docs AI Visibility Audit
Find out whether ChatGPT, Perplexity and Claude can crawl, understand and cite your product documentation, and which fixes matter first.
One public documentation site. No subscription. Report delivered within 48 hours of checkout.
- Crawl access
- robots.txt rules plus live fetches using named AI crawler user agents.
- Discovery
- sitemap.xml, llms.txt and canonical coverage across your key docs.
- Answers
- 10 real user questions tested across ChatGPT, Perplexity and Claude.
Illustrative report scope, not a customer result. Every report states the test date.
Tested, not assumed We make real requests with documented AI crawler user agents instead of only reading robots.txt.
Tied to your URLs Each finding names the page and the section that caused the problem.
Ordered by impact The fix list starts with what blocks retrieval, not a generic checklist.
What the audit covers
One fixed scope, reviewed against your live documentation. Every check is recorded in the report with the date it was run.
- 01
AI crawler access check
We review robots.txt rules and fetch key documentation URLs with real crawler user agents for OpenAI, Anthropic and Perplexity. Blocked paths, challenge pages and empty responses are recorded.
- 02
Sitemap, llms.txt and canonical coverage
We check whether important documentation pages appear in sitemap.xml, whether an llms.txt file exists and resolves, and whether canonical tags point to the version you want cited.
- 03
Readability sample
We sample your highest-value pages for clear headings, answer-first paragraphs, extractable code blocks and tables, and navigation that does not bury the answer.
- 04
10 real user question tests
We run ten real user questions across ChatGPT, Perplexity and Claude and record the answers, cited sources and gaps. Questions cover setup, pricing, troubleshooting and comparison intent.
- 05
Impact-ranked fix list
Every issue is tied to a page and ordered by retrieval impact. You get a short fix-first list plus the evidence behind each finding.
From checkout to report in 48 hours
- 01
Buy the audit
Checkout asks for your company name and documentation URL. If you have specific questions, email up to ten to support@docapta.com.
- 02
We test the live docs
We run the crawler, discovery and readability checks, then test the ten questions against ChatGPT, Perplexity and Claude.
- 03
You get the written report
The report includes the test date, evidence, current answers and a prioritized fix list. No call is required.
Two ways to buy the audit
Both options cover the same audit. The agency option is white-label and priced per report.
Refund policy: If the audit isn't useful, reply within 14 days of delivery for a full refund.
Questions before you buy
Does this guarantee AI citations or rankings?
No. The audit shows whether your documentation is accessible and readable today, removes technical blockers, and records current answers. Assistants, indexes and answers change.
Which AI assistants do you test?
ChatGPT, Perplexity and Claude, tested through each provider's API with web search enabled. Answers in the consumer apps can differ; the report names the model and the date of each test.
What do you need from me?
A public documentation URL (asked for at checkout) and, if you have them, up to ten real user questions. If you do not send questions, we choose ten based on your docs and product.
Can you audit private or login-protected docs?
No. The audit uses public pages only. Private documentation, PDFs behind a login and customer accounts are out of scope.
Is this a fix service?
No. You receive a written diagnosis and a prioritized fix list. Your team implements the changes; the report is written so an engineer or technical writer can act on it.
What counts as delivery?
A written report sent to the email used at checkout within 48 hours of payment. The report states the test date.
See what AI can read before your next docs release.
A fixed-scope audit gives you evidence, a test date and a fix list your team can ship.