Use this page to route questions about diagnostics, evidence limits, protected reports, and data requests.
For a protected report, use the owner access path delivered with the report email and include the report token when requesting help. That keeps report support tied to the correct diagnostic without exposing private report data in a public URL. Useful context includes the scanned domain, the public URL that produced the report, the report type, and the specific evidence section that needs review.
Use the Data Deletion page for revocation or deletion requests involving report data or user-authorized answer snapshots. Include the domain, report token if available, and the email used for unlock so the request can be matched to stored records. Do not send private API keys, payment secrets, cookies, or confidential customer data when asking for support.
Run the free checker from the homepage first, then compare the result with the Agent-Ready Standard, sample report, GEO audit guide, and Pricing pages before unlocking a paid diagnostic. The fastest support conversation usually starts from a public page that has already been scanned, especially when the question involves crawler blockers, thin comparison assets, pricing explanations, proof pages, structured data, or llms.txt coverage.
VisAI is best suited for SaaS founders, AI tool founders, SEO consultants, and small growth agencies that need a concise way to turn public-page evidence into first fixes. Questions about white-label workflows, client handoffs, or report interpretation should include the use case and the public domain being evaluated. If the goal is a client proposal, include the buyer segment, target market, and whether the team needs a free preview, Starter Snapshot, or agency workflow.
The most helpful first message is short and specific: the public domain, the page type being checked, the result you expected, the result you saw, and whether the question is about SEO, GEO, AI search visibility, payment, report access, or data deletion. That keeps support focused on the action the team can actually take next. For growth questions, include the target query or page so recommendations can stay tied to search intent.