Evidence before interpretation
Show the policy, response, HTML, structured data, identity signal, or source behind the conclusion.
For agencies and technical consultants
Turn AI-readiness advice into evidence your clients can inspect
Audit an authorized prospect or client domain, show the public evidence behind each finding, guide the smallest useful remediation, and run a fresh check before describing the condition as resolved.
Technical readiness does not guarantee indexing, citation, ranking, recommendation, traffic, model use, or revenue.
The client problem
AI visibility conversations often begin with outcomes nobody can fully explain
A client sees an inconsistent citation, a competitor mention, or a crawler block and asks for a fix. The agency needs to separate what is publicly observable from what remains inside a provider's private systems.
Purpose before verdict
Distinguish search discovery, training, user-triggered retrieval, ordinary search, and data-use controls.
Fresh checks before resolution
A reported technical change is not verified until compatible new evidence confirms the condition changed.
Agency workflow
From prospect question to verified technical change
Use the public audit during prospect qualification and client delivery while keeping permission, evidence boundaries, and external outcomes explicit.
- 01
Qualify
Run an audit on an authorized public domain and identify whether a material, explainable condition exists.
- 02
Explain
Present the raw source, parsed signals, conclusion, business relevance, and strongest limitation.
- 03
Remediate
Recommend the smallest change supported by evidence and compatible with the client's declared crawler policy.
- 04
Re-check
Collect fresh compatible evidence after deployment and distinguish verified technical resolution from later citation observations.
Available now
Use the current product for client-facing technical reviews
The public audit is stateless and domain-by-domain. Agencies can use it today for authorized research, prospect conversations, remediation planning, and fresh checks.
Current free capabilities
- Crawler-policy interpretation by documented crawler purpose
- Response, redirect, header, and initial-HTML evidence
- Business clarity, structured-data, llms.txt, and entity-signal checks
- Evidence-labelled findings with explicit limitations
- A prioritised improvement plan with fresh re-check conditions
- No-account public audit for authorized prospect and client domains
Planned — not available yet
Future agency capabilities
- Reusable agency branding and client-ready portable reports
- Portfolio workspaces and synchronized domain history
- Scheduled verification and evidence-change alerts
- Permissioned public verification records and signed manifests
These are roadmap directions rather than available features or delivery commitments. If one would materially improve your client workflow, tell us what task it should make easier.
Trust and permission
A responsible audit is not a fear-based sales tactic
Use OpenForBots on public resources within authorization, contractual, and professional boundaries. Do not publish a named third-party report or claim lost revenue, invisibility, or guaranteed citations from a technical observation.
- Obtain client permission before publishing named results or evidence.
- Keep audit-target hostnames, URLs, and content out of aggregate analytics.
- Do not use robots.txt as a security or confidentiality control.
- Separate agency commentary from OpenForBots observations and methodology.
- Preserve negative, unavailable, and uncertain results.
Agency feedback
Help improve the workflow around real client work
If you manage several public domains, we want to understand where the evidence-to-remediation-to-re-check workflow is useful, where client communication is difficult, and which recurring tasks would save meaningful time.