Confirm public access
The scan starts with the website address, follows redirects, and checks whether the homepage and other public pages are available.
Methodology
The method behind every score and fix.
Each check looks at evidence the website makes publicly available and compares it with current crawler guidance. The report shows what was found, how serious it is, and what to do next.
Audit framework
Six connected stages from page selection to final priority.
Find public pages
The scan uses the site's sitemaps and links to find public pages, up to the limit included with the selected report.
Check AI visibility
The scan checks whether crawlers can reach, understand, identify, and navigate the website's public content.
Save the evidence
Every problem includes the affected page and the exact response, setting, or page element that caused it.
Calculate the score and priority
The score starts at 100. Each unique issue has one severity-weighted maximum deduction. A page-specific issue starts at half that weight and scales toward the full weight based on the share of applicable evaluated pages it affects, rounded up. A genuinely sitewide issue receives its full rule weight. Repeated instances of the same issue are grouped into one scored finding, so they increase prevalence without creating another severity penalty. No single finding deducts more than its published rule weight.
Explain how to fix it
The report tells you whether to start with one site-wide setting, shared website code, or a specific page. It then shows where to make the change, what steps to follow, and an example when available.
Ruleset governance
Current guidance, controlled changes, traceable reports.
The technical ruleset is maintained as a versioned part of the service so changes in crawler documentation can be detected, recorded, and applied consistently.
First-party sources
Provider documentation and established web standards anchor crawler tokens and technical requirements.
Source monitoring
Scheduled source checks identify changes in the guidance used by the active ruleset.
Conservative discovery
Newly observed crawler tokens are recorded for visibility without changing scored access recommendations.
Versioned refresh
When source guidance changes, the ruleset gets a new version number and review date.
Report traceability
Every scan records the ruleset version used to produce its findings and score.
Defined scope
Page, response-size, redirect, origin, and time limits keep every scan consistent with the selected plan.
Understanding the result
A score for orientation. Clear evidence for action.
The score gives the company a starting point. Priority shows what to fix first. Every problem includes the affected pages, what was found, and the steps needed to correct it.
100Starting Score
18Website Checks
9Visibility Categories
4Priority Levels
Check your site against recent AI crawler rules.
Receive a traceable report connecting every finding to its affected page, observed evidence, and exact correction, to take immediate action.