ivision-china.cn
✓ verified
Checked on 2026-11-02 Checked 6 of up to 6 pages standard 2.0
Site type: Not sure
Content access
Can AI read it?
Issues: 13 · could not verify: 0 · passed: 12 · not applicable: 3
1 × Blocks AI
Content discovery
Can AI find it?
Issues: 2 · could not verify: 0 · passed: 4 · not applicable: 3
Task use
Can AI act on it?
Issues: 3 · could not verify: 14 · passed: 1 · not applicable: 2
Issues to fix18
Blocks AI There is very little readable text in the HTML. Content access
- Where
- /index.php
- Impact
- AI crawlers and assistants may be unable to read or trust this content.
- Evidence
- only 23 word-equivalents of main content in the HTML (need 40)
- How to fix
- Put the page's main text in the HTML the server sends, not only in images or script-built elements.
ssr_content / v_ssr_readable
Improvement No JSON-LD or microdata found. Content access
- Where
- /index.php, /vaioproduction.html, /categorylist.html
- Impact
- AI crawlers and assistants may be unable to read or trust this content.
- Evidence
- no JSON-LD or microdata found
- How to fix
- Add JSON-LD (`<script type="application/ld+json">`) describing the page, such as WebSite, Organization or Article.
schema_org / v_schema_org
Improvement There is very little readable text in the HTML. Content access
- Where
- /index.php
- Impact
- AI crawlers and assistants may be unable to read or trust this content.
- Evidence
- only 23 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
- /index.php
- Impact
- AI crawlers and assistants may be unable to read or trust this content.
- Evidence
- only 23 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 XML sitemap at the conventional locations or in robots.txt. Content discovery
- Where
- the whole site
- Impact
- Pages may be missed, indexed under the wrong address, or never surface in AI answers.
- Evidence
- no sitemap at the conventional locations or in robots.txt
- How to fix
- Publish an XML sitemap (for example /sitemap.xml) and reference it from robots.txt with a `Sitemap:` line.
sitemap / v_xml_sitemap
Improvement No canonical URL declared. Content discovery
- Where
- all 6 pages checked
- 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 Uses semantic HTML elements such as header, nav, main, article, section, and footer so agents can better understand page structure. 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
- only 1 semantic elements found (need 3): article
- How to fix
- Use semantic elements such as header, nav, main, article, section and footer instead of generic divs.
semantic_html
Best practice Article without author attribution. Content access
- Where
- /financial/fin-institution.html, /itconsulting/supportconsulting.html, /company.html
- Impact
- A best practice, not a barrier: AI can still read the site, but this helps it understand and cite it more accurately.
- Evidence
- article without author attribution
- How to fix
- Show the author on articles and mark it up with `author` in the Article data.
v_author_attribution
Best practice Inner page without BreadcrumbList markup. Content access
- Where
- /financial/fin-institution.html, /itconsulting/supportconsulting.html
- 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 BreadcrumbList markup on an inner page
- How to fix
- Add BreadcrumbList JSON-LD matching the page's breadcrumb trail.
v_breadcrumb_schema
Best practice The page has a clear H1 and uses H2/H3 headings to organize content logically. Content access
- Where
- /index.php, /categorylist.html
- 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, 4 H2, 0 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
- /index.php, /vaioproduction.html, /itconsulting/supportconsulting.html and 1 more
- 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 (37 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 Open Graph tags provide supplementary title and summary information. 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
- missing: og:title, og:description
- How to fix
- Add `og:title` and `og:description` meta tags.
v_og_tags
Best practice No Organization structured data. 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 Organization/LocalBusiness structured data
- How to fix
- Add Organization JSON-LD with at least name and url (and a logo) to the home page.
v_org_schema
Best practice Article without publish or update dates. Content access
- Where
- /financial/fin-institution.html, /itconsulting/supportconsulting.html, /company.html
- Impact
- A best practice, not a barrier: AI can still read the site, but this helps it understand and cite it more accurately.
- Evidence
- article without publish or update dates
- How to fix
- Show publish and update dates on articles (a `<time datetime>` element) and add `datePublished` / `dateModified`.
v_publish_dates
Best practice Pages contain FAQs, tables, lists, definitions, etc., making it easy for AI to extract and summarize. Content access
- Where
- /index.php, /vaioproduction.html, /financial/fin-institution.html and 2 more
- 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
Best practice An API was found, but it publishes no machine-readable authentication (OAuth metadata or a declared security scheme). Task use
- 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
- an API was found but it publishes no machine-readable authentication (OAuth metadata or a declared security scheme)
- How to fix
- Publish OAuth metadata (`/.well-known/oauth-protected-resource`, `/.well-known/oauth-authorization-server`) or declare `securitySchemes` in your OpenAPI document.
agent_auth
Best practice An API was found, but neither its responses nor its description expose rate limits. Task use
- 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
- an API was found, but neither its responses nor its description expose rate limits
- How to fix
- Return `RateLimit-*` (or `X-RateLimit-*`) headers and `429` with `Retry-After`, and document them.
rate_limits_documented
Best practice A missing API resource returns an HTML page instead of a machine-readable error. Task use
- 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
- a missing API resource returns an HTML page (404) instead of a machine-readable error
- How to fix
- Return JSON errors (for example RFC 9457 problem details) from API paths instead of HTML pages.
structured_errors
Suggestions1
These checks passed. The notes below would make them stronger.
-
Provides a robots.txt file that permits access for legitimate crawlers and agent systems where appropriate.
No robots.txt: nothing restricts crawlers. Publishing one lets you state an AI policy.
Could not be verified (14)
These are not counted as problems: the scanner could not complete them.
Not discovered 13
Nothing was found at the standard locations or in the page's links. That does not prove it is absent.
- documentation Provides comprehensive documentation in a format that is easy for machines and agents to parse and use. 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
- 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
- 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.
- json_responses Returns JSON payloads with stable and predictable schemas across endpoints. the whole site — The sampled API request answered HTTP 404.
Checked 6 of up to 6 pages
- Home https://www.ivision-china.cn/index.php
- Product https://www.ivision-china.cn/vaioproduction.html
- Docs https://www.ivision-china.cn/financial/fin-institution.html
- Help https://www.ivision-china.cn/itconsulting/supportconsulting.html
- Contact / about https://www.ivision-china.cn/company.html
- Other https://www.ivision-china.cn/categorylist.html
AI Readiness Report
Executive Summary
本次审计覆盖 ivision-china.cn 的 6 个页面(样本,非全站)。站点基础条件良好:HTTPS 有效、robots.txt 未屏蔽主流 AI 爬虫、响应速度快、无登录墙,但页面内容在 HTML 中过于单薄(仅约 23 个词当量),且缺少结构化数据、站点地图、标题层级与发布/作者信息,导致 AI 难以理解与引用。AI 可见性为 1/5,AI 能力为 0/5,核心短板集中在内容可读性与机器可解析性。
AI Visibility
AI 爬虫可以正常抓取本站,但页面正文在初始 HTML 中几乎为空,meta description 过短、缺少 H1、Schema.org/JSON-LD、Open Graph 与 canonical,也没有 XML 站点地图,AI 很难准确判断页面主题并推荐。信任层面缺少组织信息、作者署名与发布/更新时间,进一步削弱被引用的可能性。内容访问维度有 13 项问题、内容发现维度 2 项问题,均无未能验证项。
AI Capability
站点虽暴露了 API,但缺少 OpenAPI 描述、机器可读的认证方式、限流说明与结构化错误响应,错误请求返回 HTML 页面而非 JSON,AI 代理难以稳定调用。语义化 HTML 元素不足、正文文本量过少,也影响代理理解页面结构。任务使用维度有 3 项问题,另有 14 项无法验证(如 MCP、WebMCP、写操作、Webhook、事件流等),因此代理互操作能力整体无法确认。
等级按“仅 PASS 计分”的规则计算,因此低分部分反映的是缺失与未验证的检查项,而非全部确认为故障。可见性维度 0 项未能验证,结论较为确定;能力维度有 14 项未能验证,占比较大,实际代理支持能力可能高于当前评分,需补充 API 文档与描述后再评估。
Top Issues
Why it matters: AI 爬虫与检索代理大多只读取服务器返回的原始 HTML,不执行或只有限执行 JavaScript。首页 HTML 中仅有 23 个词当量的主内容(标准要求 40 以上),意味着 AI 抓取到的几乎是一个空壳页面,无法判断网站主题与业务。
Business impact: 这是阻断性问题:ChatGPT、Perplexity、Gemini、Claude 等系统在抓取首页时拿不到有效内容,网站几乎不可能被收录、引用或推荐,直接损失来自 AI 搜索的潜在客户与询盘。
How to fix: 1) 改为服务端渲染(SSR)或静态生成(SSG),确保首页核心文案(公司定位、服务介绍、客户价值)直接出现在返回的 HTML 中;2) 若使用前端框架,启用 SSR/预渲染(如 Next.js、Nuxt 的 SSR 模式或 prerender 中间件);3) 避免用纯图片或 JS 注入方式承载首屏文字;4) 上线后用 curl 抓取 https://www.ivision-china.cn/index.php 检查源码中是否包含完整正文。
Why it matters: AI 需要足够的文本才能理解页面主题、判断专业度并生成摘要或引用。内容过少的页面难以被判定为有价值的信息源。
Business impact: 即使页面被抓取,AI 也难以提炼出可引用的答案,品牌在 AI 回答中出现的概率大幅降低,影响获客与品牌曝光。
How to fix: 1) 在首页补充 300–800 字的实质性文案:公司简介、核心服务(VAIO 生产、IT 咨询、金融行业解决方案等)、服务流程、典型客户场景;2) 使用小标题分段,便于 AI 抽取;3) 内容需真实反映业务,避免堆砌关键词;4) 与 SSR 改造同步进行,确保文本出现在 HTML 源码中。
Why it matters: AI 代理只能处理可解析的文本。若关键信息锁在图片、视频或不可解析的 PDF 中,代理无法读取、理解或执行后续任务。
Business impact: AI 无法基于网站内容完成问答、比较或推荐,网站的“可被 AI 使用”能力接近于零,客户在 AI 渠道的转化路径被切断。
How to fix: 1) 将图片中的文字(如宣传图、产品图上的说明)以真实 HTML 文本形式补充到页面;2) 为图片添加有意义的 alt 文本;3) 重要资料(产品手册、案例)同时提供 HTML 版本或可解析的文本版 PDF;4) 目标是把首页可解析文本提升到 60 个词当量以上,并逐步覆盖各内页。
Why it matters: JSON-LD 用机器可读的方式告诉 AI 页面是什么(公司、服务、文章等)及其关键字段,显著提升内容理解的准确性。当前扫描未发现任何 JSON-LD 或 microdata。
Business impact: AI 只能靠猜测理解页面,实体识别与引用准确度下降,品牌在 AI 答案中出现的结构化依据缺失。
How to fix: 1) 在首页加入 WebSite 与 Organization 类型的 JSON-LD(name、url、logo);2) 服务页(如 vaioproduction.html)加入 Service 类型,包含 name、description、provider;3) 内容页加入 Article 类型;4) 使用 <script type="application/ld+json"> 嵌入,并用 Google Rich Results Test 校验。
Why it matters: canonical 标签告诉搜索引擎与 AI 哪个 URL 是权威版本,避免 index.php、带参数 URL、www/非 www 等重复版本分散权重。
Business impact: 重复 URL 会导致 AI 与搜索引擎抓取分散、内容重复判定,降低页面被正确收录与引用的概率。
How to fix: 1) 在每个页面的 <head> 中添加 <link rel="canonical" href="绝对URL">,指向该页面的规范地址;2) 统一 www 与非 www、index.php 与根路径的跳转规则;3) 在服务器层配置 301 重定向到规范版本;4) 覆盖扫描列出的全部页面(首页、vaioproduction.html、financial/fin-institution.html、itconsulting/supportconsulting.html、company.html 等)。
Quick Wins
Could not be verified
These checks could not be completed (a timeout, an access limit, a login, or a method the scanner does not have). They are not counted as problems.
30-Day Roadmap
第 1 周:快速见效项
— 为扫描列出的全部页面(首页、vaioproduction.html、financial/fin-institution.html、itconsulting/supportconsulting.html、company.html、categorylist.html)在 <head> 中添加 <link rel="canonical" href="绝对URL">,并在服务器层配置 www/非 www、index.php/根路径的 301 重定向到规范版本
— 为首页、vaioproduction.html、itconsulting/supportconsulting.html、categorylist.html 等页面撰写 50–160 字符且每页唯一的 meta description,说明业务与价值,并同步检查 <title> 是否清晰包含品牌与业务关键词
— 在所有页面 <head> 添加 og:title、og:description,并补充 og:url、og:type、og:image,内容与 meta title/description 保持一致,覆盖扫描列出的 6 个页面
— 为首页与 categorylist.html 添加唯一且描述性的 H1,按逻辑层级使用 H2/H3 组织内容、不跳级,并检查现有 4 个 H2 是否覆盖主要板块
— 生成 /sitemap.xml 列出所有重要页面及 lastmod,在 robots.txt 中添加 Sitemap: https://www.ivision-china.cn/sitemap.xml,并提交到 Google Search Console 与 Bing Webmaster Tools
Visibility L1 稳定,基础可发现性项全部达标,为后续内容与结构化改造打好基础
第 2 周:基础改造
— 将首页改为服务端渲染(SSR)或静态生成(SSG),确保公司定位、服务介绍、客户价值等核心文案直接出现在返回的 HTML 中;若使用前端框架,启用 SSR/预渲染(如 Next.js、Nuxt 的 SSR 模式或 prerender 中间件)
— 避免用纯图片或 JS 注入方式承载首屏文字,上线后用 curl 抓取 https://www.ivision-china.cn/index.php 检查源码中是否包含完整正文
— 与 SSR 改造同步,在首页补充 300–800 字实质性文案(公司简介、核心服务如 VAIO 生产、IT 咨询、金融行业解决方案、服务流程、典型客户场景),使用小标题分段便于 AI 抽取,内容真实反映业务、避免堆砌关键词
— 将宣传图、产品图上的说明文字以真实 HTML 文本形式补充到页面,为图片添加有意义的 alt 文本,重要资料(产品手册、案例)同时提供 HTML 版本或可解析的文本版 PDF
Visibility L1 → L2;Capability L0 → L1(首页可解析文本达到 60 个词当量以上并逐步覆盖内页)
第 3–4 周:结构化数据与验证
— 在首页加入 WebSite 与 Organization 类型的 JSON-LD(name、url、logo),使用 <script type="application/ld+json"> 嵌入
— 为服务页(如 vaioproduction.html)加入 Service 类型 JSON-LD,包含 name、description、provider;内容页加入 Article 类型
— 用 Google Rich Results Test 校验全部 JSON-LD,修复报错并确认可被解析
— 复查 canonical、meta description、Open Graph、H1 层级与 sitemap 在 SSR 改造后仍然正确,并用 curl 与 Search Console 验证首页正文已进入 HTML 源码
Visibility L2 巩固并具备向 L3 过渡的条件;Capability L1 稳定
30 天内可现实地达到 Visibility 2/5、Capability 1/5:首页正文进入 HTML 源码、结构化数据与基础可发现性项全部落地。进一步提升需持续扩充内页文本与结构化覆盖,不宜承诺 L4/L5。