visibility

capability

devsource.dev

✓ verified

AI Visibility: ✓ check completed — level L5

AI Capability: ✓ check completed — level L2

Levels are cumulative — you must pass L1 before reaching L2, L2 before L3, and so on.

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 4/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 0/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 0/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 0/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

devsource.dev is exceptionally well-prepared for AI-driven discovery and recommendation, achieving a top-tier visibility score by ensuring its content is crawlable, clearly structured, and rich with trust signals. However, its AI capability is severely limited, as the site offers no programmatic interfaces for AI agents to interact with beyond basic content retrieval. The primary gap is the complete absence of APIs, structured interaction protocols, and agent integration features, which prevents the site from supporting autonomous or semi-autonomous AI workflows.

AI Visibility — L5

The site demonstrates near-perfect AI discoverability, passing all checks for crawlability, content clarity, and discoverability, and most checks for trust and AI optimization. This means AI systems like ChatGPT, Perplexity, and Gemini can easily find, understand, and recommend the site's content, with strong signals from structured data, sitemaps, and an llms.txt file. The only minor gaps are missing contact/author attribution and breadcrumb/review schema, which slightly reduce the depth of trust and contextual signals available to AI.

AI Capability — L2

AI agent interoperability is minimal, with the site passing only basic accessibility and discoverability checks. While agents can read the content and understand its structure, there are no APIs, JSON responses, search/filter capabilities, or agent descriptor files, making it impossible for agents to perform actions or retrieve data programmatically. The site lacks all advanced integration features such as MCP servers, webhooks, authentication for automation, and event streaming, meaning it cannot support any form of autonomous agent operation or complex workflow.

The 5/5 visibility score means the site is fully optimized to appear in AI-generated answers and recommendations, capturing the growing traffic from AI assistants. However, the 2/5 capability score means the site is missing out on the emerging wave of AI agents that can perform tasks, book services, or retrieve dynamic data on behalf of users, limiting its potential for automation-driven engagement and transactions.

Top Issues

CRITICAL No structured REST or GraphQL API for programmatic access capability · L3 · developer

Why: Without a well-defined API, AI agents cannot programmatically retrieve data or perform actions on the site. This is the foundational capability for all agent interactions and blocks most advanced AI use cases.

Impact: AI systems cannot integrate with the site's data or services, severely limiting the potential for AI-driven automation, integrations, and new revenue streams. Competitors with APIs will be preferred by AI agents.

Fix: Design and expose a REST or GraphQL API for core resources. Start with read-only endpoints for key content (e.g., posts, products, docs). Document endpoints with OpenAPI. Ensure consistent URL structure and HTTP methods.

CRITICAL No machine-parseable documentation for agents capability · L2 · content

Why: AI agents need clear, structured documentation to understand how to use the site's features and APIs. Without it, they cannot discover or correctly invoke capabilities.

Impact: Even if an API existed, agents would not know how to use it. This blocks AI-driven usage and reduces the site's usefulness to AI systems, leading to lost AI referral traffic and automation opportunities.

Fix: Create comprehensive documentation in Markdown or HTML with clear sections for getting started, endpoints, parameters, and examples. Publish it at a predictable URL (e.g., /docs). Include an llms.txt file that links to the docs for LLM consumption.

HIGH No OpenAPI/Swagger specification published capability · L2 · developer

Why: An OpenAPI spec is the standard way for AI agents to programmatically understand available API endpoints, request/response formats, and authentication. Without it, agents cannot reliably integrate with the API.

Impact: AI agents cannot discover or use the API, making the site effectively invisible to AI-driven automation. This reduces the site's value as a data source or service provider in AI ecosystems.

Fix: Generate an OpenAPI 3.0 specification from your API code (e.g., using Swagger tools). Publish it at a standard location like /openapi.json or /swagger.json. Ensure it includes all endpoints, parameters, and response schemas.

HIGH No MCP (Model Context Protocol) server provided capability · L4 · developer

Why: MCP is the emerging standard for AI agents to access tools and data through a standardized interface. Without an MCP server, agents cannot easily connect to the site's capabilities, limiting integration with major AI platforms.

Impact: The site will be excluded from the growing ecosystem of MCP-compatible AI agents, missing out on AI-driven traffic, automation, and partnership opportunities.

Fix: Implement an MCP server that exposes the site's core data and actions as tools. Follow the MCP specification (modelcontextprotocol.io). Start with read-only tools, then add write tools. Host it at a stable URL and document it.

HIGH Contact or about page not easily discoverable visibility · L4 · content

Why: AI systems and users need to verify the site's legitimacy and find ways to contact the owner. A missing or hidden contact page reduces trust and can cause AI to deprioritize the site.

Impact: Reduced trust signals can lower AI referral traffic and user confidence, potentially decreasing conversions and credibility.

Fix: Create a /contact or /about page with clear contact information (email, form, or social links). Link to it from the main navigation and footer. Add Organization schema with contactPoint to make it machine-readable.

Quick Wins

⚡

Add a visible contact or about page — Create a /contact or /about page with clear contact information (email, form, or social links). Link to it from the main navigation and footer. Add Organization schema with contactPoint to make it machine-readable. (content)

⚡

Add author attribution to pages — Add author bylines to all content pages. Include author name, bio, and link to an author profile page. Use schema.org Person or Organization markup to make it machine-readable. (content)

⚡

Add breadcrumb structured data — Implement breadcrumb navigation on pages and add BreadcrumbList JSON-LD schema to each page. Ensure the breadcrumb trail reflects the site's actual structure. (developer)

⚡

Add review/rating structured data — Add Review or AggregateRating JSON-LD schema to product, service, or content pages where user reviews exist. Ensure the markup matches visible content. (content)

⚡

Document rate limits and return 429 responses — Document rate limits in the API docs and include them in the OpenAPI spec. Implement rate limiting on the server and return 429 with Retry-After header when exceeded. (developer)

30-Day Roadmap

Week 1: Quick Wins

— Create a /contact page with contact information (email, form, or social links) and link it from the main navigation and footer

— Add Organization schema with contactPoint to the /contact page

— Add author bylines to all content pages, including author name, bio, and link to an author profile page

— Add schema.org Person or Organization markup to author bylines

— Implement breadcrumb navigation on pages and add BreadcrumbList JSON-LD schema to each page

— Add Review or AggregateRating JSON-LD schema to pages where user reviews exist

— Document rate limits in the API docs and include them in the OpenAPI spec

— Implement rate limiting on the server and return 429 with Retry-After header when exceeded

Visibility L5 maintained; Capability L2 → L2 (rate limits documented, no level change yet)

Week 2: Foundation

— Design a REST API for core resources (posts, products, docs) with read-only endpoints

— Implement the REST API endpoints with consistent URL structure and HTTP methods

— Generate an OpenAPI 3.0 specification from the API code using Swagger tools

— Publish the OpenAPI spec at /openapi.json or /swagger.json

— Create comprehensive machine-parseable documentation in Markdown or HTML with sections for getting started, endpoints, parameters, and examples

— Publish the documentation at a predictable URL (e.g., /docs)

— Create an llms.txt file that links to the documentation for LLM consumption

Capability L2 → L3 (API and OpenAPI spec published, machine-parseable docs available)

Weeks 3-4: Advanced

— Implement an MCP server that exposes the site's core data and actions as tools

— Follow the MCP specification (modelcontextprotocol.io) and start with read-only tools

— Host the MCP server at a stable URL and document it

— Add write tools to the MCP server after read-only tools are stable

— Ensure the MCP server is linked from the /docs page and llms.txt file

Capability L3 → L4 (MCP server implemented and documented)

Within 30 days, the site can realistically reach AI Visibility Level 5/5 (maintained) and AI Capability Level 4/5, with a fully documented REST API, OpenAPI spec, machine-parseable docs, and an MCP server. The quick wins will solidify visibility, while the foundation and advanced phases will significantly boost capability.