uSERP · SEO Operations

Client Hubs

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

02

02 Why hubs

From reactive to proactive.

Before · reactive

Account skimmed 30 minutes before the call
Campaigns run with no SEO eye on anchors or publishers
Pace gaps surface in month 3, at the QBR
Churn caught late

After · proactive

Every client, a short structured review, every month
Pace, anchors, publishers, relevance checked in time to fix
The account manager gets SEO judgment in writing
The point, in Gordon's words: reduce churn

03

03 The partnership org

A hub is one account manager's book.

Partnerships Director

Felipe Gallo

LPAM Manager

Ayah Safieldin

DanangIrene RondónYanga Sauli

LPAM Manager

Md Umar Khan

Diego RuedaScherezade GiolJuan Camilo

Each account manager carries a book of clients. That book is a hub. Seven hubs across the partnership team.

04

04 Who runs which hub

Seven hubs, four SEO leads.

Robert2 hubs

Danang

HightouchSiteCapture

Irene Rondón

BlinkBucket ListFusionNewport+3

Mari2 hubs

Yanga Sauli

FormHealthHemlaneRampATP+3

Diego Rueda

ActivTrakPortageAdvocateNumeral+4

Gordon1 hub

Juan Camilo

AdaptiveAmazon HealthCCNCruise America+1

Rebecca2 hubs

Md Umar Khan

Group OneSuperviral

Scherezade Giol

SoFiJacob BayerNorthernerVelosio+3

The lead runs the hub. They do not take over its clients. CS (Gabby, Nikita) sits across every hub.

05

05 The four roles

One client, four clear lanes.

Client SEO Lead

Owns the account. Logs one Week 2 line: pace, anchors, publishers, relevance, signals.

Account ManagerFelipe's team

Brings the blockers: publisher rejections, anchor questions, campaign issues.

Client CS LeadGabby / Nikita

Optional at the meeting. Drops in or reads the recording when their client comes up.

Hub SEO LeadRobert, Mari, Gordon, Rebecca

Runs the meeting. Observations in, AM issues out, escalates what needs it.

A liaison, not the owner

06

06 The monthly cadence

Each week, and where it lands.

Week 1 Run the work

Normal delivery. No hub activity.

Nothing to file

Week 2 Log it

One line per client: pace, anchors, publishers, relevance, signals.

→ The sheet

Week 3 Hub meeting

Two per lead, one per account manager. Walk the book. Actions get an owner and a date.

→ Sheet + doc

Week 4 Execute

Action the items. Overdue or contract-adjacent escalates.

→ Risk matrix / Gordon

Internal only. It sits one to two weeks before the client-facing Launch+ strategy call, and feeds it.

07

07 The tracker

The sheet is the operating board.

Client	SEO Lead	CS	Week 2 observation	New action (from AM)	Status
Blink	Robert	Gabby	Close-out. 13 May links live, DR 61-82. POC leaves May 22.	Gabby gets the replacement POC before next update.	Watch
SoFi	Gordon	Gabby	Pace on track. Anchor mix healthy across target pages.	Scher flags any editor pushback on finance anchors.	In progress
Portage	Rebecca	Gabby	New client, mixed DR (5x DR60+, 10x DR20-59). Ramping pace.	Confirm first-month targets with the Senior VP team.	In progress

One tab per hub. Status: Not started, In progress, Blocked, Complete, Escalated. Each row links to its hub doc.

08

08 The hub doc

The doc is the memory.

Blink · Hub Notes

SEO RobertAM Irene13/moCS GabbyStatus Watch

Carried over, April: new POC still pending before weekly updates resume.

Week 2 · observation

Pace, anchor mix, publisher quality, relevance, client signals.

Week 3 · AM notes

Pipeline status, blockers, recommended adjustments.

Routed actions

Who owns what, by when.

May 2026, in the doc

Link pace

13 May links live, 61 close-out tasks still moving.

Publishers

DR 61-82, all clear the DR60+ floor.

Client signal

In close-out. POC's last day May 22. Replacement is the dependency.

AM pipeline

309 published, 41 sourced, 2 final-check, 18 planned. Blocker is routing, not SEO.

Routed

Gabby gets the POC. Robert keeps the link sheet current. Irene surfaces publisher issues.

09

09 Escalation & success

Catch it early. Route it up.

The Hub Lead escalates when

A lead flags an observation as Escalated
An action runs two weeks past its date
An AM raises a signal a lead can't resolve (POC dark 10+ days, scope reversal)
Anything revenue or contract: straight to Gordon

What success looks like

1-2 moearlier that a pace or anchor problem surfaces, vs the QBR, KPI, or a client complaint

Everyamber or red client has a logged signal in Nikita's risk matrix

Fewerchurn surprises, because the warning hit the tracker first