yourwebsite.com
50 public pages checked
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.
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 siteThis problem comes from one site-wide setting or file. Fix it there once, then confirm all 1 affected page.
Claude-SearchBot is blocked from a public location page
The published robots policy prevents this required search crawler from retrieving the affected public location page.
This problem comes from one site-wide setting or file. Fix it there once, then confirm all 1 affected page.
Claude-SearchBot is blocked from a public location page
yourwebsite.com/locations/chicago
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
- Find the rule that disallows the affected public location path for Claude-SearchBot.
- Narrow that block or add an equally specific Allow rule for the affected public path.
- 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
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 pageWe found this problem on one page. Use the page-specific details below to correct it.
Delete the WordPress "Hello world!" starter post
Default placeholder content can appear instead of the organization’s intended information and makes the site look unfinished.
We found this problem on one page. Use the page-specific details below to correct it.
Delete the WordPress "Hello world!" starter post
yourwebsite.com/blog/hello-world
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
- Confirm the starter post is not intentional website content.
- Delete the published starter post and remove it from navigation, feeds, and sitemap output.
- 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.