is-agentic Scored Promptway 74. Here Is What I Changed

查看原文 / View Original 编辑 / Edit

is-agentic Scored Promptway 74. Here Is What I Changed

I ran npx is-agentic promptway.com and the report came back 74 out of 100. Essential was 59 of 80. Recommended 12.6 of 20. A 2.4-point bonus. The label was “Ready with a few material gaps.” Earlier this week I did the same work on my personal site and wrote it up there (I fixed my site for agents by hand. Then Vercel shipped a scoreboard). Promptway is the publication I want agents to cite, so I pointed the grader at this host next.

我运行了 npx is-agentic promptway.com，报告显示得分为 74/100。其中基础项（Essential）为 59/80，推荐项（Recommended）为 12.6/20，外加 2.4 分的奖励分。评级标签为“已准备就绪，但存在少量实质性缺失”。本周早些时候，我在个人网站上做了同样的工作并记录了下来（我手动修复了网站以适配 AI Agent，随后 Vercel 发布了计分板）。Promptway 是我希望 Agent 引用的刊物，所以我接下来将评分工具指向了这个主机。

We already shipped the eight-layer stack I described in Optimizing Your Site for AI Agents and LLMs: robots allowlist, sitemap, llms.txt, llms-full.txt, JSON-LD, feeds, article markdown siblings. The scoreboard still found holes. Most of them were ordinary web hygiene. A couple were “developer resources” checks that assume you are a SaaS. I fixed the first group and refused to fake the second.

我们已经部署了我在《为 AI Agent 和 LLM 优化你的网站》一文中描述的八层技术栈：robots 允许列表、sitemap、llms.txt、llms-full.txt、JSON-LD、订阅源（feeds）以及文章的 Markdown 对应版本。但计分板仍然发现了漏洞。其中大多数是常规的网页规范问题，有几个则是假设你是 SaaS 产品的“开发者资源”检查。我修复了前者，并拒绝为了分数而伪造后者。

What 74 was made of

74 分的构成

is-agentic.com wraps Ora’s agent-readiness research. Essential checks share 80 points, recommended share 20, and a small bonus can add up to 5. Checks that do not apply get excluded. The methodology page is worth reading before you argue with a number. Reports cache for six hours, so a re-scan right after a deploy can lie to you. The CLI is the useful interface: npx is-agentic promptway.com or npx is-agentic promptway.com --json. It returns a stored report if one exists, or starts a scan and waits. --json is the shape an agent wants.

is-agentic.com 封装了 Ora 的 Agent 就绪度研究。基础检查占 80 分，推荐检查占 20 分，另有最多 5 分的奖励分。不适用的检查项会被排除。在质疑分数之前，建议先阅读其方法论页面。报告缓存时间为 6 小时，因此在部署后立即重新扫描可能会得到误导性的结果。CLI 是最实用的接口：npx is-agentic promptway.com 或 npx is-agentic promptway.com --json。它会返回已有的报告（如果存在），或者启动扫描并等待。--json 是 Agent 所需的数据格式。

The failures that mattered on this site, in the order the report ranked them: 本站中值得关注的失败项（按报告排名顺序）：

  • Agent-friendly 404s: HTTP 404 already, but the body was a styled dead end. Partial credit until the 404 points at llms.txt, the sitemap, and a next step. 对 Agent 友好的 404 页面： 虽然已经是 HTTP 404，但页面主体只是一个带样式的死胡同。只有当 404 页面指向 llms.txt、sitemap 和下一步操作时，才能获得部分分数。
  • Content without JavaScript: The homepage had an H1 and enough characters. The outline was flat, because the only nested headings lived inside card links, which the grader did not count. 无需 JavaScript 的内容： 首页有 H1 标签且字符数足够。但大纲结构扁平，因为唯一的嵌套标题都在卡片链接内，而评分工具并未将其计入。
  • Markdown content negotiation: Accept: text/markdown returned text/html. Vary had the Next.js RSC list and no Accept. Failed. Markdown 内容协商： 请求头 Accept: text/markdown 返回了 text/html。Vary 响应头中包含 Next.js RSC 列表但没有 Accept。失败。
  • Developer resource discoverability: An agent searched for “promptway developer resources” and found nothing named that. 开发者资源可发现性： Agent 搜索“promptway developer resources”时，没有找到任何以此命名的内容。
  • Agent instruction / when-to-use: llms.txt listed pages. It did not say when to reach for us, or when not to. Agent 指令 / 使用时机： llms.txt 列出了页面，但没有说明何时应该访问我们，以及何时不应该。
  • Trust pages: About existed. Contact and privacy did not. 信任页面： 有“关于”页面，但缺少“联系方式”和“隐私政策”。
  • Organization JSON-LD: Name and description were there. contactPoint and address were not. 组织 JSON-LD： 有名称和描述，但缺少 contactPoint 和地址。
  • Content efficiency: Readable text was 4.83 percent of the homepage HTML. The bar is 5. 内容效率： 可读文本占首页 HTML 的 4.83%，标准是 5%。

There was also an MCP check. The site mentions MCP because we write about other people’s servers. We do not run one. I did not publish a fake manifest to chase the points. 此外还有一个 MCP 检查。本站提到 MCP 是因为我们撰写关于他人服务器的文章，但我们自己并不运行 MCP 服务器。我没有为了分数而发布虚假的清单文件。

What I changed

我的修改

The 404 now returns a real 404 with a recovery list: llms.txt, Promptway developer resources, sitemap, archive, about, contact. Send Accept: text/markdown and the same miss is a short markdown body instead of HTML. 404 页面现在返回真实的 404 状态码，并附带恢复列表：llms.txt、Promptway 开发者资源、sitemap、归档、关于、联系方式。发送 Accept: text/markdown 请求时，同样的错误页面会返回简短的 Markdown 正文而非 HTML。

Verify with: 验证方式： curl -s -o /dev/null -w "%{http_code}" https://promptway.com/some-path-that-does-not-exist curl -sI -H "Accept: text/markdown" https://promptway.com/some-path-that-does-not-exist

The first must print 404. The second must print content-type: text/markdown and a vary that includes Accept. Markdown negotiation follows acceptmarkdown.com. proxy.ts (Next.js 16’s name for middleware) parses Accept, skips RSC requests, and rewrites markdown-preferring GETs to a catch-all that already knew how to render articles, bots, about, and the new pages. Vary: Accept is set on that response. HTML still comes back for a browser Accept. A client that rejects both HTML and markdown gets 406. 第一个命令必须输出 404。第二个必须输出 content-type: text/markdown 以及包含 Accept 的 Vary 响应头。Markdown 协商遵循 acceptmarkdown.com 的规范。proxy.ts（Next.js 16 中中间件的名称）会解析 Accept，跳过 RSC 请求，并将偏好 Markdown 的 GET 请求重写到已具备渲染文章、机器人、关于页面及新页面能力的通用路由中。响应中设置了 Vary: Accept。浏览器请求仍会返回 HTML。如果客户端同时拒绝 HTML 和 Markdown，则会收到 406 错误。

I did not invent a public product API. Promptway is a magazine. The developer surface is the content stack plus Prompt Inspector, which is a same-origin tool. That now lives at /for-agents under the title “Promptway developer resources,” with OpenAPI at /openapi.json and an RFC 9727 catalog at /.well-known/api-catalog. llms.txt links all three. 我没有凭空捏造一个公共产品 API。Promptway 是一本杂志。其开发者接口是内容栈加上 Prompt Inspector（一个同源工具）。该工具现在位于 /for-agents，标题为“Promptway developer resources”，OpenAPI 位于 /openapi.json，RFC 9727 目录位于 /.well-known/api-catalog。llms.txt 链接了这三者。

llms.txt also gained a “When to use Promptway” section. The jobs we are right for are AEO guidance from this live Next.js site, a prompt structure with a copy-paste example, a founder interview with a number, a tool writeup that names the skip list, and a sourced news filter. We are the wrong fetch if you need a model API, an MCP server, OAuth, webhooks, or unlabeled AI copy. llms.txt 还增加了一个“何时使用 Promptway”部分。我们适合的任务包括：基于此 Next.js 站点的 AEO 指导、带有复制粘贴示例的提示词结构、带有数据的创始人访谈、列出跳过列表的工具评测，以及来源明确的新闻筛选。如果你需要模型 API、MCP 服务器、OAuth、Webhook 或未经标注的 AI 生成内容，我们不是合适的抓取对象。

/contact and /privacy are real pages, each well over 500 characters. The inbox is agnel@promptway.com. The address in JSON-LD is San Juan, PR. Organization schema now has url, sameAs, logo, email, address, and contactPoint. /contact 和 /privacy 现在是真实的页面，每个都超过 500 字符。收件箱是 agnel@promptway.com。JSON-LD 中的地址是波多黎各圣胡安。组织 Schema 现在包含 url、sameAs、logo、email、address 和 contactPoint。

The homepage grew a “How to read this site” band with an H2 and two H3s that are not inside links, plus enough server-rendered prose that a no-JS crawler sees a nested outline and more than a dek. 首页增加了一个“如何阅读本站”区域，包含一个 H2 和两个不在链接内的 H3 标签，以及足够多的服务端渲染文本，确保无 JS 的爬虫能看到嵌套的大纲和超过一段的导语。

What I did not change

我没有修改的部分

I did not stand up an MCP server. The recommended check is fair for a product with tools. For a publication it would be a toy endpoint whose only job is the score. If we ever ship one, it will have a job besides the grader. 我没有搭建 MCP 服务器。对于有工具的产品来说，这项推荐检查是合理的；但对于刊物来说，它只是一个为了刷分而存在的玩具接口。如果我们未来发布 MCP，它将会有除了应付评分之外的实际用途。

I did not strip the magazine layout to win content-efficiency on markup ratio. The cards, the footer, the fonts, and the JSON-LD are the site. I added copy instead of deleting chrome. Locally that moved the homepage text ratio from 4.83 percent to about 5. If the production crawler still calls it partial, I will live with it. 我没有为了提高标记比率（markup ratio）的内容效率而删减杂志布局。卡片、页脚、字体和 JSON-LD 构成了网站本身。我选择增加文案而不是删除界面元素。在本地测试中，首页文本比率从 4.83% 提升到了约 5%。如果生产环境的爬虫仍然判定为部分达标，我也能接受。

I did not 406 ordinary browsers. Chrome sends text/html,application/xhtml+xml,... and still gets HTML. 我没有对普通浏览器返回 406。Chrome 发送 text/html,application/xhtml+xml,... 时依然会获得 HTML。

The prompt I would hand an agent

我会交给 Agent 的提示词

Copy this, put your domain in, and run it in whatever coding agent you use. It is the is-agentic fix-it prompt, rewritten for a site that might be a publication rather than a SaaS. 复制这段内容，填入你的域名，并在你使用的任何编码 Agent 中运行。这是 is-agentic 的修复提示词，我针对可能属于刊物而非 SaaS 的网站进行了重写。

# Audit and fix this site for agents
Use npx is-agentic to audit this site and fix any issues that arise. 
Inspect the existing codebase before changing files. 
Follow each published protocol exactly. 
Preserve visual design and product behavior. 
Add or update tests for every behavior you change. 
Verify every public endpoint after implementation. 

Site: YOUR_DOMAIN_HERE

1. Run the audit
   - `npx is-agentic YOUR_DOMAIN_HERE`
   - `npx is-agentic YOUR_DOMAIN_HERE --json` if you need machine-readable output.
2. Prioritize fixes based on the report.
3. Implement missing files (llms.txt, etc.) and fix content negotiation.
4. Ensure JSON-LD and semantic HTML are correct.
← 返回新闻列表 / Back to news list