Step 1
Discover
Core finds supported content, forms, and WooCommerce capabilities already present on the WordPress site.
How it works
Decide what agents can use on your WordPress site
Open for Agents Core gives a WordPress owner one place to discover, review, publish, and validate the capabilities agents may use.
The owner stays in charge from discovery to publication
Step 2
Review
The owner sees what each capability reads, returns, or changes before deciding whether to expose it.
Step 3
Publish
Core publishes only the tools the owner approves. Everything else stays private.
Step 4
Validate
Public checks confirm that the intended files and endpoints work through the real host, cache, and CDN.
Choose separately what agents can read, submit, or change
- Content: publish reviewed tools for posts, navigation, search, taxonomies, and public site information.
- Forms: discover eligible Contact Form 7 and WPForms Lite forms. Submission stays off by default, is enabled for an exact reviewed form, and requires the visitor to approve the final values.
- Commerce: let agents find and compare WooCommerce products. Selected cart changes require visitor approval; checkout, payment, orders, login, and account changes remain human-controlled.
The integrations guide lists current providers, tested versions, defaults, and limitations.
People and agents can use the same approved tools
The human website
Semantic HTML, navigation, structured data, and sitemaps remain the foundation for people, search engines, and agents.
Compatible agent clients
Machine-readable files and published tools give compatible clients explicit information instead of making them infer every task from buttons and page structure.
The optional Assistant
Visitors can ask naturally, see proposed tool use, and approve an exact consequential action before the site changes anything.
How agents find and use the published tools
Core derives its public outputs from the same owner-reviewed WordPress catalogue. llms.txt, Markdown, readiness metadata, and Agent Skills help compatible clients understand the site. ActionMap, API Catalog, the MCP Server Card, and ARD help clients discover the published resources and capabilities.
Core's current Streamable HTTP MCP endpoint is read-only. Separately reviewed browser WebMCP and Assistant operations may include a state change, but only behind their own authorization and exact visitor approval. Publishing a tool never bypasses the site's access control.
llms.txt is an optional compatibility resource for clients that choose to read it. It is not a Google Search inclusion or ranking signal. Google's guidance continues to emphasize crawlable, useful content, indexing, and normal SEO foundations. Read the official Google Search guidance.
WebMCP is useful, emerging, and optional
Chrome 149+ includes a WebMCP origin trial for enrolled origins. Open for Agents can publish reviewed page tools through that browser API, but the proposal is still subject to change and compatible browser support is not universal. The WordPress plugin, hosted demo, and Assistant do not depend on native WebMCP being available.
Read why agent-ready websites matter for the plain-language comparison, or open the live WordPress demos to see reviewed capabilities in use.
Check how public routes respond over HTTP
A WordPress setting can look correct while the public URL still fails because of redirects, caches, proxy rules, or host security settings. Open for Agents makes bounded external HTTP requests to the public files and endpoints the owner meant to publish. This observation does not establish compatibility with any particular agent or model.
You can also browse published directory entries.