Connectors are plugins.
Site Brain is four small interfaces and a lot of plugins. That was deliberate - I didn't want to build a WordPress product and then rebuild it for each other platform.
Four interfaces
Connectors
A connector reads a site and writes approved changes. One implements read (crawl, metrics), write (titles, descriptions, structured data, content, redirects), verify (did the change land as approved) and revert. The edge, WordPress, Webflow, Wix, Shopify, HubSpot, Ghost, pull requests and my own CMS are all connectors, and so is the one you'd write for a platform I haven't met.
Sources
Sources bring numbers in: Search Console, GA4, your forms, HubSpot, Salesforce, Google Ads, Meta, your consent platform. Plausible, Matomo, Pipedrive and the rest are a source each.
Approval channels
Approval channels carry a proposal to a person and the answer back. Email and Slack are being tested on my own sites; Teams, Linear, Jira and your own on request.
Playbooks
Playbooks are files: what to look for, what to propose, what evidence to attach, what risk to declare. You can read mine, switch them off, and add your own.
One empty socket, and it's 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.
What exists, and what doesn't yet
Available means it's running. Testing means it exists and I'm trying it on my own sites. Building means I'm making it. On request means I'll build it when someone needs it.
| Kind | Name | What it does | Status |
|---|---|---|---|
| Connector | Edge | Writes titles, descriptions, structured data, link fixes, redirects, content variants. | Building |
| Connector | WordPress | Writes titles, descriptions, structured data, content. | Testing |
| Connector | Webflow | Writes page titles, slugs, SEO and Open Graph fields, CMS items. | Building |
| Connector | Wix | Writes SEO tags at site, page-type and item level. | Building |
| Connector | Shopify | Writes products, pages, blogs, SEO metafields. | Building |
| Connector | HubSpot | Writes site pages and landing pages. | Building |
| Connector | Ghost | Writes posts and pages, including meta fields. | Building |
| Connector | Code | Writes titles, descriptions, structured data, content, as a pull request. | Building |
| Connector | Native | Writes layout, templates, content and the full measurement setup. | Testing |
| Source | Google Search Console | Impressions, clicks and queries for each page. | Available |
| Source | Google Analytics 4 | Visits, events and conversions. | Building |
| Source | Your forms | The submissions that were actually sent. | Building |
| Source | HubSpot | Leads and lifecycle stages in the CRM. | Building |
| Source | Salesforce | Leads and opportunities in the CRM. | On request |
| Source | Google Ads | Spend and conversions. | Building |
| Source | Meta | Spend and conversions. | Building |
| Source | Your consent platform | What visitors accepted, so the counts can be explained. | Building |
| Source | Plausible, Matomo, Pipedrive and the rest | One source each. | On request |
| Approval channel | A proposal in your inbox that you approve, decline or edit. | Testing | |
| Approval channel | Slack | A proposal in a channel that you approve, decline or edit. | Testing |
| Approval channel | Teams | The same, in Microsoft Teams. | On request |
| Approval channel | Linear | A proposal as an issue, approved from the ticket. | On request |
| Approval channel | Jira | A proposal as an issue, approved from the ticket. | On request |
| Approval channel | Your own | Anywhere a person can say yes. | On request |
| Playbook | Search visibility | A rewritten title and description. Clearer headings, redirects and merges for pages that compete with each other are being built. | Testing |
| Playbook | Visibility in AI answers | Clearer summaries, direct answers to the questions people ask, and markup that makes a page easy to quote. | Building |
| Playbook | Page speed | Right-sized images, a better loading order, and removing what the page doesn't need. | Building |
| Playbook | Structured data | Product, article, FAQ, organisation and breadcrumb markup that matches what's on the page. | Building |
| Playbook | Stale content | A list of what to refresh, the facts that changed, and a draft of the update. | Building |
| Playbook | Conversion paths | A clearer call to action, a shorter form, or a fix for a broken handoff. | Building |
| Playbook | Accessibility | Alt text, labels, heading fixes and contrast changes. | Building |
I'd rather say "on request" than pretend. If something you run is missing, tell me what it is and I'll say when, or read the SDK docs once they're up and build it yourself.