Skip to content

SiteBridge

SiteBridge is a WordPress plugin we are building. It lets an AI assistant work on a WordPress site, and every change it proposes waits as a draft until a person approves it in WordPress.

In development. Version 0.5.0, not released yet.

Ask about SiteBridge

SiteBridge review table in our local lab: a button link changes from # to the DistroCode About page, and a custom attribute is removed. Both wait for approval.
A proposed change waiting for review, in our local lab.

What does SiteBridge do today?

An AI assistant connects to the plugin, reads the site and proposes a change. The change goes to a review inbox in wp-admin, headed “Pending review”, where a person approves it or declines it. The assistant cannot approve its own proposal.

An approved change can be restored later. Restore puts back the fields SiteBridge saved before the change. It is not a full site backup.

What does a proposed change look like?

In one lab test, the assistant proposed changing a button link from “#” to our About page. The review table showed three columns: Setting, Before and Proposed. A second row removed a custom attribute from the same button.

Both rows waited. Nothing on the page changed until someone approved them.

How does it handle plugin updates?

It runs checked plugin updates. Before an update, SiteBridge saves a copy of the version you have. After it, a health check loads four pages: the home page, the newest page, the newest post and a 404 page. An update that fails the check is rolled back.

Four pages is not the whole site. The check does not judge layout or test every page’s scripts.

What did testing find?

A plugin update can crash a WordPress site and still be reported as healthy. We found that out about our own tool, while testing the check that is meant to catch a crashed site.

The health check could read the old cached copy of the plugin for about 2 seconds in our lab, and for up to 60 seconds on many hosts. So a plugin that took the site down passed as fine. We reproduced it 5 times out of 5.

The fix is in review, not released. After an update, it asks the web server to drop the old copy. If it cannot confirm that, it waits up to 10 seconds, then checks the site.

Why are we building SiteBridge?

Because we look after WordPress sites, and the riskiest moment on any site is a change nobody checked. SiteBridge is the rule we already work by, written into software: nothing changes until a person has seen it.

It sits next to PluginSprout, our line of WordPress plugins. The same approval rule runs through our AI and workflow automation work.

Where does SiteBridge stand?

Not released yet. Version 0.5.0 has been tested in our own lab. Real payments and real emails have not gone through it, and we have not tried it with the desktop AI apps most people use. There is no hosted version, no signup and no billing.

If you run WordPress sites and want to hear when that changes, write to us and we will tell you where it stands.

Ask about SiteBridge