changfangzl.com

✓ verified

Checked on 2026-10-10 Checked 6 of up to 6 pages standard 2.0

Site type: Not sure

Content access

Can AI read it?

Issues found

Issues: 8 · could not verify: 0 · passed: 16 · not applicable: 4

Content discovery

Can AI find it?

Issues found

Issues: 1 · could not verify: 0 · passed: 6 · not applicable: 2

Task use

Can AI act on it?

Could not verify

Issues: 0 · could not verify: 18 · passed: 0 · not applicable: 2

Issues to fix9

Improvement There is very little readable text in the HTML. Content access
Where
/demand
Impact
AI crawlers and assistants may be unable to read or trust this content.
Evidence
only 51 word-equivalents of text in the HTML (need 60)
How to fix
Put the page's main text in the HTML the server sends, not only in images or script-built elements.

text_content

Improvement There is very little readable text in the HTML. Content access
Where
/agent-login, /demand, /favorites
Impact
AI crawlers and assistants may be unable to read or trust this content.
Evidence
only 64 word-equivalents of page text in the HTML (need 120)
How to fix
Put the page's main text in the HTML the server sends, not only in images or script-built elements.

v_content_length

Improvement No canonical URL declared. Content discovery
Where
/agent-login, /demand, /favorites
Impact
Pages may be missed, indexed under the wrong address, or never surface in AI answers.
Evidence
no canonical URL declared (no <link rel="canonical"> or Link header)
How to fix
Add `<link rel="canonical" href="…">` pointing to this page's preferred address.

v_canonical_url

Best practice No contact or about page found. Content access
Where
the whole site
Impact
A best practice, not a barrier: AI can still read the site, but this helps it understand and cite it more accurately.
Evidence
no contact or about page found from the page's links or the conventional paths
How to fix
Add a contact or about page and link it from the navigation or footer.

v_contact_visible

Best practice The page has FAQ-style content but no FAQPage markup. Content access
Where
/qushi/taicang/changfang
Impact
A best practice, not a barrier: AI can still read the site, but this helps it understand and cite it more accurately.
Evidence
the page has FAQ-style content (2 question headings) but no FAQPage markup
How to fix
Mark up the questions and answers with FAQPage JSON-LD that matches the visible text.

v_faq_schema

Best practice The page has a clear H1 and uses H2/H3 headings to organize content logically. Content access
Where
/favorites
Impact
A best practice, not a barrier: AI can still read the site, but this helps it understand and cite it more accurately.
Evidence
no H1 found (0 H1, 1 H2, 2 H3)
How to fix
Use one H1 for the page topic and H2/H3 headings to organise the content.

v_heading_structure

Best practice The page has a clear title and meta description, helping AI quickly identify the topic. Content access
Where
/agent-login, /demand, /favorites
Impact
A best practice, not a barrier: AI can still read the site, but this helps it understand and cite it more accurately.
Evidence
description too short (29 chars, need 50+)
How to fix
Write a clear `<title>` and a meta description of 50+ characters that says what the page is about.

v_meta_title_desc

Best practice No privacy policy or terms of service found. Content access
Where
the whole site
Impact
A best practice, not a barrier: AI can still read the site, but this helps it understand and cite it more accurately.
Evidence
no privacy policy or terms of service found
How to fix
Publish a privacy policy and terms of service and link them in the footer.

v_privacy_terms

Best practice Pages contain FAQs, tables, lists, definitions, etc., making it easy for AI to extract and summarize. Content access
Where
all 6 pages checked
Impact
A best practice, not a barrier: AI can still read the site, but this helps it understand and cite it more accurately.
Evidence
0 structured block type(s) found (need 2+): none
How to fix
Use lists, tables with headers, definition lists or Q&A blocks so key facts are easy to extract.

v_structured_content_blocks

Could not be verified (18)

These are not counted as problems: the scanner could not complete them.

Not discovered 17

Nothing was found at the standard locations or in the page's links. That does not prove it is absent.

  • json_responses Returns JSON payloads with stable and predictable schemas across endpoints. the whole site
  • mcp_server Provides an MCP (Model Context Protocol) server so agents can access tools, resources, and actions through a standardized interface. the whole site
  • openapi_spec Publishes an OpenAPI or Swagger specification so agents can understand available API endpoints programmatically. the whole site
  • search_filter_api Supports query parameters for search, filtering, pagination, and retrieval refinement. the whole site
  • structured_api Exposes a well-defined REST or GraphQL API for programmatic access to data and actions. the whole site
  • agent_auth Supports automation-ready authentication methods such as API keys or OAuth client credentials flows. the whole site
  • cross_service_handoff Supports handoff between agents or services so tasks can continue across system boundaries. the whole site
  • event_streaming Supports real-time update channels such as SSE or WebSockets for low-latency agent workflows. the whole site
  • idempotency Write operations support idempotency keys or equivalent safeguards to prevent duplicate execution. the whole site
  • proactive_notifications Can proactively notify agents when relevant content, state, or business events change. the whole site
  • rate_limits_documented Clearly documents rate limits and returns proper 429 Too Many Requests responses when limits are exceeded. the whole site
  • structured_errors Returns machine-readable error responses with clear codes, messages, and actionable context. the whole site
  • subscription_api Provides APIs for subscription, lifecycle management, or registration of agent integrations. the whole site
  • webhooks Supports webhooks so agents can receive event-driven updates instead of relying only on polling. the whole site
  • webmcp Supports WebMCP or comparable browser-oriented agent interaction patterns for web-based automation. the whole site — No WebMCP tool registration was found in the page or its same-site scripts. Tools registered at runtime or in other scripts can only be seen by running the page.
  • workflow_orchestration Supports multi-step workflows, task coordination, and stateful execution across actions or services. the whole site
  • write_api Supports write operations such as POST, PUT, PATCH, and DELETE, enabling agents to create and update resources. the whole site
Request failed 1

A timeout, connection problem or HTTP error got in the way. Re-checking often resolves these.

  • documentation Provides comprehensive documentation in a format that is easy for machines and agents to parse and use. the whole site — no documentation page found from the page's links or the conventional paths (could not fetch: http_403) (/docs)

How are checks judged?