visibility

capability

dify.ai

✓ verified

AI Visibility: ✓ check completed — level L3

AI Capability: ✓ check completed — level L3

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

Dify.ai demonstrates solid foundational readiness for AI systems, with strong basic accessibility and advanced agent integration features. However, it lacks key trust signals and structured data that would maximize its discoverability and recommendation by AI assistants.

AI Visibility — L3

The site is easily crawlable and has clear content, but it misses opportunities to build authority and trust with AI systems by not using Schema.org data, author attribution, or publication dates. This limits its potential to be confidently recommended as a source.

AI Capability — L3

The platform is well-equipped for programmatic use by AI agents, offering a structured API, MCP server, and real-time features. Gaps in agent-specific discovery files and standardized error handling slightly hinder seamless, autonomous agent integration.

A score of 3/5 indicates a functional but unoptimized presence. The site is findable and usable by AI, but it is missing the structured data and agent-friendly protocols that would make it a top-tier, trusted resource for AI systems to recommend and interact with.

Top Issues

HIGH Missing Semantic HTML Structure capability · L1 · developer

Why: Semantic HTML elements (like <header>, <nav>, <main>, <article>) provide a clear, programmatic structure for AI agents to parse and understand the purpose of different page sections. Without it, AI must infer structure from generic <div> tags, which is error-prone.

Impact: AI agents may misinterpret your content, fail to navigate correctly, or provide poor summaries to users, degrading the user experience for those arriving via AI.

Fix: Audit key pages (homepage, product, docs, blog). Replace generic <div> containers with appropriate semantic HTML5 elements. Ensure a logical document outline with one <main> element and proper use of <section> and <article>.

HIGH Missing Basic Schema.org Structured Data capability · L1 · developer

Why: JSON-LD structured data is a primary way for AI systems to unambiguously understand the entities, topics, and purpose of a page. It's a foundational signal for AI comprehension.

Impact: Your content is less likely to be accurately summarized, cited, or recommended by AI assistants. You miss opportunities for rich AI-driven features like direct answer extraction.

Fix: Implement core JSON-LD schemas on all pages. Start with WebSite and Organization on the homepage. Add Article schema for blog posts and SoftwareApplication or Product schema for your core product pages.

HIGH Lacks Schema.org for Content Clarity visibility · L2 · developer

Why: Schema.org markup helps AI understand page content with high accuracy, moving beyond keyword matching to understanding entities and relationships. This is critical for AI visibility.

Impact: Reduces the likelihood and accuracy of your site appearing in AI-generated answers. Competitors with structured data will be favored for precise information retrieval.

Fix: Add JSON-LD blocks to key content pages. For a product site like dify.ai, prioritize SoftwareApplication, Organization, and FAQPage schemas. Use a structured data testing tool to validate.

MEDIUM Poor Internal Linking for Discoverability visibility · L3 · product

Why: AI crawlers, like search crawlers, discover content by following links. If key pages are buried or not linked from primary navigation, they may be invisible to AI systems.

Impact: Important product, pricing, or documentation pages may not be indexed or considered by AI, limiting the depth of information AI can access and share about your business.

Fix: Conduct a crawl to identify orphaned or deep pages. Ensure all primary content sections (Product, Use Cases, Docs, Blog, Pricing) are accessible via clear navigation in the header, footer, or homepage body links.

MEDIUM No Public OpenAPI Specification capability · L2 · developer

Why: An OpenAPI spec is a machine-readable blueprint of your API. It allows AI agents to autonomously discover, understand, and potentially interact with your API endpoints.

Impact: Prevents AI agents from programmatically integrating with your platform, blocking a pathway for automated workflows, customer support bots, or developer assistance tools built on AI.

Fix: Generate and publish an OpenAPI (Swagger) specification for your public API. Host it at a predictable URL (e.g., /api/v1/openapi.json). Ensure it is accurate, versioned, and linked from your developer documentation.

Quick Wins

⚡

Missing Organization Schema for Trust — Add a JSON-LD Organization block to your homepage. Include required properties: @type (Organization), name, url, and logo. Link it to the page using the @id property. (developer)

⚡

Missing Author Attribution on Content — Add visible author bylines to blog articles and key documentation pages. For even better AI visibility, implement Person or Organization schema within the Article markup. (content)

⚡

Missing Publish/Update Dates — Ensure all blog posts, news articles, and documentation pages display a clear publication date. For technical docs, also consider an 'Last Updated' date. Use the datePublished and dateModified properties in Article schema. (content)

⚡

Lacks FAQ Schema for Direct Answer Extraction — Identify common customer questions (e.g., 'What is Dify?', 'How does pricing work?'). Create an FAQ page or section and mark it up with FAQPage schema. Add to high-traffic pages like homepage or pricing. (content)

30-Day Roadmap

Week 1: Quick Wins

— Add JSON-LD Organization schema to homepage with required properties (@type, name, url, logo, @id).

— Add visible author bylines to blog articles and key docs; implement Person/Organization schema within Article markup.

— Ensure all blog posts and docs display clear publication dates; implement datePublished and dateModified in Article schema.

— Create an FAQ page/section for common questions and mark it up with FAQPage schema; add to high-traffic pages.

Visibility L3 → L4

Week 2: Foundation

— Audit key pages (homepage, product, docs, blog) and replace generic <div> containers with semantic HTML5 elements (e.g., <main>, <section>, <article>).

— Implement core JSON-LD schemas on all pages: WebSite and Organization on homepage, Article for blog posts, SoftwareApplication for product pages.

— Add JSON-LD blocks for content clarity, prioritizing SoftwareApplication, Organization, and FAQPage schemas; validate with structured data testing tool.

Capability L3 → L4, Visibility L4 → L4 (consolidation)

Weeks 3-4: Advanced

— Crawl site to identify orphaned or deep pages; improve internal linking by ensuring all primary content sections are accessible via clear navigation in header, footer, or homepage links.

— Generate and publish an accurate, versioned OpenAPI specification for the public API at a predictable URL (e.g., /api/v1/openapi.json); link from developer documentation.

Visibility L4 → L5, Capability L4 → L5

By addressing foundational HTML and structured data first, then enhancing discoverability and API documentation, the site can realistically achieve AI Visibility Level 5 and AI Capability Level 5 within 30 days.

// embed badge

L3 AI Visibility L3 AI Capability

AI Visibility — markdown:

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

AI Capability — markdown:

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

About badges