Connecting your tools

Connecting WordPress to an AI agent

The average company blog stops at the fourth article. The first three are written in the initial burst, the fourth waits for "next week", and two years later the "News" page still shows a date that makes a poor impression. The WordPress connector gives an agent the reading and updating of articles, pages, media and comments. It has precise prerequisites, stated here bluntly, because they rule out part of the WordPress installations out there.

1. What you need before connecting

Better to start with what rules people out than to discover it along the way. Three conditions:

A WordPress.com account, with a paid plan. The connection server is the WordPress.com one. A free plan is not enough.
Access enabled in that account. It is not open by default; it is a setting to make on your side, at WordPress.com.
Writing tools explicitly opened. An important point, often discovered too late: WordPress.com closes writing by default. An agent connected without this being opened will be able to read the site and nothing else. It is not a fault, it is the factory setting.

And the limit that rules out the most people: a self-hosted WordPress is not covered by this connector. A site installed with a hosting provider, with its own plugins, exposes its own interface and would require a separate connection. As a large share of professional WordPress sites are self-hosted, this sentence probably concerns many readers of this page, and it is better to read it here than to discover it while trying.

2. What the agent does on the site

Once the prerequisites are met, the scope is broad — broader than on most connectors — and is named site by site, article by article, media by media:

Articles. Write, update, correct a text published long ago. That is the heart of the use.
Pages. Static pages age worse than articles, because nobody looks at them: outdated prices, a service area that has changed, a team member who left two years ago.
Media. Upload an image, attach a visual to an article.
Comments. Read them, answer them — a space often left abandoned, where questions from potential clients linger unanswered.

3. Publishing means modifying a live website

This is what sets WordPress apart from Notion or a spreadsheet: here, writing is immediately public. A badly updated internal page is corrected quietly; a wrong pricing page on an indexed site is seen by clients, and may be picked up in a search result for days.

Two consequences:

Validation before writing is the setting to keep, particularly on static pages. A wrong blog article is awkward; a wrong "our prices" page is a commercial problem.
A comment is content written by a stranger. It is read as data, never as an instruction — a general platform rule, particularly useful where anyone can write.

WordPress is classified at the high stakes level of the catalogue, which matches this reality: the result of an action is publicly visible within the second.

4. What it changes over time

A website is not a project that finishes; it is a thing that goes stale if nobody touches it. That is where everything is decided.

Week 1. The inventory of what is wrong is done: outdated dates, old prices, dead links, orphan pages. Most sites have more of them than one thinks.
Month 3. The fourth article has appeared, then the fifth. That is the step almost nobody clears alone — not for lack of ideas, but because the urgency of the day always wins.
Year 2. The site has a history. For search engines as for a visitor, a site that has moved every month for two years does not say the same thing as a site frozen since launch.

No ranking and no traffic is promised: search visibility depends on your market, your competition and the quality of what is published.

5. Frequently asked questions

My WordPress is with my hosting provider. Does it work?

No, not with this connector. It goes through the WordPress.com server. A self-hosted installation exposes its own interface and would require a different connection. If you have to choose, know it before committing.

Why can my agent only read?

Almost always because the writing tools are not opened on the WordPress.com side — they are closed by default. That is a setting to make in your WordPress.com account, not with us.

Can an agent publish an article without my seeing it?

Not with the default setting: any write requires human approval before execution. On a public site, we recommend keeping it, at the very least for static pages and prices.

And what if I don't have a site yet?

Then the question is not connecting WordPress but having a site at all. nullbot can build and host a website described in conversation, with its publication and its version history — and in that case, the agents that keep it alive have direct access, with no connector and no prerequisites.