visibility

capability

sky-cloud.net

✓ verified

AI Visibility: ✓ check completed — level L1

AI Capability: ✓ check completed — level L1

L1 Basic Accessibility 5/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 0/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 2/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 1/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 5/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 2/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 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

Sky-Cloud.net has a foundational technical setup but lacks the structured data and proactive signals needed for effective AI discovery and agent integration. Its core content is accessible and it has a basic API, but it misses critical opportunities to be recommended by AI assistants or to enable advanced automated workflows.

AI Visibility — L1

The site is technically crawlable by AI but fails to provide clear, structured information about its content, authority, and freshness. This makes it unlikely to be surfaced as a trusted recommendation by AI assistants like ChatGPT or Perplexity for user queries.

AI Capability — L1

While the site offers a basic, well-documented API for data access, it lacks the standardized interfaces, discovery files, and authentication methods required for AI agents to reliably discover and integrate with its services in an automated fashion.

A score of 1/5 in both tracks means the site is largely invisible to AI discovery systems and offers only minimal, basic programmability, missing out on traffic from AI-driven search and the ability to participate in automated agent ecosystems.

Top Issues

CRITICAL Main Content Not Visible in HTML Source visibility · L1 · developer

Why: AI crawlers like GPTBot often do not execute JavaScript. If core content is loaded only via JavaScript, the AI will see an empty or incomplete page, making the site invisible.

Impact: AI systems cannot discover or understand your services, leading to zero AI-driven traffic, recommendations, or answers about your business.

Fix: Ensure the primary page content (e.g., service descriptions, key information) is present in the initial HTML response. Use server-side rendering (SSR) or static generation for critical pages. Test by viewing the page source (Ctrl+U) and checking for text.

HIGH Missing Basic Structured Data capability · L1 · developer

Why: Structured data (JSON-LD) explicitly defines entities (like your company, services, articles) for AI, making your content machine-readable and far easier to understand and cite accurately.

Impact: AI summaries about your company will be generic or incorrect. You miss opportunities to be featured in rich AI answers, reducing trust and visibility.

Fix: Add a JSON-LD script block to your site's <head>. Start with basic types like 'Organization' (with name, url, logo) and 'WebSite'. Use Google's Structured Data Testing Tool to validate.

HIGH No Schema.org Markup for Content Clarity visibility · L2 · developer

Why: Schema.org markup helps AI understand the specific type and properties of your page content (e.g., is it a software service, an article, a product), leading to more accurate interpretation.

Impact: AI may misinterpret your page's purpose, leading to poor relevance in answers. Competitors with structured data will be prioritized.

Fix: Implement JSON-LD structured data on key pages. For a service site, use 'SoftwareApplication' or 'Service'. For blog posts, use 'Article'. Include properties like name, description, and url.

HIGH Missing or Restrictive robots.txt File capability · L2 · devops

Why: The robots.txt file controls which crawlers can access your site. If missing or blocking AI crawlers, they may not index your content at all.

Impact: AI crawlers (GPTBot, ClaudeBot) may be blocked, preventing your site from ever appearing in AI chat responses or search.

Fix: Create a /robots.txt file. Explicitly allow major AI crawlers: 'User-agent: GPTBot', 'User-agent: ClaudeBot', 'User-agent: PerplexityBot', 'User-agent: Google-Extended' with 'Allow: /'. Ensure it's accessible at sky-cloud.net/robots.txt.

MEDIUM Poor or Missing Heading Hierarchy visibility · L2 · content

Why: Headings (H1, H2, H3) provide a semantic outline of your page. AI uses this structure to understand content organization and extract key topics.

Impact: AI will struggle to parse your content logically, making it less likely to be summarized correctly or cited for specific topics.

Fix: Ensure every page has a single, descriptive H1 tag. Use H2 tags for major sections and H3 for subsections. Avoid using headings purely for visual styling; maintain a logical hierarchy.

Quick Wins

⚡

Missing or Restrictive robots.txt File — Create a /robots.txt file. Explicitly allow major AI crawlers: 'User-agent: GPTBot', 'User-agent: ClaudeBot', 'User-agent: PerplexityBot', 'User-agent: Google-Extended' with 'Allow: /'. Ensure it's accessible at sky-cloud.net/robots.txt. (devops)

⚡

HTML Language Not Declared — Add the 'lang' attribute to the opening <html> tag of every page. For English content, use <html lang="en">. For other languages, use the appropriate ISO language code. (developer)

⚡

Missing Open Graph Tags — Add essential Open Graph meta tags to the <head> of your pages: og:title, og:description, og:image, and og:url. Use your page's core title and a compelling summary. (developer)

⚡

Missing Canonical URL Tag — Add a <link rel="canonical" href="[full-page-url]" /> tag to the <head> of every page. For the homepage, it should point to your root domain (e.g., https://sky-cloud.net). (developer)

⚡

Missing LLMs.txt Guidance File — Create a plain text file at /llms.txt. Follow the llmstxt.org spec: Start with '# Sky-Cloud', a tagline in a blockquote '>', then sections like '## Docs', '## API' with bullet-point links to important pages. Do not use robots.txt syntax. (developer)

30-Day Roadmap

Week 1: Quick Wins

— Create and deploy a /robots.txt file explicitly allowing major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended).

— Add the 'lang' attribute (e.g., lang="en") to the opening <html> tag on every page.

— Add essential Open Graph meta tags (og:title, og:description, og:image, og:url) to the <head> of all pages.

— Add a canonical URL tag (<link rel="canonical" href="..." />) to the <head> of every page.

— Create and deploy an /llms.txt file following the llmstxt.org specification.

Visibility L1 → L2, Capability L1 → L2

Week 2: Foundation

— Implement server-side rendering (SSR) or static generation to ensure primary page content (service descriptions, key info) is present in the initial HTML source.

— Add a JSON-LD script block for basic 'Organization' and 'WebSite' structured data to the site's <head> and validate with Google's Structured Data Testing Tool.

Visibility L2 → L3, Capability L2 → L3

Weeks 3-4: Advanced

— Implement JSON-LD structured data for key content types (e.g., 'SoftwareApplication' or 'Service' for service pages, 'Article' for blog posts) including properties like name, description, and url.

— Audit and correct heading hierarchy across all pages: ensure a single descriptive H1 per page, use H2 for major sections and H3 for subsections, and avoid headings for visual styling only.

Visibility L3 → L4, Capability L3 → L4

By addressing foundational visibility and capability issues, the site can realistically achieve AI Visibility Level 4 and AI Capability Level 4 within 30 days, establishing a robust technical base for AI interaction.

// embed badge

L1 AI Visibility L1 AI Capability

AI Visibility — markdown:

[![ReadyforAI](https://readyforai.dev/badge/sky-cloud.net)](https://readyforai.dev/websites/sky-cloud.net)

AI Capability — markdown:

[![ReadyforAI](https://readyforai.dev/badge/sky-cloud.net?track=capability)](https://readyforai.dev/websites/sky-cloud.net)

About badges