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": "企业网站建设_电商网站制作_外贸网站制作_网站维护 | 锐基科技 - 企业数字基础设施服务商 Product Name",
  "image": ["https://30t.cn/images/projects/p1.webp"],
  "description": "Brief product description",
  "brand": { "@type": "Brand", "name": "企业网站建设_电商网站制作_外贸网站制作_网站维护 | 锐基科技 - 企业数字基础设施服务商" },
  "offers": { "@type": "Offer", "priceCurrency": "USD", "price": "0" }
}
</script>

No FAQPage schema.

No FAQPage schema was detected. Common questions and answers cannot be cited directly by AI as authoritative answers, and you miss rich-result opportunities.

1. Add the FAQPage JSON-LD below to your FAQ page.
2. Make sure the question/answer text matches the visible page content exactly.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [{
    "@type": "Question",
    "name": "Your first question?",
    "acceptedAnswer": { "@type": "Answer", "text": "The authoritative answer." }
  }]
}
</script>

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": "企业网站建设_电商网站制作_外贸网站制作_网站维护 | 锐基科技 - 企业数字基础设施服务商" },
  "datePublished": "2026-01-01",
  "dateModified": "2026-01-01"
}
</script>

No Breadcrumb schema.

No Breadcrumb schema was detected. AI cannot infer the site hierarchy and breadcrumb relationships as easily, which affects internal-link context.

1. Add the BreadcrumbList JSON-LD below to relevant pages.
2. Increment position from 1 and use real, accessible URLs for each item.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [{
    "@type": "ListItem", "position": 1,
    "name": "Home", "item": "https://30t.cn/"
  },{
    "@type": "ListItem", "position": 2,
    "name": "Products", "item": "https://30t.cn/products"
  }]
}
</script>

Entity fields covered: 3/11.

Brand entity coverage is insufficient. AI cannot build a complete entity profile (description, contact details, industry, sameAs social links, etc.), lowering the chance of accurate citations.

1. Extend your Organization / WebSite schema with description, telephone, email, address, industry, founder and foundingDate.
2. Link official social profiles, Wikipedia or other authoritative pages via sameAs.
3. Keep the brand name and logo consistent across all pages.

Homepage content depth: 3/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.

Product page reachable.

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.

Blog / Case page reachable.

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

Moderate content depth.

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

Blog / case / news section reachable.

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.

No OpenAPI descriptor detected.

No OpenAPI / Swagger descriptor was detected. AI agents cannot auto-discover or invoke your API, which means you miss tool-integration opportunities.

1. Serve the OpenAPI 3.0 manifest below at /openapi.json.
2. Fill in your real paths, component schemas and authentication method.
3. Link to the descriptor from your homepage or developer docs.

{
  "openapi": "3.0.3",
  "info": {
    "title": "企业网站建设_电商网站制作_外贸网站制作_网站维护 | 锐基科技 - 企业数字基础设施服务商 API",
    "version": "1.0.0",
    "description": "Machine-readable API for 企业网站建设_电商网站制作_外贸网站制作_网站维护 | 锐基科技 - 企业数字基础设施服务商"
  },
  "servers": [{ "url": "https://30t.cn/api" }],
  "paths": {
    "/health": {
      "get": {
        "summary": "Service health",
        "responses": { "200": { "description": "OK" } }
      }
    }
  }
}

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": "企业网站建设_电商网站制作_外贸网站制作_网站维护 | 锐基科技 - 企业数字基础设施服务商", "version": "1.0.0" },
  "capabilities": { "tools": {} },
  "endpoints": { "base": "https://30t.cn/mcp" }
}

No AI Actions manifest detected.

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

No API documentation link found.

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

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.