Four ways to connect, two of them being tested.
Site Brain doesn't ask you to move your website. It connects in whichever of four ways fits how the site is built, and you can change connector later.
Four ways in, and a socket for yours
- 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.
Through your CMS
Being tested on my own sites: WordPress. Being built: Webflow, Wix, Shopify, HubSpot, Ghost.
It writes approved changes into the system you already use - WordPress through a plugin, Webflow, Wix, Shopify, HubSpot and Ghost through their APIs - so the change shows up in your CMS like any other edit, with your CMS's own history.
The APIs cover titles, descriptions and SEO fields for certain; whole-content and layout writes vary by platform, and I'll say per platform what's covered before you connect.
- WordPressTestingtitles, descriptions, structured data, content
- WebflowBuildingpage titles, slugs, SEO and Open Graph fields, CMS items
- WixBuildingSEO tags at site, page-type and item level
- ShopifyBuildingproducts, pages, blogs, SEO metafields
- HubSpotBuildingsite pages and landing pages
- GhostBuildingposts and pages, including meta fields
Through your code
Being built.
For sites built from a repository (Astro, Next.js, Hugo, Eleventy and the rest), it opens a pull request with the approved change. Your normal review and deploy path applies and nothing bypasses your engineers.
At the edge
Being built.
For a platform with no usable API - Squarespace, for example - Site Brain sits in front of the site the way a CDN does and applies approved changes to what visitors receive: titles, descriptions, structured data, link fixes, redirects. The site itself isn't touched. This is the most general connector and also the one I'd pick last, because sitting in front of a site I don't control is where the surprises are.
It ships after the CMS and code connectors have run on real sites.
Edge changes live in the page the visitor receives, not in your CMS, so they last as long as the connector runs unless they're written back to the source. The report marks which changes are which.
Natively
Being tested on my own sites.
Sites on my own publishing platform get the deepest integration, including proposals that touch layout and templates.
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.
What I won't do
Ask you to replatform in order to use the product. If I think your site should be rebuilt I'll say so and why, and that's a separate conversation.
Not sure which connector fits?
Email me what you run and I'll tell you. I reply within a business day, myself.
Email me