From the platform
- Sign in to your account at app.beseenby.ai.
- Open a project or create a new one. Projects group the URLs you want to audit, track, and monitor together. Give the project a name that matches the site you are working on.
- Start an audit and choose a mode. The audit dialog has three tabs:
- Single — audit one URL. Enter the full URL including
https://. - Batch — paste or upload a list of URLs to audit together. See Batch Audits.
- Website Audit — enter your domain and let the tool discover, rank, and audit your pages in one run for a whole-site view. This is the fastest way to get started on a site you haven’t mapped yourself, and it’s available on Pro and Agency. See Website Audit.
- Single — audit one URL. Enter the full URL including
- Run the audit. It runs in the background — a single audit completes in about 15–30 seconds; a website audit takes longer because it maps the whole site first.
- Review results in the project. After a website audit, the project view is your starting point: a site-level score, a ranked list of top issues, and the list of audited pages. Open any page to see its full report. Single and batch reports are saved to the project the same way and can be compared over time.
If you’re on Pro or Agency, running a Website Audit first is the recommended way to start — you get the whole-site picture up front, then drill into the individual pages that need work.
From the free tool
The free tool at beseenby.ai runs a full audit on any public URL without requiring an account. Enter the URL and click the audit button. Free tool audits are not saved — they give you a one-time snapshot. To track changes over time, use the platform.
What happens during an audit
BeSeenByAI fetches the page using the same user agents that real AI crawlers send — including GPTBot (used by ChatGPT), ClaudeBot, PerplexityBot, and Google-Extended. It checks whether those bots can actually reach the page, what content is in the raw HTML they receive, and how the server performs.
For performance, it uses real-world field data from the Chrome UX Report (CrUX) if your page has enough traffic for that data to exist. For pages with no field data — new pages, low-traffic URLs, or URLs that are intentionally not indexed — it falls back to lab-based measurements.
Reading your results
After the audit completes, you will see:
- An AI Visibility Score (0–100) and a status label: Excellent, Warning, or Critical
- A priority issues list if any significant problems were found
- Report tabs: Overview, AI Crawlability, Content Visibility, Authority, and — on paid plans — Content Coverage, Prompt Fit, Prompt Discovery, and Lab (plus a History tab on saved reports)
Speed metrics (TTFB, CLS, INP) don’t have their own tab — TTFB appears in AI Crawlability and CLS/INP in Content Visibility.
Start with the Overview tab. If the status is Critical, the priority issues list will point you to the most urgent blocker. Fix that before looking at anything else.
For a full explanation of the score and what it means, see Understanding your AI Visibility Score.
Tips for your first audit
- Audit the page you want to rank, not the homepage. Unless the homepage is your target, audit the specific page that should appear in AI answers for a given topic.
- Check your robots.txt first if you suspect access issues. Blocked bots are the most common reason a page scores low on crawlability.
- Wait 30 seconds after page changes before re-auditing. Cache layers on the server may still serve the old response immediately after a deploy.
Scan more pages
A single audit covers one URL, but most sites have many pages that should show up in AI answers. Rather than checking them one at a time, audit them together: run a Website Audit to have the tool find and rank your pages automatically (Pro and Agency), or a Batch Audit if you already have the list. Product pages, service pages, comparison pages, and key blog posts are all worth checking. Auditing them together in one project lets you compare scores and spot patterns across the site.