How Site Brain works.

It connects to Google Search Console, your analytics, your forms, your CRM and your ad accounts and reconciles them: a submission should show up as a lead, a lead as a conversion, a conversion against the spend that produced it. Where they disagree it says so and why. It also crawls the site for speed, structured data, accessibility and broken paths, and checks how your pages show up in AI answers.

Once a week you get a short list, ranked by expected effect. Each proposal names the page, the exact change, the evidence, the expected effect, the risk and how to undo it. “Rewrite the title and description on these six pages that get impressions but no clicks.” “Add product structured data to the pricing page.” “This form's submissions aren't reaching your CRM; here's the fix.” Not “improve your SEO.”

You approve, decline or edit from an email or a Slack message. Standing approvals for low-risk changes (title tags, structured data, alt text) if you want them, and everything else waits for you. A named person on your side is the approver. Site Brain never approves its own work.

The approved change goes live through the connector you chose - through your CMS, as a pull request, at the edge, or natively. Each connector records what it replaced: a CMS change keeps the previous value, a pull request can be reverted, an edge change can be switched off. You can see every change ever made, who approved it, and when. Changes made through your CMS or your code stay on your site whatever happens to Site Brain. Edge changes last as long as the edge connector runs, unless they've been written back into the source, and the report marks which is which.

The next report shows what changed and what happened in the 28 days after, on the reconciled numbers, and says when it's too early to tell. Changes that didn't help get reversed or revised. Over a few months the reports become the history of the site, with the evidence attached.