Most advice about making a site readable by AI agents is guesswork, so I’ve been testing it on this one. Posts here cover the scores that went up, the files that turned out to do nothing, and what it took to let an agent send me a message through my own contact form.
The chat on this site has no search index and no vector database. Every question sends my whole site to Claude in one request. Here’s how that works, what it costs, and what I found when I finally measured how big that blob had grown.
Two scanners graded my site on how usable it is by AI agents. The highest-scoring thing I added was a text file saying my site has no login.
WordPress now has two AI systems that point in opposite directions: one where WordPress calls an AI, and one where an AI calls WordPress. Here’s how each actually works as of WordPress 7.1, and why the Abilities API sitting underneath them is the part that matters.
I gave a talk at WordCamp US about whether WordPress is ready for the agentic web. My answer: core has the plumbing, the plugin ecosystem hasn’t shown up yet, and most of the agent-readiness checklist we’re all chasing does nothing at all right now.
Most agent-readiness advice is about helping agents read your site. Here is what it took to let one actually do something: send me a message through my contact form, using the same endpoint the form itself uses.
I don’t only want my site to be agent-ready; I also want it to be generally healthy and optimized for the web overall. So I have a monthly process running…
I’m a tiny bit obsessed with iterating my site to agenty-ready and web-optimized perfection. That’s why I’ve spent many sessions running my site against specification.website‘s checklist and fixing what it…
A conversation about why WordPress core still ships so few AI abilities and the limitations they have got me thinking: why am I making my site fully dependent on Abilities…