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 15, 2026, 3:21 PM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
62/100

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability62%Agent Easeof Use62%Security& Trust65%GEO, AIO, AEO65%SEO92%Performance59%Accessibility53%
  • AI Discoverability 62 out of 100
  • Agent Ease of Use 62 out of 100
  • Security & Trust 65 out of 100
  • GEO, AIO and AEO 65 out of 100
  • SEO 92 out of 100
  • Performance 59 out of 100
  • Accessibility 53 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Graves Disease, Hashimoto's thyroiditis treatment and Natural Thyroid Treatment | Natural Endocrine Solutions favicon

Graves Disease, Hashimoto's thyroiditis treatment and Natural Thyroid Treatment | Natural Endocrine Solutions

Thyroid Issues | Discover the comprehensive solutions to hashimoto's treatment, thyroid illnesses and Graves disease at Natural Endocrine Solutions. Offering natural treatments, our team aids in managing thyroid related symptoms such as ha...

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
62
Needs work3221View details
Discoverability
67
Needs work800
Content Readiness
79
Mostly ready2311View details
Bot Access Control
45
Priority fix110View details
Agent Ease of Use
62
Needs work400
API
67
Needs work100
Google Agentic Browsing
100
Strong300
GEO, AIO and AEO
65
Needs work700
GEO Readiness
Not Applicable
Not Applicable200
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
65
Needs work1622View details
Security & Trust
65
Needs work1622View details
Performance
59
Needs work900
Performance
59
Needs work900

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.

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=21 unspecified=0

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

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

50 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

CSP does not define default-src; several fetch directives may have no restrictive fallback.

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

    CSP does not define default-src; several fetch directives may have no restrictive fallback.

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

    No script-src or default-src directive constrains script execution.

    CSP script execution policy is unsafe
  3. Review hardening directives

    CSP is missing recommended hardening directives: base-uri, form-action.

    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]! CSP does not define default-src; several fetch directives may have no restrictive fallback.INFOEvaluate fetch baselineINFOEvaluate resource loading fallback explicitFetchDirectives=["object-src"]FAILCompare fetch baseline actual="0 explicit fetch directives" expected="restricted default-src or broad explicit fetch coverage" issue="CSP does not define default-src; several fetch directives may have no restrictive fallback."FAILCSP does not define default-src; several fetch directives may have no restrictive fallback.Evaluate script execution [fail]! No script-src or default-src directive constrains script execution.INFOEvaluate script executionINFOInspect effective script directive FAILCompare script execution posture actual={"hasNonce":false,"hasHash":false,"hasStrictDynamic":false,"hasUnsafeInline":false,"hasUnsafeEval":false,"hasWildcardHost":false,"hasBroadScheme":false,"dangerousSchemes":[]} expected="constrained script sources without unsafe execution allowances" issue="No script-src or default-src directive constrains script execution."FAILNo script-src or default-src directive constrains script execution.Review hardening directives [warning]! CSP is missing recommended hardening directives: base-uri, form-action.INFOReview hardening directivesINFOInspect CSP hardening directives objectSrc=["'none'"] formCount=1WARNCompare recommended hardening coverage actual=["base-uri","form-action"] expected="no missing object-src/base-uri/form-action requirements" issue="CSP is missing recommended hardening directives: base-uri, form-action."WARNCSP is missing recommended hardening directives: base-uri, form-action.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.

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

0 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are invalid: dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-07-09T06:00:44-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-07-09T06:00:44-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-07-02T06:00:14-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-07-02T06:00:14-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-25T06:00:02-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-25T06:00:02-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-18T06:00:43-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-18T06:00:43-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-11T06:00:41-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-11T06:00:41-04:00)..

Details

02

Why it matters

Freshness signals help agents, crawlers, and search systems decide whether content is current enough to cite, summarize, cache, or compare against newer sources.

Check name

Content freshness signals

Score

100/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose modified and published dates for freshness-aware retrieval, citation, and ranking.

Result

Content freshness signals is missing or incomplete.

Validation steps

  1. Corroborate with sitemap lastmod

    Add a sitemap entry with a valid lastmod for the canonical page URL when sitemap corroboration is useful.

    Sitemap lastmod corroboration is missing
  2. Check date validity and consistency

    dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-07-09T06:00:44-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-07-09T06:00:44-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-07-02T06:00:14-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-07-02T06:00:14-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-25T06:00:02-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-25T06:00:02-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-18T06:00:43-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-18T06:00:43-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-11T06:00:41-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-11T06:00:41-04:00).

    Freshness dates are invalid or inconsistent
Evidence log2 steps · 8 lines
Corroborate with sitemap lastmod [warning]INFOCorroborate with sitemap lastmodINFODiscovering sitemap candidates and matching the scanned page URL candidateCount=1 attempts=1WARNCheck matching sitemap lastmod actual="no match" expected="valid match when available" robotsStatusCode=200WARNNo matching sitemap lastmod found after sitemap attempts attempts=1Check date validity and consistency [fail]! dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-07-09T06:00:44-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-07-09T06:00:44-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-07-02T06:00:14-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-07-02T06:00:14-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-25T06:00:02-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-25T06:00:02-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-18T06:00:43-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-18T06:00:43-04:00).; dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-11T06:00:41-04:00).; article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-11T06:00:41-04:00).INFOCheck date validity and consistencyINFOChecking collected freshness dates for invalid values, future dates, and inconsistent orderingFAILCheck critical freshness issue count actual=10 expected=0 warningIssueCount=0 issues=[{"severity":"fail","message":"dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-07-09T06:00:44-04:00)."},{"severity":"fail","message":"article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-07-09T06:00:44-04:00)."},{"severity":"fail","message":"dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-07-02T06:00:14-04:00)."},{"severity":"fail","message":"article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-07-02T06:00:14-04:00)."},{"severity":"fail","message":"dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-25T06:00:02-04:00)."},{"severity":"fail","message":"article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-25T06:00:02-04:00)."},{"severity":"fail","message":"dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-18T06:00:43-04:00)."},{"severity":"fail","message":"article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-18T06:00:43-04:00)."},{"severity":"fail","message":"dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-11T06:00:41-04:00)."},{"severity":"fail","message":"article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-06-11T06:00:41-04:00)."}]FAILInvalid freshness date issue found issues=["dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-07-09T06:00:44-04:00).","article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-07-09T06:00:44-04:00).","dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-07-02T06:00:14-04:00).","article:modified_time (2018-03-31T08:46:55+00:00) is earlier than datePublished (2026-07-02T06:00:14-04:00).","dateModified (2018-03-31T04:46:55-04:00) is earlier than datePublished (2026-06-25T06:00:02-04:00)."]

Sign in to see 42 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