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

OVERALL SCORE

Level 3, Bot-Aware

Moderate readiness for AI agents
AIDiscoverability72%Agent Easeof Use61%Security& Trust80%GEO, AIO, AEO64%SEO100%Performance& Accessibility76%
  • AI Discoverability 72 out of 100
  • Agent Ease of Use 61 out of 100
  • Security & Trust 80 out of 100
  • GEO, AIO and AEO 64 out of 100
  • SEO 100 out of 100
  • Performance and Accessibility 76 out of 100

CAPTURED SCREENSHOT

Captured website desktop screenshot

What AI sees of your website

Wraps - The Email Platform That Sends Through Your AWS favicon

Wraps - The Email Platform That Sends Through Your AWS

Write email templates as React components. Define automations as TypeScript. Review in PRs, deploy with your app. Your marketing team edits and sends without code.

Next step

Turn this report into a fix workflow

8 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
72
Needs work36115View details
Discoverability
100
Strong1000
Content Readiness
63
Needs work23103View details
Bot Access Control
58
Needs work312View details
Agent Ease of Use
61
Needs work15418View details
API
79
Mostly ready703
Auth
54
Needs work312View details
MCP
59
Needs work204
Skill Discovery
50
Needs work339View details
GEO, AIO and AEO
64
Needs work828View details
GEO Readiness
61
Needs work312View details
AIO Readiness
80
Mostly ready303
AEO Readiness
51
Needs work213View details
SEO
100
Strong1000
SEO
100
Strong1000
Security & Trust
80
Mostly ready1814View details
Security & Trust
80
Mostly ready1814View details
Performance and Accessibility
76
Mostly ready1934View details
Performance
71
Needs work1424View details
Accessibility
86
Mostly ready510View details

Prioritized recommendations

Issues ranked by score impact

41 items need attention

Agent Ease of UseMCPEmerging recommendation

MCP Server Card

MCP Server Card has a validation warning at "Discover MCP server card".

25 Warning

Needs attention

MCP Server Card

Warning
01

Issue

No MCP server card was found at current, transitional, or linked discovery paths.

02

Why it matters

MCP server cards give agents a stable, public pre-connection discovery surface for server identity, remote transports, protocol compatibility, and safe routing without guessing endpoints.

Check name

MCP Server Card

Score

50/100

Status

warning

Category

MCP

Maturity

Emerging recommendation

Goal

Publish an MCP Server Card that helps agents discover remote MCP server transports before opening a session.

Result

MCP Server Card has a validation warning at "Discover MCP server card".

Validation steps

  1. Discover MCP server card

    No MCP server card was found at current, transitional, or linked discovery paths.

Evidence log1 step · 14 lines
Discover MCP server card [warning]! No MCP server card was found at current, transitional, or linked discovery paths.INFODiscover MCP server card candidateCount=5INFOBuild MCP server-card candidate list currentPath="/.well-known/mcp-server-card" transitionalPaths=["/.well-known/mcp/server-card.json","/.well-known/mcp/server-cards.json","/mcp.json","/.well-known/mcp.json"] linkedPaths=[]PASSCheck whether page claims MCP support actual=false expected="true only when HTML or Link headers mention MCP" textMatches=[] headerLinkCount=0INFOTrying to fetch /.well-known/mcp-server-card url="https://wraps.dev/.well-known/mcp-server-card" source="current"FAIL/.well-known/mcp-server-card did not return a usable server card statusCode=404 contentType="text/html; charset=utf-8"INFOTrying to fetch /.well-known/mcp/server-card.json url="https://wraps.dev/.well-known/mcp/server-card.json" source="transitional"FAIL/.well-known/mcp/server-card.json did not return a usable server card statusCode=404 contentType="text/html; charset=utf-8"INFOTrying to fetch /.well-known/mcp/server-cards.json url="https://wraps.dev/.well-known/mcp/server-cards.json" source="transitional"FAIL/.well-known/mcp/server-cards.json did not return a usable server card statusCode=404 contentType="text/html; charset=utf-8"INFOTrying to fetch /mcp.json url="https://wraps.dev/mcp.json" source="transitional"FAIL/mcp.json did not return a usable server card statusCode=404 contentType="text/html; charset=utf-8"INFOTrying to fetch /.well-known/mcp.json url="https://wraps.dev/.well-known/mcp.json" source="transitional"FAIL/.well-known/mcp.json did not return a usable server card statusCode=404 contentType="text/html; charset=utf-8"WARNNo MCP server card was found reason="No MCP server card was found at current, transitional, or linked discovery paths."

AI DiscoverabilityBot Access ControlEstablished

AI bot rules in robots.txt

AI bot rules in robots.txt failed at "Classify AI crawler rules".

23 Fail

Needs attention

AI bot rules in robots.txt

Failed check
01

Issue

No explicit User-agent rules were found for major AI crawler tokens.

02

Why it matters

AI crawler product tokens have different meanings. Explicit robots.txt groups make training, search, and retrieval access policy auditable for compliant crawler operators.

Check name

AI bot rules in robots.txt

Score

31/100

Status

fail

Category

Bot Access Control

Maturity

Established

Goal

Declare deliberate robots.txt rules for major AI training, AI search, user-triggered, and dataset crawlers.

Result

AI bot rules in robots.txt failed at "Classify AI crawler rules".

Validation steps

  1. Classify AI crawler rules

    No explicit User-agent rules were found for major AI crawler tokens.

Evidence log1 step · 6 lines
Classify AI crawler rules [fail]! No explicit User-agent rules were found for major AI crawler tokens.INFOClassify AI crawler rulesINFOParsing User-agent groups and Allow/Disallow records for known AI crawler tokens evaluatedPath="/"INFOEvaluating exact User-agent matches before wildcard fallback exactAiPolicyCount=0 totalCrawlerTokens=18FAILNo explicit AI crawler User-agent groups were found examplesExpected=["GPTBot","OAI-SearchBot","ClaudeBot","Google-Extended","CCBot"]FAILCompare explicit AI crawler coverage actual=0 expected="> 0 explicit non-search AI crawler policies" missingTokens=["GPTBot","OAI-SearchBot","ChatGPT-User","ClaudeBot","Claude-SearchBot","Claude-User","Google-Extended","Applebot-Extended","Amazonbot","Amzn-SearchBot","Amzn-User","PerplexityBot"]INFOResolved effective root-path policy for crawler tokens blocked=0 allowed=21 unspecified=0

AI DiscoverabilityContent ReadinessEstablished

Markdown negotiation

Markdown negotiation is missing or incomplete.

18 Fail

Needs attention

Markdown negotiation

Failed check
01

Issue

Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown.

02

Why it matters

Markdown representations give agents a cleaner page form while preserving normal HTML for browsers and cache-safe representation handling.

Check name

Markdown negotiation

Score

10/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose a useful Markdown representation through negotiation or an explicit alternate URL.

Result

Markdown negotiation is missing or incomplete.

Validation steps

  1. Markdown representation

    No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.

  2. Same-URL negotiation

    Same-URL Accept: text/markdown did not return a valid Markdown representation.

  3. Markdown format validation

    Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown.

  4. Advertised Markdown alternate

    No Link or HTML rel=alternate text/markdown URL was advertised.

  5. Conventional .md mirror

    Conventional .md mirror candidates did not return valid Markdown.

Evidence log5 steps · 15 lines
Markdown representation [fail]! No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks.INFOMarkdown representationFAILCheck usable Markdown representation was selected actual={"source":"negotiated","url":"https://wraps.dev/","statusCode":200,"contentType":"text/markdown; charset=utf-8","mediaType":"text/markdown","vary":"Accept","requireVaryAccept":true,"contentTypeStatus":"pass","cacheStatus":"pass","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"mdx-like","hasHeading":true,"headingCount":4,"wordCount":199,"features":{"markdownLinks":8,"referenceLinks":0,"listItems":8,"tables":1,"taskListItems":0,"fencedCodeBlocks":3,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":2,"jsxOrMdxSignals":1},"issues":["mdx-jsx-source-leakage"],"excerpt":"# Wraps\n\n> Deploy email, SMS, and CDN infrastructure to your AWS account with one command.\n> Modern DX. AWS economics. Full ownership.\n\nWraps is a CLI and TypeScript SDK that deploys production-ready AWS infrastructure (SES, Lambda, DynamoD","issue":"Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."}} expected="negotiated, advertised alternate, or conventional mirror" selected={"source":"negotiated","url":"https://wraps.dev/","statusCode":200,"contentType":"text/markdown; charset=utf-8","mediaType":"text/markdown","vary":"Accept","requireVaryAccept":true,"contentTypeStatus":"pass","cacheStatus":"pass","bodyStatus":"fail","pass":false,"quality":{"valid":false,"formatStatus":"fail","dialect":"mdx-like","hasHeading":true,"headingCount":4,"wordCount":199,"features":{"markdownLinks":8,"referenceLinks":0,"listItems":8,"tables":1,"taskListItems":0,"fencedCodeBlocks":3,"yamlFrontmatter":false,"jsonLdFencedBlocks":0,"admonitions":0,"strikethrough":0,"autolinks":0,"rawHtmlTags":2,"jsxOrMdxSignals":1},"issues":["mdx-jsx-source-leakage"],"excerpt":"# Wraps\n\n> Deploy email, SMS, and CDN infrastructure to your AWS account with one command.\n> Modern DX. AWS economics. Full ownership.\n\nWraps is a CLI and TypeScript SDK that deploys production-ready AWS infrastructure (SES, Lambda, DynamoD","issue":"Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."}} candidatesChecked=2FAILMarkdown representation failed issue="No usable Markdown representation was found through negotiation, advertised alternates, or conservative .md mirror checks."Same-URL negotiation [fail]! Same-URL Accept: text/markdown did not return a valid Markdown representation.INFOSame-URL negotiationFAILCheck negotiated Markdown response actual={"statusCode":200,"mediaType":"text/markdown","vary":"Accept"} expected="HTTP 2xx text/markdown with Vary: Accept" url="https://wraps.dev/" statusCode=200 mediaType="text/markdown" vary="Accept"FAILSame-URL negotiation failed issue="Same-URL Accept: text/markdown did not return a valid Markdown representation."Markdown format validation [fail]! Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown.INFOMarkdown format validationFAILCheck Markdown body quality actual={"valid":false,"wordCount":199,"headingCount":4,"dialect":"mdx-like"} expected="valid Markdown with substantive text and headings" valid=false dialect="mdx-like" wordCount=199 headingCount=4FAILMarkdown format validation failed issue="Markdown response appears to expose MDX/JSX source rather than rendered agent-facing Markdown."Advertised Markdown alternate [warning]! No Link or HTML rel=alternate text/markdown URL was advertised.INFOAdvertised Markdown alternateWARNCheck advertised Markdown alternate candidates actual=0 expected="> 0 when HTML advertises a Markdown alternate" advertisedUrls=[] candidateCount=0WARNAdvertised Markdown alternate has a warning issue="No Link or HTML rel=alternate text/markdown URL was advertised."Conventional .md mirror [fail]! Conventional .md mirror candidates did not return valid Markdown.INFOConventional .md mirrorFAILCheck conventional Markdown mirror candidates actual=1 expected="> 0 when a conventional mirror is discoverable" conventionalUrls=["https://wraps.dev/index.html.md"] candidateCount=1FAILConventional .md mirror failed issue="Conventional .md mirror candidates did not return valid Markdown."

Agent Ease of UseSkill DiscoveryEmerging recommendation

Agent Skills index

Agent Skills index failed at "Validate discovery index schema".

17 Fail

Needs attention

Agent Skills index

Failed check
01

Issue

Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.

Details

02

Why it matters

An Agent Skills index lets agents discover task-specific instructions through a small trusted index, then verify and load only the skill artifacts they need.

Check name

Agent Skills index

Score

33/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish an Agent Skills discovery index that advertises digest-pinned SKILL.md or archive artifacts.

Result

Agent Skills index failed at "Validate discovery index schema".

Validation steps

  1. Discover Agent Skills index

    Agent Skills index was found only at the legacy /.well-known/skills/index.json path.

  2. Validate discovery index schema

    Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.

    Top-level issues
    • $schema must be https://schemas.agentskills.io/discovery/0.2.0/schema.json
    Invalid skills
    [
      {
        "url": "",
        "name": "aws-ses-best-practices",
        "type": "",
        "index": 0,
        "valid": false,
        "digest": "",
        "invalid": [],
        "missing": [
          "type",
          "url",
          "digest"
        ],
        "warnings": [],
        "description": "Email deliverability, warming, compliance, and operational guidelines for AWS Simple Email Service.",
        "originClass": "same-origin",
        "resolvedUrl": "https://wraps.dev/.well-known/skills/index.json"
      },
      {
        "url": "",
        "name": "email-content-guide",
        "type": "",
        "index": 1,
        "valid": false,
        "digest": "",
        "invalid": [],
        "missing": [
          "type",
          "url",
          "digest"
        ],
        "warnings": [],
        "description": "Best practices for email content that avoids spam filters. Apply these rules when writing email copy, building templates, or debugging spam placement issues.",
        "originClass": "same-origin",
        "resolvedUrl": "https://wraps.dev/.well-known/skills/index.json"
      },
      {
        "url": "",
        "name": "ses-troubleshoot",
        "type": "",
        "index": 2,
        "valid": false,
        "digest": "",
        "invalid": [],
        "missing": [
          "type",
          "url",
          "digest"
        ],
        "warnings": [
          "description should explain when to use the skill"
        ],
        "description": "Interactive SES deliverability troubleshooting. Diagnoses bounces, spam placement, send failures, account health, and complaint issues with targeted AWS CLI commands and ordered remediation steps.",
        "originClass": "same-origin",
        "resolvedUrl": "https://wraps.dev/.well-known/skills/index.json"
      },
      {
        "url": "",
        "name": "wraps-cli",
        "type": "",
        "index": 3,
        "valid": false,
        "digest": "",
        "invalid": [],
        "missing": [
          "type",
          "url",
          "digest"
        ],
        "warnings": [],
        "description": "CLI that deploys SES, DynamoDB, Lambda, and IAM resources to your AWS account with automatic DKIM, SPF, DMARC configuration.",
        "originClass": "same-origin",
        "resolvedUrl": "https://wraps.dev/.well-known/skills/index.json"
      },
      {
        "truncated": true,
        "omittedCount": 4,
        "originalCount": 8
      }
    ]
  3. Validate skill entries

    One or more Agent Skills entries have invalid required fields.

    Skill entry findings
    [
      {
        "url": "",
        "name": "aws-ses-best-practices",
        "type": "",
        "index": 0,
        "valid": false,
        "digest": "",
        "invalid": [],
        "missing": [
          "type",
          "url",
          "digest"
        ],
        "warnings": [],
        "description": "Email deliverability, warming, compliance, and operational guidelines for AWS Simple Email Service.",
        "originClass": "same-origin",
        "resolvedUrl": "https://wraps.dev/.well-known/skills/index.json"
      },
      {
        "url": "",
        "name": "email-content-guide",
        "type": "",
        "index": 1,
        "valid": false,
        "digest": "",
        "invalid": [],
        "missing": [
          "type",
          "url",
          "digest"
        ],
        "warnings": [],
        "description": "Best practices for email content that avoids spam filters. Apply these rules when writing email copy, building templates, or debugging spam placement issues.",
        "originClass": "same-origin",
        "resolvedUrl": "https://wraps.dev/.well-known/skills/index.json"
      },
      {
        "url": "",
        "name": "ses-troubleshoot",
        "type": "",
        "index": 2,
        "valid": false,
        "digest": "",
        "invalid": [],
        "missing": [
          "type",
          "url",
          "digest"
        ],
        "warnings": [
          "description should explain when to use the skill"
        ],
        "description": "Interactive SES deliverability troubleshooting. Diagnoses bounces, spam placement, send failures, account health, and complaint issues with targeted AWS CLI commands and ordered remediation steps.",
        "originClass": "same-origin",
        "resolvedUrl": "https://wraps.dev/.well-known/skills/index.json"
      },
      {
        "url": "",
        "name": "wraps-cli",
        "type": "",
        "index": 3,
        "valid": false,
        "digest": "",
        "invalid": [],
        "missing": [
          "type",
          "url",
          "digest"
        ],
        "warnings": [],
        "description": "CLI that deploys SES, DynamoDB, Lambda, and IAM resources to your AWS account with automatic DKIM, SPF, DMARC configuration.",
        "originClass": "same-origin",
        "resolvedUrl": "https://wraps.dev/.well-known/skills/index.json"
      },
      {
        "truncated": true,
        "omittedCount": 4,
        "originalCount": 8
      }
    ]
  4. Verify advertised artifacts

    No valid skill artifacts were available to verify.

  5. Validate skill content

    For skill-md artifacts, include valid YAML frontmatter with name and description followed by Markdown. For archives, include a safe root SKILL.md and no unsafe paths.

  6. Review skill artifact security

    Do not publish secrets or prompt-injection instructions in skill artifacts. Treat scripts, archives, and cross-origin artifacts as software supply-chain surfaces.

Evidence log6 steps · 31 lines
Discover Agent Skills index [warning]! Agent Skills index was found only at the legacy /.well-known/skills/index.json path.INFODiscover Agent Skills indexINFOTry Agent Skills index paths in priority order paths=["/.well-known/agent-skills/index.json","/.well-known/skills/index.json"]WARNAgent Skills index candidate was not usable path="/.well-known/agent-skills/index.json" url="https://wraps.dev/.well-known/agent-skills/index.json" statusCode=404PASSFetched Agent Skills index candidate path="/.well-known/skills/index.json" url="https://wraps.dev/.well-known/skills/index.json" statusCode=200 contentType="application/json" bytes=1699 selected="selected"WARNAgent Skills index was found only at the legacy /.well-known/skills/index.json path.Validate discovery index schema [fail]! Agent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.INFOValidate discovery index schemaINFOParse Agent Skills index JSON validJson=true contentTypeCompatible=trueFAILCompare $schema URI expected="https://schemas.agentskills.io/discovery/0.2.0/schema.json"FAILCompare top-level schema issue count actual=1 expected=0FAILCompare unknown top-level field count actual=0 expected=0FAILAgent Skills index must use $schema https://schemas.agentskills.io/discovery/0.2.0/schema.json.Validate skill entries [fail]! One or more Agent Skills entries have invalid required fields.INFOValidate skill entriesFAILCompare advertised skill count actual=8 expected="> 0"FAILCompare valid skill entry count actual=0 expected="same as advertised skill count"FAILInvalid skill entry skill={"index":0,"valid":false,"name":"aws-ses-best-practices","type":"","description":"Email deliverability, warming, compliance, and operational guidelines for AWS Simple Email Service.","url":"","digest":"","resolvedUrl":"https://wraps.dev/.well-known/skills/index.json","originClass":"same-origin","missing":["type","url","digest"],"invalid":[],"warnings":[]}FAILInvalid skill entry skill={"index":1,"valid":false,"name":"email-content-guide","type":"","description":"Best practices for email content that avoids spam filters. Apply these rules when writing email copy, building templates, or debugging spam placement issues.","url":"","digest":"","resolvedUrl":"https://wraps.dev/.well-known/skills/index.json","originClass":"same-origin","missing":["type","url","digest"],"invalid":[],"warnings":[]}FAILInvalid skill entry skill={"index":2,"valid":false,"name":"ses-troubleshoot","type":"","description":"Interactive SES deliverability troubleshooting. Diagnoses bounces, spam placement, send failures, account health, and complaint issues with targeted AWS CLI commands and ordered remediation steps.","url":"","digest":"","resolvedUrl":"https://wraps.dev/.well-known/skills/index.json","originClass":"same-origin","missing":["type","url","digest"],"invalid":[],"warnings":["description should explain when to use the skill"]}FAILInvalid skill entry skill={"index":3,"valid":false,"name":"wraps-cli","type":"","description":"CLI that deploys SES, DynamoDB, Lambda, and IAM resources to your AWS account with automatic DKIM, SPF, DMARC configuration.","url":"","digest":"","resolvedUrl":"https://wraps.dev/.well-known/skills/index.json","originClass":"same-origin","missing":["type","url","digest"],"invalid":[],"warnings":[]}FAILInvalid skill entry skill={"index":4,"valid":false,"name":"wraps-email","type":"","description":"TypeScript SDK for AWS SES with automatic credential resolution, React.email support, and template management.","url":"","digest":"","resolvedUrl":"https://wraps.dev/.well-known/skills/index.json","originClass":"same-origin","missing":["type","url","digest"],"invalid":[],"warnings":[]}FAILInvalid skill entry skill={"index":5,"valid":false,"name":"wraps-quickstart","type":"","description":"Get started with Wraps email infrastructure. Guides through deploying infrastructure, verifying a domain, installing the SDK, and sending the first email. Adapts to project framework and hosting provider.","url":"","digest":"","resolvedUrl":"https://wraps.dev/.well-known/skills/index.json","originClass":"same-origin","missing":["type","url","digest"],"invalid":[],"warnings":[]}FAILInvalid skill entry skill={"index":6,"valid":false,"name":"wraps-sms","type":"","description":"TypeScript SDK for AWS End User Messaging (Pinpoint SMS) with opt-out management, batch sending, and E.164 validation.","url":"","digest":"","resolvedUrl":"https://wraps.dev/.well-known/skills/index.json","originClass":"same-origin","missing":["type","url","digest"],"invalid":[],"warnings":[]}FAILInvalid skill entry skill={"index":7,"valid":false,"name":"wraps-workflows","type":"","description":"Build email and SMS automation workflows using the @wraps.dev/client TypeScript DSL. Covers triggers, steps, branching, cascades, and the full defineWorkflow API.","url":"","digest":"","resolvedUrl":"https://wraps.dev/.well-known/skills/index.json","originClass":"same-origin","missing":["type","url","digest"],"invalid":[],"warnings":["description should explain when to use the skill"]}FAILOne or more Agent Skills entries have invalid required fields.Verify advertised artifacts [warning]! No valid skill artifacts were available to verify.INFOVerify advertised artifactsWARNCompare artifact fetch count actual=0 expected="> 0"WARNNo valid skill artifacts were available to verify.Validate skill content [warning]INFOValidate skill contentWARNAgent Skills step completed with warningsReview skill artifact security [warning]INFOReview skill artifact securityWARNCompare security finding count actual=0 expected=0WARNAgent Skills step completed with warnings

Agent Ease of UseAuthEmerging recommendation

Auth.md Agent Registration

Auth.md Agent Registration has a validation warning at "Warn when auth surface lacks Auth.md".

17 Warning

Needs attention

Auth.md Agent Registration

Warning
01

Issue

The site appears to support login, signup, account access, or credentials but does not publish /auth.md.

02

Why it matters

Human login and signup flows are often opaque to agents. Auth.md gives automated clients a stable registration contract instead of forcing them to scrape docs, automate browser forms, or guess credential flows.

Check name

Auth.md Agent Registration

Score

50/100

Status

warning

Category

Auth

Maturity

Emerging recommendation

Goal

Publish Auth.md v1 metadata so agents can discover how to register, claim a user, and obtain credentials.

Result

Auth.md Agent Registration has a validation warning at "Warn when auth surface lacks Auth.md".

Validation steps

  1. Warn when auth surface lacks Auth.md

    The site appears to support login, signup, account access, or credentials but does not publish /auth.md.

Evidence log1 step · 2 lines
Warn when auth surface lacks Auth.md [warning]! The site appears to support login, signup, account access, or credentials but does not publish /auth.md.INFOWarn when auth surface lacks Auth.mdWARNThe site appears to support login, signup, account access, or credentials but does not publish /auth.md.

Agent Ease of UseAuthEmerging recommendation

OAuth Protected Resource

OAuth Protected Resource has a validation warning at "Detect protected-resource applicability".

17 Warning

Needs attention

OAuth Protected Resource

Warning
01

Issue

Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.

02

Why it matters

Protected-resource metadata tells agents which API/resource is locked, which authorization servers can issue tokens for it, and how a 401 challenge maps back to the correct resource.

Check name

OAuth Protected Resource

Score

50/100

Status

warning

Category

Auth

Maturity

Emerging recommendation

Goal

Publish OAuth Protected Resource Metadata for OAuth-protected APIs and MCP resources so clients can identify the resource and its authorization servers.

Result

OAuth Protected Resource has a validation warning at "Detect protected-resource applicability".

Validation steps

  1. Detect protected-resource applicability

    Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.

Evidence log1 step · 4 lines
Detect protected-resource applicability [warning]! Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected.INFODetect protected-resource applicabilityINFOInspecting auth headers, MCP/OAuth claims, and protected-resource hints applies=false requiresAuthorizationServers=false signalsCount=0 genericAuthSignalsCount=2 checkedCount=1WARNCheck protected-resource metadata applicability actual=false expected="true when RFC 9728 metadata exists or support is claimed" checked=[{"url":"https://wraps.dev/.well-known/oauth-protected-resource","path":"/.well-known/oauth-protected-resource","source":"root-well-known","resourceIdentifier":"https://wraps.dev","statusCode":404,"contentType":"text/html; charset=utf-8","length":19708}]WARNDetect protected-resource applicability completed with warnings issue="Generic authentication signals were found, but no OAuth Protected Resource metadata signal was detected."

AI DiscoverabilityBot Access ControlEmerging recommendation

RSL license signal

No RSL declarations were found.

17 Warning

Needs attention

RSL license signal

Warning
01

Issue

No RSL declarations were found.

02

Why it matters

Really Simple Licensing is an emerging rights-expression layer for communicating content usage and licensing terms separately from robots.txt crawl permission.

Check name

RSL license signal

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Declare machine-readable content licensing terms for compliant AI and crawler systems when the site needs them.

Result

No RSL declarations were found.

Validation steps

  1. Discover RSL declarations

    No RSL declarations were found.

Evidence log1 step · 4 lines
Discover RSL declarations [warning]! No RSL declarations were found.INFODiscover RSL declarationsINFOChecking robots.txt License records, HTTP Link rel=license headers, HTML license links, and inline RSL XML robotsFound=trueSKIPCount discovered RSL declarations actual=0 expected=">= 1 when RSL licensing terms are published" sources={}WARNNo RSL declarations were found on any supported discovery surface.

AI DiscoverabilityBot Access ControlEmerging recommendation

TDMRep declaration

No TDMRep declaration was found.

17 Warning

Needs attention

TDMRep declaration

Warning
01

Issue

No TDMRep declaration was found at /.well-known/tdmrep.json.

02

Why it matters

TDMRep is a W3C Community Group protocol and IANA-registered well-known URI for declaring text and data mining reservation policy on applicable content.

Check name

TDMRep declaration

Score

50/100

Status

warning

Category

Bot Access Control

Maturity

Emerging recommendation

Goal

Publish a machine-readable text and data mining reservation declaration and verifiable ODRL policy when the site needs one.

Result

No TDMRep declaration was found.

Validation steps

  1. Fetch /.well-known/tdmrep.json

    No TDMRep declaration was found at /.well-known/tdmrep.json.

Evidence log1 step · 4 lines
Fetch /.well-known/tdmrep.json [warning]! No TDMRep declaration was found at /.well-known/tdmrep.json.INFOFetch /.well-known/tdmrep.jsonINFORequesting origin-level TDMRep declaration at /.well-known/tdmrep.jsonWARNCompare TDMRep file response actual=404 expected="2xx with JSON array when origin-level TDMRep is published" contentType="text/html; charset=utf-8" length=19708WARNNo TDMRep declaration was found at /.well-known/tdmrep.json. 

Agent Ease of UseAPIEstablished

OpenAPI discovery

OpenAPI discovery has a validation warning at "Discover OpenAPI document".

17 Warning

Needs attention

OpenAPI discovery

Warning
01

Issue

The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.

02

Why it matters

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

Check name

OpenAPI discovery

Score

67/100

Status

warning

Category

API

Maturity

Established

Goal

Publish a valid OpenAPI or Swagger document for public API discovery when this origin exposes public APIs.

Result

OpenAPI discovery has a validation warning at "Discover OpenAPI document".

Validation steps

  1. Discover OpenAPI document

    The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.

Evidence log1 step · 16 lines
Discover OpenAPI document [warning]! The site appears to publish or document a public API, but no OpenAPI or Swagger document was found.INFODiscover OpenAPI document status="warning"INFOBuild OpenAPI candidate list conventionalPaths=19 candidateCount=19 sources={"conventional-path":19}INFOFetch OpenAPI candidate path="/openapi.json" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/openapi.yaml" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/swagger.json" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/swagger.yaml" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/api/openapi.json" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/api/openapi.yaml" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/api/swagger.json" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/api/swagger.yaml" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/docs/openapi.json" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/docs/openapi.yaml" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/api-docs" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"INFOFetch OpenAPI candidate path="/v3/api-docs" source="conventional-path" statusCode=404 contentType="text/html; charset=utf-8"WARNSelect a usable OpenAPI candidate actual="none" expected="same-origin candidate with a parseable OpenAPI or Swagger document"WARNThe site appears to publish or document a public API, but no OpenAPI or Swagger document was found.

Agent Ease of UseMCPEmerging recommendation

WebMCP

WebMCP has a validation warning at "Detect WebMCP runtime API".

17 Warning

Needs attention

WebMCP

Warning
01

Issue

WebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.

02

Why it matters

WebMCP gives agents structured page and browser tool hints so they can understand actions without relying only on screen scraping.

Check name

WebMCP

Score

67/100

Status

warning

Category

MCP

Maturity

Emerging recommendation

Goal

Expose browser/page WebMCP tools and compatible static WebMCP metadata when a site wants agents to understand in-page actions.

Result

WebMCP has a validation warning at "Detect WebMCP runtime API".

Validation steps

  1. Detect WebMCP runtime API

    WebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.

  2. Probe WebMCP operability

    Static WebMCP runtime strings were found, but rendered browser probing did not confirm a runtime API.

    WebMCP operability findings
    • Static WebMCP runtime strings were found, but rendered browser probing did not confirm a runtime API.
    • Conventional WebMCP manifest paths were checked but did not return a valid manifest.
  3. Validate declarative WebMCP form tools

    No W3C-style declarative WebMCP form attributes were found.

  4. Validate MCP-aware HTML annotations

    No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.

  5. Validate static WebMCP JSON compatibility

    No static WebMCP JSON manifest or WMCP interaction graph was found.

Evidence log5 steps · 24 lines
Detect WebMCP runtime API [warning]! WebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.INFODetect WebMCP runtime API status="warning"INFOProbe rendered browser for WebMCP runtime objects WARNCheck current W3C runtime API actual="not detected" expected="document.modelContext/registerTool available"WARNWebMCP-like strings were found, but rendered browser evidence did not confirm a usable runtime API.Probe WebMCP operability [warning]! Static WebMCP runtime strings were found, but rendered browser probing did not confirm a runtime API.INFOProbe WebMCP operability status="warning"INFORun safe WebMCP operability checks safeProbeOnly=trueWARNCheck usable WebMCP evidence actual=0 expected="at least 1 usable runtime, declarative, annotation, or static manifest signal"WARNWebMCP operability warning warning="Static WebMCP runtime strings were found, but rendered browser probing did not confirm a runtime API."WARNWebMCP operability warning warning="Conventional WebMCP manifest paths were checked but did not return a valid manifest."WARNStatic WebMCP runtime strings were found, but rendered browser probing did not confirm a runtime API.Validate declarative WebMCP form tools [informational]! No W3C-style declarative WebMCP form attributes were found.INFOValidate declarative WebMCP form tools status="informational"INFOInspect visible forms and controls for current declarative WebMCP attributes annotatedElements=0 formsWithAttributes=0 controlsWithAttributes=0SKIPValidate declarative WebMCP attribute quality actual=0 expected=0INFONo W3C-style declarative WebMCP form attributes were found. status="informational"Validate MCP-aware HTML annotations [informational]! No data-mcp-tool or hyphenated WebMCP compatibility annotations were found.INFOValidate MCP-aware HTML annotations status="informational"INFOInspect HTML for MCP compatibility annotations compatibilityAttributeCount=0 dataMcpToolCount=0 examples=[]SKIPValidate compatibility annotation quality actual=0 expected=0INFONo data-mcp-tool or hyphenated WebMCP compatibility annotations were found. status="informational"Validate static WebMCP JSON compatibility [warning]! No static WebMCP JSON manifest or WMCP interaction graph was found.INFOValidate static WebMCP JSON compatibility status="warning"INFODiscover static WebMCP manifest candidates conventionalPaths=["/.well-known/webmcp.json","/webmcp.json"] checkedCount=2 profileCounts={}INFOWebMCP manifest candidate checked source="path" path="/.well-known/webmcp.json" url="https://wraps.dev/.well-known/webmcp.json" statusCode=404 contentType="text/html; charset=utf-8"INFOWebMCP manifest candidate checked source="path" path="/webmcp.json" url="https://wraps.dev/webmcp.json" statusCode=404 contentType="text/html; charset=utf-8"WARNValidate discovered static WebMCP metadata actual={"validManifestCount":0,"invalidManifestCount":0,"toolCount":0,"wmcpActionCount":0} expected="at least 1 valid tools[] manifest or WMCP graph when static metadata is present"WARNNo static WebMCP JSON manifest or WMCP interaction graph was found.

Security & TrustSecurity & TrustEstablished

Content-Security-Policy

Content-Security-Policy failed at "Find enforcing CSP delivery".

15 Fail

Needs attention

Content-Security-Policy

Failed check
01

Issue

Applicable HTML response is missing an enforcing Content-Security-Policy header.

02

Why it matters

Content Security Policy reduces the impact of injection bugs by limiting where scripts, styles, frames, forms, and other browser resources can load or execute.

Check name

Content-Security-Policy

Score

40/100

Status

fail

Category

Security & Trust

Maturity

Established

Goal

Constrain browser resource loading and script execution with an enforcing Content-Security-Policy header.

Result

Content-Security-Policy failed at "Find enforcing CSP delivery".

Validation steps

  1. Find enforcing CSP delivery

    Applicable HTML response is missing an enforcing Content-Security-Policy header.

Evidence log1 step · 4 lines
Find enforcing CSP delivery [fail]! Applicable HTML response is missing an enforcing Content-Security-Policy header.INFOFind enforcing CSP deliveryINFORead CSP delivery headers enforcingHeader="missing" reportOnlyHeader="missing" metaPolicyCount=0 legacyHeadersPresent=[]FAILRequire enforcing Content-Security-Policy header actual="missing" expected="present" issue="Applicable HTML response is missing an enforcing Content-Security-Policy header."FAILApplicable HTML response is missing an enforcing Content-Security-Policy header.

Agent Ease of UseAuthEstablished

OAuth / OIDC discovery

OAuth / OIDC discovery failed at "Validate metadata profile".

13 Fail

Needs attention

OAuth / OIDC discovery

Failed check
01

Issue

OAuth/OIDC discovery metadata did not match the expected profile. missing: response_types_supported.

02

Why it matters

OAuth and OIDC discovery let agents and API clients find authorization, token, and key endpoints programmatically instead of scraping login pages or guessing provider setup.

Check name

OAuth / OIDC discovery

Score

62/100

Status

fail

Category

Auth

Maturity

Established

Goal

Publish OAuth/OIDC discovery metadata only when the site operates or advertises a real OAuth/OIDC authorization server.

Result

OAuth / OIDC discovery failed at "Validate metadata profile".

Validation steps

  1. Validate metadata profile

    OAuth/OIDC discovery metadata did not match the expected profile. missing: response_types_supported.

Evidence log1 step · 12 lines
Validate metadata profile [fail]! OAuth/OIDC discovery metadata did not match the expected profile. missing: response_types_supported.INFOValidate metadata profileINFOParsing and validating OAuth/OIDC metadata profile valid=false compatibleContentType=true profile="oauth-authorization-server" issue="OAuth/OIDC discovery metadata did not match the expected profile. missing: response_types_supported." missingCount=1 warningsCount=6 endpointIssuesCount=0 issuer="https://api.wraps.dev" tokenEndpoint="https://app.wraps.dev/api/auth/device/token"PASSCheck metadata profile was recognized actual="oauth-authorization-server" expected="oauth-authorization-server, oidc, or hybrid"FAILCheck required metadata fields are present actual=1 expected=0 missing=["response_types_supported"]WARNCheck OAuth metadata is fully usable by browser and agent clients actual="6 client-usage warning(s)" expected="no CORS, endpoint, or compatibility warnings" warnings=["jwks_uri is omitted; this can be valid for pure OAuth metadata but limits signed-token/OIDC verification.","scopes_supported is omitted; clients may need additional documentation to request correct scopes.","PKCE code_challenge_methods_supported is omitted.","response_modes_supported is omitted.","revocation_endpoint is omitted.","introspection_endpoint is omitted."]WARNOAuth metadata client-usage warning warning="jwks_uri is omitted; this can be valid for pure OAuth metadata but limits signed-token/OIDC verification."WARNOAuth metadata client-usage warning warning="scopes_supported is omitted; clients may need additional documentation to request correct scopes."WARNOAuth metadata client-usage warning warning="PKCE code_challenge_methods_supported is omitted."WARNOAuth metadata client-usage warning warning="response_modes_supported is omitted."WARNOAuth metadata client-usage warning warning="revocation_endpoint is omitted."WARNOAuth metadata client-usage warning warning="introspection_endpoint is omitted."FAILValidate metadata profile failed issue="OAuth/OIDC discovery metadata did not match the expected profile. missing: response_types_supported."

Agent Ease of UseSkill DiscoveryEmerging recommendation

agents.json

agents.json has a validation warning at "Discover agents.json".

13 Warning

Needs attention

agents.json

Warning
01

Issue

No Wildcard-style agents.json file was found.

02

Why it matters

Wildcard agents.json gives agents workflow-level context beyond plain OpenAPI, including flows, links, examples, and API action structure. It is an emerging OpenAPI-adjacent proposal, so scanners should validate the contract shape without treating it as an A2A or IETF standard.

Check name

agents.json

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish a Wildcard-style agents.json file so agents can discover OpenAPI-backed workflows, links, examples, and authentication requirements.

Result

agents.json has a validation warning at "Discover agents.json".

Validation steps

  1. Discover agents.json

    No Wildcard-style agents.json file was found.

Evidence log1 step · 6 lines
Discover agents.json [warning]! No Wildcard-style agents.json file was found.INFODiscover agents.jsonINFOTry agents.json discovery paths in priority order paths=["/.well-known/agents.json","/agents.json"]WARNagents.json candidate path did not return a usable contract path="/.well-known/agents.json" statusCode=404 contentType="text/html; charset=utf-8"WARNagents.json candidate path did not return a usable contract path="/agents.json" statusCode=404 contentType="text/html; charset=utf-8"WARNNo agents.json candidate was selectedWARNNo Wildcard-style agents.json file was found.

Agent Ease of UseSkill DiscoveryEmerging recommendation

DNS-AID Agent Discovery

DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".

13 Warning

Needs attention

DNS-AID Agent Discovery

Warning
01

Issue

No DNS-AID HTTPS/SVCB records were found under _agents.

02

Why it matters

DNS-AID lets agents discover index, A2A, and other agent entrypoints before fetching HTTP metadata. HTTPS/SVCB records provide the service-binding substrate, while DNSSEC can authenticate the discovery answer when available.

Check name

DNS-AID Agent Discovery

Score

50/100

Status

warning

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

Publish DNS-AID HTTPS/SVCB records under _agents for DNS-based agent entrypoint discovery.

Result

DNS-AID Agent Discovery has a validation warning at "Query DNS-AID records".

Validation steps

  1. Query DNS-AID records

    No DNS-AID HTTPS/SVCB records were found under _agents.

  2. Check DNSSEC authentication evidence

    DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

Evidence log2 steps · 23 lines
Query DNS-AID records [warning]! No DNS-AID HTTPS/SVCB records were found under _agents.INFOQuery DNS-AID recordsINFOBuild DNS-AID query names from hostname hostname="wraps.dev" labels=["_index._agents.wraps.dev","_a2a._agents.wraps.dev"] claimedOnPage=falseWARNDNS query returned no DNS-AID answers name="_index._agents.wraps.dev" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.wraps.dev" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_index._agents.wraps.dev" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _index._agents.wraps.dev"WARNDNS query returned no DNS-AID answers name="_a2a._agents.wraps.dev" rrtype="HTTPS" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.wraps.dev" rrtype="SVCB" resolver="cloudflare-doh-json" rcode=3 ad=false answerCount=0WARNDNS query returned no DNS-AID answers name="_a2a._agents.wraps.dev" rrtype="ANY" resolver="node-resolveAny-fallback" answerCount=0 error="queryAny ETIMEOUT _a2a._agents.wraps.dev"WARNCompare total DNS-AID answer count actual=0 expected="> 0"WARNNo DNS-AID HTTPS/SVCB records were found under _agents.Check DNSSEC authentication evidence [warning]! DNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.INFOCheck DNSSEC authentication evidenceWARNCompare DNSSEC authenticated-data flag actual=false expected=trueWARNCompare visible DNSSEC material actual=false expected=trueWARNResolver did not confirm authenticated DNSSEC data name="_index._agents.wraps.dev" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.wraps.dev" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.wraps.dev" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.wraps.dev" rrtype="HTTPS" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.wraps.dev" rrtype="SVCB" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.wraps.dev" rrtype="ANY" resolver="node-resolveAny-fallback" dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_index._agents.wraps.dev" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="_a2a._agents.wraps.dev" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNResolver did not confirm authenticated DNSSEC data name="wraps.dev" rrtype="DNSKEY" resolver="cloudflare-doh-json" ad=false dnssecTypes=[]WARNDNSSEC authentication evidence was not visible for the DNS-AID labels or hostname.

AI DiscoverabilityContent ReadinessEstablished

Organization / WebSite schema

Organization / WebSite schema is partially implemented.

10 Warning

Needs attention

Organization / WebSite schema

Warning
01

Issue

No WebSite entity was found in Schema.org structured data. WebSite.publisher is missing.

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

48/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify the site owner and website entity in structured data.

Result

Organization / WebSite schema is partially implemented.

Validation steps

  1. WebSite entity

    No WebSite entity was found in Schema.org structured data.

  2. Identity fields

    Missing identity field(s): WebSite.name, WebSite.url.

  3. WebSite publisher linkage

    WebSite.publisher is missing.

Evidence log3 steps · 14 lines
WebSite entity [fail]! No WebSite entity was found in Schema.org structured data.INFOWebSite entityINFOLooking for WebSite entity in structured data FAILCheck WebSite entity presence actual=false expected=true fields=[{"name":"WebSite.@type","present":false},{"name":"WebSite.@id","present":false},{"name":"WebSite.name","present":false},{"name":"WebSite.url","present":false},{"name":"WebSite.publisher.@id","present":false},{"name":"WebSite.publisher.name","present":false},{"name":"WebSite.publisher.url","present":false}]FAILWebSite entity is missingIdentity fields [warning]! Missing identity field(s): WebSite.name, WebSite.url.INFOIdentity fieldsINFOChecking Organization and WebSite name/url fields organizationFormat="json-ld"WARNCheck required identity fields actual=2 expected=4 missing=["WebSite.name","WebSite.url"] organizationFields=[{"name":"Organization.@type","present":true,"value":"Organization","format":"json-ld"},{"name":"Organization.@id","present":false,"format":"json-ld"},{"name":"Organization.name","present":true,"value":"Wraps","format":"json-ld"},{"name":"Organization.url","present":true,"value":"https://wraps.dev","format":"json-ld"},{"name":"Organization.logo","present":true,"value":"https://wraps.dev/logo.png","format":"json-ld"},{"name":"Organization.sameAs","present":true,"value":["https://github.com/wraps-team/wraps","https://twitter.com/useWraps"],"format":"json-ld"}] websiteFields=[{"name":"WebSite.@type","present":false},{"name":"WebSite.@id","present":false},{"name":"WebSite.name","present":false},{"name":"WebSite.url","present":false},{"name":"WebSite.publisher.@id","present":false},{"name":"WebSite.publisher.name","present":false},{"name":"WebSite.publisher.url","present":false}]WARNCheck identity URLs match scanned origin actual={"organizationUrlMatchesOrigin":true,"websiteUrlMatchesOrigin":false} expected={"organizationUrlMatchesOrigin":true,"websiteUrlMatchesOrigin":true}WARNIdentity fields are partially complete missing=["WebSite.name","WebSite.url"]WebSite publisher linkage [fail]! WebSite.publisher is missing.INFOWebSite publisher linkageINFOChecking whether WebSite.publisher points to the Organization entity organizationFormat="json-ld"FAILCheck publisher presence actual=false expected=true publisher={"present":false,"matchesOrganization":false} website={} organization={"name":"Wraps","url":"https://wraps.dev"}FAILCheck publisher matches Organization actual=false expected=trueFAILWebSite publisher is missing

AI DiscoverabilityContent ReadinessEstablished

Author attribution

Author attribution is partially implemented.

9 Warning

Needs attention

Author attribution

Warning
01

Issue

No named author or publisher identity could be extracted.

02

Why it matters

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

Check name

Author attribution

Score

55/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Identify content authors or publishers for trust and attribution.

Result

Author attribution is partially implemented.

Validation steps

  1. Schema.org attribution

    Schema.org attribution is incomplete or relies only on publisher/fallback evidence.

  2. Author identity quality

    No named author or publisher identity could be extracted.

Evidence log2 steps · 8 lines
Schema.org attribution [warning]! Schema.org attribution is incomplete or relies only on publisher/fallback evidence.INFOSchema.org attributionINFOChecking structured data for author, creator, and publisher contributorsWARNCheck named Schema.org author count actual=0 expected="> 0" authorCount=0 publisherCount=0 namedContributors=0 authors=[] publishers=[] formats=[]WARNSchema.org attribution is incomplete or fallback-only authorCount=0 publisherCount=0 authors=[] publishers=[]Author identity quality [fail]! No named author or publisher identity could be extracted.INFOAuthor identity qualityINFOChecking contributors for stable identity signalsFAILCheck identified contributor count actual=0 expected="> 0" namedContributors=0 identifiedContributors=[] unidentifiedContributors=[]FAILNo named contributor identity could be extracted

Agent Ease of UseSkill DiscoveryEmerging recommendation

A2A Agent Card

A2A Agent Card failed at "Probe same-origin A2A endpoint".

9 Fail

Needs attention

A2A Agent Card

Failed check
01

Issue

The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.

02

Why it matters

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

Check name

A2A Agent Card

Score

65/100

Status

fail

Category

Skill Discovery

Maturity

Emerging recommendation

Goal

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

Result

A2A Agent Card failed at "Probe same-origin A2A endpoint".

Validation steps

  1. Discover A2A Agent Card

    The A2A Agent Card was found at a legacy or fallback path.

  2. Review public-card safety

    The A2A Agent Card security declarations need review.

  3. Probe same-origin A2A endpoint

    The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.

Evidence log3 steps · 17 lines
Discover A2A Agent Card [warning]! The A2A Agent Card was found at a legacy or fallback path.INFODiscover A2A Agent CardINFOTry A2A discovery paths in priority order paths=["/.well-known/agent-card.json","/.well-known/agent.json","/agent-card.json","/.well-known/a2a/agent-card.json"]WARNA2A candidate path did not return a usable card path="/.well-known/agent-card.json" statusCode=404 contentType="text/html; charset=utf-8"PASSFound an A2A candidate path="/.well-known/agent.json" statusCode=200 contentType="application/json; charset=utf-8" bytes=3108WARNA2A candidate path did not return a usable card path="/agent-card.json" statusCode=404 contentType="text/html; charset=utf-8"WARNA2A candidate path did not return a usable card path="/.well-known/a2a/agent-card.json" statusCode=404 contentType="text/html; charset=utf-8"WARNSelected non-canonical A2A Agent Card path="/.well-known/agent.json" pathClass="legacy-a2a" requestedUrl="https://wraps.dev/.well-known/agent.json"WARNThe A2A Agent Card was found at a legacy or fallback path.Review public-card safety [warning]! The A2A Agent Card security declarations need review.INFOReview public-card safetyWARNCompare public secret findings actual=0 expected=0WARNSecurity declaration needs review warning="security scheme \"bearer\" is declared but not referenced by security requirements"WARNSecurity declaration needs review warning="security scheme \"aws_credentials\" is declared but not referenced by security requirements"WARNThe A2A Agent Card security declarations need review.Probe same-origin A2A endpoint [fail]! The same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.INFOProbe same-origin A2A endpointINFOProbe same-origin A2A endpoint when scanner policy allows itFAILA2A endpoint probe did not validate url="https://wraps.dev/" statusCode=405FAILThe same-origin A2A endpoint did not return a valid A2A Message, Task, or authentication challenge.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Citable passages

GEO: Citable passages scored 35/100 and needs a fix.

8 Fail

Needs attention

GEO: Citable passages

Failed check
01

Issue

No evidence-backed, citation-length explanatory paragraph was found.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Citable passages

Score

35/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Citable passages scored 35/100 and needs a fix.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Answer-first passages

AEO: Answer-first passages scored 23/100 and needs a fix.

7 Fail

Needs attention

AEO: Answer-first passages

Failed check
01

Issue

26 section(s) bury or omit a concise opening answer.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Answer-first passages

Score

23/100

Status

fail

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Answer-first passages scored 23/100 and needs a fix.

AI DiscoverabilityContent ReadinessEstablished

Semantic HTML

Semantic HTML is partially implemented.

6 Warning

Needs attention

Semantic HTML

Warning
01

Issue

Semantic HTML is incomplete: skipped or empty headings; 3 controls 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

70/100

Status

warning

Category

Content Readiness

Maturity

Established

Goal

Expose readable page structure through semantic HTML and accessible controls.

Result

Semantic HTML is partially implemented.

Validation steps

  1. Heading structure

    Headings skip levels or include empty heading elements.

  2. Buttons and interactive controls

    3 button controls are missing accessible names.

Evidence log2 steps · 6 lines
Heading structure [fail]! Headings skip levels or include empty heading elements.INFOHeading structureFAILCheck heading structure evidence actual={"counts":{"h1":1,"visibleH1":1,"headings":33,"emptyHeadings":0},"meaningfulH1":true} expected="semantic HTML evidence for this step"FAILHeading structure failed issue="Headings skip levels or include empty heading elements."Buttons and interactive controls [fail]! 3 button controls are missing accessible names.INFOButtons and interactive controlsFAILCheck buttons and interactive controls evidence actual={"counts":{"buttons":23,"inaccessibleButtons":3},"accessibleButtons":false} expected="links, buttons, and form controls expose accessible names"FAILButtons and interactive controls failed issue="3 button controls are missing accessible names."

Agent Ease of UseAPIEstablished

API Catalog

API Catalog has a validation warning at "Check API catalog HEAD Link header".

5 Warning

Needs attention

API Catalog

Warning
01

Issue

HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".

02

Why it matters

API catalogs help agents find API endpoints, service descriptions, documentation, status resources, auth metadata, and related machine-readable contracts without guessing entry points.

Check name

API Catalog

Score

90/100

Status

warning

Category

API

Maturity

Established

Goal

Publish an API catalog for automated public API discovery using RFC 9727 when this origin exposes public APIs.

Result

API Catalog has a validation warning at "Check API catalog HEAD Link header".

Validation steps

  1. Check API catalog HEAD Link header

    HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".

  2. Validate API catalog media type

    The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.

Evidence log2 steps · 8 lines
Check API catalog HEAD Link header [warning]! HEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog".INFOCheck API catalog HEAD Link headerINFOSend HEAD request to API catalog path attempted=true statusCode=200 contentType="application/linkset+json"WARNCompare HEAD Link rel=api-catalog count actual=0 expected="> 0"WARNHEAD /.well-known/api-catalog did not expose a Link header with rel="api-catalog". status="warning"Validate API catalog media type [warning]! The API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter.INFOValidate API catalog media typeWARNCompare API catalog media type actual="application/linkset+json" expected="application/linkset+json"WARNCompare RFC 9727 profile parameter actual=false expected=trueWARNThe API catalog uses application/linkset+json but does not include the recommended RFC 9727 profile parameter. status="warning"

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Source and trust signals

AIO: Source and trust signals scored 50/100 and needs improvement.

5 Warning

Needs attention

AIO: Source and trust signals

Warning
01

Issue

Missing AIO trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Source and trust signals

Score

50/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Source and trust signals scored 50/100 and needs improvement.

Security & TrustSecurity & TrustEstablished

Frame protection

Frame protection has a validation warning at "Validate CSP frame-ancestors".

5 Warning

Needs attention

Frame protection

Warning
01

Issue

Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.

02

Why it matters

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

Check name

Frame protection

Score

81/100

Status

warning

Category

Security & Trust

Maturity

Established

Goal

Prevent unwanted framing with an enforcing CSP frame-ancestors directive or a valid X-Frame-Options fallback.

Result

Frame protection has a validation warning at "Validate CSP frame-ancestors".

Validation steps

  1. Validate CSP frame-ancestors

    Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.

Evidence log1 step · 4 lines
Validate CSP frame-ancestors [warning]! Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.INFOValidate CSP frame-ancestorsINFORead CSP frame-ancestors signals enforcingHeaderPresent=false reportOnlyHeaderPresent=false metaFrameAncestors=false policyCount=0 duplicateDirectives=[]WARNCompare effective frame-ancestors directive actual="missing" expected="valid restrictive enforcing frame-ancestors" issue="Frame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control."WARNFrame protection relies only on X-Frame-Options; CSP frame-ancestors is the modern control.

Security & TrustSecurity & TrustEstablished

Referrer-Policy

Referrer-Policy has a validation warning at "Review policy strength".

4 Warning

Needs attention

Referrer-Policy

Warning
01

Issue

origin-when-cross-origin can send origin information on HTTPS to HTTP downgrades.

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

83/100

Status

warning

Category

Security & Trust

Maturity

Established

Goal

Limit how much referrer data leaves the site with an explicit Referrer-Policy header.

Result

Referrer-Policy has a validation warning at "Review policy strength".

Validation steps

  1. Review policy strength

    origin-when-cross-origin can send origin information on HTTPS to HTTP downgrades.

  2. Review observed browser responses

    One or more same-origin HTML documents observed by Chrome emitted a weaker Referrer-Policy.

Evidence log2 steps · 8 lines
Review policy strength [warning]! origin-when-cross-origin can send origin information on HTTPS to HTTP downgrades.INFOReview policy strengthINFOClassify effective referrer policy effectivePolicy="origin-when-cross-origin" classification="weak" strongPolicies=["no-referrer","same-origin","strict-origin","strict-origin-when-cross-origin"] weakPolicies=["no-referrer-when-downgrade","origin","origin-when-cross-origin"] unsafePolicy="unsafe-url"WARNCompare policy privacy strength actual="weak" expected="strong or modern-baseline" issue="origin-when-cross-origin can send origin information on HTTPS to HTTP downgrades."WARNorigin-when-cross-origin can send origin information on HTTPS to HTTP downgrades.Review observed browser responses [warning]! One or more same-origin HTML documents observed by Chrome emitted a weaker Referrer-Policy.INFOReview observed browser responsesINFOSample Chrome-observed same-origin responses observedResponseCount=37 sameOriginCount=35 htmlDocumentCount=1WARNCompare observed Referrer-Policy coverage actual={"missingPolicyCount":0,"unsafeOrInvalidPolicyCount":0,"weakPolicyCount":1,"affected":[{"url":"https://wraps.dev/","status":200,"resourceType":"document","contentType":"text/html; charset=utf-8","referrerPolicy":"origin-when-cross-origin","effectivePolicy":"origin-when-cross-origin","classification":"weak"}]} expected="0 missing, unsafe, invalid, or weak same-origin HTML responses" issue="One or more same-origin HTML documents observed by Chrome emitted a weaker Referrer-Policy."WARNOne or more same-origin HTML documents observed by Chrome emitted a weaker Referrer-Policy.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Source and trust signals

GEO: Source and trust signals scored 67/100 and needs improvement.

4 Warning

Needs attention

GEO: Source and trust signals

Warning
01

Issue

Missing source or trust signals: authorOrOwner, freshnessDate.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Source and trust signals

Score

67/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Source and trust signals scored 67/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Evidence and trust

AEO: Evidence and trust scored 57/100 and needs improvement.

4 Warning

Needs attention

AEO: Evidence and trust

Warning
01

Issue

Missing answer evidence or trust signals: author, publisher, freshnessDate.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Evidence and trust

Score

57/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Evidence and trust scored 57/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

GEO: Structured extraction

GEO: Structured extraction scored 75/100 and needs improvement.

3 Warning

Needs attention

GEO: Structured extraction

Warning
01

Issue

Missing or weak extraction signals: clean heading hierarchy, summary or key takeaways.

Details

02

Why it matters

Generative answer systems work best with visible, self-contained, evidence-backed content, clear entities, trustworthy attribution, structured page sections, and crawler-accessible HTML. These signals improve machine understanding even though they do not guarantee AI citations.

Check name

GEO: Structured extraction

Score

75/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for AI answer engines to extract, cite, and attribute without promising inclusion in any proprietary answer surface.

Result

GEO: Structured extraction scored 75/100 and needs improvement.

AI DiscoverabilityContent ReadinessEstablished

Structured data

Structured data failed at "Page-relevant schema family".

3 Fail

Needs attention

Structured data

Failed check
01

Issue

The page has specific visible content intent, but structured data does not include a matching primary schema family.

02

Why it matters

Structured data gives agents explicit entities, relationships, and page meaning that are harder to infer reliably from visual layout alone.

Check name

Structured data

Score

87/100

Status

fail

Category

Content Readiness

Maturity

Established

Goal

Expose machine-readable page entities and relationships through a recognized structured-data syntax.

Result

Structured data failed at "Page-relevant schema family".

Validation steps

  1. Page-relevant schema family

    The page has specific visible content intent, but structured data does not include a matching primary schema family.

Evidence log1 step · 4 lines
Page-relevant schema family [fail]! The page has specific visible content intent, but structured data does not include a matching primary schema family.INFOPage-relevant schema familyINFOInferring specific page intent and comparing it with detected Schema.org typesFAILCheck schema types matching specific visible page intent actual=0 expected="> 0" inferredIntents=["software"] expectedTypes=["SoftwareApplication","WebApplication","MobileApplication"] matchingTypes=[] observedTypes=["FAQPage","Organization"]FAILNo primary schema family matches the inferred page intent expectedTypes=["SoftwareApplication","WebApplication","MobileApplication"] primaryTypes=["FAQPage"]

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Page experience proxy

AIO: Page experience proxy scored 80/100 and needs improvement.

2 Warning

Needs attention

AIO: Page experience proxy

Warning
01

Issue

4 image(s) are missing width/height attributes.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Page experience proxy

Score

80/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Page experience proxy scored 80/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AIO: Visible content clarity

AIO: Visible content clarity scored 85/100 and needs improvement.

2 Warning

Needs attention

AIO: Visible content clarity

Warning
01

Issue

26 section(s) may benefit from clearer answer-first openings. Heading outline issues were detected.

Details

02

Why it matters

Google AI Overviews and AI Mode depend on normal Google Search eligibility, snippet permissions, useful visible content, consistent structured data, trust signals, and page experience basics. These signals help Google understand and preview a page, but they do not guarantee selection.

Check name

AIO: Visible content clarity

Score

85/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content eligible, understandable, and previewable for Google Search AI features without promising inclusion.

Result

AIO: Visible content clarity scored 85/100 and needs improvement.

Security & TrustSecurity & TrustEstablished

HSTS header

HSTS header has a validation warning at "Review subdomain scope".

2 Warning

Needs attention

HSTS header

Warning
01

Issue

HSTS is valid, but includeSubDomains is absent.

02

Why it matters

HSTS tells browsers to keep using HTTPS after the first secure visit, reducing downgrade, SSL-stripping, and mixed-transport risk for repeat users.

Check name

HSTS header

Score

94/100

Status

warning

Category

Security & Trust

Maturity

Established

Goal

Require HTTPS for repeat browser visits with a valid Strict-Transport-Security policy.

Result

HSTS header has a validation warning at "Review subdomain scope".

Validation steps

  1. Review subdomain scope

    HSTS is valid, but includeSubDomains is absent.

Evidence log1 step · 4 lines
Review subdomain scope [warning]! HSTS is valid, but includeSubDomains is absent.INFOReview subdomain scopeINFOInspect subdomain enforcement scope includeSubDomains=falseWARNCompare includeSubDomains coverage actual="absent" expected="included after subdomains are HTTPS-ready" issue="HSTS is valid, but includeSubDomains is absent."WARNHSTS is valid, but includeSubDomains is absent.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Question and answer structure

AEO: Question and answer structure scored 84/100 and needs improvement.

1 Warning

Needs attention

AEO: Question and answer structure

Warning
01

Issue

4 Q&A structured-data value(s) were not found in visible content. Heading structure issues were detected.

Details

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Question and answer structure

Score

84/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

AEO: Question and answer structure scored 84/100 and needs improvement.

GEO, AIO and AEOGEO, AIO & AEOEmerging recommendation

AEO: Entity and definition clarity

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

1 Warning

Needs attention

AEO: Entity and definition clarity

Warning
01

Issue

26 section(s) bury or omit a concise opening answer.

02

Why it matters

Answer engines need visible answer passages, clear question and heading structure, entity definitions, evidence, and trust signals. These signals improve extraction and attribution, but they do not guarantee answer-engine citations or search features.

Check name

AEO: Entity and definition clarity

Score

87/100

Status

warning

Category

GEO, AIO & AEO

Maturity

Emerging recommendation

Goal

Make page content easy for answer engines and assistants to extract, answer from, and attribute without promising inclusion in any proprietary answer surface.

Result

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

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 log2 steps · 10 lines
Find advertised IndexNow key location [informational]! No IndexNow key location was advertised in HTML, Link headers, or robots.txt.INFOFind advertised IndexNow key locationINFOLook for IndexNow key hints in HTML, Link headers, and robots.txt supportedHints=["robots.txt IndexNow-Key","rel=indexnow-key","meta name=indexnow-key-location"]PASSCompare advertised key location count actual=0 expected="> 0"WARNNo IndexNow key location was advertised in HTML, Link headers, or robots.txt.Fetch and validate IndexNow key file [informational]! No discoverable IndexNow key file was found.INFOFetch and validate IndexNow key fileINFOLook for IndexNow key hints in HTML, Link headers, and robots.txt supportedHints=["robots.txt IndexNow-Key","rel=indexnow-key","meta name=indexnow-key-location"]PASSCompare advertised key location count actual=0 expected="> 0"INFOFetch each advertised same-origin key file and validate filename/body matchFAILCompare valid IndexNow key file count actual=0 expected="> 0"WARNNo discoverable IndexNow key file was found.

Performance and AccessibilityAccessibilityBrowser audit

Buttons do not have an accessible name

100 Fail

Check name

Buttons do not have an accessible name

Score

0/100

Status

fail

Device

desktop

Category

Accessibility

Fix guidance

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. [Learn how to make buttons more accessible](https://dequeuniversity.com/rules/axe/4.11/button-name).

Evidence
{
  "description": "When a button doesn't have an accessible name, screen readers announce it as \"button\", making it unusable for users who rely on screen readers. [Learn how to make buttons more accessible](https://dequeuniversity.com/rules/axe/4.11/button-name)."
}

Performance and AccessibilityPerformanceBrowser audit

Links rely on color to be distinguishable.

17 Fail

Check name

Links rely on color to be distinguishable.

Score

0/100

Status

fail

Device

desktop

Category

Performance

Fix guidance

Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. [Learn how to make links distinguishable](https://dequeuniversity.com/rules/axe/4.11/link-in-text-block).

Evidence
{
  "description": "Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. [Learn how to make links distinguishable](https://dequeuniversity.com/rules/axe/4.11/link-in-text-block)."
}

Performance and AccessibilityPerformanceBrowser audit

Duplicated JavaScript

8 Warning

Check name

Duplicated JavaScript

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 52 KiB

Fix guidance

Remove large, [duplicate JavaScript modules](https://developer.chrome.com/docs/performance/insights/duplicated-javascript) from bundles to reduce unnecessary bytes consumed by network activity.

Evidence
{
  "description": "Remove large, [duplicate JavaScript modules](https://developer.chrome.com/docs/performance/insights/duplicated-javascript) from bundles to reduce unnecessary bytes consumed by network activity.",
  "displayValue": "Est savings of 52 KiB"
}

Performance and AccessibilityPerformanceBrowser audit

Improve image delivery

8 Warning

Check name

Improve image delivery

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 123 KiB

Fix guidance

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

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

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 42 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
{
  "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)",
  "displayValue": "Est savings of 42 KiB"
}

Performance and AccessibilityPerformanceBrowser audit

Use efficient cache lifetimes

8 Warning

Check name

Use efficient cache lifetimes

Score

50/100

Status

warning

Device

desktop

Category

Performance

Estimated savings

Est savings of 66 KiB

Fix guidance

A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).

Evidence
{
  "description": "A long cache lifetime can speed up repeat visits to your page. [Learn more about caching](https://developer.chrome.com/docs/performance/insights/cache).",
  "displayValue": "Est savings of 66 KiB"
}

Performance and AccessibilityPerformanceBrowser audit

Loading performance

4 Fail

Check name

Loading performance

Score

74/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": "first-contentful-paint",
      "score": 100,
      "title": "First Contentful Paint",
      "displayValue": "0.3 s",
      "numericValue": 321
    },
    {
      "id": "speed-index",
      "score": 94,
      "title": "Speed Index",
      "displayValue": "1.1 s",
      "numericValue": 1133.990893963198
    },
    {
      "id": "max-potential-fid",
      "score": 1,
      "title": "Max Potential First Input Delay",
      "displayValue": "810 ms",
      "numericValue": 806
    },
    {
      "id": "server-response-time",
      "score": 100,
      "title": "Initial server response time was short",
      "displayValue": "Root document took 0 ms",
      "numericValue": 3
    },
    {
      "id": "network-rtt",
      "score": 100,
      "title": "Network Round Trip Times",
      "displayValue": "10 ms",
      "numericValue": 8.88159
    },
    {
      "id": "interactive",
      "score": 91,
      "title": "Time to Interactive",
      "displayValue": "2.4 s",
      "numericValue": 2389
    },
    {
      "id": "largest-contentful-paint",
      "score": 99,
      "title": "Largest Contentful Paint",
      "displayValue": "0.7 s",
      "numericValue": 661
    },
    {
      "id": "total-blocking-time",
      "score": 6,
      "title": "Total Blocking Time",
      "displayValue": "960 ms",
      "numericValue": 962
    }
  ]
}

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
70/100Level 3, Bot-AwareCurrent report