AI Readiness Report

robots.txt reachable.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

sitemap.xml declared.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

GPTBot allowed in robots.txt.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

ClaudeBot allowed in robots.txt.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Google-Extended allowed in robots.txt.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Bytespider allowed in robots.txt.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

KimiBot allowed in robots.txt.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Organization schema with name + url.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No Product schema.

No Product schema was detected. E-commerce or product content cannot be recognised and cited by AI as a structured entity, which costs you rich-result placement.

1. Add the Product JSON-LD below to each product detail page.
2. Replace name, image, price and brand with real values (price must be a numeric string).
3. Use ItemList to aggregate multiple products on listing pages.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "AI-Powered Software Development Company | CMARIX Product Name",
  "image": ["https://cdn.cmarix.com/images/header/logo.svg"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "AI-Powered Software Development Company | CMARIX" },
  "offers": { "@type": "Offer", "priceCurrency": "USD", "price": "0" }
}
</script>

FAQPage schema present.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No Article schema.

No Article schema was detected. Editorial content is less likely to be treated as an authoritative source by AI, and you miss rich-result placement.

1. Add the Article JSON-LD below to each article page.
2. Ensure author, publisher and datePublished match the visible content.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Article title",
  "author": { "@type": "Person", "name": "Author name" },
  "publisher": { "@type": "Organization", "name": "AI-Powered Software Development Company | CMARIX" },
  "datePublished": "2026-01-01",
  "dateModified": "2026-01-01"
}
</script>

Breadcrumb schema present.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Entity fields covered: 7/11.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Homepage content depth: 5/5.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

About page reachable.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No Product page found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No FAQ page found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No Blog / Case page found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Rich topical content detected.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No blog or case section found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No author attribution detected.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Brand entity consistent across pages.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Few external trust signals.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

OpenAPI / Swagger descriptor found.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No Model Context Protocol endpoint found.

No Model Context Protocol (MCP) endpoint was detected. AI agents cannot tool-enable your service through tools or resources without it.

1. Serve the manifest below at /.well-known/mcp.json.
2. Implement the corresponding MCP server (tools and resources).
3. Document the integration path in your developer docs.

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "AI-Powered Software Development Company | CMARIX", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://cmarix.com/mcp" }
}

No AI Actions manifest detected.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

API / developer documentation linked.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

No RFC 8288 Link response header detected.

No RFC 8288 Link response header was found. Agents cannot discover your API, docs or AI feed from response headers.

1. Add a Link header on your homepage pointing to key machine-readable resources.
2. Example: Link: <https://cmarix.com/openapi.json>; rel="service-desc", <https://cmarix.com/llms.txt>; rel="describedby"

No DNS-AID (SVCB/HTTPS) records detected.

No DNS-AID (SVCB/HTTPS) records were detected. Agents cannot discover your AI service endpoint directly from DNS.

1. Publish SVCB or HTTPS DNS records that point to your AI/agent service.
2. These let agents resolve your MCP or API endpoint without crawling HTML.

No Markdown content negotiation (Accept: text/markdown) detected.

No Markdown content negotiation (Accept: text/markdown) was detected. Agents must parse HTML instead of clean Markdown.

1. When the request Accept header is text/markdown, return a clean Markdown version of the page.
2. Point agents to /llms.txt as a fallback machine-readable overview.

No Content Signals directive (ai-train/search/ai-input) detected.

No Content Signals directive (ai-train / search / ai-input) was detected. You are not explicitly telling AI bots how they may use your content.

1. Add a Content-Signals response header or <meta name="content-signals" content="ai-train=yes; search=yes; ai-input=yes">.

No MCP Server Card (.well-known/mcp/server-card.json) found.

No MCP Server Card was found at .well-known/mcp/server-card.json. Agents cannot discover your MCP tools and resources.

1. Serve the Server Card below at /.well-known/mcp/server-card.json.
2. Implement the corresponding MCP server (tools and resources).

{
  "protocolVersion": "2024-11-05",
  "serverInfo": { "name": "AI-Powered Software Development Company | CMARIX", "version": "1.0.0" },
  "capabilities": { "tools": {}, "resources": {} },
  "endpoints": { "base": "https://cmarix.com/mcp" }
}

No Agent Skills catalog (.well-known/agent-skills) found.

No Agent Skills catalog was found at .well-known/agent-skills. Agents cannot discover the skills your site offers.

1. Create .well-known/agent-skills/ with an index.json listing your skills.
2. Each skill should have a SKILL.md describing when and how to use it.

No OAuth discovery (.well-known/oauth-authorization-server) found.

No OAuth discovery endpoint (.well-known/oauth-authorization-server) was detected. Agents cannot securely authenticate to your API.

1. Publish an OAuth 2.0 authorization server metadata document at /.well-known/oauth-authorization-server.

No Auth.md found.

No Auth.md was found. Agents lack guidance on how to authenticate against your services.

1. Add an Auth.md at your site root or .well-known/ describing authentication flows for agents.

Served over HTTPS.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

Business contact visible.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.

HTTP status 200.

No automated fix snippet for this item — address it directly, or see Actionable Recommendations.