Rescan Report
Share Report
Copy Report Link
Rescan Report
Share Report
Copy Report Link
Export Report
54/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability44%Agent Easeof Use50%Security& Trust71%GEO, AIO, AEO64%SEO85%Performance98%Accessibility0%
  • AI Discoverability 44 out of 100
  • Agent Ease of Use 50 out of 100
  • Security & Trust 71 out of 100
  • GEO, AIO and AEO 64 out of 100
  • SEO 85 out of 100
  • Performance 98 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

How To Make a Website – Free Website Builder | Strikingly favicon

How To Make a Website – Free Website Builder | Strikingly

Strikingly is the best free website builder for anyone to create a gorgeous, mobile-friendly website easily. Quick, simple and stylish. Make your own free website today.

Next step

Turn this report into a fix workflow

2 failed checks are ready to move into MCP or CLI remediation. Generate a repair prompt, connect the scanner to your coding agent, or open the integration docs before your next rescan.

Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
44
Priority fix1821View details
Discoverability
63
Needs work700
Content Readiness
23
Priority fix811View details
Bot Access Control
45
Priority fix310View details
Agent Ease of Use
50
Needs work2141View details
API
44
Priority fix741View details
Auth
54
Needs work500
MCP
45
Priority fix200
Agent Commerce
58
Needs work700
GEO, AIO and AEO
64
Needs work1000
GEO Readiness
Not Applicable
Not Applicable300
AIO Readiness
Not Applicable
Not Applicable400
AEO Readiness
Not Applicable
Not Applicable300
SEO
85
Mostly ready800
SEO
85
Mostly ready800
Security & Trust
71
Needs work1600
Security & Trust
71
Needs work1600
Performance
98
Strong1500
Performance
98
Strong1500

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Classify AI crawler rules".

69 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No explicit User-agent rules were found for major AI crawler tokens.

02

Why it matters

AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.

Check name

AI bot rules in robots.txt

Score

31/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.

Result

AI bot rules in robots.txt failed at "Classify AI crawler rules".

Validation steps

  1. Classify AI crawler rules

    No explicit User-agent rules were found for major AI crawler tokens.

Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Validate API catalog media type".

63 Fail

Needs attention

API Catalog

Failed check
01

Issue

Content-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.

02

Why it matters

API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.

Check name

API Catalog

Score

37/100

Status

fail

Category

API

Maturity

Established

Goal

Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.

Result

API Catalog failed at "Validate API catalog media type".

Validation steps

  1. Check API catalog HEAD Link header

    HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".

  2. Validate API catalog media type

    Content-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.

  3. Validate Linkset shape

    Unexpected token '<', "<!DOCTYPE "... is not valid JSON

    Unexpected token '<', "<!DOCTYPE "... is not valid JSON

  4. Classify API catalog relations

    API catalog did not include API endpoint links or useful API discovery relations.

  5. Validate API catalog targets

    API catalog did not expose any href targets to validate.

Evidence log5 steps · 23 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="text/html; charset=utf-8"WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog media type [fail]! Content-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.INFOValidate API catalog media typeFAILCompare API catalog media type actual="text/html; charset=utf-8" expected="application/linkset+json"FAILCompare JSON compatibility fallback actual=false expected=trueFAILContent-Type "text/html; charset=utf-8" is not valid for an RFC 9727 API catalog.Validate Linkset shape [fail]! Unexpected token '<', "<!DOCTYPE "... is not valid JSONINFOValidate Linkset shapeFAILCompare Linkset JSON parse result actual=false expected=trueFAILCompare top-level linkset item count actual=0 expected="> 0"FAILCompare extracted href target count actual=0 expected="> 0"FAILLinkset shape issue issue="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"FAILLinkset JSON parse error error="Unexpected token '<', \"<!DOCTYPE \"... is not valid JSON"FAILUnexpected token '<', "<!DOCTYPE "... is not valid JSONClassify API catalog relations [fail]! API catalog did not include API endpoint links or useful API discovery relations.INFOClassify API catalog relationsINFOClassify API catalog relation types relations=[] summary={"registered":[],"metadata":[],"adjacent":[],"community":[],"legacy":[],"unknown":[]}FAILCompare registered or metadata API relation count actual=0 expected="> 0"FAILAPI catalog did not include API endpoint links or useful API discovery relations.Validate API catalog targets [fail]! API catalog did not expose any href targets to validate.INFOValidate API catalog targetsINFOFetch same-origin API catalog targets and record same-site/external skipsFAILCompare API catalog target failure count actual=0 expected=0FAILAPI catalog did not expose any href targets to validate.

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

45 Warning

Needs attention

Author attribution

Warning
01

Issue

No named author or publisher identity could be extracted.

02

Why it matters

Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.

Check name

Author attribution

Score

55/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify content authors or publishers for trust and attribution.

Result

Author attribution is partially implemented.

Validation steps

  1. Schema.org attribution

    Schema.org attribution is incomplete or relies only on publisher/fallback evidence.

  2. Author identity quality

    No named author or publisher identity could be extracted.

Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=0 authors=[] publishers=[]Author identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extracted

Sign in to see 47 other issues and the full report

Create a free account to unlock every issue, evidence details, exports, and higher free limits.

Development Note:

Please configure GOOGLE_CLIENT_ID in .env to activate live login.

Fix with MCP or CLI

Use this report as the handoff into remediation. Generate a coding-agent prompt with the failing checks attached, or jump to the MCP and CLI setup docs before your next rescan.

Score history

Public scan score over time

Public reports for this website origin. Select any point or report link to open that canonical report.

2 reports
Public score history report links
Scan dateScoreReadinessReport
57/100Level 3, Bot-AwareView report
54/100Level 3, Bot-AwareCurrent report