visibility

capability

myclaw.ai

✓ verified

AI Visibility: ✓ check completed — level L5

AI Capability: ✓ check completed — level L2

L1 Basic Accessibility 6/6

✓ Major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) are permitted to access your site. AI crawling allowed

✓ Main content is visible in the HTML source, not only rendered after JavaScript executes. Page content directly readable

✓ The page has a clear title and meta description, helping AI quickly identify the topic. Clear title and description

✓ The page responds quickly enough to avoid AI crawl failures or timeouts. Reasonable response time

✓ The site uses a valid HTTPS certificate. HTTPS secured

✓ Core content isn't blocked by login walls, membership gates, or paywalls. Content is not gated

L2 Content Comprehensibility 6/6

✓ Uses Schema.org / JSON-LD to help AI understand page content more accurately. Has structured data

✓ Open Graph tags provide supplementary title and summary information. Has social sharing info

✓ A canonical URL tells search engines and AI which version of the URL is authoritative. Clear canonical address

✓ The page has a clear H1 and uses H2/H3 headings to organize content logically. Clear heading hierarchy

✓ The HTML lang attribute is set, helping AI identify the page language. Language declared correctly

✓ The page has meaningful text content, not just a few sentences of boilerplate. Substantial content

L3 Discoverability 6/6

✓ An accessible XML sitemap helps AI and search engines discover your pages. Provides a sitemap

✓ The sitemap includes recent pages and isn't neglected over time. Sitemap stays updated

✓ Key content pages are easily reachable from the homepage and main pages. Clear internal linking

✓ Page URLs clearly reflect the content topic, rather than being cryptic parameter strings. Clean, readable URLs

✓ A /llms.txt file proactively tells LLMs which content is most worth paying attention to. Provides llms.txt

✓ The canonical tag points to the current page's standard address, avoiding duplicate page confusion. Consistent canonical setup

L4 Trust & Authority 5/6

✓ Structured data includes basic info like company/organization name, website, and logo. Organization info is clear

✓ Both users and AI can easily find your contact or about page. About and contact info visible

✓ Pages attribute content to an author, team, or organization. Content source is clear

✗ Pages include publish or update dates, helping assess content freshness. Publication dates are clear

✓ The site has essential pages like privacy policy and terms of service. Legal info is complete

✓ Basic security response headers are set, reflecting site maintenance quality. Proper security configuration

L5 AI-Optimized 4/6

✓ Page content is structured for AI to directly extract answers. Has FAQ / HowTo / Q&A structure

✗ Helps AI understand the page's position and hierarchy within the site. Has breadcrumb structure

✗ Products, services, or content include structured Review/Rating data. Has review information

✓ Multilingual pages have clear corresponding relationships, such as hreflang tags. Supports multiple languages

✓ Uses multiple effective Schema.org types, not just one. Richer structured data

✓ Pages contain FAQs, tables, lists, definitions, etc., making it easy for AI to extract and summarize. Clear content block structure

L1 Basic Accessibility 6/6

✓ Uses semantic HTML elements such as header, nav, main, article, section, and footer so agents can better understand page structure. Semantic HTML

✓ Includes essential metadata such as page title, description, and social sharing tags to improve machine interpretation. Metadata

✓ Provides JSON-LD structured data based on Schema.org to make entities and page meaning more explicit. Structured Data

✓ Public content is accessible without CAPTCHA or other anti-bot challenges that block legitimate automated access. No CAPTCHA Barriers

✓ Core content is present in the initial HTML response, rather than relying entirely on client-side JavaScript rendering. Server-Rendered Content

✓ Uses stable, human-readable URLs without excessive query parameters, session tokens, or hash-fragment routing. Clean URLs

L2 Discoverability 4/6

✓ Provides a robots.txt file that permits access for legitimate crawlers and agent systems where appropriate. robots.txt

✓ Publishes a valid XML sitemap to help agents and crawlers discover indexable pages efficiently. XML Sitemap

✓ Exposes a /llms.txt file that gives LLM-based systems guidance on important content and site structure. llms.txt

✗ Publishes an OpenAPI or Swagger specification so agents can understand available API endpoints programmatically. OpenAPI Specification

✗ Provides comprehensive documentation in a format that is easy for machines and agents to parse and use. Machine-Readable Documentation

✓ Ensures primary content is available as text, rather than being locked inside images, videos, or non-parsable PDFs. Text-Accessible Content

L3 Structured Interaction 3/6

✗ Exposes a well-defined REST or GraphQL API for programmatic access to data and actions. Structured API

✓ Returns JSON payloads with stable and predictable schemas across endpoints. Consistent JSON Responses

✓ Supports query parameters for search, filtering, pagination, and retrieval refinement. Search and Filtering Support

✗ Provides an agent descriptor, such as an A2A agent card at /.well-known/agent.json, to advertise agent capabilities. A2A Agent Card

✓ Clearly documents rate limits and returns proper 429 Too Many Requests responses when limits are exceeded. Documented Rate Limits

✗ Returns machine-readable error responses with clear codes, messages, and actionable context. Structured Error Handling

L4 Agent Integration 3/6

✗ Provides an MCP (Model Context Protocol) server so agents can access tools, resources, and actions through a standardized interface. MCP Server

✗ Supports WebMCP or comparable browser-oriented agent interaction patterns for web-based automation. WebMCP Support

✓ Supports write operations such as POST, PUT, PATCH, and DELETE, enabling agents to create and update resources. Write-Capable API

✓ Supports automation-ready authentication methods such as API keys or OAuth client credentials flows. Agent-Friendly Authentication

✓ Supports webhooks so agents can receive event-driven updates instead of relying only on polling. Webhooks

✗ Write operations support idempotency keys or equivalent safeguards to prevent duplicate execution. Idempotent Writes

L5 Autonomous Operation 4/6

✗ Supports real-time update channels such as SSE or WebSockets for low-latency agent workflows. Event Streaming

✗ Supports agent-to-agent capability discovery or negotiation so systems can adapt to each other dynamically. Capability Negotiation

✓ Provides APIs for subscription, lifecycle management, or registration of agent integrations. Subscription and Management API

✓ Supports multi-step workflows, task coordination, and stateful execution across actions or services. Workflow Orchestration

✓ Can proactively notify agents when relevant content, state, or business events change. Proactive Notifications

✓ Supports handoff between agents or services so tasks can continue across system boundaries. Cross-Service Handoff

AI Readiness Report

download .md

Executive Summary

MyClaw.ai is exceptionally well-prepared for AI discovery and recommendation, achieving a near-perfect visibility score. However, its readiness for direct programmatic interaction by AI agents is limited, representing a significant missed opportunity for automation and integration. The site excels at being found and understood by AI but lacks the structured interfaces needed for AI to act on its behalf.

AI Visibility — L5

The site is highly discoverable and trustworthy for AI systems like ChatGPT and Perplexity, with excellent foundational SEO, clear content structure, and proactive AI guidance via an llms.txt file. A minor gap in publishing dates and some advanced schema types slightly reduces its ability to signal content freshness and detailed product information to AI.

AI Capability — L2

While the site is accessible and provides some structured data, it lacks the core APIs, documentation, and standardized agent interfaces required for robust AI agent integration. This prevents agents from performing automated tasks, accessing services programmatically, or engaging in real-time workflows with the platform.

The high visibility score means AI can easily find and recommend the site to users. The low capability score means AI agents cannot programmatically use the site's services, limiting potential for automation, customer support integrations, and advanced AI-driven workflows.

Top Issues

CRITICAL No Programmatic API for AI Access capability · L3 · product

Why: AI agents and systems cannot directly interact with your service to retrieve data or perform actions without a well-defined API. This is a foundational requirement for AI capability.

Impact: Severely limits or prevents AI-driven automation, integration, and advanced use cases. AI systems can only read your public website, not *use* your service, missing a major channel for growth and user acquisition.

Fix: Design and implement a public REST or GraphQL API. Start by identifying core data entities (e.g., 'claws', 'projects', 'users') and actions (e.g., 'create', 'analyze', 'fetch'). Define clear endpoints, HTTP methods, request/response formats (JSON), and authentication (e.g., API keys).

HIGH Lacks Machine-Parsable Documentation capability · L2 · developer

Why: Even if an API exists, AI agents need structured documentation to discover and understand how to use it. Without it, agents cannot reliably integrate with your service.

Impact: Hinders AI developer adoption and increases support burden. Agents will struggle to use your service correctly, leading to errors and poor user experiences, reducing trust and utility.

Fix: Create comprehensive API documentation in a standard, machine-friendly format. The best practice is to generate documentation automatically from your OpenAPI specification. Use tools like Swagger UI, Redoc, or Stoplight to host interactive docs.

HIGH Missing OpenAPI Specification capability · L2 · developer

Why: An OpenAPI (Swagger) spec is the lingua franca for describing REST APIs. It allows AI agents and developer tools to programmatically discover endpoints, parameters, and data models.

Impact: Prevents automated tooling and AI agents from reliably integrating with your API. Significantly increases the manual effort required for developers and AI systems to understand your service.

Fix: Create an OpenAPI 3.0 specification file (YAML or JSON) that describes all your API endpoints, methods, request/response schemas, and authentication. Use code annotations or a dedicated library to generate it from your API codebase to keep it in sync.

MEDIUM API Lacks Structured Error Responses capability · L3 · developer

Why: When an API call fails, AI agents need consistent, machine-readable error details to understand the problem and decide on a corrective action (e.g., retry, ask user for clarification).

Impact: Leads to fragile AI integrations. Agents cannot handle failures gracefully, resulting in poor user experiences, abandoned tasks, and increased support tickets for issues that could be resolved automatically.

Fix: Define a standard error response schema for your API. All error responses (4xx, 5xx) should return a JSON object with fields like 'code' (machine-readable string), 'message' (human-readable), 'details' (optional context). Implement this consistently across all endpoints.

MEDIUM No Agent Self-Description File capability · L3 · developer

Why: The A2A agent card is a standard way for a service to advertise its capabilities, endpoints, and authentication requirements to AI agents, making initial discovery and setup seamless.

Impact: Misses an opportunity to be easily discoverable and integrable by the growing ecosystem of AI agents. Agents must manually infer or be configured to use your service, creating friction.

Fix: Create a JSON file at the well-known URL path '/.well-known/agent.json'. Follow the A2A protocol spec. Include basic fields: 'name', 'description', 'api_version', 'capabilities' (list of actions), and 'authentication' (required methods).

Quick Wins

⚡

Content Pages Lack Publication Dates — Add a visible 'Published on' or 'Last updated' date to blog posts, documentation, and key content pages. Also, include this date within the page's HTML metadata (e.g., using 'article:published_time' meta tag or Schema.org). (content)

⚡

Missing Breadcrumb Structured Data — Implement BreadcrumbList JSON-LD on all pages with a clear hierarchy (e.g., Docs > API Reference > Authentication). List each breadcrumb item with 'position', 'name', and 'item' (URL). This can often be added via a site template or CMS plugin. (developer)

⚡

No Agent Self-Description File — Create a JSON file at the well-known URL path '/.well-known/agent.json'. Follow the A2A protocol spec. Include basic fields: 'name', 'description', 'api_version', 'capabilities' (list of actions), and 'authentication' (required methods). (developer)

30-Day Roadmap

Week 1: Quick Wins

— Create the Agent Self-Description JSON file at '/.well-known/agent.json' following A2A protocol spec.

— Add visible publication dates and corresponding HTML metadata (e.g., 'article:published_time') to all blog posts and key content pages.

— Implement BreadcrumbList JSON-LD structured data on all pages with a clear hierarchy.

Capability L2 → L3 (via agent file), Visibility L5 → L5 (enhanced)

Week 2: Foundation

— Design and implement the core public API (REST/GraphQL) with authentication (API keys), focusing on key entities ('claws', 'projects', 'users') and actions ('create', 'analyze', 'fetch').

— Define and implement a standard JSON error response schema (with 'code', 'message', 'details') across all new API endpoints.

Capability L3 → L4 (via functional API)

Weeks 3-4: Advanced

— Create an OpenAPI 3.0 specification file (YAML/JSON) for the API, ideally generated from code annotations to ensure accuracy.

— Generate and publish comprehensive, interactive API documentation (e.g., using Swagger UI or Redoc) from the OpenAPI spec.

Capability L4 → L5 (via complete, documented API)

The site will achieve AI Capability Level 5 by establishing a fully functional, well-documented, and agent-accessible API. AI Visibility Level will remain at 5, but with enhanced structured data and metadata.

// embed badge

L5 AI Visibility L2 AI Capability

AI Visibility — markdown:

[![ReadyforAI](https://readyforai.dev/badge/myclaw.ai)](https://readyforai.dev/websites/myclaw.ai)

AI Capability — markdown:

[![ReadyforAI](https://readyforai.dev/badge/myclaw.ai?track=capability)](https://readyforai.dev/websites/myclaw.ai)

About badges