SEO agency operations are the system that moves a client from signed contract to delivered, reported and renewed work. It has six stages: intake, scoping, delivery, QA, reporting and capacity planning. When one stage is informal, the problem rarely shows up there. It shows up two stages later as a missed fix, a thin report or a client who stops replying.
I ran W3whiz, an SEO agency, for nine years, and I now look at agency delivery from the platform side as a product manager at Search Atlas. When a client is unhappy, the SEO usually takes the blame first. Often the weak point is a handoff between two stages. This post walks through the model stage by stage, then covers where it breaks and how to size it.
The SEO agency operations model in six stages
An SEO operating model defines who does what at each stage, what must be true before work moves to the next stage, and what gets recorded. It is a set of gates. The gates matter more than the job titles.
| Stage | Question it answers | What must exist before moving on |
|---|---|---|
| Intake | Do we have what we need to start? | Site access, analytics access, goals, stakeholder list, existing history |
| Scoping | What exactly are we doing and not doing? | A written scope, a prioritized backlog, agreed reporting cadence |
| Delivery | Who ships which task, in what order? | Tasks with owners, due dates and a definition of done |
| QA | Is this correct before it goes live? | A checked list per task type, signed off by someone other than the author |
| Reporting | What changed and what happens next? | A report that ties work shipped to movement and next actions |
| Capacity | Can we take on more without quality dropping? | Hours per task type, clients per manager, per-person load |
Intake ends with access in hand
Intake should end with every access and every fact you need already in hand. SEO work stalls most often on access: the CMS login, the search console property, the analytics view, the developer who can deploy a redirect. Request access piecemeal over three weeks and the first month of the retainer is spent waiting.
Good intake is one checklist, sent once, with an owner on your side who chases it. It also records the things nobody writes down: who approves content, who can deploy code, what has been tried before, and what the client believes SEO will do for them. That last item prevents the hardest conversation at month four.
Scoping needs an edge
Scoping turns an open-ended retainer into a finite backlog with a clear edge. The edge is the part agencies skip. If the scope says only that you will do ongoing SEO, every client request becomes in-scope by default, and you absorb it.
I split scoping into a diagnostic and an execution layer. The diagnostic is senior and bespoke: where the site stands, what to fix first, what to leave alone. The execution is repeatable: technical fixes, content production, on-page changes, reporting. Customize the first, standardize the second. I cover why in the staffing-arrangement post.
Keeping delivery moving
Delivery stays on track when every task has one owner, one due date and a written definition of done. A task called fix technical issues is not a task. A task called add canonical tags to the filtered category pages, owned by one person, done when a re-crawl returns the correct canonical, is.
- Backlog, not inbox. Work comes from a prioritized list, not from whoever emailed last.
- Waiting states. Add a visible status for work blocked on the client or on a developer. Without it, blocked work looks like slow work.
- Weekly review. One short review of what shipped, what is blocked and what is next, per account.
- Done means checked. A task closes when its definition of done is met and someone else has looked, not when the author says so.
Why does QA matter so much in SEO?
SEO has silent failure modes. A creative deadline missed is obvious the same day. A noindex tag left on after a deploy, a redirect chain, a title template that overwrote good titles: these can sit for a full reporting cycle before anyone notices. By then it is a churn conversation, not a fix.
QA is the cheap defense. It needs to be a checked list per task type, run by someone other than the person who made the change, before the change goes live and again after it does. The author sees what they intended. A second person sees what is there. Examples of what the list contains are in the SEO agency SOPs post.
What a report has to do
A report should connect work shipped to what moved and say what happens next. A page of rankings and traffic charts with no sentence of interpretation makes the client do your analysis. A report that lists tasks completed with no movement makes the work look like activity.
Keep three parts: what we shipped, what changed in search performance, and what we are doing next and why. Pull the data automatically so the analyst's hour goes into the second and third parts, not into copying numbers between tabs. Manual reporting is one of the steps that tends to stay manual after intake and delivery are templated, which makes it one of the fastest places to recover hours.
Where SEO delivery breaks first
- Access and approvals. Work waits on the client, nobody records the wait, and the agency looks slow.
- The unrebuilt process. A manager gets hired, but the ad hoc workflow the founder ran is left as it was. Two people now improvise differently.
- Scope creep. Small requests are absorbed without a conversation, then become the expectation.
- Reporting by hand. Senior hours go into assembling numbers, so analysis gets squeezed out.
- Utilization read in isolation. The number looks fine while margin falls, because logged hours and productive hours drift apart. I explain that mechanism in why utilization can look fine while margin drops.
How do you plan capacity for SEO delivery?
Capacity planning in SEO starts with how standardized the work is, because that sets how many clients one person can carry. Sakas & Company's agency research puts high-touch account management at roughly 4 to 8 clients per manager, rising to 15 to 20 with a standardized process. Treat it as a rule of thumb, not a guarantee. The utilization targets for each tier are in the benchmark guide for marketing and SEO agencies.
Plan from the bottom up: hours per task type, times the tasks a client's scope generates, summed per person, compared with each person's available hours. Then look at the spread across people, not just the average. A team average that looks healthy can hide one person overloaded and one under-loaded.
AI search and the SEO model
Clients now ask whether they show up in AI answers, and an SEO team is the natural place for that question to land. It does not slot cleanly into the SEO model above, because the measurement and the deliverables differ. I cover those differences in AEO agency operations and GEO agency operations. For the broader picture, the AI SEO guide is the place to start.
Where I come in
A workflow audit usually shows which of these stages is failing. That is the core of my agency utilization consulting: I look at where hours go, where work waits and which gate is missing, then help you rebuild it so the process does the work the founder used to do.
FAQ
What are SEO agency operations?
SEO agency operations are the processes that carry a client from intake through 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. Strong operations make delivery repeatable, so results do not depend on one senior person's memory.
Where does SEO delivery break first in an agency?
It usually breaks at the handoffs: access and approvals stalling work, a new manager running an unchanged ad hoc process, and QA that happens after changes go live. Those failures are silent in SEO, so a problem can sit for a full reporting cycle before the client notices.
How many clients can one SEO manager handle?
Sakas & Company's agency research puts high-touch account management at roughly 4 to 8 clients per manager, rising to 15 to 20 with a standardized process. Where your agency lands depends on how much of intake, QA and reporting is templated. Test it against per-person hours, not a fixed number.
Should an SEO agency standardize delivery?
Standardize the execution layer and keep the diagnostic layer bespoke. Technical fixes, content production, QA and reporting can run from versioned playbooks. Prioritization and strategy need senior judgment per client. Standardizing everything makes the work generic, and customizing everything makes it unscalable.