Members and roles
Invite people by email; joining costs nothing, because a workspace is priced per site watched rather than per person. There are three roles:
- Owner — everything, including billing and deleting the workspace.
- Admin — everything except the owner-only actions.
- Member — reads the site, decides on suggestions, cannot change who is in the workspace or what it pays.
Support conversations are the exception to all of this: a ticket is visible to the person who opened it and to us, and to nobody else in the workspace.
Billing
Per site, per month, with two months free on an annual plan. The 3-day trial starts when your first site is verified and connected rather than when you sign up, and converts automatically at the end unless you cancel.
Adding or removing a site changes the quantity on the subscription rather than creating a second one. Invoices are in the billing screen; card details are held by Stripe and we never see a card number.
If a subscription lapses, reads keep working and writes are refused. You can still see everything you have collected, export it, and decide what to do — nothing is held hostage. Cancelling starts a period during which the data stays readable and is then deleted, and the app says the date.
Notifications
The bell in the sidebar carries two things: what happened to your sites, and what we shipped. Each category can be turned down independently for in-app and for email — verdicts landing, suggestions surfacing, a connection breaking, product news.
Two things are deliberately not switchable. Anything about money and access, because a declined card is a fact about your account rather than the product talking about itself; and our answer to a question you asked, because an opt-out that could swallow it would lose mail you are waiting on.
Every bulk email carries a one-click unsubscribe that works without signing in. Turning off an email leaves the in-app record on.
Webhooks
The third receiver, for when the thing that should hear about a verdict is Slack, Linear, a queue or a script rather than a person. Add one in the site’s settings — they are per site, not per workspace, because the events are about a site.
Two events can be subscribed to: verdict.landed when a measurement finishes, and suggestion.surfaced when something new reaches the inbox. Choosing neither means both, including any event added later.
A delivery is a JSON POST carrying the event name in x-seo-event and a signature in x-seo-signature, formed as t=<unix seconds>,v1=<hex> where the hex is an HMAC-SHA256 over <timestamp>.<body> keyed on the endpoint’s secret. The secret is shown once, when the endpoint is created. Verify the signature before trusting the body, and compare the timestamp against your own clock — that is what makes a replayed delivery detectable.
A delivery has 10 seconds to answer, and redirects are not followed. After 10 consecutive failures the endpoint stops being tried and says why; resuming it keeps the same URL and the same secret, so a receiver that was down for an afternoon does not cost you a re-deploy. The list shows how many events each endpoint has actually received, because zero is the number worth being able to see: it is the difference between nothing having happened yet and a receiver quietly rejecting us.
Getting your data out
Export the workspace at any time from the account screen. It is a JSON file containing what the engine holds about your sites — findings, decisions, the ledger, the measurements behind them — and it needs no request and no waiting.
Deleting things
Deleting a site, a workspace or your account starts a 30-day window during which it can be restored. Inside that window the data is still there and nothing is collected. After it, deletion is real and is not reversible.
The window exists because the most common deletion is a mistake, and the second most common is a decision somebody regrets within the week.
Workspaces nobody comes back to
A workspace with no live subscription that has gone 180 days without anybody signing in, adding or verifying a site, running a pass or writing to us is emailed and given 30 days in which it is readable and collects nothing. After that it goes the way a cancelled one does. Subscribing again at any point during those 30 days stops it, and so does simply signing in and using it.
180 days rather than a quarter, because the cost of being wrong is lopsided: an abandoned workspace kept another three months costs us a few thousand rows, and a seasonal customer reaped early loses their ledger and their fitted click curve — the two things that take months to rebuild rather than minutes. A paying workspace is never on this ladder, however quiet it goes.
Asking us something
The help menu in the sidebar opens a question form. It reaches us directly, the answer comes back both in the app and by email, and the thread stays where you can find it. It is faster than mailing [email protected], and it arrives knowing which site and which build you were on.
For how the data itself is handled, see the privacy policy and the list of subprocessors.