CanAgentUse

CanAgentUse products

Agentic Browsing AuditCheck dialogs, menus, drawers, popovers, form errors, checkout steps, and other UI states that a standard Lighthouse scan may not capture.View product MCP ServerInstall CanAgentUse in your coding agent so scan findings become repo-ready fixes.View product WooCommerce PluginPublish UCP discovery and agent-ready commerce signals from WooCommerce without rebuilding checkout.View product Shopify PluginAdd UCP discovery, storefront metadata checks, and controlled cart-to-checkout flows for shopping agents.View product AgentReady CIScan commits and PRs, publish reports, and choose which agent-readiness failures should block merges.View product

CanAgentUse tools

UCP Suite

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

UCP ValidatorUCP Playground

MCP Playground

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

MCP Playground

A2A Playground

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

A2A Playground

Agent Website Viewer

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

Agent Website Viewer
New Scan
https://smartskintech.com/
SCANNED
Jul 10, 2026, 7:03 AM
VISIBILITY
Public
SUITE2026.06.10
Rescan Report
Share Report
Copy Report Link
Export Report
66/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability70%Agent Easeof Use43%Security& Trust63%GEO, AIO, AEO55%SEO92%Performance88%Accessibility86%
  • AI Discoverability 70 out of 100
  • Agent Ease of Use 43 out of 100
  • Security & Trust 63 out of 100
  • GEO, AIO and AEO 55 out of 100
  • SEO 92 out of 100
  • Performance 88 out of 100
  • Accessibility 86 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

SmartSkin: Real-Time Line Intelligence. Zero Defects favicon

SmartSkin: Real-Time Line Intelligence. Zero Defects

SmartSkin helps pharma and beverage manufacturers reduce breakage, optimize line efficiency, and achieve zero-defect operations.

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
70
Needs work3600
Discoverability
67
Needs work800
Content Readiness
81
Mostly ready2500
Bot Access Control
63
Needs work300
Agent Ease of Use
43
Priority fix430View details
Auth
10
Priority fix130View details
Skill Discovery
54
Needs work100
Google Agentic Browsing
67
Needs work200
GEO, AIO and AEO
55
Needs work600
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable200
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
63
Needs work1222View details
Security & Trust
63
Needs work1222View details
Performance
88
Mostly ready1400
Performance
88
Mostly ready1400

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration failed at "Fetch and validate /auth.md".

90 Fail

Needs attention

Auth.md Agent Registration

Failed check
01

Issue

auth.md could not be fetched.

Details

02

Why it matters

Human login and signup flows are often opaque to agents. Auth.md gives automated clients a stable registration contract instead of forcing them to scrape docs, automate browser forms, or guess credential flows.

Check name

Auth.md Agent Registration

Score

10/100

Status

fail

Category

Auth

Maturity

Emerging recommendation

Goal

Publish Auth.md v1 metadata so agents can discover how to register, claim a user, and obtain credentials.

Result

Auth.md Agent Registration failed at "Fetch and validate /auth.md".

Validation steps

  1. Fetch and validate /auth.md

    auth.md could not be fetched.

    /auth.md is missing or not usable as agent registration guidance

  2. Validate protected resource metadata

    OAuth Protected Resource Metadata could not be fetched.

    Auth.md protected-resource metadata is missing or incomplete

  3. Validate Auth.md authorization metadata

    OAuth authorization-server metadata could not be fetched.

    Authorization-server metadata lacks Auth.md v1 fields
Evidence log3 steps · 18 lines
Fetch and validate /auth.md [fail]! auth.md could not be fetched.INFOFetch and validate /auth.mdINFOFetch Auth.md-related resource path="/auth.md" statusCode=404 contentType="text/html; charset=UTF-8" bytes=106786FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="auth.md could not be fetched."FAILauth.md could not be fetched.Validate protected resource metadata [fail]! OAuth Protected Resource Metadata could not be fetched.INFOValidate protected resource metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-protected-resource" statusCode=404 contentType="text/html" bytes=146FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="OAuth Protected Resource Metadata could not be fetched."FAILOAuth Protected Resource Metadata could not be fetched.Validate Auth.md authorization metadata [fail]! OAuth authorization-server metadata could not be fetched.INFOValidate Auth.md authorization metadataINFOFetch Auth.md-related resource path="/.well-known/oauth-authorization-server" statusCode=404 contentType="text/html" bytes=146FAILCompare response Content-Type with expected Auth.md media type actual=false expected=trueFAILCompare Auth.md/OAuth metadata validation result actual=false expected=trueFAILAuth.md validation issue issue="OAuth authorization-server metadata could not be fetched."FAILOAuth authorization-server metadata could not be fetched.

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Find enforcing CSP delivery".

30 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Applicable HTML response is missing an enforcing Content-Security-Policy header.

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

40/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 "Find enforcing CSP delivery".

Validation steps

  1. Find enforcing CSP delivery

    Applicable HTML response is missing an enforcing Content-Security-Policy header.

    Enforcing Content-Security-Policy header is missing
Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Applicable HTML response is missing an enforcing Content-Security-Policy header.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="missing" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Applicable HTML response is missing an enforcing Content-Security-Policy header."FAILApplicable HTML response is missing an enforcing Content-Security-Policy header.

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection failed at "Validate X-Frame-Options".

28 Fail

Needs attention

Frame protection

Failed check
01

Issue

No valid X-Frame-Options fallback is present.

Details

02

Why it matters

Frame protection blocks hostile sites from embedding pages in deceptive frames, reducing clickjacking and UI redressing risk.

Check name

Frame protection

Score

44/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent unwanted framing with an enforcing CSP frame-ancestors directive or a valid X-Frame-Options fallback.

Result

Frame protection failed at "Validate X-Frame-Options".

Validation steps

  1. Validate CSP frame-ancestors

    No enforcing CSP frame-ancestors directive is present.

    CSP frame-ancestors is missing or ineffective

  2. Validate X-Frame-Options

    No valid X-Frame-Options fallback is present.

    X-Frame-Options is missing, invalid, or obsolete

  3. Review observed browser responses

    One or more same-origin HTML documents observed by Chrome did not emit valid frame protection.

    Observed same-origin HTML responses lack frame protection
Evidence log3 steps · 12 lines
Validate CSP frame-ancestors [warning]! No enforcing CSP frame-ancestors directive is present.INFOValidate CSP frame-ancestorsINFORead CSP frame-ancestors signals enforcingHeaderPresent=false reportOnlyHeaderPresent=false metaFrameAncestors=false policyCount=0 duplicateDirectives=[]WARNCompare effective frame-ancestors directive actual="missing" expected="valid restrictive enforcing frame-ancestors" issue="No enforcing CSP frame-ancestors directive is present."WARNNo enforcing CSP frame-ancestors directive is present.Validate X-Frame-Options [fail]! No valid X-Frame-Options fallback is present.INFOValidate X-Frame-OptionsINFORead X-Frame-Options fallback value="missing" parsedValues=[] normalizedValues=[]FAILCompare X-Frame-Options value actual="missing" expected="DENY or SAMEORIGIN" valid=false obsoleteAllowFrom=false duplicateOrConflicting=false issue="No valid X-Frame-Options fallback is present."FAILNo valid X-Frame-Options fallback is present.Review observed browser responses [warning]! One or more same-origin HTML documents observed by Chrome did not emit valid frame protection.INFOReview observed browser responsesINFOSample Chrome-observed same-origin responses observedResponseCount=63 sameOriginCount=28 htmlDocumentCount=1WARNCompare observed HTML frame protection actual={"missingOrInvalidFrameProtectionCount":1,"broadFrameAncestorsCount":0,"affected":[{"url":"https://smartskintech.com/","status":200,"resourceType":"document","contentType":"text/html; charset=UTF-8","contentSecurityPolicy":null,"contentSecurityPolicyReportOnly":null}]} expected="0 missing/invalid or broad same-origin HTML responses" issue="One or more same-origin HTML documents observed by Chrome did not emit valid frame protection."WARNOne or more same-origin HTML documents observed by Chrome did not emit valid frame protection.

Sign in to see 35 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
66/100Level 3, Bot-AwareCurrent report