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

OVERALL SCORE

Level 2, Agent-Limited

Priority improvements needed for AI agents
AIDiscoverability43%Agent Easeof Use31%Security& Trust20%GEO, AIO, AEO59%SEO92%Performance& Accessibility56%
  • AI Discoverability 43 out of 100
  • Agent Ease of Use 31 out of 100
  • Security & Trust 20 out of 100
  • GEO, AIO and AEO 59 out of 100
  • SEO 92 out of 100
  • Performance and Accessibility 56 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Agent.ai | The #1 Professional Network for AI Agents favicon

Agent.ai | The #1 Professional Network for AI Agents

Discover, use and build agents to create your personal AI agent team.

Next step

Turn this report into a fix workflow

26 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
43
Priority fix10150View details
Discoverability
17
Priority fix270View details
Content Readiness
40
Priority fix560View details
Bot Access Control
83
Mostly ready320View details
Agent Ease of Use
31
Priority fix19222View details
API
17
Priority fix150View details
Auth
Not Applicable
Not Applicable620View details
MCP
47
Priority fix471View details
Skill Discovery
30
Priority fix481View details
Agent Commerce
Not Applicable
Not Applicable400
GEO, AIO and AEO
59
Needs work2512View details
GEO Readiness
56
Needs work023View details
AIO Readiness
60
Needs work223View details
AEO Readiness
62
Needs work016View details
SEO
92
Strong1010View details
SEO
92
Strong1010View details
Security & Trust
20
Priority fix540View details
Security & Trust
20
Priority fix140View details
AI Training Exposure
Not Applicable
Not Applicable400
Performance and Accessibility
56
Needs work1951View details
Performance
35
Priority fix1451View details
Accessibility
96
Strong500

Prioritized recommendations

Issues ranked by score impact

50 items need attention

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery failed at "Find valid OpenAPI document".

50 Fail

Needs attention

OpenAPI discovery

Failed check
01

Issue

OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=UTF-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.

02

Why it matters

OpenAPI documents let agents understand available operations, schemas, authentication, and request formats before calling an API.

Check name

OpenAPI discovery

Score

0/100

Status

fail

Category

API

Maturity

Established

Goal

Publish a valid OpenAPI or Swagger document for API discovery.

Result

OpenAPI discovery failed at "Find valid OpenAPI document".

Validation steps

  1. Find valid OpenAPI document

    OpenAPI YAML document did not match the expected shape. Content-Type "text/html; charset=UTF-8" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Find valid OpenAPI document",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/openapi.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-8daHez7bvtnLIfLm7IouA5&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/openapi.yaml",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-N233WkTiHjsPf2CPea5Cj4&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/swagger.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-vMijUMw20W9Aydd44uNpcg&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/swagger.yaml",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-cmhCLVZFlOAbz7x5z1zZP5&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/api/openapi.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-em3qR3NqmxdBVnwFdbkuvN&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/api/swagger.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-tcYwGDxphikRGIsfP7Nv55&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          },
          {
            "path": "/docs/openapi.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "valid": false,
            "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
            "compatibleContentType": false,
            "format": "yaml",
            "version": "",
            "pathCount": 0,
            "operationCount": 0,
            "rawExcerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scale=1\"><meta http-equiv=\"content-security-policy\" content=\"default-src &#39;none&#39;; script-src &#39;nonce-5DnNFrAjNNWM8HsGhphfht&#39; &#39;unsafe-eval&#39; https://challenges.cloudflare.com; script-src-attr &#39;none&#39;; style-src &#39;unsafe-inline&#39;; img-src &#39;self&#39; https://challenges.cloudflare.com; connect-src &#39;self&#39; https://challenges.cloudflare.com; frame-src &#39;self&#39; https://challenges.cloudflare.com blob:; child-src &#39;self&#39; https://challenges.cloudflare."
          }
        ]
      },
      "issue": "OpenAPI YAML document did not match the expected shape. Content-Type \"text/html; charset=UTF-8\" is not a recognized type; unsupported version: ; missing info block with title and version; missing paths block; no operations found.",
      "howToFix": "Publish a valid OpenAPI 3.x or Swagger 2.0 JSON/YAML document with info, paths, operations, and responses."
    }
  ]
}

AI DiscoverabilityBot Access ControlInformational

Web Bot Auth request signing

Web Bot Auth request signing failed at "Validate resource body".

50 Fail

Needs attention

Web Bot Auth request signing

Failed check
01

Issue

Web Bot Auth Directory response did not match the expected shape. Content-Type "application/json; charset=utf-8" is not a valid directory type.

02

Why it matters

Web Bot Auth discovery lets servers and clients find signing keys for bot identity workflows based on HTTP Message Signatures.

Check name

Web Bot Auth request signing

Score

50/100

Status

fail

Category

Bot Access Control

Maturity

Informational

Goal

Advertise HTTP Message Signatures keys when this site operates signed bot clients or supports Web Bot Auth workflows.

Result

Web Bot Auth request signing failed at "Validate resource body".

Validation steps

  1. Validate resource body

    Web Bot Auth Directory response did not match the expected shape. Content-Type "application/json; charset=utf-8" is not a valid directory type.

Evidence
{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/http-message-signatures-directory",
        "statusCode": 200,
        "contentType": "application/json; charset=utf-8"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": true,
        "compatibleContentType": false,
        "document": {
          "keys": [
            {
              "kty": "OKP",
              "crv": "Ed25519",
              "kid": "agentai-web-bot-auth-2026",
              "alg": "EdDSA",
              "use": "sig",
              "x": "REPLACE_WITH_BASE64URL_ED25519_PUBLIC_KEY",
              "nbf": 1780919938,
              "exp": 1796471998
            }
          ]
        },
        "rawExcerpt": "{\"keys\":[{\"kty\":\"OKP\",\"crv\":\"Ed25519\",\"kid\":\"agentai-web-bot-auth-2026\",\"alg\":\"EdDSA\",\"use\":\"sig\",\"x\":\"REPLACE_WITH_BASE64URL_ED25519_PUBLIC_KEY\",\"nbf\":1780919938,\"exp\":1796471998}]}",
        "issue": "Web Bot Auth Directory response did not match the expected shape. Content-Type \"application/json; charset=utf-8\" is not a valid directory type.",
        "keyCount": 1,
        "invalidKeys": []
      },
      "issue": "Web Bot Auth Directory response did not match the expected shape. Content-Type \"application/json; charset=utf-8\" is not a valid directory type.",
      "howToFix": "If publishing Web Bot Auth keys, return a JSON key directory with a non-empty keys array and the draft media type."
    }
  ]
}

Agent Ease of UseAPIEstablished

API Catalog

API Catalog failed at "Validate RFC 9727 linkset".

34 Fail

Needs attention

API Catalog

Failed check
01

Issue

API Catalog response did not match the expected shape. Content-Type "application/json; charset=utf-8" is not application/linkset+json.

02

Why it matters

API catalogs help agents find service descriptions, documentation, and status resources without guessing API entry points.

Check name

API Catalog

Score

33/100

Status

fail

Category

API

Maturity

Established

Goal

Publish an API catalog for automated API discovery using RFC 9727.

Result

API Catalog failed at "Validate RFC 9727 linkset".

Validation steps

  1. Validate RFC 9727 linkset

    API Catalog response did not match the expected shape. Content-Type "application/json; charset=utf-8" is not application/linkset+json.

  2. Fetch advertised API catalog targets

    API Catalog target https://agent.ai/api/specs/openapi.json (service-desc) returned HTTP 403 instead of a 2xx/3xx response.

Evidence
{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch API catalog",
      "status": "pass",
      "evidence": {
        "statusCode": 200,
        "contentType": "application/json; charset=utf-8"
      },
      "howToFix": "Publish /.well-known/api-catalog."
    },
    {
      "id": "validate",
      "title": "Validate RFC 9727 linkset",
      "status": "fail",
      "evidence": {
        "valid": false,
        "issue": "API Catalog response did not match the expected shape. Content-Type \"application/json; charset=utf-8\" is not application/linkset+json.",
        "compatibleContentType": false,
        "linksetItems": 1,
        "relations": [
          "service-desc",
          "service-doc",
          "service-meta",
          "item"
        ],
        "usefulRelations": [
          "service-desc",
          "service-doc"
        ],
        "legacyRelations": [],
        "hrefIssues": [],
        "targetUrlIssues": [],
        "links": [
          {
            "anchor": "https://agent.ai/",
            "rel": "service-desc",
            "href": "https://agent.ai/api/specs/openapi.json",
            "type": "application/vnd.oai.openapi+json"
          },
          {
            "anchor": "https://agent.ai/",
            "rel": "service-doc",
            "href": "https://docs.agent.ai/api-reference",
            "type": "text/html"
          },
          {
            "anchor": "https://agent.ai/",
            "rel": "service-meta",
            "href": "https://agent.ai/.well-known/oauth-authorization-server",
            "type": "application/json"
          },
          {
            "anchor": "https://agent.ai/",
            "rel": "service-meta",
            "href": "https://agent.ai/.well-known/oauth-protected-resource",
            "type": "application/json"
          },
          {
            "anchor": "https://agent.ai/",
            "rel": "item",
            "href": "https://mcp.agent.ai/mcp"
          },
          {
            "anchor": "https://agent.ai/",
            "rel": "item",
            "href": "https://agent.ai/ask"
          },
          {
            "anchor": "https://agent.ai/",
            "rel": "item",
            "href": "https://agent.ai/.well-known/agent-card.json",
            "type": "application/json"
          },
          {
            "anchor": "https://agent.ai/",
            "rel": "item",
            "href": "https://agent.ai/.well-known/ai-plugin.json",
            "type": "application/json"
          },
          {
            "anchor": "https://agent.ai/",
            "rel": "item",
            "href": "https://agent.ai/.well-known/agent.json",
            "type": "application/json"
          }
        ],
        "parsedSummary": [
          {
            "anchor": "https://agent.ai/",
            "service-desc": [
              {
                "href": "https://agent.ai/api/specs/openapi.json",
                "type": "application/vnd.oai.openapi+json",
                "title": "Agent.ai REST API — OpenAPI 3.0 spec (176+ operations)"
              }
            ],
            "service-doc": [
              {
                "href": "https://docs.agent.ai/api-reference",
                "type": "text/html",
                "title": "Agent.ai REST API reference"
              }
            ],
            "service-meta": [
              {
                "href": "https://agent.ai/.well-known/oauth-authorization-server",
                "type": "application/json",
                "title": "OAuth 2.1 authorization server metadata (RFC 8414)"
              },
              {
                "href": "https://agent.ai/.well-known/oauth-protected-resource",
                "type": "application/json",
                "title": "OAuth protected resource metadata (RFC 9728)"
              }
            ],
            "item": [
              {
                "href": "https://mcp.agent.ai/mcp",
                "title": "Agent.ai MCP server (Streamable HTTP)",
                "describedby": [
                  {
                    "href": "https://agent.ai/.well-known/mcp/server-card.json",
                    "type": "application/json"
                  }
                ]
              },
              {
                "href": "https://agent.ai/ask",
                "title": "Agent.ai NLWeb /ask natural-language endpoint"
              },
              {
                "href": "https://agent.ai/.well-known/agent-card.json",
                "title": "A2A (agent-to-agent) agent card",
                "type": "application/json"
              },
              {
                "href": "https://agent.ai/.well-known/ai-plugin.json",
                "title": "OpenAI plugin manifest",
                "type": "application/json"
              },
              {
                "href": "https://agent.ai/.well-known/agent.json",
                "title": "Generic agent discovery",
                "type": "application/json"
              }
            ]
          }
        ],
        "rawExcerpt": "{\"linkset\":[{\"anchor\":\"https://agent.ai/\",\"service-desc\":[{\"href\":\"https://agent.ai/api/specs/openapi.json\",\"type\":\"application/vnd.oai.openapi+json\",\"title\":\"Agent.ai REST API — OpenAPI 3.0 spec (176+ operations)\"}],\"service-doc\":[{\"href\":\"https://docs.agent.ai/api-reference\",\"type\":\"text/html\",\"title\":\"Agent.ai REST API reference\"}],\"service-meta\":[{\"href\":\"https://agent.ai/.well-known/oauth-authorization-server\",\"type\":\"application/json\",\"title\":\"OAuth 2.1 authorization server metadata (RFC 8414)\"},{\"href\":\"https://agent.ai/.well-known/oauth-protected-resource\",\"type\":\"application/json\",\"title\":\"OAuth protected resource metadata (RFC 9728)\"}],\"item\":[{\"href\":\"https://mcp.agent.ai/mcp\",\"title\":\"Agent.ai MCP server (Streamable HTTP)\",\"describedby\":[{\"href\":\"https://agent.ai/.well-known/mc"
      },
      "issue": "API Catalog response did not match the expected shape. Content-Type \"application/json; charset=utf-8\" is not application/linkset+json.",
      "howToFix": "Use application/linkset+json with service-desc, service-doc, and status relations that each include href."
    },
    {
      "id": "target-validation",
      "title": "Fetch advertised API catalog targets",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "rel": "service-desc",
            "href": "https://agent.ai/api/specs/openapi.json",
            "type": "application/vnd.oai.openapi+json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "typeMatches": false
          },
          {
            "rel": "service-doc",
            "href": "https://docs.agent.ai/api-reference",
            "skipped": "External target was not fetched."
          },
          {
            "rel": "service-meta",
            "href": "https://agent.ai/.well-known/oauth-authorization-server",
            "type": "application/json",
            "statusCode": 200,
            "contentType": "application/json",
            "typeMatches": true
          },
          {
            "rel": "service-meta",
            "href": "https://agent.ai/.well-known/oauth-protected-resource",
            "type": "application/json",
            "statusCode": 200,
            "contentType": "application/json; charset=utf-8",
            "typeMatches": true
          },
          {
            "rel": "item",
            "href": "https://mcp.agent.ai/mcp",
            "skipped": "External target was not fetched."
          },
          {
            "rel": "item",
            "href": "https://agent.ai/ask",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "typeMatches": true
          },
          {
            "rel": "item",
            "href": "https://agent.ai/.well-known/agent-card.json",
            "type": "application/json",
            "statusCode": 200,
            "contentType": "application/json; charset=utf-8",
            "typeMatches": true
          },
          {
            "rel": "item",
            "href": "https://agent.ai/.well-known/ai-plugin.json",
            "type": "application/json",
            "statusCode": 200,
            "contentType": "application/json; charset=utf-8",
            "typeMatches": true
          },
          {
            "rel": "item",
            "href": "https://agent.ai/.well-known/agent.json",
            "type": "application/json",
            "statusCode": 200,
            "contentType": "application/json; charset=utf-8",
            "typeMatches": true
          }
        ],
        "failures": [
          {
            "rel": "service-desc",
            "href": "https://agent.ai/api/specs/openapi.json",
            "expectedType": "application/vnd.oai.openapi+json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "reason": "Target did not return HTTP 2xx/3xx."
          },
          {
            "rel": "service-desc",
            "href": "https://agent.ai/api/specs/openapi.json",
            "expectedType": "application/vnd.oai.openapi+json",
            "actualContentType": "text/html; charset=UTF-8",
            "reason": "Content-Type did not match advertised type."
          },
          {
            "rel": "item",
            "href": "https://agent.ai/ask",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "reason": "Target did not return HTTP 2xx/3xx."
          }
        ]
      },
      "issue": "API Catalog target https://agent.ai/api/specs/openapi.json (service-desc) returned HTTP 403 instead of a 2xx/3xx response.",
      "howToFix": "Make each same-origin API catalog href reachable and serve the advertised media type."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Content freshness signals

Content freshness signals is missing or incomplete.

33 Fail

Needs attention

Content freshness signals

Failed check
01

Issue

Content freshness signals are incomplete: missing Last-Modified HTTP header; missing dateModified/datePublished in JSON-LD; missing meta or <time> freshness tags.

02

Why it matters

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

Check name

Content freshness signals

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

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

Result

Content freshness signals is missing or incomplete.

Evidence
{
  "lastModified": null,
  "schemaDates": [],
  "metaDateCount": 0,
  "timeDateCount": 0
}

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation failed at "Markdown content type".

33 Fail

Needs attention

Markdown negotiation

Failed check
01

Issue

Content-Type "text/html; charset=UTF-8" does not indicate Markdown when requested with Accept: text/markdown.

02

Why it matters

Markdown negotiation gives agents a cleaner representation of page content while preserving normal HTML for browsers.

Check name

Markdown negotiation

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Return HTML responses as markdown when agents request it.

Result

Markdown negotiation failed at "Markdown content type".

Validation steps

  1. Markdown content type

    Content-Type "text/html; charset=UTF-8" does not indicate Markdown when requested with Accept: text/markdown.

  2. Vary: Accept header

    Markdown negotiation is missing Vary: Accept; current Vary header is "(none)".

  3. Structured Markdown body

    Markdown response is missing a heading.

Evidence
{
  "failedStep": "content-type",
  "steps": [
    {
      "id": "content-type",
      "title": "Markdown content type",
      "status": "fail",
      "evidence": {
        "statusCode": 403,
        "contentType": "text/html; charset=UTF-8"
      },
      "issue": "Content-Type \"text/html; charset=UTF-8\" does not indicate Markdown when requested with Accept: text/markdown.",
      "howToFix": "Return Content-Type: text/markdown; charset=utf-8 for requests with Accept: text/markdown."
    },
    {
      "id": "vary-accept",
      "title": "Vary: Accept header",
      "status": "fail",
      "evidence": {
        "vary": ""
      },
      "issue": "Markdown negotiation is missing Vary: Accept; current Vary header is \"(none)\".",
      "howToFix": "Add Vary: Accept on negotiated Markdown responses so shared caches keep HTML and Markdown variants separate."
    },
    {
      "id": "markdown-content",
      "title": "Structured Markdown body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "hasHeading": false,
        "wordCount": 355,
        "excerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><m",
        "issue": "Markdown response is missing a heading."
      },
      "issue": "Markdown response is missing a heading.",
      "howToFix": "Return Markdown with at least one heading and substantive page content, including useful links or instructions for agents."
    }
  ]
}

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is missing or incomplete.

33 Fail

Needs attention

Semantic HTML

Failed check
01

Issue

Semantic HTML is incomplete: 1 buttons missing accessible names.

Details

02

Why it matters

Semantic HTML gives browsers, assistive technology, search systems, and agents reliable landmarks, headings, controls, form semantics, and image context.

Check name

Semantic HTML

Score

0/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose readable page structure through semantic HTML and accessible controls.

Result

Semantic HTML is missing or incomplete.

Evidence
{
  "main": true,
  "nav": true,
  "footer": true,
  "meaningfulH1": true,
  "headingOrder": true,
  "accessibleLinks": true,
  "accessibleButtons": false,
  "imageAltCoverage": true,
  "formAutocompleteCoverage": true,
  "details": {
    "inaccessibleLinks": [],
    "inaccessibleButtons": [
      "<button type=\"button\" class=\"chakra-button undefined align-items-center justify-content-center css-1mmjvrq\" id=\"back-to-top\"><svg stroke=\"currentColor\" fill=\"currentColor\" stroke-width=\"0\" viewBox=\"0 0 20 20\" aria-hidden=\"true\" class=\"flex-shrink-0\" height=\"32\" width=\"32\" xmlns=\"http://www.w3.org/2000/svg\"><path fill-rule=\"evenodd\" d=\"M3.293 9.707a1 1 0 010-1.414l6-6a1 1 0 011.414 0l6 6a1 1 0 01-1.414 1.414L11 5.414V17a1 1 0 11-2 0V5.414L4.707 9.707a1 1 0 01-1.414 0z\" clip-rule=\"evenodd\"/></svg>"
    ],
    "missingAutocompleteInputs": [],
    "imagesMissingAlt": [],
    "skippedHeadingLevels": []
  },
  "counts": {
    "h1": 1,
    "headings": 1,
    "links": 21,
    "inaccessibleLinks": 0,
    "buttons": 2,
    "inaccessibleButtons": 1,
    "images": 6,
    "imagesWithAlt": 6,
    "autocompleteInputs": 0,
    "inputsWithAutocomplete": 0,
    "missingAutocompleteInputs": 0
  }
}

Agent Ease of UseMCPInformational

WebMCP manifest

WebMCP manifest failed at "Fetch to find resource".

33 Fail

Needs attention

WebMCP manifest

Failed check
01

Issue

WebMCP manifest was not found at the expected path.

02

Why it matters

A WebMCP manifest advertises browser-exposed tools declaratively so agents can understand available site actions before invoking them.

Check name

WebMCP manifest

Score

0/100

Status

fail

Category

MCP

Maturity

Informational

Goal

Publish a WebMCP manifest for declarative browser tool discovery when using the draft manifest convention.

Result

WebMCP manifest failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    WebMCP manifest was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/webmcp.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 104554
          },
          {
            "path": "/webmcp.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5432
          },
          {
            "path": "/mcp.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5402
          }
        ]
      },
      "issue": "WebMCP manifest was not found at the expected path.",
      "howToFix": "Keep declarative WebMCP manifest discovery informational until the manifest shape stabilizes; validate tools if you publish one."
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Fetch to find resource".

25 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index was not found at the expected path.

02

Why it matters

An Agent Skills index lets clients find task-specific SKILL.md documents that describe how to use site capabilities correctly.

Check name

Agent Skills index

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent skills discovery index.

Result

Agent Skills index failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    Agent Skills index was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agent-skills/index.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 104555
          },
          {
            "path": "/.well-known/skills/index.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 104554
          }
        ]
      },
      "issue": "Agent Skills index was not found at the expected path.",
      "howToFix": "Publish an index with a non-empty skills array and reachable SKILL.md URLs."
    }
  ]
}

Agent Ease of UseSkill DiscoveryInformational

agents.json

agents.json failed at "Fetch to find resource".

25 Fail

Needs attention

agents.json

Failed check
01

Issue

agents.json was not found at the expected path.

02

Why it matters

agents.json gives clients a simple directory of agent-facing capabilities and contacts when a site chooses to advertise them.

Check name

agents.json

Score

0/100

Status

fail

Category

Skill Discovery

Maturity

Informational

Goal

Publish an agents.json directory for agent-facing capabilities and contacts when using this convention.

Result

agents.json failed at "Fetch to find resource".

Validation steps

  1. Fetch to find resource

    agents.json was not found at the expected path.

Evidence
{
  "failedStep": "fetch",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "fail",
      "evidence": {
        "checked": [
          {
            "path": "/.well-known/agents.json",
            "statusCode": 404,
            "contentType": "text/html; charset=utf-8",
            "length": 104556
          },
          {
            "path": "/agents.json",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5432
          }
        ]
      },
      "issue": "agents.json was not found at the expected path.",
      "howToFix": "If this site uses agents.json, publish JSON with an agents array containing name and url for each agent."
    }
  ]
}

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy is missing or incomplete.

25 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Content-Security-Policy is missing or incomplete.

02

Why it matters

Content Security Policy limits where scripts, styles, frames, and connections can load from, reducing the impact of injection bugs.

Check name

Content-Security-Policy

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain script, style, frame, and resource loading with a Content-Security-Policy header.

Result

Content-Security-Policy is missing or incomplete.

Evidence
{
  "header": "content-security-policy",
  "value": null
}

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection is missing or incomplete.

25 Fail

Needs attention

Frame protection

Failed check
01

Issue

Frame protection is missing or incomplete.

02

Why it matters

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

Check name

Frame protection

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent unwanted framing with X-Frame-Options or CSP frame-ancestors.

Result

Frame protection is missing or incomplete.

Evidence
{
  "xFrameOptions": null,
  "validXFrame": false,
  "contentSecurityPolicy": null,
  "cspFrameAncestors": false
}

Security & TrustSecurity & TrustEstablished

Referrer-Policy

Referrer-Policy is missing or incomplete.

25 Fail

Needs attention

Referrer-Policy

Failed check
01

Issue

Referrer-Policy is missing or incomplete.

02

Why it matters

Referrer-Policy controls how much URL context is sent to other origins, limiting accidental leakage of paths, queries, and identifiers.

Check name

Referrer-Policy

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Limit how much referrer data leaves the site.

Result

Referrer-Policy is missing or incomplete.

Evidence
{
  "header": "referrer-policy",
  "value": null
}

Security & TrustSecurity & TrustEstablished

X-Content-Type-Options

X-Content-Type-Options is missing or incomplete.

25 Fail

Needs attention

X-Content-Type-Options

Failed check
01

Issue

X-Content-Type-Options is missing or incomplete.

02

Why it matters

X-Content-Type-Options prevents browsers from treating mislabeled files as executable content, reducing content-sniffing attacks.

Check name

X-Content-Type-Options

Score

0/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Prevent MIME sniffing for browser-loaded resources.

Result

X-Content-Type-Options is missing or incomplete.

Evidence
{
  "header": "x-content-type-options",
  "value": null
}

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

MCP Server Card failed at "Validate resource body".

21 Fail

Needs attention

MCP Server Card

Failed check
01

Issue

MCP Server Card response is missing required fields or has invalid transports.

Details

02

Why it matters

MCP Server Cards help agents discover server transports, capabilities, and protocol details before opening an MCP session.

Check name

MCP Server Card

Score

38/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

Publish an MCP Server Card for agent discovery.

Result

MCP Server Card failed at "Validate resource body".

Validation steps

  1. Validate resource body

    MCP Server Card response is missing required fields or has invalid transports.

    Missing required fields
    • serverInfo.name
    • serverInfo.version
    • protocolVersion
    • capabilities object
  2. Verify advertised MCP transport endpoints

    At least one same-origin transport failed MCP initialize or advertised capability list probes. See probes[].capabilityProbes for the exact method, status, JSON-RPC error, and response excerpt.

  3. Verify advertised MCP tool execution

    MCP discovery passed, but no advertised tool could be safely executed by this scanner.

Evidence
{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/mcp/server-card.json",
        "statusCode": 200,
        "contentType": "application/json; charset=utf-8"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": true,
        "compatibleContentType": true,
        "document": {
          "schemaVersion": "2025-06-18",
          "name": "agent-ai",
          "displayName": "Agent.ai",
          "description": "First-party MCP server for Agent.ai. Exposes the full Agent.ai action catalog (web research, scraping, LLM calls, image/audio, 60+ third-party integrations, and every published marketplace agent) as typed MCP tools with descriptions, input schemas, and behavioral annotations.",
          "version": "1.1.0",
          "iconUrl": "https://agent.ai/web-app-manifest-512x512.png",
          "homepage": "https://agent.ai",
          "documentation": "https://docs.agent.ai/mcp",
          "publisher": {
            "name": "Agent.ai",
            "url": "https://agent.ai/about",
            "contactEmail": "[email protected]"
          },
          "serverUrl": "https://mcp.agent.ai/mcp",
          "transports": [
            {
              "type": "streamable-http",
              "url": "https://mcp.agent.ai/mcp",
              "recommended": true
            },
            {
              "type": "sse",
              "url": "https://mcp.agent.ai/sse",
              "deprecated": true
            }
          ],
          "authentication": {
            "required": true,
            "type": "oauth2",
            "authorizationServerMetadata": "https://mcp.agent.ai/.well-known/oauth-authorization-server",
            "protectedResourceMetadata": "https://agent.ai/.well-known/oauth-protected-resource",
            "scopes": [
              "openid",
              "email",
              "profile",
              "mcp:access"
            ],
            "pkce": {
              "required": true,
              "methods": [
                "S256"
              ]
            },
            "alternate": {
              "type": "apiKey",
              "header": "Authorization",
              "format": "Bearer <AGENTAI_API_KEY>"
            }
          },
          "instructions": "Call `tools/list` to discover available tools. Every tool name follows `snake_case` and every tool declares an inputSchema. Tools that modify state carry `annotations.destructiveHint=true`; confirm with the user before calling those. Tools that only read data carry `annotations.readOnlyHint=true`. Use `agent_ai_marketplace_search` for natural-language discovery of agents. Use `agent_ai_run_agent` to execute a specific agent by id. Errors follow JSON-RPC 2.0 with machine-readable `code` + `message`.",
          "categories": [
            "sales",
            "marketing",
            "recruiting",
            "research",
            "productivity",
            "automation",
            "integrations"
          ],
          "tools": [
            {
              "name": "agent_ai_marketplace_search",
              "description": "Search the Agent.ai marketplace for agents that match a natural-language task description. Returns id, name, description, and call signature.",
              "annotations": {
                "readOnlyHint": true,
                "destructiveHint": false
              }
            },
            {
              "name": "agent_ai_list_actions",
              "description": "List every built-in action (176) available inside the Agent.ai builder: web scraping, LLM prompts, image generation, integrations, etc.",
              "annotations": {
                "readOnlyHint": true,
                "destructiveHint": false
              }
            },
            {
              "name": "agent_ai_run_agent",
              "description": "Execute a specific Agent.ai agent by id or slug with a typed input payload. Returns the run id and (when complete) the run outputs.",
              "annotations": {
                "readOnlyHint": false,
                "destructiveHint": false,
                "idempotentHint": false
              }
            },
            {
              "name": "agent_ai_get_run",
              "description": "Fetch the status and outputs of a previously started agent run by run id.",
              "annotations": {
                "readOnlyHint": true,
                "destructiveHint": false
              }
            }
          ],
          "resources": [
            {
              "uri": "https://agent.ai/llms.txt",
              "name": "llms.txt",
              "description": "Index of developer and agent-facing resources"
            },
            {
              "uri": "https://agent.ai/api/specs/openapi.json",
              "name": "OpenAPI spec",
              "description": "Full REST API description (176 operations)"
            }
          ]
        },
        "rawExcerpt": "{\n  \"schemaVersion\": \"2025-06-18\",\n  \"name\": \"agent-ai\",\n  \"displayName\": \"Agent.ai\",\n  \"description\": \"First-party MCP server for Agent.ai. Exposes the full Agent.ai action catalog (web research, scraping, LLM calls, image/audio, 60+ third-party integrations, and every published marketplace agent) as typed MCP tools with descriptions, input schemas, and behavioral annotations.\",\n  \"version\": \"1.1.0\",\n  \"iconUrl\": \"https://agent.ai/web-app-manifest-512x512.png\",\n  \"homepage\": \"https://agent.ai\",\n  \"documentation\": \"https://docs.agent.ai/mcp\",\n  \"publisher\": {\n    \"name\": \"Agent.ai\",\n    \"url\": \"https://agent.ai/about\",\n    \"contactEmail\": \"[email protected]\"\n  },\n  \"serverUrl\": \"https://mcp.agent.ai/mcp\",\n  \"transports\": [\n    {\n      \"type\": \"streamable-http\",\n      \"url\": \"https://mcp.age",
        "issue": "MCP Server Card response is missing required fields or has invalid transports.",
        "issueDetails": [
          {
            "title": "Missing required fields",
            "items": [
              "serverInfo.name",
              "serverInfo.version",
              "protocolVersion",
              "capabilities object"
            ]
          }
        ],
        "missing": [
          "serverInfo.name",
          "serverInfo.version",
          "protocolVersion",
          "capabilities object"
        ],
        "protocolVersion": "",
        "transportCount": 2,
        "transports": [
          {
            "type": "streamable-http",
            "url": "https://mcp.agent.ai/mcp",
            "recommended": true
          },
          {
            "type": "sse",
            "url": "https://mcp.agent.ai/sse",
            "deprecated": true
          }
        ],
        "invalidTransports": [],
        "capabilityKeys": []
      },
      "issue": "MCP Server Card response is missing required fields or has invalid transports.",
      "howToFix": "Publish an MCP server card with valid transports and make each advertised local endpoint answer an MCP initialize request.",
      "issueDetails": [
        {
          "title": "Missing required fields",
          "items": [
            "serverInfo.name",
            "serverInfo.version",
            "protocolVersion",
            "capabilities object"
          ]
        }
      ]
    },
    {
      "id": "endpoint-verification",
      "title": "Verify advertised MCP transport endpoints",
      "status": "fail",
      "evidence": {
        "probes": [
          {
            "url": "https://mcp.agent.ai/mcp",
            "skipped": "External transport endpoint was not probed."
          },
          {
            "url": "https://mcp.agent.ai/sse",
            "skipped": "External transport endpoint was not probed."
          }
        ]
      },
      "issue": "At least one same-origin transport failed MCP initialize or advertised capability list probes. See probes[].capabilityProbes for the exact method, status, JSON-RPC error, and response excerpt.",
      "howToFix": "Expose a real MCP endpoint for advertised transports, or remove transports that point to ordinary HTTP APIs."
    },
    {
      "id": "tool-execution",
      "title": "Verify advertised MCP tool execution",
      "status": "warning",
      "evidence": {
        "probes": [
          {
            "url": "https://mcp.agent.ai/mcp",
            "skipped": "External transport endpoint was not probed."
          },
          {
            "url": "https://mcp.agent.ai/sse",
            "skipped": "External transport endpoint was not probed."
          }
        ]
      },
      "issue": "MCP discovery passed, but no advertised tool could be safely executed by this scanner.",
      "howToFix": "Implement tools/call for advertised tools, or report the MCP card as discovery-only until tools are executable."
    }
  ]
}

AI DiscoverabilityDiscoverabilityEstablished

High-value schema types

High-value schema types is missing or incomplete.

20 Fail

Needs attention

High-value schema types

Failed check
01

Issue

No high-value schema types (e.g. Article, Product, Service) were found.

02

Why it matters

High-value schema types tell agents whether a page is an article, product, event, service, or other actionable content type.

Check name

High-value schema types

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Use schema types that describe the page's primary content or offering.

Result

High-value schema types is missing or incomplete.

Evidence
{
  "found": [],
  "expected": [
    "Article",
    "BlogPosting",
    "NewsArticle",
    "Product",
    "SoftwareApplication",
    "FAQPage",
    "LocalBusiness",
    "VideoObject",
    "HowTo",
    "Event",
    "Course",
    "Review",
    "Service"
  ],
  "allTypes": []
}

AI DiscoverabilityDiscoverabilityEstablished

JSON-LD present

JSON-LD present is missing or incomplete.

20 Fail

Needs attention

JSON-LD present

Failed check
01

Issue

No JSON-LD blocks found.

02

Why it matters

JSON-LD is a low-friction structured data format that agents can extract without interpreting page presentation or microdata markup.

Check name

JSON-LD present

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Expose schema.org JSON-LD so AI search systems can parse page entities.

Result

JSON-LD present is missing or incomplete.

Evidence
{
  "blocks": 0,
  "validBlocks": 0,
  "schemaContextBlocks": 0,
  "errors": [],
  "documents": [],
  "nodes": []
}

AI DiscoverabilityDiscoverabilityEstablished

Link headers

Link headers failed at "Find useful Link headers".

20 Fail

Needs attention

Link headers

Failed check
01

Issue

No useful agent discovery Link headers were found.

02

Why it matters

Link headers let automated clients discover API catalogs, documentation, and machine-readable alternates without parsing page markup first.

Check name

Link headers

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Include Link response headers for agent discovery using RFC 8288.

Result

Link headers failed at "Find useful Link headers".

Validation steps

  1. Find useful Link headers

    No useful agent discovery Link headers were found.

  2. Fetch same-origin Link header targets

    Link headers did not expose any same-origin targets to validate.

Evidence
{
  "failedStep": "presence",
  "steps": [
    {
      "id": "presence",
      "title": "Find useful Link headers",
      "status": "fail",
      "evidence": {
        "links": []
      },
      "issue": "No useful agent discovery Link headers were found.",
      "howToFix": "Expose useful Link headers such as rel=\"api-catalog\", rel=\"service-doc\", and rel=\"service-desc\"."
    },
    {
      "id": "target-validation",
      "title": "Fetch same-origin Link header targets",
      "status": "fail",
      "evidence": {
        "checked": [],
        "failures": [
          {
            "reason": "No same-origin Link header targets were available to fetch."
          }
        ]
      },
      "issue": "Link headers did not expose any same-origin targets to validate.",
      "howToFix": "Make each same-origin Link href reachable and serve the advertised media type."
    }
  ]
}

AI DiscoverabilityDiscoverabilityEstablished

Organization / WebSite schema

Organization / WebSite schema is missing or incomplete.

20 Fail

Needs attention

Organization / WebSite schema

Failed check
01

Issue

Neither Organization nor WebSite schema types were found in JSON-LD.

02

Why it matters

Organization and WebSite schema help agents identify the publisher, canonical site identity, logo, and related profiles for attribution.

Check name

Organization / WebSite schema

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is missing or incomplete.

Evidence
{
  "found": [],
  "allTypes": []
}

AI DiscoverabilityDiscoverabilityEstablished

Sitemap

Sitemap is missing or incomplete.

20 Fail

Needs attention

Sitemap

Failed check
01

Issue

No valid XML sitemap found at checked locations: https://agent.ai/sitemap.xml, https://agent.ai/sitemap.xml, https://agent.ai/sitemap_index.xml, https://agent.ai/sitemap-index.xml.

02

Why it matters

Sitemaps help crawlers and agents discover canonical URLs, updated pages, and deeper content that may not be obvious from the homepage navigation.

Check name

Sitemap

Score

0/100

Status

fail

Category

Discoverability

Maturity

Established

Goal

Publish a sitemap and reference it from robots.txt.

Result

Sitemap is missing or incomplete.

Evidence
{
  "checked": [
    "https://agent.ai/sitemap.xml",
    "https://agent.ai/sitemap.xml",
    "https://agent.ai/sitemap_index.xml",
    "https://agent.ai/sitemap-index.xml"
  ]
}

Agent Ease of UseMCPEmerging recommendation

mcp.json

mcp.json failed at "Validate resource body".

17 Fail

Needs attention

mcp.json

Failed check
01

Issue

mcp.json response did not match the expected MCP server metadata shape. missing: serverInfo.name, protocolVersion, capabilities object.

Details

02

Why it matters

MCP clients need trustworthy server metadata, protocol version, transport details, and capability hints before connecting to a remote MCP server.

Check name

mcp.json

Score

50/100

Status

fail

Category

MCP

Maturity

Emerging recommendation

Goal

Expose a stable MCP server metadata document that points agents to the site's MCP endpoint.

Result

mcp.json failed at "Validate resource body".

Validation steps

  1. Validate resource body

    mcp.json response did not match the expected MCP server metadata shape. missing: serverInfo.name, protocolVersion, capabilities object.

    Missing required fields
    • serverInfo.name
    • protocolVersion
    • capabilities object
Evidence
{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/mcp/server-card.json",
        "statusCode": 200,
        "contentType": "application/json; charset=utf-8"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": true,
        "compatibleContentType": true,
        "document": {
          "schemaVersion": "2025-06-18",
          "name": "agent-ai",
          "displayName": "Agent.ai",
          "description": "First-party MCP server for Agent.ai. Exposes the full Agent.ai action catalog (web research, scraping, LLM calls, image/audio, 60+ third-party integrations, and every published marketplace agent) as typed MCP tools with descriptions, input schemas, and behavioral annotations.",
          "version": "1.1.0",
          "iconUrl": "https://agent.ai/web-app-manifest-512x512.png",
          "homepage": "https://agent.ai",
          "documentation": "https://docs.agent.ai/mcp",
          "publisher": {
            "name": "Agent.ai",
            "url": "https://agent.ai/about",
            "contactEmail": "[email protected]"
          },
          "serverUrl": "https://mcp.agent.ai/mcp",
          "transports": [
            {
              "type": "streamable-http",
              "url": "https://mcp.agent.ai/mcp",
              "recommended": true
            },
            {
              "type": "sse",
              "url": "https://mcp.agent.ai/sse",
              "deprecated": true
            }
          ],
          "authentication": {
            "required": true,
            "type": "oauth2",
            "authorizationServerMetadata": "https://mcp.agent.ai/.well-known/oauth-authorization-server",
            "protectedResourceMetadata": "https://agent.ai/.well-known/oauth-protected-resource",
            "scopes": [
              "openid",
              "email",
              "profile",
              "mcp:access"
            ],
            "pkce": {
              "required": true,
              "methods": [
                "S256"
              ]
            },
            "alternate": {
              "type": "apiKey",
              "header": "Authorization",
              "format": "Bearer <AGENTAI_API_KEY>"
            }
          },
          "instructions": "Call `tools/list` to discover available tools. Every tool name follows `snake_case` and every tool declares an inputSchema. Tools that modify state carry `annotations.destructiveHint=true`; confirm with the user before calling those. Tools that only read data carry `annotations.readOnlyHint=true`. Use `agent_ai_marketplace_search` for natural-language discovery of agents. Use `agent_ai_run_agent` to execute a specific agent by id. Errors follow JSON-RPC 2.0 with machine-readable `code` + `message`.",
          "categories": [
            "sales",
            "marketing",
            "recruiting",
            "research",
            "productivity",
            "automation",
            "integrations"
          ],
          "tools": [
            {
              "name": "agent_ai_marketplace_search",
              "description": "Search the Agent.ai marketplace for agents that match a natural-language task description. Returns id, name, description, and call signature.",
              "annotations": {
                "readOnlyHint": true,
                "destructiveHint": false
              }
            },
            {
              "name": "agent_ai_list_actions",
              "description": "List every built-in action (176) available inside the Agent.ai builder: web scraping, LLM prompts, image generation, integrations, etc.",
              "annotations": {
                "readOnlyHint": true,
                "destructiveHint": false
              }
            },
            {
              "name": "agent_ai_run_agent",
              "description": "Execute a specific Agent.ai agent by id or slug with a typed input payload. Returns the run id and (when complete) the run outputs.",
              "annotations": {
                "readOnlyHint": false,
                "destructiveHint": false,
                "idempotentHint": false
              }
            },
            {
              "name": "agent_ai_get_run",
              "description": "Fetch the status and outputs of a previously started agent run by run id.",
              "annotations": {
                "readOnlyHint": true,
                "destructiveHint": false
              }
            }
          ],
          "resources": [
            {
              "uri": "https://agent.ai/llms.txt",
              "name": "llms.txt",
              "description": "Index of developer and agent-facing resources"
            },
            {
              "uri": "https://agent.ai/api/specs/openapi.json",
              "name": "OpenAPI spec",
              "description": "Full REST API description (176 operations)"
            }
          ]
        },
        "rawExcerpt": "{\n  \"schemaVersion\": \"2025-06-18\",\n  \"name\": \"agent-ai\",\n  \"displayName\": \"Agent.ai\",\n  \"description\": \"First-party MCP server for Agent.ai. Exposes the full Agent.ai action catalog (web research, scraping, LLM calls, image/audio, 60+ third-party integrations, and every published marketplace agent) as typed MCP tools with descriptions, input schemas, and behavioral annotations.\",\n  \"version\": \"1.1.0\",\n  \"iconUrl\": \"https://agent.ai/web-app-manifest-512x512.png\",\n  \"homepage\": \"https://agent.ai\",\n  \"documentation\": \"https://docs.agent.ai/mcp\",\n  \"publisher\": {\n    \"name\": \"Agent.ai\",\n    \"url\": \"https://agent.ai/about\",\n    \"contactEmail\": \"[email protected]\"\n  },\n  \"serverUrl\": \"https://mcp.agent.ai/mcp\",\n  \"transports\": [\n    {\n      \"type\": \"streamable-http\",\n      \"url\": \"https://mcp.age",
        "issue": "mcp.json response did not match the expected MCP server metadata shape. missing: serverInfo.name, protocolVersion, capabilities object.",
        "issueDetails": [
          {
            "title": "Missing required fields",
            "items": [
              "serverInfo.name",
              "protocolVersion",
              "capabilities object"
            ]
          }
        ],
        "missing": [
          "serverInfo.name",
          "protocolVersion",
          "capabilities object"
        ],
        "protocolVersion": "",
        "transportCount": 2,
        "transports": [
          {
            "type": "streamable-http",
            "url": "https://mcp.agent.ai/mcp",
            "recommended": true
          },
          {
            "type": "sse",
            "url": "https://mcp.agent.ai/sse",
            "deprecated": true
          }
        ],
        "invalidTransports": [],
        "toolCount": 4,
        "capabilityKeys": []
      },
      "issue": "mcp.json response did not match the expected MCP server metadata shape. missing: serverInfo.name, protocolVersion, capabilities object.",
      "howToFix": "Publish mcp.json or an MCP server card with serverInfo, protocolVersion, transport endpoint, and capabilities.",
      "issueDetails": [
        {
          "title": "Missing required fields",
          "items": [
            "serverInfo.name",
            "protocolVersion",
            "capabilities object"
          ]
        }
      ]
    }
  ]
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

agent.json

agent.json failed at "Validate resource body".

13 Fail

Needs attention

agent.json

Failed check
01

Issue

agent.json response did not match the expected AWP shape. missing: awp_version, domain, intent; no actions found.

02

Why it matters

agent.json is an emerging machine-readable manifest for declaring what a website does, how agents authenticate, and which actions or protocols are available.

Check name

agent.json

Score

50/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish the singular Agent Web Protocol agent.json manifest without confusing it with the separate agents.json directory convention.

Result

agent.json failed at "Validate resource body".

Validation steps

  1. Validate resource body

    agent.json response did not match the expected AWP shape. missing: awp_version, domain, intent; no actions found.

Evidence
{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/agent.json",
        "statusCode": 200,
        "contentType": "application/json; charset=utf-8"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "validJson": true,
        "compatibleContentType": true,
        "document": {
          "schema_version": "v1",
          "name": "Agent.ai",
          "handle": "agent.ai",
          "description": "Marketplace and execution layer for professional AI agents. Discover agents for sales prospecting, content marketing, social content, meeting prep, cold-call prep, and research — then call them via REST or MCP.",
          "url": "https://agent.ai",
          "logo_url": "https://agent.ai/web-app-manifest-512x512.png",
          "contact_email": "[email protected]",
          "legal_info_url": "https://agent.ai/terms",
          "privacy_policy_url": "https://agent.ai/privacy-policy",
          "documentation_url": "https://docs.agent.ai",
          "openapi_url": "https://agent.ai/api/specs/openapi.json",
          "llms_txt_url": "https://agent.ai/llms.txt",
          "markdown_url": "https://agent.ai/index.md",
          "mcp": {
            "transport": "streamable-http",
            "url": "https://mcp.agent.ai/mcp",
            "sse_url": "https://mcp.agent.ai/sse",
            "server_card_url": "https://agent.ai/.well-known/mcp/server-card.json",
            "discovery_url": "https://agent.ai/.well-known/mcp"
          },
          "a2a": {
            "agent_card_url": "https://agent.ai/.well-known/agent-card.json"
          },
          "auth": {
            "oauth2": {
              "issuer": "https://mcp.agent.ai",
              "metadata_url": "https://agent.ai/.well-known/oauth-authorization-server",
              "protected_resource_metadata_url": "https://agent.ai/.well-known/oauth-protected-resource",
              "authorization_endpoint": "https://mcp.agent.ai/authorize",
              "token_endpoint": "https://mcp.agent.ai/token",
              "registration_endpoint": "https://mcp.agent.ai/register",
              "scopes_supported": [
                "openid",
                "email",
                "profile",
                "mcp:access"
              ],
              "code_challenge_methods_supported": [
                "S256"
              ]
            },
            "api_key": {
              "header": "Authorization",
              "format": "Bearer <AGENTAI_API_KEY>",
              "docs_url": "https://docs.agent.ai/authentication"
            }
          },
          "capabilities": [
            "agent-marketplace-search",
            "agent-execution",
            "rest-api",
            "mcp-tools",
            "webhooks",
            "nlweb-ask",
            "a2a"
          ],
          "categories": [
            "sales",
            "marketing",
            "recruiting",
            "research",
            "productivity",
            "automation"
          ],
          "teams": [
            {
              "slug": "sales-prospecting",
              "name": "Sales Prospecting Team",
              "url": "https://agent.ai/team/sales-prospecting",
              "description": "Find, research, qualify, and draft outreach in one connected workflow."
            },
            {
              "slug": "content-marketing",
              "name": "Content Marketing Team",
              "url": "https://agent.ai/team/content-marketing",
              "description": "Audit, research, plan, and create SEO+AEO optimized content."
            },
            {
              "slug": "social-content",
              "name": "Social Content Team",
              "url": "https://agent.ai/team/social-content",
              "description": "Plan, create, and analyze LinkedIn content with AI-powered agents."
            }
          ]
        },
        "rawExcerpt": "{\n  \"schema_version\": \"v1\",\n  \"name\": \"Agent.ai\",\n  \"handle\": \"agent.ai\",\n  \"description\": \"Marketplace and execution layer for professional AI agents. Discover agents for sales prospecting, content marketing, social content, meeting prep, cold-call prep, and research \\u2014 then call them via REST or MCP.\",\n  \"url\": \"https://agent.ai\",\n  \"logo_url\": \"https://agent.ai/web-app-manifest-512x512.png\",\n  \"contact_email\": \"[email protected]\",\n  \"legal_info_url\": \"https://agent.ai/terms\",\n  \"privacy_policy_url\": \"https://agent.ai/privacy-policy\",\n  \"documentation_url\": \"https://docs.agent.ai\",\n  \"openapi_url\": \"https://agent.ai/api/specs/openapi.json\",\n  \"llms_txt_url\": \"https://agent.ai/llms.txt\",\n  \"markdown_url\": \"https://agent.ai/index.md\",\n  \"mcp\": {\n    \"transport\": \"streamable-http\",\n    \"",
        "issue": "agent.json response did not match the expected AWP shape. missing: awp_version, domain, intent; no actions found.",
        "missing": [
          "awp_version",
          "domain",
          "intent"
        ],
        "actionCount": 0,
        "invalidActions": [],
        "protocolKeys": [],
        "actions": []
      },
      "issue": "agent.json response did not match the expected AWP shape. missing: awp_version, domain, intent; no actions found.",
      "howToFix": "Publish agent.json with awp_version, domain, intent, and typed actions that point to real same-origin API or protocol endpoints."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible structured data match

AIO: Visible structured data match scored 0/100 and needs a fix.

10 Fail

Needs attention

AIO: Visible structured data match

Failed check
01

Issue

No JSON-LD structured data was detected.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Visible structured data match

Score

0/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Visible structured data match scored 0/100 and needs a fix.

Evidence
{
  "schemaCount": 0,
  "mismatches": [],
  "score": 0,
  "weight": 18
}

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Verify advertised A2A endpoint".

8 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

message/send did not return a successful A2A Message or Task result. Evidence includes status, JSON-RPC error, and response excerpt.

02

Why it matters

A2A Agent Cards let compatible clients discover agent skills, input and output modes, and the endpoint used to invoke those skills.

Check name

A2A Agent Card

Score

70/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an agent card so A2A-compatible clients can discover capabilities.

Result

A2A Agent Card failed at "Verify advertised A2A endpoint".

Validation steps

  1. Verify advertised A2A endpoint

    message/send did not return a successful A2A Message or Task result. Evidence includes status, JSON-RPC error, and response excerpt.

  2. Verify advertised A2A skill execution

    A2A endpoint responded, but advertised skill execution was not verified. Evidence includes the requested skill, status, JSON-RPC error, and response excerpt.

Evidence
{
  "failedStep": "endpoint-verification",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/agent-card.json",
        "statusCode": 200,
        "contentType": "application/json; charset=utf-8"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "pass",
      "evidence": {
        "valid": true,
        "validJson": true,
        "compatibleContentType": true,
        "document": {
          "protocolVersion": "0.3.0",
          "name": "Agent.ai",
          "description": "Marketplace and execution layer for professional AI agents. Agent.ai hosts thousands of purpose-built agents — Sales Prospecting, Content Marketing, Social Content, plus individual agents for meeting prep, cold-call prep, outreach, and research — and exposes each one as a typed A2A skill and MCP tool.",
          "url": "https://agent.ai",
          "iconUrl": "https://agent.ai/web-app-manifest-512x512.png",
          "provider": {
            "organization": "Agent.ai",
            "url": "https://agent.ai/about"
          },
          "version": "1.1.0",
          "documentationUrl": "https://docs.agent.ai",
          "defaultInputModes": [
            "text/plain",
            "application/json"
          ],
          "defaultOutputModes": [
            "text/plain",
            "application/json"
          ],
          "capabilities": {
            "streaming": true,
            "pushNotifications": true,
            "stateTransitionHistory": true
          },
          "securitySchemes": {
            "oauth2": {
              "type": "oauth2",
              "flows": {
                "authorizationCode": {
                  "authorizationUrl": "https://mcp.agent.ai/authorize",
                  "tokenUrl": "https://mcp.agent.ai/token",
                  "scopes": {
                    "openid": "OpenID Connect",
                    "email": "Email address",
                    "profile": "Profile info",
                    "mcp:access": "Call Agent.ai MCP tools and REST actions on behalf of the user"
                  }
                }
              }
            },
            "apiKey": {
              "type": "apiKey",
              "in": "header",
              "name": "Authorization",
              "description": "Bearer <AGENTAI_API_KEY>. See https://docs.agent.ai/authentication for how to obtain one."
            }
          },
          "security": [
            {
              "oauth2": [
                "openid",
                "email",
                "profile",
                "mcp:access"
              ]
            },
            {
              "apiKey": []
            }
          ],
          "endpoint": {
            "url": "https://mcp.agent.ai/mcp",
            "transport": "streamable-http"
          },
          "skills": [
            {
              "id": "marketplace_search",
              "name": "Search the agent marketplace",
              "description": "Given a natural-language query (e.g. 'find me an agent that researches companies on LinkedIn'), return a ranked list of Agent.ai agents that can do the job, with their IDs, descriptions, and call signatures.",
              "tags": [
                "marketplace",
                "search",
                "discovery"
              ],
              "inputModes": [
                "text/plain",
                "application/json"
              ],
              "outputModes": [
                "application/json"
              ]
            },
            {
              "id": "sales_prospecting_team",
              "name": "Sales Prospecting Team",
              "description": "Find, research, qualify, and draft outreach in one connected workflow. Delegates to Prospect Finder, Prospect Researcher, Lead Qualifier, and Outreach Drafter.",
              "tags": [
                "sales",
                "prospecting",
                "outreach"
              ],
              "inputModes": [
                "text/plain",
                "application/json"
              ],
              "outputModes": [
                "application/json",
                "text/markdown"
              ]
            },
            {
              "id": "content_marketing_team",
              "name": "Content Marketing Team",
              "description": "Audit, research, plan, and create SEO+AEO optimized content. Delegates to Content Audit, AEO & SEO Research, Content Planner, and Content Creator.",
              "tags": [
                "marketing",
                "content",
                "seo",
                "aeo"
              ],
              "inputModes": [
                "text/plain",
                "application/json"
              ],
              "outputModes": [
                "application/json",
                "text/markdown"
              ]
            },
            {
              "id": "social_content_team",
              "name": "Social Content Team",
              "description": "Plan, create, and analyze LinkedIn content. Delegates to Social Planner, Social Post Creator, and Social Performance Analyzer.",
              "tags": [
                "marketing",
                "social",
                "linkedin"
              ],
              "inputModes": [
                "text/plain",
                "application/json"
              ],
              "outputModes": [
                "application/json",
                "text/markdown"
              ]
            },
            {
              "id": "meeting_prep",
              "name": "Meeting prep",
              "description": "Given a calendar event or attendee list, produce a research brief, an agenda, and suggested talking points.",
              "tags": [
                "meetings",
                "research"
              ],
              "inputModes": [
                "application/json"
              ],
              "outputModes": [
                "application/json",
                "text/markdown"
              ]
            },
            {
              "id": "cold_call_prep",
              "name": "Cold-call prep",
              "description": "Given a target prospect and an offer, produce a call game-plan with opener, talking points, likely objections, and a closing CTA.",
              "tags": [
                "sales",
                "cold-call"
              ],
              "inputModes": [
                "application/json"
              ],
              "outputModes": [
                "application/json",
                "text/markdown"
              ]
            },
            {
              "id": "outreach_strategy",
              "name": "Outreach strategy & sequence",
              "description": "Generate a multi-step outreach strategy and the corresponding email/LinkedIn/phone sequence for a target persona.",
              "tags": [
                "sales",
                "outreach"
              ],
              "inputModes": [
                "application/json"
              ],
              "outputModes": [
                "application/json",
                "text/markdown"
              ]
            }
          ]
        },
        "rawExcerpt": "{\n  \"protocolVersion\": \"0.3.0\",\n  \"name\": \"Agent.ai\",\n  \"description\": \"Marketplace and execution layer for professional AI agents. Agent.ai hosts thousands of purpose-built agents \\u2014 Sales Prospecting, Content Marketing, Social Content, plus individual agents for meeting prep, cold-call prep, outreach, and research \\u2014 and exposes each one as a typed A2A skill and MCP tool.\",\n  \"url\": \"https://agent.ai\",\n  \"iconUrl\": \"https://agent.ai/web-app-manifest-512x512.png\",\n  \"provider\": {\n    \"organization\": \"Agent.ai\",\n    \"url\": \"https://agent.ai/about\"\n  },\n  \"version\": \"1.1.0\",\n  \"documentationUrl\": \"https://docs.agent.ai\",\n  \"defaultInputModes\": [\"text/plain\", \"application/json\"],\n  \"defaultOutputModes\": [\"text/plain\", \"application/json\"],\n  \"capabilities\": {\n    \"streaming\": true,\n  ",
        "missing": [],
        "endpointIssues": [],
        "protocolVersion": "0.3.0",
        "latestVersion": false,
        "versionCompatibility": "legacy-compatible",
        "defaultInputModes": [
          "text/plain",
          "application/json"
        ],
        "defaultOutputModes": [
          "text/plain",
          "application/json"
        ],
        "supportedInterfaces": [],
        "cardShapeWarnings": [],
        "invalidSkills": [],
        "skills": [
          {
            "id": "marketplace_search",
            "name": "Search the agent marketplace",
            "description": "Given a natural-language query (e.g. 'find me an agent that researches companies on LinkedIn'), return a ranked list of Agent.ai agents that can do the job, with their IDs, descriptions, and call signatures.",
            "tags": [
              "marketplace",
              "search",
              "discovery"
            ],
            "inputModes": [
              "text/plain",
              "application/json"
            ],
            "outputModes": [
              "application/json"
            ]
          },
          {
            "id": "sales_prospecting_team",
            "name": "Sales Prospecting Team",
            "description": "Find, research, qualify, and draft outreach in one connected workflow. Delegates to Prospect Finder, Prospect Researcher, Lead Qualifier, and Outreach Drafter.",
            "tags": [
              "sales",
              "prospecting",
              "outreach"
            ],
            "inputModes": [
              "text/plain",
              "application/json"
            ],
            "outputModes": [
              "application/json",
              "text/markdown"
            ]
          },
          {
            "id": "content_marketing_team",
            "name": "Content Marketing Team",
            "description": "Audit, research, plan, and create SEO+AEO optimized content. Delegates to Content Audit, AEO & SEO Research, Content Planner, and Content Creator.",
            "tags": [
              "marketing",
              "content",
              "seo",
              "aeo"
            ],
            "inputModes": [
              "text/plain",
              "application/json"
            ],
            "outputModes": [
              "application/json",
              "text/markdown"
            ]
          },
          {
            "id": "social_content_team",
            "name": "Social Content Team",
            "description": "Plan, create, and analyze LinkedIn content. Delegates to Social Planner, Social Post Creator, and Social Performance Analyzer.",
            "tags": [
              "marketing",
              "social",
              "linkedin"
            ],
            "inputModes": [
              "text/plain",
              "application/json"
            ],
            "outputModes": [
              "application/json",
              "text/markdown"
            ]
          },
          {
            "id": "meeting_prep",
            "name": "Meeting prep",
            "description": "Given a calendar event or attendee list, produce a research brief, an agenda, and suggested talking points.",
            "tags": [
              "meetings",
              "research"
            ],
            "inputModes": [
              "application/json"
            ],
            "outputModes": [
              "application/json",
              "text/markdown"
            ]
          },
          {
            "id": "cold_call_prep",
            "name": "Cold-call prep",
            "description": "Given a target prospect and an offer, produce a call game-plan with opener, talking points, likely objections, and a closing CTA.",
            "tags": [
              "sales",
              "cold-call"
            ],
            "inputModes": [
              "application/json"
            ],
            "outputModes": [
              "application/json",
              "text/markdown"
            ]
          },
          {
            "id": "outreach_strategy",
            "name": "Outreach strategy & sequence",
            "description": "Generate a multi-step outreach strategy and the corresponding email/LinkedIn/phone sequence for a target persona.",
            "tags": [
              "sales",
              "outreach"
            ],
            "inputModes": [
              "application/json"
            ],
            "outputModes": [
              "application/json",
              "text/markdown"
            ]
          }
        ],
        "endpointUrl": "https://agent.ai",
        "skillCount": 7,
        "capabilityKeys": [
          "streaming",
          "pushNotifications",
          "stateTransitionHistory"
        ]
      },
      "howToFix": "Publish an A2A Agent Card with required skill details and make the advertised url answer A2A JSON-RPC requests."
    },
    {
      "id": "protocol-version",
      "title": "Report A2A protocol version compatibility",
      "status": "pass",
      "evidence": {
        "protocolVersion": "0.3.0",
        "versionCompatibility": "legacy-compatible",
        "latestVersion": false,
        "cardShapeWarnings": []
      },
      "howToFix": "Publish a latest A2A card with supportedInterfaces when targeting v1.x, or keep reporting legacy cards as legacy-compatible."
    },
    {
      "id": "endpoint-verification",
      "title": "Verify advertised A2A endpoint",
      "status": "fail",
      "evidence": {
        "url": "https://agent.ai/",
        "statusCode": 403,
        "contentType": "text/html; charset=UTF-8",
        "validA2aResponse": false,
        "excerpt": "<!DOCTYPE html><html lang=\"en-US\"><head><title>Just a moment...</title><meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"><meta http-equiv=\"X-UA-Compatible\" content=\"IE=Edge\"><meta name=\"robots\" content=\"noindex,nofollow\"><meta name=\"viewport\" content=\"width=device-width,initial-scal"
      },
      "issue": "message/send did not return a successful A2A Message or Task result. Evidence includes status, JSON-RPC error, and response excerpt.",
      "howToFix": "Point the card url to a real A2A endpoint that can execute or decline advertised skills with a valid A2A response."
    },
    {
      "id": "skill-execution",
      "title": "Verify advertised A2A skill execution",
      "status": "warning",
      "evidence": {
        "ok": false,
        "skipped": "No create_scan skill was advertised.",
        "advertisedSkillIds": [
          "marketplace_search",
          "sales_prospecting_team",
          "content_marketing_team",
          "social_content_team",
          "meeting_prep",
          "cold_call_prep",
          "outreach_strategy"
        ]
      },
      "issue": "A2A endpoint responded, but advertised skill execution was not verified. Evidence includes the requested skill, status, JSON-RPC error, and response excerpt.",
      "howToFix": "Make advertised A2A skills executable through message/send, or mark them as discovery-only until execution is implemented."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 40/100 and needs a fix.

6 Fail

Needs attention

AIO: Source and trust signals

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Source and trust signals

Score

40/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Source and trust signals scored 40/100 and needs a fix.

Evidence
{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": true,
    "policyLinks": true
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [
    {
      "href": "https://www.linkedin.com/company/agentdotai/",
      "text": "",
      "html": "<a href=\"https://www.linkedin.com/company/agentdotai/\" class=\"chakra-link fs-5 css-1zuobb\" aria-label=\"LinkedIn\" rel=\"me noopener\" target=\"_blank\"><img class=\"chakra-image css-uiqjid\" src=\"/social/linkedin.svg\" alt=\"LinkedIn icon\"></a>"
    }
  ],
  "contactLinks": [],
  "privacyLinks": [
    {
      "href": "/terms",
      "text": "Terms",
      "html": "<a href=\"/terms\">Terms</a>"
    },
    {
      "href": "/privacy-policy",
      "text": "Privacy",
      "html": "<a href=\"/privacy-policy\">Privacy</a>"
    }
  ],
  "score": 40,
  "weight": 20
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: AI crawler accessibility

GEO: AI crawler accessibility scored 45/100 and needs a fix.

5 Fail

Needs attention

GEO: AI crawler accessibility

Failed check
01

Issue

robots.txt blocks these AI crawlers: gptbot. No rendered JSON-LD schema block was detected.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: AI crawler accessibility

Score

45/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: AI crawler accessibility scored 45/100 and needs a fix.

Evidence
{
  "textWords": 106,
  "htmlBytes": 122272,
  "robots": {
    "checkedCrawlers": [
      "gptbot",
      "chatgpt-user",
      "claudebot",
      "perplexitybot",
      "google-extended"
    ],
    "blocked": [
      "gptbot"
    ],
    "allows": false
  },
  "schemaBlocks": 0,
  "finalUrl": "https://agent.ai/crewai",
  "robotsExcerpt": "# Agent.ai robots policy\n# See /.well-known/ for machine-readable agent discovery\n# See /llms.txt for an index of developer + agent resources\n\n# ---- Default: allow respectful crawling, disallow internal APIs ----\nUser-agent: *\nDisallow: /api/\nDisallow: /admin/\nDisallow: /oauth-connecting/\nAllow: /\n\n# ---- Cloudflare Content Signals (purpose-based crawl permissions) ----\n# search=yes   -> OK to index us for user-facing search results\n# ai-input=yes -> OK to use our pages as grounding/citations for AI answers\n# ai-train=no  -> Do NOT use our content to train foundation models\nContent-Signal: search=yes, ai-input=yes, ai-train=no\n\n# ---- Tier 1: AI assistants that act on behalf of a user (allow) ----\n# These crawlers fetch pages on-demand to answer user questions.\nUser-agent: ChatGPT-User\nAl",
  "score": 45,
  "weight": 26
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer evidence and trust

AEO: Answer evidence and trust scored 40/100 and needs a fix.

5 Fail

Needs attention

AEO: Answer evidence and trust

Failed check
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer evidence and trust

Score

40/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer evidence and trust scored 40/100 and needs a fix.

Evidence
{
  "signals": {
    "author": false,
    "publisher": false,
    "freshnessDate": false,
    "aboutOrContact": true,
    "policyLinks": true
  },
  "missing": [
    "author",
    "publisher",
    "freshnessDate"
  ],
  "authorMeta": "",
  "schemaAuthors": [],
  "schemaPublishers": [],
  "schemaDates": [],
  "visibleDates": [],
  "aboutLinks": [
    {
      "href": "https://www.linkedin.com/company/agentdotai/",
      "text": "",
      "html": "<a href=\"https://www.linkedin.com/company/agentdotai/\" class=\"chakra-link fs-5 css-1zuobb\" aria-label=\"LinkedIn\" rel=\"me noopener\" target=\"_blank\"><img class=\"chakra-image css-uiqjid\" src=\"/social/linkedin.svg\" alt=\"LinkedIn icon\"></a>"
    }
  ],
  "contactLinks": [],
  "privacyLinks": [
    {
      "href": "/terms",
      "text": "Terms",
      "html": "<a href=\"/terms\">Terms</a>"
    },
    {
      "href": "/privacy-policy",
      "text": "Privacy",
      "html": "<a href=\"/privacy-policy\">Privacy</a>"
    }
  ],
  "score": 40,
  "weight": 22
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Extraction-friendly structure

GEO: Extraction-friendly structure scored 50/100 and needs improvement.

4 Warning

Needs attention

GEO: Extraction-friendly structure

Warning
01

Issue

Missing extraction signals: optional top summary / TL;DR / key takeaways block, table with <thead> only if the page already has tabular/comparative data, ordered list only if the page explains a workflow/process, optional visible FAQ or FAQPage schema, clear definition sentence using "is", "means", or "refers to" where natural, JSON-LD structured data.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Extraction-friendly structure

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Extraction-friendly structure scored 50/100 and needs improvement.

Evidence
{
  "hasSummary": false,
  "tableCount": 0,
  "tablesWithHead": 0,
  "tablesMissingThead": [],
  "orderedLists": 0,
  "hasFaq": false,
  "definitionPatterns": 0,
  "schemaBlocks": 0,
  "missingSignals": [
    "optional top summary / TL;DR / key takeaways block",
    "table with <thead> only if the page already has tabular/comparative data",
    "ordered list only if the page explains a workflow/process",
    "optional visible FAQ or FAQPage schema",
    "clear definition sentence using \"is\", \"means\", or \"refers to\" where natural",
    "JSON-LD structured data"
  ],
  "score": 50,
  "weight": 24
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Explanatory content depth

GEO: Explanatory content depth scored 45/100 and needs a fix.

4 Fail

Needs attention

GEO: Explanatory content depth

Failed check
01

Issue

No substantial explanatory paragraphs were found.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Explanatory content depth

Score

45/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Explanatory content depth scored 45/100 and needs a fix.

Evidence
{
  "candidatePassages": 1,
  "citablePassages": 0,
  "failingCandidateParagraphs": [],
  "citableParagraphs": [],
  "score": 45,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question-led structure

AEO: Question-led structure scored 50/100 and needs improvement.

3 Warning

Needs attention

AEO: Question-led structure

Warning
01

Issue

No question-led h2 sections or FAQ pattern was detected.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Question-led structure

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Question-led structure scored 50/100 and needs improvement.

Evidence
{
  "h2Count": 0,
  "questionH2s": [],
  "hasFaq": false,
  "score": 50,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Entity clarity

GEO: Entity clarity scored 79/100 and needs improvement.

2 Warning

Needs attention

GEO: Entity clarity

Warning
01

Issue

Title/H1 terms missing from description: professional, network, may, have, been, looking, crewai, com, don, worry, common, mistake.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Entity clarity

Score

79/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Entity clarity scored 79/100 and needs improvement.

Evidence
{
  "title": "Agent.ai | The #1 Professional Network for AI Agents",
  "h1": "You may have been looking for CrewAI.com (don't worry, common mistake).",
  "description": "Discover, use and build agents to create your personal AI agent team.",
  "topicOverlap": 0.2857142857142857,
  "topicTerms": [
    "agent",
    "professional",
    "network",
    "agents",
    "may",
    "have",
    "been",
    "looking",
    "crewai",
    "com",
    "don",
    "worry",
    "common",
    "mistake"
  ],
  "descriptionTerms": [
    "discover",
    "build",
    "agents",
    "create",
    "personal",
    "agent",
    "team"
  ],
  "missingFromDescription": [
    "professional",
    "network",
    "may",
    "have",
    "been",
    "looking",
    "crewai",
    "com",
    "don",
    "worry",
    "common",
    "mistake"
  ],
  "score": 79,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

AEO: Entity and definition clarity scored 67/100 and needs improvement.

2 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

Entity or definition gaps: professional, network, may, have, been, looking, crewai, com, don, worry, common, mistake.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Entity and definition clarity

Score

67/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Entity and definition clarity scored 67/100 and needs improvement.

Evidence
{
  "title": "Agent.ai | The #1 Professional Network for AI Agents",
  "h1": "You may have been looking for CrewAI.com (don't worry, common mistake).",
  "description": "Discover, use and build agents to create your personal AI agent team.",
  "topicOverlap": 0.2857142857142857,
  "definitionCount": 0,
  "topicTerms": [
    "agent",
    "professional",
    "network",
    "agents",
    "may",
    "have",
    "been",
    "looking",
    "crewai",
    "com",
    "don",
    "worry",
    "common",
    "mistake"
  ],
  "descriptionTerms": [
    "discover",
    "build",
    "agents",
    "create",
    "personal",
    "agent",
    "team"
  ],
  "missingFromDescription": [
    "professional",
    "network",
    "may",
    "have",
    "been",
    "looking",
    "crewai",
    "com",
    "don",
    "worry",
    "common",
    "mistake"
  ],
  "score": 67,
  "weight": 18
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first sections

AEO: Answer-first sections scored 80/100 and needs improvement.

2 Warning

Needs attention

AEO: Answer-first sections

Warning
01

Issue

AEO readiness is incomplete.

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer-first sections

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer-first sections scored 80/100 and needs improvement.

Evidence
{
  "sectionCount": 0,
  "passing": 0,
  "failing": [],
  "score": 80,
  "weight": 28
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience for AIO

AIO: Page experience for AIO scored 75/100 and needs improvement.

1 Warning

Needs attention

AIO: Page experience for AIO

Warning
01

Issue

5 image(s) are missing width/height attributes. 1 possible modal/interstitial element(s) detected.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Page experience for AIO

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Page experience for AIO scored 75/100 and needs improvement.

Evidence
{
  "viewportContent": "width=device-width, initial-scale=1",
  "visibleWords": 106,
  "htmlBytes": 122272,
  "imagesMissingDimensions": [
    {
      "src": "/logo-2025/agent-ai-logo-2025-white.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img class=\"chakra-image css-1phd9a0\" src=\"/logo-2025/agent-ai-logo-2025-white.svg\" alt=\"agent ai logo\">"
    },
    {
      "src": "/header/mobile-toggle-icon.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img class=\"chakra-image css-o8l6mr\" src=\"/header/mobile-toggle-icon.svg\" alt>"
    },
    {
      "src": "/_next/static/media/crew-ai.0j02t402hls0-.png",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img src=\"/_next/static/media/crew-ai.0j02t402hls0-.png\" alt=\"CrewAI logo\" style=\"width:250px;margin:0 auto;display:block\">"
    },
    {
      "src": "/logo-2025/agent-ai-logo-new-dark.svg",
      "width": "",
      "height": "",
      "loading": "lazy",
      "html": "<img class=\"chakra-image css-gd6c7j\" loading=\"lazy\" src=\"/logo-2025/agent-ai-logo-new-dark.svg\" alt=\"Agent.ai logo\">"
    },
    {
      "src": "/social/linkedin.svg",
      "width": "",
      "height": "",
      "loading": "",
      "html": "<img class=\"chakra-image css-uiqjid\" src=\"/social/linkedin.svg\" alt=\"LinkedIn icon\">"
    }
  ],
  "possibleDialogs": [
    "<div data-scope=\"popover\" data-part=\"content\" dir=\"ltr\" id=\"popover:mobile-nav-popover:content\" tabindex=\"-1\" role=\"dialog\" hidden data-state=\"closed\" aria-labelledby=\"popover:mobile-nav-popover:title\" aria-describedby=\"popover:mobile-nav-popover:desc\" class=\"chakra-popover__content css-h2ors3\"><div class=\"chakra-stack css-2faujs\"><div class=\"chakra-stack css-n3aogz\"><a data-track-id=\"nav_agent_network_link\" title=\"Agent Network\" class=\"chakra-link css-1lti3r8\" href=\"/agents\">Agent Network</a..."
  ],
  "score": 75,
  "weight": 10
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Answer block readiness

AIO: Answer block readiness scored 80/100 and needs improvement.

1 Warning

Needs attention

AIO: Answer block readiness

Warning
01

Issue

No JSON-LD structured data was detected.

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Answer block readiness

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Answer block readiness scored 80/100 and needs improvement.

Evidence
{
  "sectionCount": 0,
  "passing": 0,
  "failing": [],
  "score": 80,
  "weight": 8
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer intent coverage

AEO: Answer intent coverage scored 70/100 and needs improvement.

1 Warning

Needs attention

AEO: Answer intent coverage

Warning
01

Issue

Missing likely AI Overview intent sections: what, how, benefits, cost, compare.

Details

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Answer intent coverage

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Answer intent coverage scored 70/100 and needs improvement.

Evidence
{
  "headings": [],
  "expected": [
    {
      "id": "what",
      "label": "What is Agent.ai?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Agent.ai work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Agent.ai?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Agent.ai free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Agent.ai compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Agent.ai?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Agent.ai work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Agent.ai?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Agent.ai free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Agent.ai compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 8
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Extractable visible copy

AEO: Extractable visible copy scored 70/100 and needs improvement.

1 Warning

Needs attention

AEO: Extractable visible copy

Warning
01

Issue

Only 106 visible words were detected for answer extraction.

02

Why it matters

Answer engines need concise answers, question-led structure, entity clarity, visible evidence, and trust signals that can be extracted without relying on search-only metadata checks.

Check name

AEO: Extractable visible copy

Score

70/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to answer from directly.

Result

AEO: Extractable visible copy scored 70/100 and needs improvement.

Evidence
{
  "visibleWords": 106,
  "schemaCount": 0,
  "score": 70,
  "weight": 6
}

Agent Ease of UseAPIEmerging recommendation

AI context endpoint

AI context endpoint is informational for this page.

Informational

Needs attention

AI context endpoint

Informational
01

Issue

AI context endpoint is informational for this page.

02

Why it matters

A context endpoint gives agents a small, low-latency summary of product purpose, safe actions, and canonical machine-readable resources without scraping the whole site.

Check name

AI context endpoint

Score

100/100

Status

informational

Category

API

Maturity

Emerging recommendation

Goal

Expose a compact API context endpoint agents can fetch before deciding which public API or discovery resource to use.

Result

AI context endpoint is informational for this page.

Validation steps

  1. Fetch to find resource

    AI context endpoint was not found at the expected path.

Evidence
{
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch to find resource",
      "status": "informational",
      "evidence": {
        "checked": [
          {
            "path": "/api/ai/context",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5441
          },
          {
            "path": "/api/context",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5432
          },
          {
            "path": "/context",
            "statusCode": 403,
            "contentType": "text/html; charset=UTF-8",
            "length": 5399
          }
        ]
      },
      "issue": "AI context endpoint was not found at the expected path.",
      "howToFix": "Publish a concise JSON or Markdown AI context endpoint describing the product, public actions, and machine-readable resources."
    }
  ]
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Query intent coverage

AIO: Query intent coverage is informational for this page.

Informational

Needs attention

AIO: Query intent coverage

Informational
01

Issue

Missing likely AI Overview intent sections: what, how, benefits, cost, compare.

Details

02

Why it matters

AI Overviews depend on Google-search eligibility, useful visible content, consistent structured data, answer-first sections, trust signals, and preview controls that permit snippets.

Check name

AIO: Query intent coverage

Score

70/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible and useful for Google AI Overviews and AI Mode extraction.

Result

AIO: Query intent coverage is informational for this page.

Evidence
{
  "headings": [],
  "expected": [
    {
      "id": "what",
      "label": "What is Agent.ai?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Agent.ai work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Agent.ai?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Agent.ai free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Agent.ai compare with alternatives?",
      "pattern": {}
    }
  ],
  "missing": [
    {
      "id": "what",
      "label": "What is Agent.ai?",
      "pattern": {}
    },
    {
      "id": "how",
      "label": "How does Agent.ai work?",
      "pattern": {}
    },
    {
      "id": "benefits",
      "label": "Why use Agent.ai?",
      "pattern": {}
    },
    {
      "id": "cost",
      "label": "Is Agent.ai free or paid?",
      "pattern": {}
    },
    {
      "id": "compare",
      "label": "How does Agent.ai compare with alternatives?",
      "pattern": {}
    }
  ],
  "score": 70,
  "weight": 4
}

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Q&A and FAQ opportunities

GEO: Q&A and FAQ opportunities is informational for this page.

Informational

Needs attention

GEO: Q&A and FAQ opportunities

Informational
01

Issue

No visible FAQ or FAQPage schema was detected; this is optional unless the page answers common questions.

Details

02

Why it matters

Generative engines favor pages with self-contained answer passages, clear entities, structured data, summaries, FAQ patterns, and crawler-accessible HTML that can be cited without extra interpretation.

Check name

GEO: Q&A and FAQ opportunities

Score

75/100

Status

informational

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute.

Result

GEO: Q&A and FAQ opportunities is informational for this page.

Evidence
{
  "h2Count": 0,
  "questionH2s": 0,
  "hasFaq": false,
  "nonQuestionH2s": [],
  "score": 75,
  "weight": 4
}

AI DiscoverabilityDiscoverabilityEstablished

IndexNow key

IndexNow key is informational for this page.

Informational

Needs attention

IndexNow key

Informational
01

Issue

IndexNow key is informational for this page.

02

Why it matters

IndexNow lets sites notify participating search engines about changed URLs, but ownership verification requires a UTF-8 key file whose filename matches the key.

Check name

IndexNow key

Score

100/100

Status

informational

Category

Discoverability

Maturity

Established

Goal

Verify that IndexNow ownership key placement is detectable when the site advertises it.

Result

IndexNow key is informational for this page.

Validation steps

  1. Find advertised IndexNow key location

    No IndexNow key location was advertised in HTML, Link headers, or robots.txt.

  2. Fetch and validate IndexNow key file

    No discoverable IndexNow key file was found.

Evidence
{
  "steps": [
    {
      "id": "advertised-location",
      "title": "Find advertised IndexNow key location",
      "status": "informational",
      "evidence": {
        "advertised": []
      },
      "issue": "No IndexNow key location was advertised in HTML, Link headers, or robots.txt.",
      "howToFix": "Advertise the key location with robots.txt IndexNow-Key, rel=\"indexnow-key\", or meta name=\"indexnow-key-location\" if you want scanners to verify it."
    },
    {
      "id": "fetch-key",
      "title": "Fetch and validate IndexNow key file",
      "status": "informational",
      "evidence": {
        "advertised": [],
        "checked": []
      },
      "issue": "No discoverable IndexNow key file was found.",
      "howToFix": "Host a UTF-8 text file named {key}.txt using a 32-character hexadecimal key whose body exactly matches the key."
    }
  ]
}

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

OAuth / OIDC discovery has an informational finding because the page appears to support authentication.

Informational

Needs attention

OAuth / OIDC discovery

Informational
01

Issue

OAuth Discovery response did not match the expected shape. missing: jwks_uri; endpoint issues: [{"field":"jwks_uri","issue":"Missing URL."}].

02

Why it matters

OAuth and OIDC discovery let agents find authorization, token, and key endpoints programmatically instead of relying on human documentation.

Check name

OAuth / OIDC discovery

Score

0/100

Status

informational

Category

Auth

Maturity

Established

Goal

Publish OAuth/OIDC discovery metadata so agents can authenticate with your APIs.

Result

OAuth / OIDC discovery has an informational finding because the page appears to support authentication.

Validation steps

  1. Validate resource body

    OAuth Discovery response did not match the expected shape. missing: jwks_uri; endpoint issues: [{"field":"jwks_uri","issue":"Missing URL."}].

Evidence
{
  "failedStep": "validate",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch discovery resource",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/oauth-authorization-server",
        "statusCode": 200,
        "contentType": "application/json"
      }
    },
    {
      "id": "validate",
      "title": "Validate resource body",
      "status": "fail",
      "evidence": {
        "valid": false,
        "issue": "OAuth Discovery response did not match the expected shape. missing: jwks_uri; endpoint issues: [{\"field\":\"jwks_uri\",\"issue\":\"Missing URL.\"}].",
        "compatibleContentType": true,
        "missing": [
          "jwks_uri"
        ],
        "endpointIssues": [
          {
            "field": "jwks_uri",
            "issue": "Missing URL."
          }
        ],
        "issuer": "https://agent-ai.us.auth0.com/",
        "authorizationEndpoint": "https://mcp.agent.ai/authorize",
        "tokenEndpoint": "https://mcp.agent.ai/oauth/token",
        "responseTypesSupported": [
          "code"
        ],
        "grantTypesSupported": [
          "authorization_code",
          "refresh_token"
        ],
        "idTokenSigningAlgValuesSupported": [],
        "rawExcerpt": "{\"issuer\":\"https://agent-ai.us.auth0.com/\",\"authorization_endpoint\":\"https://mcp.agent.ai/authorize\",\"token_endpoint\":\"https://mcp.agent.ai/oauth/token\",\"registration_endpoint\":\"https://mcp.agent.ai/oauth/register\",\"scopes_supported\":[\"openid\",\"profile\",\"email\",\"offline_access\",\"mcp:access\"],\"response_types_supported\":[\"code\"],\"grant_types_supported\":[\"authorization_code\",\"refresh_token\"],\"code_challenge_methods_supported\":[\"S256\"],\"token_endpoint_auth_methods_supported\":[\"none\"],\"resource\":\"http://mcp.agent.ai/mcp\"}"
      },
      "issue": "OAuth Discovery response did not match the expected shape. missing: jwks_uri; endpoint issues: [{\"field\":\"jwks_uri\",\"issue\":\"Missing URL.\"}].",
      "howToFix": "Publish valid OAuth/OIDC metadata only when the site actually supports OAuth/OIDC. Otherwise omit provider discovery and document any unauthenticated public APIs separately."
    },
    {
      "id": "authorization-endpoint",
      "title": "Probe authorization endpoint with an authorization-code request",
      "status": "pass",
      "evidence": {
        "url": "https://mcp.agent.ai/authorize?response_type=code&client_id=can-agent-use-scanner&redirect_uri=https%3A%2F%2Fcan-agent-use.invalid%2Foauth%2Fcallback&scope=openid&state=can-agent-use-probe",
        "method": "GET",
        "statusCode": 302,
        "location": "https://agent-ai.us.auth0.com/authorize?response_type=code&client_id=1LCgjflccW0GsSWxA0zZkwhnG1Ay5pF7&redirect_uri=https%3A%2F%2Fmcp.agent.ai%2Foauth%2Fcallback&scope=openid+mcp%3Aaccess&state=eyJyZWRpcmVjdF91cmkiOiJodHRwczovL2Nhbi1hZ2VudC11c2UuaW52YWxpZC9vYXV0aC9jYWxsYmFjayIsIm9yaWdpbmFsX3N0YXRlIjoiY2FuLWFnZW50LXVzZS1wcm9iZSIsImNsaWVudF9pZCI6ImNhbi1hZ2VudC11c2Utc2Nhbm5lciIsInRzIjoxNzgwOTIwMDAzfXxjODc5MGU3ZTM5ZTYyYTk1ZmEzZjEwZTA4Yzc3ZDgxNmJlNTUzMDY4OTk1ZDQ0ZTI2MGFkZTdkY2YyOTY2MTUx&audience=https%3A%2F%2Fmcp.agent.ai%2Fmcp",
        "contentType": null,
        "excerpt": ""
      },
      "howToFix": "Implement an authorization endpoint that can process syntactically valid authorization requests, or remove it from discovery metadata until it exists."
    },
    {
      "id": "authorization-redirect-safety",
      "title": "Reject unregistered authorization redirects",
      "status": "pass",
      "evidence": {
        "url": "https://mcp.agent.ai/authorize?response_type=code&client_id=can-agent-use-unknown-client&redirect_uri=https%3A%2F%2Fcan-agent-use.invalid%2Fattacker-callback&scope=openid&state=can-agent-use-redirect-safety",
        "method": "GET",
        "statusCode": 302,
        "location": "https://agent-ai.us.auth0.com/authorize?response_type=code&client_id=1LCgjflccW0GsSWxA0zZkwhnG1Ay5pF7&redirect_uri=https%3A%2F%2Fmcp.agent.ai%2Foauth%2Fcallback&scope=openid+mcp%3Aaccess&state=eyJyZWRpcmVjdF91cmkiOiJodHRwczovL2Nhbi1hZ2VudC11c2UuaW52YWxpZC9hdHRhY2tlci1jYWxsYmFjayIsIm9yaWdpbmFsX3N0YXRlIjoiY2FuLWFnZW50LXVzZS1yZWRpcmVjdC1zYWZldHkiLCJjbGllbnRfaWQiOiJjYW4tYWdlbnQtdXNlLXVua25vd24tY2xpZW50IiwidHMiOjE3ODA5MjAwMDR9fDNmMTdlZWRkMTVkZWU5NTUxOTM4ZDdkNWE4YTIyNTQzNDllOWExZmJhMGMyNTI1ZTZlNTdkMmUxYjM3MTY5MmE&audience=https%3A%2F%2Fmcp.agent.ai%2Fmcp",
        "redirectedToUntrusted": false,
        "contentType": null,
        "excerpt": ""
      },
      "howToFix": "Validate client_id and registered redirect_uri values before redirecting. Return a direct OAuth error for invalid clients or redirect URIs."
    },
    {
      "id": "token-endpoint",
      "title": "Probe token endpoint with advertised grant type",
      "status": "pass",
      "evidence": {
        "url": "https://mcp.agent.ai/oauth/token",
        "method": "POST",
        "grantType": "authorization_code",
        "statusCode": 401,
        "oauthError": "access_denied",
        "contentType": "application/json",
        "excerpt": "{\"error\":\"access_denied\",\"error_description\":\"Unauthorized\"}"
      },
      "howToFix": "Support every advertised grant type enough to return a protocol-appropriate response, or stop advertising unsupported grants."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 6,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign up"
      }
    ]
  },
  "resourceFetchSucceeded": true
}

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

OAuth Protected Resource has an informational finding because the page appears to support authentication.

Informational

Needs attention

OAuth Protected Resource

Informational
01

Issue

Protected resource metadata `resource` did not match the resource identifier used to retrieve it.

02

Why it matters

Protected Resource metadata tells agents which authorization servers protect an API and how to connect authentication challenges to the right resource.

Check name

OAuth Protected Resource

Score

0/100

Status

informational

Category

Auth

Maturity

Emerging recommendation

Goal

Publish OAuth Protected Resource Metadata so agents can discover how to authenticate.

Result

OAuth Protected Resource has an informational finding because the page appears to support authentication.

Validation steps

  1. Validate protected resource identity

    Protected resource metadata `resource` did not match the resource identifier used to retrieve it.

  2. Probe protected API Bearer challenge

    No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.

Evidence
{
  "failedStep": "resource-identity",
  "steps": [
    {
      "id": "fetch",
      "title": "Fetch protected resource metadata",
      "status": "pass",
      "evidence": {
        "path": "/.well-known/oauth-protected-resource",
        "statusCode": 200,
        "contentType": "application/json; charset=utf-8"
      },
      "howToFix": "Publish /.well-known/oauth-protected-resource JSON."
    },
    {
      "id": "metadata",
      "title": "Validate protected resource metadata",
      "status": "pass",
      "evidence": {
        "valid": true,
        "compatibleContentType": true,
        "hasResource": true,
        "authorizationServerCount": 1,
        "resource": "https://mcp.agent.ai/mcp",
        "resourceIssues": [],
        "authServerIssues": [],
        "scopesSupported": [
          "openid",
          "email",
          "profile",
          "mcp:access"
        ],
        "bearerMethodsSupported": [
          "header"
        ],
        "rawExcerpt": "{\"resource\":\"https://mcp.agent.ai/mcp\",\"authorization_servers\":[\"https://mcp.agent.ai\"],\"scopes_supported\":[\"openid\",\"email\",\"profile\",\"mcp:access\"],\"bearer_methods_supported\":[\"header\"],\"resource_documentation\":\"https://docs.agent.ai/mcp\"}"
      },
      "howToFix": "Publish resource and authorization_servers as absolute URLs."
    },
    {
      "id": "resource-identity",
      "title": "Validate protected resource identity",
      "status": "fail",
      "evidence": {
        "resource": "https://mcp.agent.ai/mcp",
        "expectedResource": "https://agent.ai"
      },
      "issue": "Protected resource metadata `resource` did not match the resource identifier used to retrieve it.",
      "howToFix": "Set `resource` to the origin/resource identifier represented by /.well-known/oauth-protected-resource."
    },
    {
      "id": "protected-route-challenge",
      "title": "Probe protected API Bearer challenge",
      "status": "informational",
      "evidence": {
        "checked": [
          {
            "path": "/api/admin/scans",
            "statusCode": 403,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://agent.ai/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "metadataResource": "https://mcp.agent.ai/mcp",
            "resourceMatchesRequestContext": false
          },
          {
            "path": "/api/admin/summary",
            "statusCode": 403,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://agent.ai/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "metadataResource": "https://mcp.agent.ai/mcp",
            "resourceMatchesRequestContext": false
          },
          {
            "path": "/api/scans",
            "statusCode": 403,
            "wwwAuthenticate": {
              "valid": false,
              "present": false
            },
            "expectedMetadataUrl": "https://agent.ai/.well-known/oauth-protected-resource",
            "metadataUrlMatches": true,
            "metadataResource": "https://mcp.agent.ai/mcp",
            "resourceMatchesRequestContext": false
          }
        ]
      },
      "issue": "No protected route with a 401 Bearer challenge was detected; metadata alone does not prove a protected resource.",
      "howToFix": "When this site exposes bearer-protected APIs, return 401 with WWW-Authenticate: Bearer and link resource_metadata."
    }
  ],
  "authApplicability": {
    "supportsAuth": true,
    "score": 6,
    "signals": [
      {
        "source": "link:href",
        "weight": 3,
        "match": "auth link"
      },
      {
        "source": "visible-text",
        "weight": 3,
        "match": "sign up"
      }
    ]
  },
  "resourceFetchSucceeded": true
}

Performance and AccessibilityBest PracticesBrowser audit

Issues were logged in the `Issues` panel in Chrome Devtools

100 Fail

Check name

Issues were logged in the `Issues` panel in Chrome Devtools

Score

0/100

Status

fail

Device

desktop

Category

Best Practices

Fix guidance

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Evidence
{
  "description": "Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue."
}

SEOSEOBrowser audit

robots.txt is not valid

100 Fail

Check name

robots.txt is not valid

Score

0/100

Status

fail

Device

desktop

Category

SEO

Estimated savings

1 error found

Fix guidance

If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. [Learn more about robots.txt](https://developer.chrome.com/docs/lighthouse/seo/invalid-robots-txt/).

Evidence
{
  "displayValue": "1 error found",
  "description": "If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. [Learn more about robots.txt](https://developer.chrome.com/docs/lighthouse/seo/invalid-robots-txt/)."
}

Performance and AccessibilityPerformanceBrowser audit

LCP breakdown

17 Fail

Check name

LCP breakdown

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Each [subpart has specific improvement strategies](https://developer.chrome.com/docs/performance/insights/lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays.

Evidence
{
  "description": "Each [subpart has specific improvement strategies](https://developer.chrome.com/docs/performance/insights/lcp-breakdown). Ideally, most of the LCP time should be spent on loading the resources, not within delays."
}

Performance and AccessibilityPerformanceBrowser audit

Reduce JavaScript execution time

17 Fail

Check name

Reduce JavaScript execution time

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

4.2 s

Fix guidance

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).

Evidence
{
  "displayValue": "4.2 s",
  "description": "Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. [Learn how to reduce Javascript execution time](https://developer.chrome.com/docs/lighthouse/performance/bootup-time/).",
  "numericValue": 4208.8589999999795
}

Performance and AccessibilityPerformanceBrowser audit

Reduce unused JavaScript

17 Fail

Check name

Reduce unused JavaScript

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 1,611 KiB

Fix guidance

Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).

Evidence
{
  "displayValue": "Est savings of 1,611 KiB",
  "description": "Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. [Learn how to reduce unused JavaScript](https://developer.chrome.com/docs/lighthouse/performance/unused-javascript/).",
  "numericValue": 920
}

Performance and AccessibilityPerformanceBrowser audit

Render-blocking requests

17 Fail

Check name

Render-blocking requests

Score

0/100

Status

fail

Device

desktop

Category

Performance

Estimated savings

Est savings of 160 ms

Fix guidance

Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path.

Evidence
{
  "displayValue": "Est savings of 160 ms",
  "description": "Requests are blocking the page's initial render, which may delay LCP. [Deferring or inlining](https://developer.chrome.com/docs/performance/insights/render-blocking) can move these network requests out of the critical path."
}

Performance and AccessibilityPerformanceBrowser audit

Loading performance

11 Fail

Check name

Loading performance

Score

37/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Review the grouped loading performance checks and improve the failing sub-checks listed in evidence.

Evidence
{
  "checks": [
    {
      "id": "network-rtt",
      "title": "Network Round Trip Times",
      "score": 100,
      "displayValue": "10 ms",
      "numericValue": 12.063239999999999
    },
    {
      "id": "interactive",
      "title": "Time to Interactive",
      "score": 16,
      "displayValue": "7.1 s",
      "numericValue": 7067.478073001383
    },
    {
      "id": "server-response-time",
      "title": "Initial server response time was short",
      "score": 100,
      "displayValue": "Root document took 0 ms",
      "numericValue": 4
    },
    {
      "id": "total-blocking-time",
      "title": "Total Blocking Time",
      "score": 0,
      "displayValue": "1,870 ms",
      "numericValue": 1872.000000000001
    },
    {
      "id": "first-contentful-paint",
      "title": "First Contentful Paint",
      "score": 67,
      "displayValue": "1.3 s",
      "numericValue": 1318.4068727900367
    },
    {
      "id": "max-potential-fid",
      "title": "Max Potential First Input Delay",
      "score": 0,
      "displayValue": "910 ms",
      "numericValue": 913
    },
    {
      "id": "largest-contentful-paint",
      "title": "Largest Contentful Paint",
      "score": 11,
      "displayValue": "4.6 s",
      "numericValue": 4556.683611544981
    },
    {
      "id": "speed-index",
      "title": "Speed Index",
      "score": 2,
      "displayValue": "5.3 s",
      "numericValue": 5325.141168232025
    }
  ]
}

Performance and AccessibilityPerformanceBrowser audit

Legacy JavaScript

8 Warning

Check name

Legacy JavaScript

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 107 KiB

Fix guidance

Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)

Evidence
{
  "displayValue": "Est savings of 107 KiB",
  "description": "Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile [Baseline](https://web.dev/articles/baseline-and-polyfills) features, unless you know you must support older browsers. [Learn why most sites can deploy ES6+ code without transpiling](https://developer.chrome.com/docs/performance/insights/legacy-javascript)"
}

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
46/100Level 2, Agent-LimitedCurrent report
Report ID cdb9eb19-2c1c-4fcd-9835-e6ff1176cd08. Scanned Jun 8, 2026, 5:30 PM.
agent.ai AI SEO Report: 46/100 (Level 2, Agent-Limited)