內容簡介
StudioMeyer Agent Readiness 外掛幫助網站擁有者檢查其網站對 AI 代理的可讀性，並發布缺失的機器可讀文件。透過 HTTP 請求，該外掛提供準確的報告，確保網站內容正確交付給 AI 代理。
【主要功能】
• 檢查網站對 AI 代理的可讀性
• 發布內容為 Markdown 格式
• 提供 Agent-Skills 文件
• 生成 API 目錄和 HTTP-Link-Header
• 本地運行，無需外部帳戶或 API 金鑰
外掛標籤
開發者團隊
原文外掛簡介
Auf Deutsch: StudioMeyer Agent Readiness prüft, was KI-Agenten von Ihrer Website tatsächlich bekommen — und veröffentlicht die maschinenlesbaren Dateien, die noch fehlen. Der Bericht fragt Ihre eigene Seite über HTTP ab, so wie ein Agent es täte, statt nur die eigenen Einstellungen abzulesen. Damit sehen Sie auch, wenn ein Cache oder eine Server-Einstellung etwas anderes ausliefert, als das Plugin glaubt. Vier Dinge kann das Plugin selbst veröffentlichen: Ihre Inhalte als Markdown (auf Accept: text/markdown oder mit angehängtem .md), ein Agent-Skills-Dokument, einen API-Katalog nach RFC 9727 und HTTP-Link-Header nach RFC 8288. Alles läuft lokal auf Ihrem Server — kein Konto, keine API-Schlüssel, kein Fremddienst. Standardmäßig ist alles ausgeschaltet; Sie entscheiden, was veröffentlicht wird. Nur bereits öffentliche Inhalte werden ausgeliefert — Entwürfe und private Seiten nie, und eine passwortgeschützte Seite verlangt ihr Passwort genau wie im Browser.
AI agents read websites differently than people do. This plugin tells you how yours looks to them, and fixes the part a plugin can fix.
This is an independent plugin by StudioMeyer. It is not affiliated with, endorsed by or connected to any company that publishes an agent-readiness checker or scoring service.
The report
One button runs the checks. Each one asks your own site over HTTP — the same loopback technique WordPress Site Health uses — because what matters is what a client actually receives. A check that only read the plugin’s own settings would show green on a site where a cache, a static file or a server rule serves something else entirely.
For every signal you get one of three honest answers:
In place — a client asking for it receives it
Missing — it is not there, and you are told who can provide it
Not measurable — it cannot be determined from your server, and it is left out of the count rather than quietly scored as a failure
Signals covered include robots.txt and its rules for AI crawlers, XML sitemap, HTTP Link headers, Markdown availability, llms.txt, JSON-LD structured data, Content Signals, Agent Skills, the API catalog, MCP and OAuth discovery, and the WooCommerce commerce manifest. Where something belongs to your server, your CDN, your DNS or the browser, the plugin says so plainly instead of pretending a plugin could fix it.
What this plugin publishes
Four surfaces, each off until you switch it on:
1. Markdown
Every published page becomes available as Markdown. Request its normal URL with Accept: text/markdown, or append .md to the permalink. Agents get your text without navigation, styling or scripts, and without having to guess which part of the page is the content. You choose which post types take part.
2. Agent Skills
A short instruction sheet at /.well-known/agent-skills/index.json telling an agent how to work with this specific site: how to search it, which structured endpoints exist, where the Markdown lives, and the ground rules. You can write the one-line summary yourself or use the generated one.
3. API catalog
/.well-known/api-catalog in the standard format defined by RFC 9727, listing your REST API, sitemap, feed and skills index in one predictable place — so a client does not need to know WordPress conventions to find them.
4. Link headers
An RFC 8288 Link header pointing at your sitemap, feed, API catalog and, on a single post or page, its Markdown twin. Existing Link headers from WordPress or other plugins are preserved, never replaced.
What it deliberately does not do
Being useful here means not overlapping with what you already run:
No llms.txt. Several SEO plugins now generate one. Two plugins writing the same file helps nobody — this one reports whether yours is there.
No robots.txt writing. Your SEO or crawler plugin owns that file. This one reads it and tells you what it says.
No MCP server card. Its location is still being settled in the Model Context Protocol specification, and a card with no MCP server behind it would be a green tick over nothing.
Private by design
Everything runs locally in PHP on your server
No cloud service, no account, no API keys, no third-party service
The checks talk to your own site, and follow a redirect only while it stays there
No personal data is collected or transmitted
Only published, publicly viewable content is ever served — drafts, private and scheduled content stay invisible, and password-protected posts behave exactly as they do in HTML: nothing without the password, the content once it has been entered
All plugin data is removed on uninstall
Who is this for?
Site owners who want to know how their site looks to AI agents, in plain language
Publishers who would rather hand agents clean Markdown than have them scrape rendered HTML
Agencies preparing client sites — one local, no-SaaS tool across every site
More free plugins by StudioMeyer
AI-Ready WP — agents.json, llms.txt, JSON-LD and SEO in one
SmartBot — AI Chatbot — an AI chat widget with a permanently free plan
Agent Discovery for WooCommerce — make your store discoverable by AI shopping agents
Barrierefrei-Check — accessibility scanner and statement generator
Transparency Toolkit for the EU AI Act — Article 50 disclosure and AI content labels
External services
This plugin contacts no third party service of its own. There is no API, no
analytics, no telemetry, no update server, no font or asset CDN. Nothing about
your site, its content or its visitors is sent to StudioMeyer, and the plugin
has no other address to send anything to. It needs no account and no API key.
The readiness check does make HTTP requests, and it addresses every one of them
to your own site at its own home URL, the way a visitor’s browser would. That is
what makes the result worth having: the plugin reads what your server actually
returns rather than what its own settings claim.
Redirects are followed only while they stay on your own site, up to three of
them. Your own site means the same host, the www. variant of it, or a
subdomain such as de.example.com, because a home page sending visitors to one
of those is doing something ordinary. A redirect leading anywhere else is
reported as a finding instead of followed.
Being honest about the limit of that: the check asks WordPress not to follow
redirects and inspects each one itself, but any plugin on your site may change
that request, and WordPress then follows inside its own HTTP library, where
nothing is visible to a plugin. So there is a second check that does not depend
on the first. The address an answer actually arrived from is read back out of
the response, and an answer from anywhere else is discarded instead of being
used as a reading of your site.
If the loopback fails outright, which happens behind some reverse proxies and
inside containers, the plugin retries against 127.0.0.1 carrying your own host
name in the Host header, so your web server still answers as the right site.
That retry is this plugin’s own arrangement.
One external URL does appear in the plugin source and in the documents it
publishes: https://schemas.agentskills.io/discovery/0.2.0/schema.json. It is a
schema identifier, written into the published agent-skills index as a $schema
value so that a consuming agent knows which format the document follows. The
plugin never requests it, and nothing is sent to that host. It is a name, in the
same way a namespace URI in an XML document is a name rather than an address the
parser fetches.
