Growth LabsEmail me

Your website, worked on every week. You say yes to each change.

Site Brain reads your search and analytics data, proposes specific changes to your pages, waits for you to say yes, makes the change on your site and tells you what happened. Today it reads Search Console. Proposing title and description changes for pages that get impressions but no clicks, sending them to you by email or Slack, and writing them to WordPress or to a site on my publishing platform once you say yes are being tested on my own sites. Webflow, Wix, Shopify, HubSpot, Ghost, code repositories and an edge connector are being built, along with the other sources and playbooks, and the check below tells you where your site stands.

Proposal (example)Approved and live
Page
yoursite.com/pricing
The change
NowPricingToPricing: plans, what each includes, and what it costs a month
Evidence
4,100 impressions in 28 days and no clicks. The title doesn't say what the page answers.
What it expects
More clicks from the same impressions, measured against the leads that reach your CRM and not clicks alone.
Risk
Low. Only the title changes.
To undo
It records the old title, so it can be put back.
A named person on your side said yes. The change is live, and the old title is recorded so it can be put back.
Today
It reads Search Console
Being tested on my sites
Title and description proposals, email and Slack approval, WordPress and my publishing platform
Being built
Webflow, Shopify, HubSpot, code, edge, the other playbooks
Each change
A named person on your side approves it, and it records what it replaced

What it does, step by step

Click or tap a step to see what it produces.

Once a weekOne proposal, from first look to report.

01 Measure

It reads Search Console, your analytics, forms and ad accounts and traces them against each other, so it knows why they differ.

Search Console, last 28 days. Made-up data.
PageImpressionsClicks
/pricing4,1000
/features3,86041
/contact92066

How it works

  1. Measure. It connects to Search Console, your analytics, your forms and your ad accounts and traces them against each other, so it knows why they differ. It reads Search Console today; the other sources are being built.
  2. Propose. Once a week it sends a short list of specific changes - the page, the exact change, why, what it expects to happen, and the risk. "Rewrite the title and description on these six pages that get impressions but no clicks," not "improve your SEO."
  3. Approve. You say yes, no, or edit it, from an email or a Slack message. You can set standing approval for low-risk things like title tags and alt text and keep the rest manual.
  4. Ship and report. The approved change goes live through whichever connector fits your site. Each change records what it replaced so it can be put back, and next week's report shows what it did.

The full loop

Works with your site, and with what comes next

  • EdgeBuildingWrites titles, descriptions, structured data, link fixes, redirects, content variants.
  • WordPressTestingWrites titles, descriptions, structured data, content.
  • WebflowBuildingWrites page titles, slugs, SEO and Open Graph fields, CMS items.
  • WixBuildingWrites SEO tags at site, page-type and item level.
  • ShopifyBuildingWrites products, pages, blogs, SEO metafields.
  • HubSpotBuildingWrites site pages and landing pages.
  • GhostBuildingWrites posts and pages, including meta fields.
  • CodeBuildingWrites titles, descriptions, structured data, content, as a pull request.
  • NativeTestingWrites layout, templates, content and the full measurement setup.
  • YoursA platform I haven't met yet.Build a connector
  • Site BrainThe sockets are plugins behind one interface.

Site Brain doesn't ask you to move your website. The two I'm testing on my own sites are a plugin for WordPress and native access to sites on my publishing platform. The APIs for Webflow, Wix, Shopify, HubSpot and Ghost, pull requests for sites built from code, and an edge connector for platforms with no usable API are being built, in roughly that order. Every connector is a plugin behind the same interface, and so are the measurement sources, the approval channels and the playbooks. If yours is missing, I'll add it, or you can.

How to extend it

Will it work with mine?

Paste your address and it'll tell you which connectors apply today, which are being built, which measurement sources it reads now, and what I'd need from you - usually a plugin or an API key for a CMS, repository access for code, or a DNS change for the edge.

Numbers you can trust

Every change is measured against numbers reconciled with your forms, your CRM and your ad spend, not against a dashboard. If you want to see what a website can see about you, the tab in the corner shows this site's view of your visit.

How I measure

Example data

One form, with example numbers. 100 submissions; 96 accepted by the form, after 4 were dropped as spam; 91 unique CRM records, after 3 duplicates were merged and 2 submissions were lost to a failed webhook. Separately, the ad platform reports54 conversions, which counts the clicks that led to a submission inside its attribution window, so it is a different quantity.

Made-up numbers, not a client's data.

A site that gets better without hiring anyone to do it.

A website is never finished, and the list of things to fix is longer than anyone's week. Connect yours and the first report is free and takes about a day. Search visibility is being tested on my own sites, and six more playbooks are being built: AI answers, speed, structured data, stale content, conversion paths and accessibility. I'm building it and testing it on my own sites first, so the first customers will be design partners, and the Managed tier means I'm in the loop with you each week.

Start with a free report