Menu
Website AuditHow It WorksPricingMethodologyContactGet Your Full Report
Full Report

Preview your score, priorities, and fixes.

Every finding identifies exactly what to change, then the "Verify fix" button rechecks that specific issue and records which affected pages pass or still need work.

Run my FREE website scanChoose a full report size
Sample website report

AI visibility summary and prioritized findings

Scan your website for FREE
Sample report

yourwebsite.com

50 public pages checked

5Unique Issues37 times on 19 pages
1Critical1 page affected
1High1 page affected
1Elevated1 page affected
2Medium17 pages affected

We found 5 unique issues: 1 critical, 1 high, 1 elevated, and 2 medium. These totals count unique issues, not the same issue on different pages. The same issue can affect many pages. Together, the issues appear 37 times across 19 pages. Each row in the page list shows how many of the report's 5 issues affect that page.

The score starts at 100. The 5 unique issues lowered it by 25 points in total, resulting in 75. 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.

Problems to fix Highest priority first
CRITICALCrawler access

Claude-SearchBot is blocked from a public location page

Why this matters

The published robots policy prevents this required search crawler from retrieving the affected public location page.

Fix this once for the whole site

This problem comes from one site-wide setting or file. Fix it there once, then confirm all 1 affected page.

View pages and exact fix Hide expanded panel

Claude-SearchBot is blocked from a public location page

Affected page

yourwebsite.com/locations/chicago

What this means on this page

The published robots policy prevents this required search crawler from retrieving the affected public location page.

What we found
Claude-SearchBot is disallowed at the affected page path by robots.txt.
Where to fix it
The User-agent: Claude-SearchBot group in https://yourwebsite.com/robots.txt

How to fix it

  1. Find the rule that disallows the affected public location path for Claude-SearchBot.
  2. Narrow that block or add an equally specific Allow rule for the affected public path.
  3. Retain separate disallow rules for private and administrative routes.

Why this fix is correct

Change only the verified rule for the named crawler and affected public path; preserve unrelated restrictions.

Example for this exact issue

User-agent: Claude-SearchBot
Allow: /locations/chicago
HIGHContent integrity

Delete the WordPress "Hello world!" starter post

Why this matters

Default placeholder content can appear instead of the organization’s intended information and makes the site look unfinished.

Fix this page

We found this problem on one page. Use the page-specific details below to correct it.

View pages and exact fix Hide expanded panel

Delete the WordPress "Hello world!" starter post

Affected page

yourwebsite.com/blog/hello-world

What this means on this page

Default placeholder content can appear instead of the organization’s intended information and makes the site look unfinished.

What we found
The public page contains the WordPress starter title "Hello world!".
Where to fix it
The published starter post in the WordPress Posts area

How to fix it

  1. Confirm the starter post is not intentional website content.
  2. Delete the published starter post and remove it from navigation, feeds, and sitemap output.
  3. Confirm the deleted URL no longer returns placeholder content.

Why this fix is correct

Remove only the verified starter content; preserve legitimate posts and the website’s existing permalink behavior.

Verify every fix

In a paid report, the "Verify fix" button performs a fresh real-time check for this specific issue on its originally affected page or pages.

Each affected URL is marked with an icon when the issue is fixed or lets you know if it is still detected. The report keeps those results so you can track progress and verify again after additional changes.
How to read the report

Every section answers an implementation question.

01

Where do we stand?

The AI Visibility Score summarizes the technical signals observed across the scanned pages of your website.

02

What comes first?

Severity totals and ordered findings identify the issues with the greatest technical impact.

03

Where is the issue?

Each finding names the affected URL and the exact page element, policy block, response header, or sitemap entry to change.

04

What proves it?

Evidence records the response, directive, element, or count that produced the finding.

05

Did the fix work?

Real-time verification rechecks the specific issue, marking it as passed or still detected with the press of a button.

06

What was evaluated?

The pages scanned and ruleset details establish the scope and timing of the report.

See what limits your website's AI visibility.

Start with a FREE website scan or choose a complete audit for up to 350 public pages.

Run the FREE website scanSee full report options