CanAgentUse tools

UCP Suite

Validate Universal Commerce Protocol discovery, then test product search, carts, checkout links, and merchant handoff flows.

MCP Playground

Connect to remote MCP servers, inspect tools and resources, test prompts, auth, headers, notifications, and JSON-RPC responses.

A2A Playground

Inspect Agent Cards, validate advertised endpoints, and prepare safe requests for agent-to-agent workflows.

Agent Website Viewer

Enter a public URL and see the roles, names, landmarks, controls, and blockers that shape how AI agents understand the page.

SCANNED
Jul 7, 2026, 11:35 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
70/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability58%Agent Easeof Use59%Security& Trust75%GEO, AIO, AEO48%SEO100%Performance95%Accessibility100%
  • AI Discoverability 58 out of 100
  • Agent Ease of Use 59 out of 100
  • Security & Trust 75 out of 100
  • GEO, AIO and AEO 48 out of 100
  • SEO 100 out of 100
  • Performance 95 out of 100
  • Accessibility 100 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Shompton | Digital Agency - Custom Web Development & AI Solutions favicon

Shompton | Digital Agency - Custom Web Development & AI Solutions

Custom web development, API integrations, SEO/GEO services, and premium hosting solutions for small businesses and entrepreneurs.

Open Agent View

Next step

Turn this report into a fix workflow

3 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.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
58
Needs work2600
Discoverability
47
Priority fix600
Content Readiness
63
Needs work1700
Bot Access Control
63
Needs work300
Agent Ease of Use
59
Needs work300
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
48
Priority fix623View details
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
34
Priority fix123View details
SEO
100
Strong900
SEO
100
Strong900
Security & Trust
75
Mostly ready1732View details
Security & Trust
75
Mostly ready1732View details
Performance
95
Strong1800
Performance
95
Strong1800

Prioritized recommendations

Issues ranked by score impact

7 items need attention

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Evaluate fetch baseline".

25 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

default-src is present but not meaningfully restrictive.

Details

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

50/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Evaluate fetch baseline".

Validation steps

  1. Evaluate fetch baseline

    default-src is present but not meaningfully restrictive.

    CSP fetch baseline is too broad or missing
  2. Evaluate script execution

    default-src leaves script execution broadly unrestricted.

    CSP script execution policy is unsafe
  3. Review hardening directives

    CSP is missing recommended hardening directives: object-src, base-uri.

    CSP hardening directives are missing or weak
  4. Review CSP reporting

    CSP does not define a reporting endpoint.

    CSP reporting is missing or incomplete
Evidence log4 steps · 16 lines
Evaluate fetch baseline [fail]! default-src is present but not meaningfully restrictive.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback defaultSrc=["'self'","'unsafe-inline'","'unsafe-eval'","https:"] explicitFetchDirectives=["font-src","img-src"]FAILCompare fetch baseline actual=["'self'","'unsafe-inline'","'unsafe-eval'","https:"] expected="restricted default-src or broad explicit fetch coverage" issue="default-src is present but not meaningfully restrictive."FAILdefault-src is present but not meaningfully restrictive.Evaluate script execution [fail]! default-src leaves script execution broadly unrestricted.INFOEvaluate script executionINFOInspect effective script directive effectiveDirective="default-src" sources=["'self'","'unsafe-inline'","'unsafe-eval'","https:"]FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":true,"hasUnsafeEval":true,"hasWildcardHost":false,"hasBroadScheme":true,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="default-src leaves script execution broadly unrestricted."FAILdefault-src leaves script execution broadly unrestricted.Review hardening directives [warning]! CSP is missing recommended hardening directives: object-src, base-uri.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrcFallback=["'self'","'unsafe-inline'","'unsafe-eval'","https:"] formCount=0WARNCompare recommended hardening coverage actual=["object-src","base-uri"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: object-src, base-uri."WARNCSP is missing recommended hardening directives: object-src, base-uri.Review CSP reporting [warning]! CSP does not define a reporting endpoint.INFOReview CSP reportingINFOInspect CSP reporting directives reportOnlyHeaderPresent=false reportOnlyDirectives=[]WARNCompare violation reporting configuration actual="no reporting endpoint" expected="report-to or report-uri present" issue="CSP does not define a reporting endpoint."WARNCSP does not define a reporting endpoint.

Security & TrustSecurity & TrustEstablished

HSTS header

HSTS header failed at "Find Strict-Transport-Security".

25 Fail

Needs attention

HSTS header

Failed check
01

Issue

HTTPS response is missing Strict-Transport-Security.

Details

02

Why it matters

HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade, SSL-stripping, and mixed-transport risk for repeat users.

Check name

HSTS header

Score

50/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Require HTTPS for repeat browser visits with a valid Strict-Transport-Security policy.

Result

HSTS header failed at "Find Strict-Transport-Security".

Validation steps

  1. Find Strict-Transport-Security

    HTTPS response is missing Strict-Transport-Security.

    Strict-Transport-Security header is missing
Evidence log1 step · 4 lines
Find Strict-Transport-Security [fail]! HTTPS response is missing Strict-Transport-Security.INFOFind Strict-Transport-SecurityINFORead Strict-Transport-Security header header="strict-transport-security" value="missing" effectiveValue=null duplicateHeaderValueCount=0FAILRequire HSTS header on HTTPS response actual="missing" expected="present" issue="HTTPS response is missing Strict-Transport-Security."FAILHTTPS response is missing Strict-Transport-Security.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

AEO: Answer-first passages scored 0/100 and needs a fix.

7 Fail

Needs attention

AEO: Answer-first passages

Failed check
01

Issue

10 section(s) bury or omit a concise opening answer. No direct definition pattern was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Answer-first passages

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Answer-first passages scored 0/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

AEO: Evidence and trust scored 29/100 and needs a fix.

5 Fail

Needs attention

AEO: Evidence and trust

Failed check
01

Issue

Missing answer evidence or trust signals: author, publisher, freshnessDate, sources, sameAs.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Evidence and trust

Score

29/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Evidence and trust scored 29/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Extractable visible copy

AEO: Extractable visible copy scored 53/100 and needs improvement.

3 Warning

Needs attention

AEO: Extractable visible copy

Warning
01

Issue

Client-rendering root signals were found with limited visible text. Visible text has few answer-oriented terms or explanatory markers.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Extractable visible copy

Score

53/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Extractable visible copy scored 53/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 69/100 and needs improvement.

2 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

No direct definition sentence was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Entity and definition clarity

Score

69/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Entity and definition clarity scored 69/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

AEO: Question and answer structure scored 81/100 and needs improvement.

1 Warning

Needs attention

AEO: Question and answer structure

Warning
01

Issue

No list or table answer format was detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Question and answer structure

Score

81/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Question and answer structure scored 81/100 and needs improvement.

Sign in to see 27 other issues and the full report

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

Email code

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.

Fix with MCP / CLI

Score history

Public scan score over time

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

1 reports
Public score history report links
Scan dateScoreReadinessReport
70/100Level 3, Bot-AwareCurrent report