توضیحات
Make your website AI-native. One open manifest plus REST and MCP endpoints so AI agents can discover, understand and safely act on your site.
تغییرات این نسخه
0.4.3
OAuth Protected Resource (RFC 9728): new /.well-known/oauth-protected-resource document telling agents (and MCP clients) which authorization server guards the AI2Web endpoints. Served only when OAuth2 is enabled.
Content Signals + robots.txt projection: the usage_policy you already declare in the manifest is now projected into robots.txt as a Content-Signal directive and sent as a Content-Signal response header, so crawlers can actually read your stated preferences. Additive only – your existing robots.txt rules are never modified – and filterable via ai2web_project_robots_txt.
Discovery Link header: every front-end response advertises the manifest via Link: <.../ai2w>; rel="ai2w" (RFC 8288), so non-HTML clients discover it without parsing a page. Filterable via ai2web_send_discovery_headers.
Markdown for agents: /ai2w/content returns Markdown when the request sends Accept: text/markdown (with Vary: accept); JSON remains the default.
0.4.2
Compatibility: the plugin no longer relies on array_is_list(), so it runs on its declared minimums (PHP 8.0, WordPress 6.0) rather than needing PHP 8.1 / WordPress 6.5.
The optional WordPress 6.9 Abilities API and WordPress 7.0 AI Client integrations are now explicitly guarded, so they are never called on cores that do not provide them.
Housekeeping: added a License URI header, escaped an admin readiness glyph, trimmed an over-long upgrade notice, and documented the OAuth redirect and table-name query annotations.
No configur
OAuth Protected Resource (RFC 9728): new /.well-known/oauth-protected-resource document telling agents (and MCP clients) which authorization server guards the AI2Web endpoints. Served only when OAuth2 is enabled.
Content Signals + robots.txt projection: the usage_policy you already declare in the manifest is now projected into robots.txt as a Content-Signal directive and sent as a Content-Signal response header, so crawlers can actually read your stated preferences. Additive only – your existing robots.txt rules are never modified – and filterable via ai2web_project_robots_txt.
Discovery Link header: every front-end response advertises the manifest via Link: <.../ai2w>; rel="ai2w" (RFC 8288), so non-HTML clients discover it without parsing a page. Filterable via ai2web_send_discovery_headers.
Markdown for agents: /ai2w/content returns Markdown when the request sends Accept: text/markdown (with Vary: accept); JSON remains the default.
0.4.2
Compatibility: the plugin no longer relies on array_is_list(), so it runs on its declared minimums (PHP 8.0, WordPress 6.0) rather than needing PHP 8.1 / WordPress 6.5.
The optional WordPress 6.9 Abilities API and WordPress 7.0 AI Client integrations are now explicitly guarded, so they are never called on cores that do not provide them.
Housekeeping: added a License URI header, escaped an admin readiness glyph, trimmed an over-long upgrade notice, and documented the OAuth redirect and table-name query annotations.
No configur