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

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability30%Agent Easeof Use46%Security& Trust68%GEO, AIO, AEO59%SEO100%Performance63%Accessibility44%
  • AI Discoverability 30 out of 100
  • Agent Ease of Use 46 out of 100
  • Security & Trust 68 out of 100
  • GEO, AIO and AEO 59 out of 100
  • SEO 100 out of 100
  • Performance 63 out of 100
  • Accessibility 44 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Department of Transportation favicon

Department of Transportation

To improve the quality of life for all American people and communities, from rural to urban, and to increase the productivity and competitiveness of American workers and businesses.

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
30
Priority fix1500
Discoverability
33
Priority fix500
Content Readiness
31
Priority fix900
Bot Access Control
26
Priority fix100
Agent Ease of Use
46
Priority fix2753View details
API
37
Priority fix300
Auth
54
Needs work500
MCP
42
Priority fix400
Skill Discovery
51
Needs work722View details
Agent Commerce
45
Priority fix721View details
Google Agentic Browsing
50
Needs work110View details
GEO, AIO and AEO
59
Needs work600
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable300
AEO Readiness
Not Applicable
Not Applicable200
SEO
100
Strong900
SEO
100
Strong900
Security & Trust
68
Needs work1500
Security & Trust
68
Needs work1500
Performance
63
Needs work1100
Performance
63
Needs work1100

Prioritized recommendations

Issues ranked by score impact

3 items need attention

Agent Ease of UseAgent CommerceInformational

ACP - Agentic Commerce Protocol

ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".

58 Fail

Needs attention

ACP - Agentic Commerce Protocol

Failed check
01

Issue

ACP discovery content type "text/plain" is not JSON-compatible.

02

Why it matters

ACP discovery lets agents find the seller's ACP API base URL, supported versions, transports, and stable services before attempting authenticated checkout-session negotiation.

Check name

ACP - Agentic Commerce Protocol

Score

42/100

Status

fail

Category

Agent Commerce

Maturity

Informational

Goal

Expose valid ACP discovery when this origin supports Agentic Commerce Protocol workflows.

Result

ACP - Agentic Commerce Protocol failed at "Fetch ACP discovery".

Validation steps

  1. Fetch ACP discovery

    ACP discovery content type "text/plain" is not JSON-compatible.

  2. Validate ACP discovery shape

    ACP discovery could not be parsed.

  3. Review ACP cache and retry metadata

    ACP discovery is missing Cache-Control guidance.

Evidence log3 steps · 14 lines
Fetch ACP discovery [fail]! ACP discovery content type "text/plain" is not JSON-compatible.INFOFetch ACP discovery status="fail"INFOFetch canonical ACP discovery /.well-known/acp.json statusCode=200 contentType="text/plain" parsed=false error="Unexpected non-whitespace character after JSON at position 1 (line 1 column 2)"FAILCheck canonical ACP discovery response actual=false expected=true canonicalFound=trueFAILACP discovery content type "text/plain" is not JSON-compatible.Validate ACP discovery shape [fail]! ACP discovery could not be parsed.INFOValidate ACP discovery shape status="fail"INFOValidate ACP protocol object, name, date version, and supported_versions orderingFAILCheck protocol object and name actual={"hasProtocol":false} expected={"hasProtocol":true,"protocolName":"acp"}FAILCheck protocol version history actual={"supportedVersionCount":0,"supportedVersionsOrdered":false,"supportedVersionsEndWithCurrent":false} expected="date version with chronological supported_versions ending in current version"FAILACP discovery could not be parsed.Review ACP cache and retry metadata [warning]! ACP discovery is missing Cache-Control guidance.INFOReview ACP cache and retry metadata status="warning"INFOInspect ACP discovery cache headers and retry guidance statusCode=200 cacheControl=null retryAfter=nullWARNCheck Cache-Control header on successful discovery actual="missing" expected="present for cacheable public discovery"WARNCheck Retry-After on rate-limit or unavailable responses actual="not required" expected="present only for 429 or 503"WARNACP discovery is missing Cache-Control guidance.

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Detect A2A card version".

52 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

The discovered JSON document does not match a supported A2A Agent Card version family.

02

Why it matters

A2A Agent Cards provide protocol-specific discovery for agent identity, skills, input and output modes, transport bindings, capabilities, and security requirements. Legacy A2A also used /.well-known/agent.json, so scanners must classify the card shape before reporting readiness.

Check name

A2A Agent Card

Score

48/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a version-appropriate A2A Agent Card so A2A-compatible clients can discover agent skills and invoke the declared endpoint safely.

Result

A2A Agent Card failed at "Detect A2A card version".

Validation steps

  1. Detect A2A card version

    The discovered JSON document does not match a supported A2A Agent Card version family.

  2. Validate version-specific card shape

    A2A Agent Card response is not valid JSON.

  3. Validate HTTP delivery

    The card was parseable JSON but was not served with a JSON-compatible content type.

  4. Probe same-origin A2A endpoint

    A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.

Evidence log4 steps · 17 lines
Detect A2A card version [fail]! The discovered JSON document does not match a supported A2A Agent Card version family.INFODetect A2A card versionINFORead version indicators from the card detectionEvidence=[]FAILCompare detected A2A version family actual="unknown" expected="v0.1, v0.2, v0.3, or v1"FAILThe discovered JSON document does not match a supported A2A Agent Card version family.Validate version-specific card shape [fail]! A2A Agent Card response is not valid JSON.INFOValidate version-specific card shapeFAILCompare missing required card fields actual="none" expected="none"FAILCheck every declared A2A skill has required name, description, and endpoint fields actual=0 expected=0 invalidSkills=[]INFOReview declared endpoint interfaces interfaces=[]FAILA2A Agent Card response is not valid JSON.Validate HTTP delivery [warning]! The card was parseable JSON but was not served with a JSON-compatible content type.INFOValidate HTTP deliveryWARNCompare card Content-Type with JSON expectation actual="text/plain" expected="application/json or +json"INFOReview selected discovery path path="/.well-known/agent-card.json" pathClass="canonical-current"WARNThe card was parseable JSON but was not served with a JSON-compatible content type.Probe same-origin A2A endpoint [warning]! A2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itSKIPSkipped endpoint probe reason="No valid A2A card was available to probe."WARNA2A endpoint probing was skipped because the endpoint was cross-origin, unavailable from the card, or uses an unsupported binding.

Agent Ease of UseGoogle Agentic BrowsingBrowser audit

Accessibility tree is not well-formed

100 Fail

Check name

Accessibility tree is not well-formed

Score

0/100

Status

fail

Device

desktop

Category

Google Agentic Browsing

Fix guidance

A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page.

Evidence
{
  "description": "A well-formed [accessibility tree](http://goo.gle/lighthouse-agentic-a11y) helps AI agents to navigate and interact with the page."
}

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

1 reports
Public score history report links
Scan dateScoreReadinessReport
47/100Level 2, Agent-LimitedCurrent report