WordPress pluginBeing built

Sitearc Connect is a WordPress plugin. It is being built and it is not available yet. This page describes the plan, not a shipped feature.

It exists because most agency client sites are on WordPress, and a repository is not always the shipping path. The plugin will give a WordPress site the same approved-change route a repository already has.

Nothing on this page works today. A WordPress site is still fully readable now. See Connect a site for what already works.

How connecting will work

The plugin will ship in the official WordPress directory. You install it the way you install any plugin.

1. Its admin page will show a connection key.
2. You paste that key into Sitearc.
3. Sitearc will call /ping to confirm the site is reachable.
4. It will then call /site-info and read the site back.
5. It will rotate the key immediately, behind a confirm step.
6. The plugin will heartbeat every five minutes from then on.

The rotation matters. The key you copied out of an admin page has been on your clipboard. It may also sit in a support thread. The one that stays in use will be the one neither of you ever saw.

What /site-info will read

The site’s name and URL. The WordPress version and the PHP version. Which SEO plugin is installed, if any. A capabilities map saying what this install can actually do.

That capabilities map is what stops Sitearc proposing a change the site cannot accept. A proposal for a field your SEO plugin does not have is a wasted review.

The editor-scoped credential

The endpoint /agent-credential will create a dedicated user with the editor role. It will mint a native WordPress Application Password for that user. Any password minted earlier will be revoked at the same moment.

Four properties of that credential are worth stating plainly.

The role is editor, and it never escalates. Not administrator. An editor can write and publish content and cannot install plugins, change users, or touch settings.

It is a native Application Password. Not a bespoke token Sitearc invented. It works with WordPress’s own wp-json/wp/v2 API. You can revoke it from your own users screen, without asking anyone.

HTTPS will be required. An Application Password over plain HTTP is a credential in the clear, so the endpoint will refuse.

The agent never sees it. Sitearc will hold it encrypted and use it on the agent’s behalf. An agent asks for a change to be applied. It does not receive a key to your site.

The other endpoints

Endpoint	What it will do
/ping	Confirm the site is reachable and the key is valid
/site-info	Return name, URL, versions, SEO plugin, capabilities
/agent-credential	Mint the editor-scoped Application Password
/plugin-version	Report the installed version of the connector
/update-plugin	Update the connector itself
/site-health	Report the state of the install
/disconnect	Break the connection and revoke the credential
/self-uninstall	Remove the plugin and everything it created

/disconnect and /self-uninstall are both there on purpose. A connector you cannot cleanly remove is a connector you should not install.

Any path that sideloads a file will sit behind a guard against server-side request forgery. The plugin will ship with PHPUnit tests covering every endpoint above.

What it will never do

It will never apply a change on its own. The plugin will be a credential and an endpoint. It will have no opinion about your content and no schedule.

Every write will still go through the loop. A proposal carries evidence and a prediction, a person approves it, and only then does anything reach the site.

It will never hold an administrator role. The editor role is the ceiling and there is no escalation path in the design.

It will never give an agent your credentials. The Application Password stays encrypted on the platform. Nothing hands it to a model.

It will never phone home with your content. The heartbeat reports that the site is alive and which version is installed. Content moves only when the platform asks for it, through WordPress’s own API.

Sitearc will never host your site. It works on the site you host. That is true for WordPress and for every other stack.

Status and what to watch

None of this exists in the plugin directory yet. There is no date, and this page will not invent one.

Track it here and on the changelog. The connector ships when the endpoints, the credential rotation and the PHPUnit suite are all done, not before.