The scan
What the scan checks
The current paid offers inspect publicly available HTML/source for the submitted webpage and look for recognized chatbot-widget signatures. The result reflects the source that was accessible when the scan ran; it is not an inventory of every page or service connected to a business.
A PDF summary includes the scan time, any detected signatures—or a note that no common widget was found—and general next steps. If no common signature appears, that does not prove that the website has no chatbot. A widget may be loaded in a way the scan cannot see, or may not use a recognized signature.
Clear boundaries
What the scan does not tell you
The scan is limited to page-source signatures. It does not test chatbot responses. It does not perform prompt-injection or other adversarial attacks. It does not certify safety or compliance, and it does not include a retest. Finding a widget signature does not establish how that chatbot behaves, and not finding one does not establish that no chatbot is present.
Common questions
Chatbot widget scan FAQ
Does “no common widget found” mean there is no chatbot?
No. It means the inspected public page source did not contain a recognized signature. A widget may be loaded in a way that is not visible to this scan, or may use a signature the scan does not recognize.
Does the scan check what the chatbot says to visitors?
No. It reads publicly available page HTML/source for recognized widget signatures. It does not open a conversation or test chatbot responses.
Does the report certify that a chatbot is safe or compliant?
No. The PDF is a summary of the page-source scan and general next steps. It is not a safety or compliance certification.
Is a retest included?
No. The current paid offers use the same initial scan flow and do not include a retest.