visibility

capability

thclouds.com

✓ verified

AI Visibility: ✓ check completed — level L1

AI Capability: ✓ check completed — level L1

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 1/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 0/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 3/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

The website thclouds.com has a foundational technical setup that allows AI crawlers to access its content, but it lacks the structured data and trust signals needed for AI systems to confidently understand and recommend it. It also provides no programmatic interfaces for AI agents to interact with its services. The site is currently missing significant opportunities for AI-driven discovery and automation.

AI Visibility — L1

AI crawlers can find and read the site's basic content, but the lack of structured data (Schema.org), clear content hierarchy, and essential trust signals like contact information and dates severely limits its potential to be recommended by AI assistants. The site is not optimized to be a reliable source of information for AI systems.

AI Capability — L1

The site is readable by AI agents but offers no APIs or structured interaction points for them to perform tasks. There are no documented endpoints, authentication methods, or write capabilities, meaning AI agents cannot programmatically retrieve data or take actions on behalf of users.

A score of 1/5 in both categories means the site is essentially invisible to AI recommendation engines and unusable by AI agents for automation. It is not positioned to benefit from the growing ecosystem of AI search and agent-based services.

Top Issues

CRITICAL Missing Basic Structured Data capability · L1 · developer

Why: AI systems like ChatGPT rely on structured data (JSON-LD) to accurately understand the entities, purpose, and content of a page. Without it, your site is just unstructured text to an AI.

Impact: AI cannot reliably identify your products, services, or content, making it unlikely to be recommended or used as a source. This is a foundational failure for AI interaction.

Fix: Add JSON-LD structured data blocks to key pages (homepage, product pages, articles). Use Schema.org types like Organization, WebSite, and relevant types for your content (e.g., SoftwareApplication). Place <script type="application/ld+json"> blocks in the <head> of your HTML.

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

Why: Schema.org markup is the primary way to give AI systems explicit, unambiguous signals about your page's content, improving comprehension and relevance for AI-driven search and recommendations.

Impact: Your content is harder for AI to parse and trust, reducing its chances of being surfaced in AI-generated answers, summaries, or recommendations.

Fix: Implement JSON-LD structured data on all key content pages. Start with the homepage (Organization, WebSite) and product/service pages (Product, Service). Use a structured data testing tool to validate.

HIGH Poor Content Hierarchy and Structure visibility · L2 · content

Why: Clear heading tags (H1, H2, H3) provide a semantic outline of your page's content, helping AI systems quickly understand the main topic and subtopics for better summarization and information extraction.

Impact: AI may misinterpret or overlook key information on your pages, leading to inaccurate summaries or failure to identify your core offerings.

Fix: Audit key pages to ensure each has a single, descriptive H1 tag. Use H2 tags for major sections and H3 for subsections. Ensure headings are descriptive and reflect the content that follows.

HIGH Insufficient Meaningful Page Content visibility · L2 · content

Why: AI systems need substantive text to analyze and understand what your page is about. Pages with only a few sentences or boilerplate text provide no value for AI to learn from or cite.

Impact: Pages are ignored or deprioritized by AI crawlers, wasting SEO and content investment. Your site provides no informational value to AI assistants.

Fix: Review key landing and product pages. Expand content to provide clear, detailed descriptions of your offerings, value proposition, and key information. Aim for several paragraphs of unique, valuable text per page.

MEDIUM Missing Organization Identity visibility · L4 · developer

Why: An Organization schema establishes your brand's identity, logo, and official contact points. This builds trust with AI systems, which are more likely to recommend and cite authoritative, verifiable sources.

Impact: Your site lacks brand authority in AI ecosystems. AI may not display your logo or correctly attribute information to your company, reducing brand recognition and trust.

Fix: Add a JSON-LD Organization block to your homepage's <head>. Include required properties: @type (Organization), name, url, and logo. Optionally add contact points and social profiles.

Quick Wins

⚡

Missing Organization Identity — Add a JSON-LD Organization block to your homepage's <head>. Include required properties: @type (Organization), name, url, and logo. Optionally add contact points and social profiles. (developer)

⚡

Missing Open Graph Tags — Add core Open Graph meta tags (og:title, og:description, og:image, og:url, og:type) to the <head> of all key pages. Ensure values are descriptive and unique per page. (developer)

⚡

Missing Canonical URL Tags — Add a <link rel="canonical" href="..."/> tag to the <head> of every page. The href should point to the preferred, clean URL for that content. (developer)

⚡

Contact or About Page Not Easily Found — Ensure a 'Contact' or 'About' link is present in the main navigation or footer of every page. The linked page should contain clear company information and contact details. (content)

⚡

Missing LLMs.txt File for AI Guidance — Create a plain text file at /llms.txt. Format it as Markdown: start with '# Site Name', a tagline in a blockquote '>', then sections like '## Docs' or '## Products' with bullet-point links to key pages. Do not use robots.txt syntax. See llmstxt.org for spec. (developer)

30-Day Roadmap

Week 1: Quick Wins

— Add a JSON-LD Organization block to the homepage's <head> with required properties: @type, name, url, logo.

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

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

— Ensure a 'Contact' or 'About' link is present in the main navigation or footer of every page.

— Create a plain text file at /llms.txt formatted as Markdown per llmstxt.org spec.

Visibility L1 → L2, Capability L1 → L2

Week 2: Foundation

— Add JSON-LD structured data blocks (Schema.org types: Organization, WebSite) to the homepage's <head>.

— Add JSON-LD structured data blocks (e.g., Product, Service) to all key product/service pages' <head>.

— Audit key pages to ensure each has a single, descriptive H1 tag and proper hierarchy (H2, H3).

— Expand content on key landing and product pages with detailed descriptions and value proposition.

Visibility L2 → L3, Capability L2 → L3

Weeks 3-4: Advanced

— Validate all implemented JSON-LD structured data using a structured data testing tool.

— Refine and expand JSON-LD blocks with optional properties (e.g., contact points, social profiles).

— Conduct a full content audit to ensure all pages meet hierarchy and depth standards.

— Plan and implement structured data for additional content types (e.g., articles, FAQs).

Visibility L3 → L4, Capability L3 → L4

After 30 days, the site should achieve AI Visibility Level 4 and AI Capability Level 4, establishing a strong foundation of structured data, clear content hierarchy, and AI-accessible metadata.

// embed badge

L1 AI Visibility L1 AI Capability

AI Visibility — markdown:

[![ReadyforAI](https://readyforai.dev/badge/thclouds.com)](https://readyforai.dev/websites/thclouds.com)

AI Capability — markdown:

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

About badges