SEO agency operations are the system that moves a client from signed contract to delivered, reported and renewed work. The part owners rarely measure is the time between stages. At my agency, production took three days and delivery took eleven, because every deliverable waited for two senior reviewers in turn, and I wrote that up on LinkedIn.
That gap is the idea this post is built on. Work runs on two clocks: the time someone spends producing it, and the time it takes to reach the client. Capacity problems show up on the first clock. Operations problems show up on the second. What follows is a six-stage model, a symptom for each stage, and a way to find the stage that is holding work.
The six stages of SEO agency operations, and how each one fails
A stage is defined by what must be true before work moves on. The last column is the one I find most useful, because a manager can see the symptom without reading a single deliverable.
| Stage | What must exist before moving on | How I would know it is failing |
|---|---|---|
| Intake | Access, goals, stakeholder list, prior history | The first month produces no shipped work, and tasks are marked blocked on access |
| Scoping | A written scope, a prioritized backlog, a reporting cadence | Requests arrive that nobody can classify as in or out of scope |
| Delivery | Tasks with an owner, a due date and a definition of done | Tasks called things like fix technical issues sit open for weeks |
| QA | A checklist per deliverable type, run before a reviewer sees the work | Delivery time is much longer than production time |
| Reporting | Work shipped tied to movement and a next step | The client asks what you actually did this month |
| Capacity | Hours per task type and accounts per person | Everyone looks busy while margin falls |
Time the gaps between stages
Stamp every deliverable when it enters a stage and again when it leaves. After a few weeks you can see where work waits, which is more useful than knowing where it is worked on. In my team, before the change, production took three days and delivery took eleven.
| Step | Days | Kind of time |
|---|---|---|
| Production | 3 | Work |
| Waiting in the senior review queue | 8 | Queue |
| Total from start to delivered | 11 | Waiting is 8 of the 11 days |
Only three of those eleven days were work. The eight-day wait sat in front of two senior reviewers who handled everything in sequence. That does not yet say whether you need another reviewer. It says to look at that stage and ask what the reviewer is spending time on. If most of what they send back is rule violations that a checklist could have caught, the queue is an operations problem. If most of it is judgment, the queue may well be a capacity problem. A change log kept by the reviewer for a few weeks answers that, and the method is set out in SEO agency SOPs.
Intake and scoping
For white label work, my team's intake is three things: a kickoff call with the partner to agree scope, one dedicated Google workbook with a sheet per end client for names and results, and access and a baseline collected before anything ships. The workbook gives every account the same place to look, whoever picks it up.
Scoping then needs an edge. If the scope says only ongoing SEO, every request is in scope by default and the agency absorbs it. Write down what is out of scope, and name the kinds of request that trigger a scope conversation before anyone starts the work.
Delivery: a task is finished when its definition says so
Compare two task cards. One says fix technical issues. The other says add canonical tags to the filtered category pages, done when a re-crawl returns the correct canonical, owned by one named person. Only the second can be timed, checked or handed over. Give blocked work its own visible status as well, so that a task waiting on the client or a developer is not mistaken for a slow one.
Reporting
In my setup the partner reports to their own clients, and my team builds reports on request for the partner to send. Results in SEO are inconsistent from month to month, and I am open with partners about that. A report that ties work shipped to what moved, with a clear next step, gives a partner something to say even in a flat month.
How do you tell whether capacity is the real constraint?
Three signs point to capacity. The longest wait sits in production, not in review or approval. Hours per task type, measured, add up to more than your people have. And the spread is wrong: one person overloaded while another has slack, which an average hides. If the longest wait sits anywhere else, hiring will not fix it.
For scale, seven people today carry 37 end-client accounts across four partner agencies, and the team peaked at nine. The hours-per-task method and the utilization ranges are in the benchmark guide, and why utilization can look fine while margin drops explains the drift between logged and productive hours. The staffing-arrangement post covers bringing in outside capacity.
The AI search versions of this model change the unit of work, and they are covered in AEO agency operations and GEO agency operations. To find which stage is holding your own work, the starting point is a workflow review in agency utilization consulting.
FAQ
What are SEO agency operations?
SEO agency operations are the processes that carry a client through intake, scoping, delivery, QA, reporting and capacity planning. They define who owns each step, what must be true before work moves on and what gets recorded, so delivery quality does not depend on one senior person's memory or availability.
How can I tell whether slow delivery is a capacity problem?
Measure production time and delivery time separately, and record how long work waits at each stage. If the longest wait is in production and your measured hours exceed what your people have, it is capacity. If the longest wait is in review or approval, look at what is being checked there first.
Why measure waiting time between stages?
Waiting is where most elapsed time hides. A deliverable can take two days of work and twelve days to ship, and only the second number reaches the client. Stage-by-stage timestamps show which hand-off holds the work, so you can fix that stage instead of adding people everywhere.
What belongs in the scope of an SEO retainer?
A written list of what is included, what is explicitly excluded, the reporting cadence and the kinds of request that trigger a scope conversation. Without an edge, every request becomes in scope by default. Agree the edge during intake, when both sides are still setting expectations.
