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 17, 2026, 7:34 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
68/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability47%Agent Easeof Use59%Security& Trust69%GEO, AIO, AEO70%SEO100%Performance99%Accessibility93%
  • AI Discoverability 47 out of 100
  • Agent Ease of Use 59 out of 100
  • Security & Trust 69 out of 100
  • GEO, AIO and AEO 70 out of 100
  • SEO 100 out of 100
  • Performance 99 out of 100
  • Accessibility 93 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Discover new people nearby and make real connections - MeetMe favicon

Discover new people nearby and make real connections - MeetMe

Connect with people nearby or worldwide on MeetMe. Join now and chat, make friends, or meet authentic matches.

Open Agent View

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.

Fix with MCP / CLI
Detailed report scores grouped by capability area
MetricScoreStatusPassedFailedWarningEvidence
AI Discoverability
47
Priority fix2310View details
Discoverability
48
Priority fix500
Content Readiness
50
Needs work1700
Bot Access Control
45
Priority fix110View details
Agent Ease of Use
59
Needs work200
Google Agentic Browsing
100
Strong200
GEO, AIO and AEO
70
Needs work800
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable300
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
69
Needs work1821View details
Security & Trust
69
Needs work1821View details
Performance
99
Strong1810View details
Performance
99
Strong1810View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection failed at "Validate CSP frame-ancestors".

75 Fail

Needs attention

Frame protection

Failed check
01

Issue

frame-ancestors allows broad embedding sources.

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

25/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 CSP frame-ancestors".

Validation steps

  1. Validate CSP frame-ancestors

    frame-ancestors allows broad embedding sources.

    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 [fail]! frame-ancestors allows broad embedding sources.INFOValidate CSP frame-ancestorsINFORead CSP frame-ancestors signals enforcingHeaderPresent=true reportOnlyHeaderPresent=false metaFrameAncestors=false policyCount=1 duplicateDirectives=[]FAILCompare effective frame-ancestors directive actual={"values":["*"],"mode":"broad","valid":true,"restrictive":false,"broadSources":["*"]} expected="valid restrictive enforcing frame-ancestors" issue="frame-ancestors allows broad embedding sources."FAILframe-ancestors allows broad embedding sources.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=24 sameOriginCount=18 htmlDocumentCount=1WARNCompare observed HTML frame protection actual={"missingOrInvalidFrameProtectionCount":1,"broadFrameAncestorsCount":1,"affected":[{"url":"https://www.meetme.com/en/","status":200,"resourceType":"document","contentType":"text/html; charset=UTF-8","contentSecurityPolicy":"default-src 'self'; base-uri 'self'; script-src 'self' 'nonce-a4265d4866b65e19eb77c5508be50bd5' 'strict-dynamic' 'unsafe-inline' https: 'report-sample' https://cdn.cookielaw.org; connect-src 'self' https://cdn.cookielaw.org *.onetrust.com; frame-ancestors *; frame-src 'none'; object-src 'none'; img-","contentSecurityPolicyReportOnly":null},{"url":"https://www.meetme.com/en/","status":200,"resourceType":"document","contentType":"text/html; charset=UTF-8","contentSecurityPolicy":"default-src 'self'; base-uri 'self'; script-src 'self' 'nonce-a4265d4866b65e19eb77c5508be50bd5' 'strict-dynamic' 'unsafe-inline' https: 'report-sample' https://cdn.cookielaw.org; connect-src 'self' https://cdn.cookielaw.org *.onetrust.com; frame-ancestors *; frame-src 'none'; object-src 'none'; img-","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.

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.

Details

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.

    robots.txt lacks explicit AI crawler rules
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=0 unspecified=21

PerformancePerformanceBrowser audit

Improve image delivery

100 Fail

Check name

Improve image delivery

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 81 KiB

Fix guidance

Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)

Evidence
{
  "displayValue": "Est savings of 81 KiB",
  "description": "Reducing the download time of images can improve the perceived load time of the page and LCP. [Learn more about optimizing image size](https://developer.chrome.com/docs/performance/insights/image-delivery)"
}

Sign in to see 33 other issues and the full report

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

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