SEO team setup: roles, hours and output for 1-person, 3-person and 5-person teams
1. How to size your team
Don’t size your team on gut feel. Use two hard numbers: how many pages your site has and how much work is on the table. Page count sets the size of your content pool; workload tells you whether you’re genuinely stretched.
To decide whether to hire, ask one question: has the current person been too busy to even schedule tasks for two weeks straight? If yes, consider adding someone. If you just feel like the team looks small, don’t.
One more thing people miss: you hire to absorb workload you’ve already proven, not to “do SEO more thoroughly.” If one person is only producing 5 articles a month, the problem isn’t headcount, it’s your topic selection or your workflow. Hiring now just means one more person stuck in the same bottleneck. It won’t speed anything up on its own.
Team size also has to line up with budget. A full-time SEO hire isn’t cheap, so work out whether the leads they bring in are worth it. Until a small site has proven SEO can bring in leads consistently, the lean setup of one person plus freelancers is the best value. Don’t start by carrying the fixed cost of a 5-person team.
| Scale | Page count it fits | Signal to expand | When it doesn’t fit |
|---|---|---|---|
| 1 person | Under 100 pages | Can’t keep up with topic selection and writing | Multiple markets, multiple languages |
| 3 people | 100 to 500 pages | Link building and content compete for time | One person hasn’t proven the process yet |
| 5 people | Over 500 pages | Technical issues drag down content | Still producing single digits per month |
For how to schedule capacity and how much one person can do in a year, see Content Capacity and Scheduling.
2. How to staff a 1-person team
The key with a 1-person team is not to chase full coverage, but to get the highest-value work done. One person handles topic selection, writing and data, but not with equal effort on each.
| Responsibility | Share of weekly hours | What we do |
|---|---|---|
| Topic selection and data | 20% | Check GSC, pick keywords, choose topics |
| Content output | 60% | Write or edit drafts, 8 to 12 articles a month |
| Technical and link building | 20% | Light audits, a few links |
The trick for a one-person team is to use tools and outsourcing to take over repetitive work. Outsource technical audits and link building, and keep only topic selection and writing for yourself, since those are the two core judgment calls. Don’t try to carry every step alone, or you’ll squeeze out the time that’s most valuable for judgment. For how an overseas team goes from 0 to 1, see Taking a go-to-market team from 0 to 1.
A one-person team needs another discipline: do only three things a week, don’t be greedy. On Monday, check GSC to set topics; midweek, write; on the weekend, review rankings. Template the repetitive work, like a fixed weekly report template and a fixed topic list, and save the remaining time for the parts that truly need judgment.
The most common mistake for a one-person team is trying to learn everything yourself. For complex technical problems and unfamiliar link resources, spend the money to outsource instead of using precious time to self-study. Save your time for the product and customer knowledge only you understand, because that’s the irreplaceable part of a one-person team.
3. How to divide work in a 3-person team
A 3-person team is the most common and easiest structure to divide: one person handles strategy and data, one handles content, and one handles link building and technology. The three-way split separates the three different capabilities of judgment, production, and outreach.
| Role | Core responsibilities | Monthly output |
|---|---|---|
| Strategy/data | Keyword library, rankings, weekly reports, topic selection | Topic list + weekly report |
| Content editor | Writing, refreshing, internal links | 15 to 20 posts |
| Link building/technology | Link building, technical fixes | 20 to 30 links |
The biggest fear for a 3-person team is unclear boundaries. Each person’s weekly output must be written clearly, such as how many posts and links the content editor produces each month, otherwise all three people are “helping” and no one delivers. For how to weave internal links into a network, see internal linking system.
A 3-person team should also avoid one trap: the strategy person becoming the meeting person. They should spend 80% of their time looking at data, setting topics, and writing weekly reports, not organizing review meetings every day. Once one person spends more than half their time in meetings, the whole team’s output will drop.
4. How to divide work in a 5-person team
A 5-person team further subdivides technology and content on top of the 3-person setup. It suits multiple markets, multiple languages, or sites that already have more than 500 pages.
| Role | Responsibility | Added compared with 3 people |
|---|---|---|
| SEO lead | Strategy, budget, reporting to management | Management layer added |
| Content editors x2 | Write by topic or language | Content output doubles |
| Link building specialist | Focus on digital PR and media | Link building becomes specialized |
| Technical SEO | Crawling, speed, structured data | New dedicated role |
The risk for a 5-person team is rising coordination costs. At this point, one person must truly manage the process, otherwise five people each doing their own thing is less efficient than three. Before expanding to five, ask: is the 3-person process running smoothly? If not, don’t add people.
A 5-person team’s core workflow has to be written down. Where topics come from, who reviews drafts, who signs off on backlinks, who schedules technical fixes — all of it on one process diagram. Otherwise, once the team grows, information travels only by word of mouth and things fall apart within two weeks. A written process is what makes a 5-person team work.
5. Benchmarks for Hours and Output
Once you’ve set the division of labor, use output benchmarks to check whether it’s reasonable. The table below shows common benchmarks. Falling short means something is wrong with the division of labor or the process.
| Scale | Monthly content output | Monthly backlink output | Healthy range |
|---|---|---|---|
| 1 person | 8 to 12 articles | 5 to 10 links | Topics never idle |
| 3 people | 25 to 35 articles | 20 to 30 links | Every article maps to a keyword |
| 5 people | 45 to 60 articles | 40 to 60 links | No technical backlog |
A real-world example: a 3-person team produces only 10 articles a month, far below the benchmark of 25. It turns out they aren’t lazy — half the team spends weekly meetings discussing topics, eating into content time. Cut the topic meeting from two hours a week to half an hour and output rises immediately. When output is low, check the process first; don’t rush to hire. For how to do backlinks, see Backlink Building and Digital PR.
Another common mistake: judging the SEO team’s output only by “how many articles we published.” The output that actually matters is “how much inquiry traffic we brought in.” Article count is just a process metric; inquiry traffic is the result metric. Evaluate the team mainly on results, with process as a secondary measure — otherwise you get the illusion of prosperity: 30 articles a month, none of which bring traffic.
One last reminder: when people leave, keep the key judgments in documents. Topic criteria, keyword lists, ranking baselines, and acceptance checklists should all be captured in handover-ready documents, not just in someone’s head. That way, when someone resigns, a new hire can pick up in two weeks instead of fumbling from scratch for three months.
FAQ
Does an SEO team get results faster with more people?
How much can one person produce doing SEO each month?
What’s the most reasonable way to divide work in a 3-person SEO team?
When should you expand from 3 people to 5?
What if your SEO team’s output falls below benchmark?
Should a small team hire a dedicated technical SEO?
Final thoughts
Team structure isn’t about headcount. It’s about putting three capabilities, judgment, production, and outreach, in the right hands. On a small site, start with one person and get the process working. When that person can’t keep up, scale in stages to three, then five. Don’t jump straight to the final number.
Three steps to put this into practice: this week, use your page count to decide whether you’re a one-, three-, or five-person team. Next week, write down a monthly output benchmark for every role. From week three on, check against those benchmarks each month. If output is low, examine the workflow before you talk about hiring. For day-to-day site maintenance, see Website Maintenance Schedule.
Looking back, the steadiest pace for team structure is this: run with one person for six months, prove the workflow works and output is stable, then expand to three. Run with three for a year, once the site and the business have both leveled up, then consider five. Teams that skip stages usually end up shrinking back to three. Going slow is actually faster.
No matter how many people you have, review the division of work every quarter: whose plate is overflowing, whose is sitting empty. Adjust right away. Team structure isn’t set once and frozen. It grows alongside the business, and adjusting gradually is steadier than getting it all right in one shot.
One line worth remembering: an SEO team isn’t better when it’s bigger, it’s better when it fits. Expand before the workflow runs smoothly and what you’re adding isn’t capacity, it’s communication cost.