Paste a documentation URL and get a readiness report in seconds: reachability, HTTPS and redirects, extractable content, robots.txt accessibility, and sitemap discovery — each finding paired with a specific fix.
Free tool · no signupPage body not returned or indexed
Enter an eligible public http:// or https:// address on port 80 or 443. Local, internal, private or reserved addresses, chattybox.ai and its subdomains, and chattybots.pages.dev are blocked; the server re-validates every request.
A docs chatbot is only as good as what it can fetch and read. The report mirrors that pipeline stage by stage.
The checker requests the URL, follows up to three redirects, and reports the HTTP status and response time it saw.
It shows whether the requested address and the last attempted address use https://, and lists the redirect responses recorded along the way.
It inspects the served HTML for a title, meta description, text, headings, code blocks, and a <main> landmark. Text counts do not measure rendered visibility.
It fetches robots.txt and heuristically looks for User-agent: * and Disallow: / in the same blank-line-separated group. This is not a full robots rules evaluation.
It checks one sitemap: the first matching Sitemap declaration in robots.txt if it is a valid same-origin URL, otherwise /sitemap.xml. It counts up to 1,000 entries and identifies sitemap indexes without crawling their children.
Every finding comes with a plain-language explanation and a specific fix, so the report turns into a to-do list rather than a score.
A check attempts to read your page, robots.txt, and one sitemap, with DNS safety lookups and limited redirects. Failed or blocked requests can stop it early. The report includes measurements, URLs, and extracted title and meta description, but not the fetched page body.
Step 1
Enter an eligible public http(s) page, such as a getting-started guide, an API reference page, or the docs homepage. Safety checks and host restrictions apply.
Step 2
The checker attempts to fetch the page, robots.txt, and one sitemap, subject to safety checks and timeouts. It also makes DNS safety lookups and can follow redirects.
Step 3
It returns readiness signals, including the extracted title and meta description when found, but not the fetched page body. The check does not index the page.
Step 4
Work through the findings, then run the check again — or paste another page — until the report matches the site you want a chatbot to answer from.
Privacy note: the checker does not crawl your whole site or index the page. The report includes URLs, findings, measurements, and extracted title and meta description when found, but not the fetched page body.
ChattyBox crawls your public pages, indexes them for retrieval, and can include source links in answers. Fallbacks may have no sources. Free includes 10 stored pages shared across the owner’s chatbots, so you can test answer quality before upgrading as your needs grow.
What the tool does, what it never does, and how to read the verdict.
It attempts to fetch one documentation page you choose, plus robots.txt and one sitemap from the last attempted page origin, and reports reachability, HTTPS and redirects, extractable content, robots accessibility, and sitemap discovery. The report includes the page title and meta description when found; the fetched page body is not returned.
The checker does not index the fetched page or use it for answers. Its report includes URLs, findings, measurements, and the extracted page title and meta description when found; it does not return the fetched page body.
“No findings recorded” means no findings were recorded, not that chatbot readiness is guaranteed. “Findings to review” means findings were recorded without triggering the blocked verdict. “Page check blocked” means the checker recorded a fetch failure, an HTTP error, or a non-HTML response; a response may still have been received.
No. The tool checks whether robots.txt could be fetched and looks for a wildcard user-agent and root disallow in the same blank-line-separated group. This heuristic is not a full rules evaluation and does not prove how any chatbot product, including ChattyBox, enforces robots rules.
The checker accepts eligible public http(s) URLs on ports 80 or 443, subject to DNS and safety checks. Local, internal, private or reserved addresses, chattybox.ai and its subdomains, and chattybots.pages.dev are blocked. Other public staging pages can be checked if reachable without authentication.
The checker is free and needs no signup. You can start ChattyBox on the Free plan, which includes 10 stored pages shared across the owner’s chatbots. The signup form prefills the last attempted URL from the report.
The checker reports what it measured on the day you ran it. Sites change — re-run the check before launch day, and after moving docs or changing hosting.
