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 4, 2026, 2:56 AM
VISIBILITY
Public
Rescan Report
Share Report
Copy Report Link
Export Report
45/100

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability45%Agent Easeof Use51%Security& Trust73%GEO, AIO, AEO56%SEO92%Performance59%Accessibility0%
  • AI Discoverability 45 out of 100
  • Agent Ease of Use 51 out of 100
  • Security & Trust 73 out of 100
  • GEO, AIO and AEO 56 out of 100
  • SEO 92 out of 100
  • Performance 59 out of 100
  • Accessibility 0 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

TNT Sports News, Fixtures & Results | Football, Rugby, UFC & More favicon

TNT Sports News, Fixtures & Results | Football, Rugby, UFC & More

TNT Sports is your go-to source for sport news, results, commentary & highlights all in one place.

Open Agent View

Next step

Turn this report into a fix workflow

1 failed check is 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
45
Priority fix1931View details
Discoverability
40
Priority fix400
Content Readiness
29
Priority fix1231View details
Bot Access Control
63
Needs work300
Agent Ease of Use
51
Needs work210View details
Skill Discovery
54
Needs work100
Google Agentic Browsing
50
Needs work110View details
GEO, AIO and AEO
56
Needs work500
GEO Readiness
Not Applicable
Not Applicable100
AIO Readiness
Not Applicable
Not Applicable200
AEO Readiness
Not Applicable
Not Applicable200
SEO
92
Strong900
SEO
92
Strong900
Security & Trust
73
Needs work1700
Security & Trust
73
Needs work1700
Performance
59
Needs work1100
Performance
59
Needs work1100
Accessibility
0
Priority fix010View details
Accessibility
0
Priority fix010View details

Prioritized recommendations

Issues ranked by score impact

3 items need attention

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

95 Fail

Needs attention

Author attribution

Failed check
01

Issue

Applicable editorial content has no usable author, creator, publisher, visible byline, or HTML attribution signal.

Details

02

Why it matters

Author attribution helps agents cite content responsibly, assess source credibility, and distinguish editorial pages from anonymous marketing copy.

Check name

Author attribution

Score

5/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Identify content authors or publishers for trust and attribution.

Result

Author attribution is partially implemented.

Validation steps

  1. Schema.org attribution

    Editorial content has no Schema.org author, creator, or publisher attribution.

    Schema.org author attribution is missing or incomplete
  2. Author identity quality

    No named author or publisher identity could be extracted.

    Author identity quality is incomplete
  3. Visible byline parity

    Structured author/publisher names were not found in visible byline text.

    Author attribution does not match visible byline content
  4. HTML attribution support

    No supporting HTML author metadata, rel=author link, or visible byline was found.

    HTML author attribution support is missing
Evidence log4 steps · 16 lines
Schema.org attribution [fail]! Editorial content has no Schema.org author, creator, or publisher attribution.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsFAILCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]FAILNo Schema.org author, creator, or publisher attribution foundAuthor identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extractedVisible byline parity [fail]! Structured author/publisher names were not found in visible byline text.INFOVisible byline parityINFOComparing structured contributor names with visible byline evidenceFAILCheck visible attribution matches actual=0 expected="> 0 or visible byline present" visibleByline=false bylineCount=0FAILNo visible byline parity foundHTML attribution support [warning]! No supporting HTML author metadata, rel=author link, or visible byline was found.INFOHTML attribution supportINFOChecking meta author, rel=author, and visible byline supportWARNCheck HTML attribution support signals actual=0 expected="> 0" metaAuthor=false relAuthor=false visibleByline=falseWARNNo supporting HTML attribution signal found

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."
}

AccessibilityAccessibilityBrowser audit

Buttons must have discernible text

100 Fail

Check name

Buttons must have discernible text

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

Buttons must have discernible text

Evidence
{
  "ruleId": "button-name",
  "impact": "critical",
  "description": "Ensure buttons have discernible text",
  "tags": [
    "cat.name-role-value",
    "wcag2a",
    "wcag412",
    "section508",
    "section508.22.a",
    "TTv5",
    "TT6.a",
    "EN-301-549",
    {
      "truncated": true,
      "omittedCount": 4,
      "originalCount": 12
    }
  ],
  "affectedNodeCount": 1,
  "nodes": [
    {
      "target": [
        ".w-75\\.5"
      ],
      "html": {
        "discarded": true,
        "reason": "[discarded fetched document data]",
        "originalType": "string",
        "originalLength": 137
      },
      "failureSummary": "Fix any of the following:\n  Element does not have inner text that is visible to screen readers\n  aria-label attribute does not exist or is empty\n  aria-labelledby attribute does not exist, references elements that do not exist or references elements that are empty\n  Element has no title attribute\n  Element does not have an implicit (wrapped) <label>\n  Element does not have an explicit <label>\n  Element's default semantics were not overridden with role=\"none\" or role=\"presentation\""
    }
  ]
}

Sign in to see 46 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
45/100Level 2, Agent-LimitedCurrent report