Tighter request handling, redirects kept on your own host, and a sitemap link that works without pretty permalinks.<\/p>","1.0.0":"
First release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3685401,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3685401,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3685401,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3685401,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.1"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3685401,"resolution":"1","location":"assets","locale":"","width":1240,"height":1500},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3685401,"resolution":"2","location":"assets","locale":"","width":1240,"height":1000},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3685401,"resolution":"3","location":"assets","locale":"","width":1240,"height":654},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3685401,"resolution":"4","location":"assets","locale":"","width":1240,"height":396}},"screenshots":{"1":"The report \u2014 every signal with an honest verdict, grouped by category","2":"What to publish \u2014 four switches, all off until you choose","3":"A page served as Markdown with front matter","4":"The Agent Skills document generated for the site"}},"plugin_section":[],"plugin_tags":[15643,1556,12928,6645,4608],"plugin_category":[],"plugin_contributors":[257623],"plugin_business_model":[],"class_list":["post-349683","plugin","type-plugin","status-publish","hentry","plugin_tags-agents","plugin_tags-api","plugin_tags-crawlers","plugin_tags-discovery","plugin_tags-markdown","plugin_contributors-studiomeyerio","plugin_committers-studiomeyerio"],"banners":{"banner":"https:\/\/ps.w.org\/studiomeyer-agent-readiness\/assets\/banner-772x250.png?rev=3685401","banner_2x":"https:\/\/ps.w.org\/studiomeyer-agent-readiness\/assets\/banner-1544x500.png?rev=3685401","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":false,"icon":"https:\/\/ps.w.org\/studiomeyer-agent-readiness\/assets\/icon-128x128.png?rev=3685401","icon_2x":"https:\/\/ps.w.org\/studiomeyer-agent-readiness\/assets\/icon-256x256.png?rev=3685401","generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/studiomeyer-agent-readiness\/assets\/screenshot-1.png?rev=3685401","caption":"The report \u2014 every signal with an honest verdict, grouped by category"},{"src":"https:\/\/ps.w.org\/studiomeyer-agent-readiness\/assets\/screenshot-2.png?rev=3685401","caption":"What to publish \u2014 four switches, all off until you choose"},{"src":"https:\/\/ps.w.org\/studiomeyer-agent-readiness\/assets\/screenshot-3.png?rev=3685401","caption":"A page served as Markdown with front matter"},{"src":"https:\/\/ps.w.org\/studiomeyer-agent-readiness\/assets\/screenshot-4.png?rev=3685401","caption":"The Agent Skills document generated for the site"}],"raw_content":"\n
Auf Deutsch:<\/strong> StudioMeyer Agent Readiness pr\u00fcft, was KI-Agenten von Ihrer Website tats\u00e4chlich bekommen \u2014 und ver\u00f6ffentlicht die maschinenlesbaren Dateien, die noch fehlen. Der Bericht fragt Ihre eigene Seite \u00fcber HTTP ab, so wie ein Agent es t\u00e4te, 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\u00f6ffentlichen: Ihre Inhalte als Markdown (auf 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.<\/strong><\/p>\n\n 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.<\/p>\n\n One button runs the checks. Each one asks your own site over HTTP \u2014 the same loopback technique WordPress Site Health uses \u2014 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.<\/p>\n\n For every signal you get one of three honest answers:<\/p>\n\n 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.<\/p>\n\n Four surfaces, each off until you switch it on:<\/p>\n\n 1. Markdown<\/strong><\/p>\n\n Every published page becomes available as Markdown. Request its normal URL with 2. Agent Skills<\/strong><\/p>\n\n A short instruction sheet at 3. API catalog<\/strong><\/p>\n\n 4. Link headers<\/strong><\/p>\n\n An RFC 8288 Being useful here means not overlapping with what you already run:<\/p>\n\n This plugin contacts no third party service of its own. There is no API, no\nanalytics, no telemetry, no update server, no font or asset CDN. Nothing about\nyour site, its content or its visitors is sent to StudioMeyer, and the plugin\nhas no other address to send anything to. It needs no account and no API key.<\/p>\n\n The readiness check does make HTTP requests, and it addresses every one of them\nto your own site at its own home URL, the way a visitor's browser would. That is\nwhat makes the result worth having: the plugin reads what your server actually\nreturns rather than what its own settings claim.<\/p>\n\n Redirects are followed only while they stay on your own site, up to three of\nthem. Your own site means the same host, the Being honest about the limit of that: the check asks WordPress not to follow\nredirects and inspects each one itself, but any plugin on your site may change\nthat request, and WordPress then follows inside its own HTTP library, where\nnothing is visible to a plugin. So there is a second check that does not depend\non the first. The address an answer actually arrived from is read back out of\nthe response, and an answer from anywhere else is discarded instead of being\nused as a reading of your site.<\/p>\n\n If the loopback fails outright, which happens behind some reverse proxies and\ninside containers, the plugin retries against 127.0.0.1 carrying your own host\nname in the Host header, so your web server still answers as the right site.\nThat retry is this plugin's own arrangement.<\/p>\n\n One external URL does appear in the plugin source and in the documents it\npublishes: Nothing is published until you switch it on.<\/p>\n\n\n No. Every check is a request from your server to your own site, and a redirect is followed only while it stays there. Nothing is sent to StudioMeyer, and the plugin has no other address to send anything to. If you want an independent second opinion, public checkers exist and you can visit one yourself \u2014 the plugin does not contact any of them for you.<\/p><\/dd>\n No. It is an independent plugin by StudioMeyer. It measures publicly documented signals \u2014 robots.txt rules, sitemaps, RFC 8288 Link headers, RFC 9727 API catalogs, Markdown content negotiation and others \u2014 and does not reproduce any specific vendor's scoring formula.<\/p><\/dd>\n Markdown responses are sent with Some things cannot be seen from your server: DNS records, bot signature verification at your CDN, and browser JavaScript APIs. Counting those as failures would blame you for something no plugin can change, so they are reported separately and left out of the ratio.<\/p><\/dd>\n A caching layer or a real static file at the same path can intercept the response before WordPress sees it. Clear your cache and check again. If a Yes. It writes no robots.txt, no sitemap and no llms.txt, so there is nothing for the two to fight over. Its Link header is appended to existing ones rather than replacing them.<\/p><\/dd>\n Only published, publicly viewable posts of the types you tick. Drafts, private posts and scheduled posts are never served. A password-protected post behaves exactly as it does in HTML: nothing is served without the password, and the content is served once the password has been entered.<\/p><\/dd>\n\n<\/dl>\n\n\nAccept: text\/markdown<\/code> oder mit angeh\u00e4ngtem .md<\/code>), ein Agent-Skills-Dokument, einen API-Katalog nach RFC 9727 und HTTP-Link-Header nach RFC 8288. Alles l\u00e4uft lokal auf Ihrem Server \u2014 kein Konto, keine API-Schl\u00fcssel, kein Fremddienst. Standardm\u00e4\u00dfig ist alles ausgeschaltet; Sie entscheiden, was ver\u00f6ffentlicht wird. Nur bereits \u00f6ffentliche Inhalte werden ausgeliefert \u2014 Entw\u00fcrfe und private Seiten nie, und eine passwortgesch\u00fctzte Seite verlangt ihr Passwort genau wie im Browser.<\/p>\n\nThe report<\/h4>\n\n
\n
What this plugin publishes<\/h4>\n\n
Accept: text\/markdown<\/code>, or append .md<\/code> 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.<\/p>\n\n\/.well-known\/agent-skills\/index.json<\/code> 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.<\/p>\n\n\/.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 \u2014 so a client does not need to know WordPress conventions to find them.\n<\/code><\/pre>\n\nLink<\/code> 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.<\/p>\n\nWhat it deliberately does not do<\/h4>\n\n
\n
Private by design<\/h4>\n\n
\n
Who is this for?<\/h4>\n\n
\n
More free plugins by StudioMeyer<\/h4>\n\n
\n
External services<\/h3>\n\n
www.<\/code> variant of it, or a\nsubdomain such as de.example.com<\/code>, because a home page sending visitors to one\nof those is doing something ordinary. A redirect leading anywhere else is\nreported as a finding instead of followed.<\/p>\n\nhttps:\/\/schemas.agentskills.io\/discovery\/0.2.0\/schema.json<\/code>. It is a\nschema identifier, written into the published agent-skills<\/code> index as a $schema<\/code>\nvalue so that a consuming agent knows which format the document follows. The\nplugin never requests it, and nothing is sent to that host. It is a name, in the\nsame way a namespace URI in an XML document is a name rather than an address the\nparser fetches.<\/p>\n\n\nQuick start<\/h4>\n\n
\n
\n
Does this send my site to an external service?<\/h3><\/dt>\n
Is this affiliated with a particular agent-readiness score?<\/h3><\/dt>\n
Will the Markdown version hurt my SEO?<\/h3><\/dt>\n
X-Robots-Tag: noindex<\/code> and a Link: rel=\"canonical\"<\/code> header pointing back at the normal page, so search engines keep indexing the HTML version.<\/p><\/dd>\nWhy does my count not include every signal?<\/h3><\/dt>\n
I switched something on but the check still says missing.<\/h3><\/dt>\n
.well-known<\/code> file exists on disk, your web server will serve that instead of WordPress.<\/p><\/dd>\nDoes it work with my SEO plugin?<\/h3><\/dt>\n
Which content is exposed as Markdown?<\/h3><\/dt>\n
1.0.1<\/h4>\n\n
\n
X-Content-Type-Options: nosniff<\/code> with the skills and API catalog documents.<\/li>\n.md<\/code> request, so anything reading them later sees the real request.<\/li>\n1.0.0<\/h4>\n\n
\n
Accept: text\/markdown<\/code> and .md<\/code> permalinks, with Vary: Accept<\/code>, noindex<\/code> and a canonical link header.<\/li>\n