uSERP · SEO Operations

Client Hubs

Proactive account management. One SEO lead, one account manager, the whole book, every month.

4hubs, one per account manager

5lines per client, due the second Thursday

45minutes per hub call, on the third Tuesday

02

02 Why hubs

From reactive to proactive.

Before · reactive

The account gets skimmed 30 minutes before the call
Campaigns run with no SEO eye on anchors or publishers
Pace gaps surface at the QBR, two months late
Churn arrives as a cancellation

After · proactive

Every client gets a short structured review on a set date
Pace, anchors, publishers and relevance get checked in time to fix
The account manager gets SEO judgment in writing
The warning lands in the tracker while it is still fixable

03

03 What a hub is

A hub is one account manager's book.

The hub

One AM's book of clients

Delivery side

Hub AM

Pipeline statusPublisher rejectionsAnchor pushbackCampaign frictionClient responsiveness

SEO side

SEO lead

Link paceAnchor and target mixPublisher qualityContextual relevanceClient signals

The two of them meet once a month for 45 minutes, on the same day as every other hub. Four hubs cover every active client.

04

04 Who runs which hub

Four hubs, four pairs.

Hub A20 clients

SEO leadMari

Hub AMAyah

Active links a month147

Hub B15 clients

SEO leadRobert

Hub AMUmar

Active links a month107

Hub C13 clients

SEO leadGordon

Hub AMDiego

Active links a month60

Hub D15 clients

SEO leadRebecca

Hub AMDaniela

Active links a month74

The hub SEO lead runs the call. They do not take over the clients. Every client keeps its own SEO lead and its own CS lead, Gabby or Nikita.

05

05 The four roles

One client, four clear lanes.

Client SEO leadWhoever owns the account

Writes the account's five monthly lines and sets its flag by end of day on the second Thursday.

Hub AMAyah, Umar, Diego, Daniela

Brings the delivery side. Pipeline status, publisher rejections, anchor pushback, campaign friction.

Client CS leadGabby, Nikita

Owns the client relationship. Not needed on the call, drops in when one of their clients is up.

Hub SEO leadMari, Robert, Gordon, Rebecca

Runs one hub call. Walks the flagged clients with the AM and routes what comes back.

A liaison, not the owner

06

06 The monthly rhythm

Four moments, and where each one lands.

Second Thursday Write it up

Five plain lines per client on pace, anchors, publishers, relevance and signals, all in by end of day. Then set that client's flag.

→ The notes doc

Second Friday Clear it up

Everyone reads through the notes. Anything unclear gets asked of the SEO lead who wrote it.

→ Straight to the lead

Third Tuesday Hub Day

All four calls, 45 minutes each. Walk the Discuss and Watch clients, skip the Good ones.

→ The Action Log

On and after the call Execute

Every action gets an owner and a due date. Anything still open comes back at the next call.

→ Gordon, if it escalates

Internal only. It sits one to two weeks before the client-facing strategy call and feeds it. Between cycles the #client-hubs channel keeps feedback live, so tag the SEO lead with the client and the issue as you spot it.

07

07 The tracker

The sheet is the operating board.

Client	SEO lead	Rate/mo	Backlog	Account status	SEO flag
Cruise America	Robert	7	93	Active	Watch
Hello Rache	Gordon	25	139	Active	Discuss
Northerner	Rebecca	13	52	Winding down	Discuss

SEO flag Good on track, skipped on the call Watch drifting, worth a look Discuss needs a decision N/A long dead, nothing to watch Account status Active At riskRenegotiatingPausedUnclear Winding downEnded

One editable All Clients table, plus an Action Log. Everyone adds and edits clients in that one table, and named views inside it hand each lead and each hub its own slice, already sorted for Hub Day. The sheet keeps itself current, with new clients appearing automatically twice a month and Backlog refreshing from delivery data on the 7th.

08

08 The client notes doc

The doc is the memory.

Cruise America · Client Hub Notes

Hub BSEO RobertAM UmarCS Gabby7/moFlag Watch

Carried over from July. Roughly 104 links still owed, and the Seattle queue is paused.

Week 2 · the five fields

One plain sentence each, 15 to 25 words. Not an essay.

Week 3 · hub meeting

One optional line from the call. Actions go to the Action Log, never here.

The record

Every month keeps its own section, so a client's whole year reads in one scroll.

August 2026, in the doc

Link pace

Scope halved to 7 a month on Aug 1. Two live, seven planned, roughly 104 still owed.

Anchor and target mix

August plan is 3 RV Rentals, 2 Las Vegas, 2 Denver. One live link hit paused Seattle.

Publisher quality

Both August publishers clear the DR 50 floor, at DR 62 and DR 71.

Contextual relevance

The travel CRM piece reads editorial. The UK luxury piece carries a Seattle anchor with no Seattle in it.

Client and CS signals

Client halved spend on budget and plans to raise volume in the new year. QBR on Aug 17.

09

09 Hub Day

The third Tuesday, four calls, one day.

Hub	SEO lead	Hub AM	Spain time	Hub AM local time
Hub A	Mari	Ayah	11:00	17:00
Hub B	Robert	Umar	13:00	16:30
Hub C	Gordon	Diego	17:00	10:00
Hub D	Rebecca	Daniela	17:00	10:00

45 minutes each, on Meet, with Gemini taking the notes so nobody has to scribe. The call walks the Discuss and Watch clients only, which is what keeps it short.

Your invite carries the time in your own zone, and each pair can move its slot if the standing time stops working.

10

10 Escalation & success

Catch it early. Route it up.

Escalate when

A client sits on Discuss two cycles running
An action is still open past its due date
The pair cannot resolve it, like a client gone quiet for weeks or a scope reversal
Anything on pricing, renewals, contracts or churn risk, which goes straight to Gordon

What good looks like

1-2 moearlier we catch a pace or anchor problem, instead of at the QBR or in a client complaint

Everyat-risk client carries a logged signal in Nikita's risk matrix

Fewerchurn surprises, because the warning hit the tracker first