visibility

capability

zhimao.cc

✓ verified

AI Visibility: ✓ check completed — level L1

AI Capability: ✓ check completed — level L1

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 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 0/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 2/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 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 zhimao.cc has a foundational technical setup that allows AI crawlers to access its basic content, but it lacks the structured data and discoverability features needed for AI systems to effectively understand, recommend, or interact with it. Its primary strengths are a crawlable, fast-loading site with clear contact information, but it fails to implement most modern AI optimization and integration standards. The site is missing significant opportunities to be found and utilized by AI agents and recommendation engines.

AI Visibility — L1

AI crawlers can find and read the site's basic content, but the site lacks the structured metadata, clear site architecture, and trust signals that AI systems use to confidently understand and recommend content. Without features like sitemaps, schema markup, and clear content attribution, the site is unlikely to be surfaced as a high-quality source by AI assistants like ChatGPT or Perplexity.

AI Capability — L1

The site is readable by AI agents but offers no programmatic interfaces for them to use. There is no public API, no structured data for automation, and no documented methods for agents to perform actions or retrieve data systematically. This makes the site a passive information source rather than an active service an AI agent could integrate with or automate.

A score of 1/5 in both categories indicates the site is merely accessible to AI, not optimized for it. Practically, this means the site is missing out on being recommended by AI search tools and cannot be used by AI agents for tasks like data retrieval, booking, or customer service automation.

Top Issues

CRITICAL Pages Lack Meaningful Text Content visibility · L2 · content

Why: AI systems and search engines need substantial, relevant text to understand the page's topic and value. Pages with only boilerplate or minimal text are often ignored.

Impact: AI assistants will not recommend or summarize your site's content, drastically reducing referral traffic and brand visibility in AI-generated answers.

Fix: Audit key pages (homepage, product/service pages, blog). For each, ensure there is at least 300-500 words of unique, descriptive text that clearly explains your offerings, value proposition, and key information.

CRITICAL Missing Basic Structured Data capability · L1 · developer

Why: JSON-LD structured data is the primary way to explicitly tell AI systems about the entities on your page (e.g., your company, products, articles). Without it, AI must guess, often incorrectly.

Impact: AI cannot reliably extract key facts about your business, products, or content, making it invisible for rich results and structured answers. This is a foundational failure for AI readiness.

Fix: Add a JSON-LD script block to the <head> of your homepage. Start with a basic 'Organization' schema (name, url, logo) and a 'WebSite' schema. Extend to other page types (e.g., 'Article' for blog posts).

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

Why: Schema.org markup provides a clear, structured signal about page content, helping AI disambiguate topics and understand context beyond plain text.

Impact: Reduces the accuracy with which AI systems categorize and recommend your content, leading to missed opportunities in AI search and chat responses.

Fix: Implement JSON-LD structured data on all key content pages. Use types relevant to the content (e.g., 'Article' for blog posts, 'SoftwareApplication' for a product page). Use Google's Structured Data Testing Tool to validate.

HIGH No XML Sitemap for Discovery visibility · L3 · developer

Why: An XML sitemap is a roadmap of your site's important pages. AI crawlers and search engines use it to efficiently discover and index content they might otherwise miss.

Impact: New or deep-linked pages may never be found by AI systems, limiting the scope of content they can access and recommend from your site.

Fix: Generate an XML sitemap (e.g., using a CMS plugin or a sitemap generator tool). Place it at the standard location (e.g., /sitemap.xml). Ensure it's referenced in your robots.txt file and submit it to search consoles.

HIGH Missing Programmatic Sitemap for Agents capability · L2 · developer

Why: For AI agents and automated systems, a sitemap is a critical API-like endpoint that programmatically lists available resources, enabling efficient site exploration.

Impact: AI agents cannot systematically discover your site's structure or content, preventing them from performing comprehensive analysis or data retrieval tasks.

Fix: Create and publish a valid XML sitemap at /sitemap.xml. Ensure it follows the sitemaps.org protocol, lists all important URLs, and is accessible without authentication. Update it automatically when content changes.

Quick Wins

⚡

Missing Open Graph Tags — Add basic Open Graph meta tags to the <head> of every page: og:title, og:description, og:image, og:url, and og:type. Use your primary page title and a compelling summary. (developer)

⚡

Missing Canonical URL Tags — Add a <link rel="canonical" href="[full-page-url]" /> tag to the <head> of every page. For the homepage, it should point to the clean base URL (e.g., https://zhimao.cc/). (developer)

⚡

HTML Language Not Declared — Add the 'lang' attribute to your site's opening <html> tag. Set it to the correct language and region code (e.g., 'zh-CN' for Simplified Chinese used in mainland China). (developer)

⚡

Missing Organization Schema for Trust — Add a JSON-LD block for 'Organization' to your homepage. Include required properties: '@type': 'Organization', 'name', 'url', and 'logo'. Optionally add 'sameAs' links to social profiles. (developer)

30-Day Roadmap

Week 1: Quick Wins

— Add a JSON-LD 'Organization' schema block to the homepage <head> (name, url, logo).

— Add basic Open Graph meta tags (og:title, og:description, og:image, og:url, og:type) to the <head> of every page.

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

— Add the 'lang' attribute (e.g., 'zh-CN') to the site's opening <html> tag.

Capability L1 → L2, Visibility L1 → L2

Week 2: Foundation

— Generate and publish a valid XML sitemap at /sitemap.xml, following the sitemaps.org protocol.

— Reference the sitemap in robots.txt and submit it to search consoles.

— Audit key pages (homepage, product/service pages, blog) and add at least 300-500 words of unique, descriptive text to each.

Visibility L2 → L3, Capability L2 → L3

Weeks 3-4: Advanced

— Extend structured data: add a 'WebSite' schema to the homepage and implement relevant types (e.g., 'Article', 'SoftwareApplication') on all key content pages using JSON-LD.

— Validate all structured data implementations using Google's Structured Data Testing Tool.

— Ensure the XML sitemap is updated automatically when content changes.

Visibility L3 → L4, Capability L3 → L4

By addressing foundational visibility and capability issues, the site can realistically achieve AI Visibility Level 3 and AI Capability Level 3 within 30 days.