The console
One screen. Is this working or not?
Every connected site carries the same console, whether it runs WordPress or was built for you. Seven sections, in the same order, answering one question each.
01Defined once
The screen is described in one place and drawn in two.
The sections are data, not a design decision made twice. A WordPress site renders them in PHP, a built site renders them in the app, and neither invents a row.
- Same sections, same order, either kind of site.
- A row can only appear if the connection declares it.
- No capability is shown to a client while it is dark.
Shared console specification 2026.09.20. Both renderers keep this published order.
02The console itself
Read live from this site's own connection.
Rows tied to a real capability read this site's manifest right now. Rows for parts nobody has built yet say exactly that.
1 · Receivers reachable
Can we reach this site at all, and can the site reach us?
Site answers our check
The public status and index documents.
Content receiver
Whether drafts can arrive here.
Page plan receiver
Whether planned pages can arrive here.
2 · Content receipts
What arrived, when, and what happened to it.
Articles and newsletters
Last received, and the post it became.
Appearances
A guest spot as a produced piece.
Report of what shipped
What this site told the timeline.
3 · Snippets rendering
Tracking and widgets placed properly, and only in production.
Analytics and tracking
Whether the snippets render on a live page.
Chat widget
Which agent or location is placed here.
4 · Funnel pages live
A funnel shows here only when its page actually answers.
Reviews
The live path on this site.
Referrals
The live path and partner links.
Booking
The live booking path.
Lead magnets
Each magnet and its follow-up.
5 · Automations and webhooks
What fires, where it goes, and whether the last attempt succeeded.
Suggested work
Proposals waiting on a person. Nothing self-applies.
Lead forwarding
Form submissions leaving this site.
6 · SEO health
The layer that can stand in for an SEO plugin, once handover is agreed.
Blueprint pull
Which page slots are still empty.
Sitemap ownership
Whether we own it, or the existing plugin still does.
Schema
Article, person, organisation, episode.
7 · Say something back
A message box on the same screen, so a problem does not need an email thread.
Feedback bar
Whether review mode is on for this site.
The manifest did not answer, so live rows report as unreachable rather than guessed.
03Handover, not a fight
An SEO plugin already on the site is read before anything is written.
Detect what is there, read its stored values once, and offer to take over. A site that already ranks is never quietly rewritten.
- Handover is opt in, and reversible.
- The first run is a report, not a write.
- Existing posts are matched on our own id, then slug — never on a title.
Next
See the dashboard behind the login.
The console answers whether the connection works. The dashboard answers what to do this week.
Dashboard concept