visibility

capability

rubyonvibes.com

✓ verified

AI Visibility: ✓ check completed — level L2

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 4/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 3/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 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 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 2/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 1/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

Rubyonvibes.com has a solid technical foundation for AI discoverability but lacks the advanced structured data and programmatic interfaces needed for high AI visibility and autonomous agent use. Its strengths are in basic accessibility and content clarity, while its key gaps are in establishing trust signals and enabling automated interactions.

AI Visibility — L2

The site is fundamentally crawlable and its content is clear, but it misses critical trust and authority signals like author attribution and publish dates, which limits its recommendation potential by AI. It also lacks advanced AI optimizations like FAQ or review schemas that would help AI systems directly extract and summarize its content.

AI Capability — L2

The site is accessible for basic agent reading and has good documentation, but it does not expose a public API or structured endpoints for programmatic interaction. This prevents AI agents from performing meaningful tasks like searching, filtering, or writing data on the site.

A score of 2/5 in both tracks means the site is visible and usable at a basic level but is missing out on being prominently featured in AI search results and cannot be integrated into automated workflows or agent-based services.

Top Issues

HIGH Missing Structured Data (Schema.org) visibility · L2 · developer

Why: AI systems like ChatGPT and Google's SGE rely on structured data to accurately understand and summarize page content. Without it, AI may misinterpret your content or fail to extract key entities.

Impact: Reduced AI visibility leads to inaccurate or missing AI-generated answers about your site, harming brand representation and missing opportunities for AI-driven traffic and recommendations.

Fix: Add JSON-LD structured data blocks to key pages. For the homepage, use 'WebSite' and 'Organization' types. For blog posts, use 'Article' or 'BlogPosting'. Include properties like name, description, and author.

HIGH Missing Canonical URL Tags visibility · L2 · developer

Why: Canonical tags tell AI and search engines which version of a page is the primary source, preventing duplicate content issues that dilute ranking and AI understanding.

Impact: AI may index and reference duplicate or non-preferred page versions, fragmenting your site's authority and reducing the visibility of your main content.

Fix: Add a <link rel="canonical" href="[full-page-url]"/> tag to the <head> of every page. Ensure it points to the single, authoritative URL for that content.

HIGH Missing XML Sitemap visibility · L3 · developer

Why: An XML sitemap is a roadmap for AI crawlers and search engines to discover all important pages on your site efficiently. Without it, pages may be missed or crawled slowly.

Impact: Key pages may remain undiscovered by AI systems, preventing them from being included in knowledge bases or answer generation, severely limiting AI-driven discovery.

Fix: Generate an XML sitemap (e.g., /sitemap.xml) listing all important URLs. Submit it via Google Search Console and ensure it's referenced in your robots.txt file with 'Sitemap: [url]'.

HIGH Missing Basic Structured Data for APIs capability · L1 · developer

Why: For AI agents to understand and interact with your site's data programmatically, they need explicit, machine-readable definitions of entities and actions via Schema.org.

Impact: AI agents cannot reliably parse or use your site's data for automation, limiting potential integrations and utility as a data source for AI workflows.

Fix: Implement JSON-LD structured data on pages that represent key entities (e.g., products, articles). Use types relevant to your content, such as 'SoftwareApplication' for tools or 'Article' for blog posts.

HIGH Missing Sitemap for Programmatic Discovery capability · L2 · developer

Why: AI agents need a machine-readable sitemap to systematically discover and index your site's pages for programmatic access and data retrieval.

Impact: Agents cannot efficiently crawl or understand your site's structure, blocking automated data collection and integration capabilities.

Fix: Create and publish a valid XML sitemap at a standard location like /sitemap.xml. Ensure it is correctly formatted and lists all indexable pages with their last modification dates.

Quick Wins

⚡

Missing Organization Schema — Add a JSON-LD block for 'Organization' to your homepage. Include required properties: '@type': 'Organization', 'name', 'url', and 'logo' (with a URL to your logo image). (developer)

⚡

Missing Author Attribution — Add author names visibly on blog posts and articles. For better AI understanding, also include the author's name in the Article schema's 'author' property. (content)

⚡

Missing Publish/Update Dates — Add a visible publication date (and optional update date) to all articles and blog posts. Include this date in the 'datePublished' property of the Article schema. (content)

⚡

Canonical Tag Does Not Self-Reference — Audit all pages to ensure the canonical URL in the <link> tag exactly matches the page's own full URL (self-referencing canonical). Fix any that point elsewhere. (developer)

30-Day Roadmap

Week 1: Quick Wins

— Add a JSON-LD block for 'Organization' to the homepage with required properties: '@type', 'name', 'url', and 'logo'.

— Add visible author names to blog posts and include the author's name in the 'author' property of the Article schema.

— Add visible publication dates to all articles and include 'datePublished' in the Article schema.

— Audit all pages to ensure the canonical URL tag self-references the page's own full URL and fix any mismatches.

Visibility L2 → L3

Week 2: Foundation

— Add JSON-LD structured data blocks to key pages: implement 'WebSite' and 'Organization' on homepage, and 'Article' or 'BlogPosting' on blog posts with properties like name, description, and author.

— Add a <link rel='canonical' href='[full-page-url]'/> tag to the <head> of every page, ensuring it points to the authoritative URL.

— Implement JSON-LD structured data for key entities (e.g., products, articles) using relevant types like 'SoftwareApplication' or 'Article'.

Capability L2 → L3

Weeks 3-4: Advanced

— Generate and publish a valid XML sitemap at /sitemap.xml listing all important URLs with last modification dates.

— Submit the XML sitemap via Google Search Console and reference it in the robots.txt file with 'Sitemap: [url]'.

— Ensure the XML sitemap is correctly formatted and comprehensive for programmatic discovery.

Visibility L3 → L4, Capability L3 → L4

After 30 days, the site's AI Visibility Level should improve from 2/5 to 4/5, and AI Capability Level from 2/5 to 4/5, by implementing foundational structured data, canonical tags, and a comprehensive sitemap for better indexing and AI understanding.