Short answer: An SEO team structure is the way a company assigns ownership of organic search across specialists, product teams and agencies; in a matrixed organisation it depends more on standards and influence than on headcount. Pick the operating model that matches your business model, give every asset one owner, and report to the board in commercial terms.
Key Takeaways
- Structure follows the business model, not the org chart. One site suits a centralised team; a multi-brand or multi-market portfolio suits hub and spoke.
- In a matrix, most of the people who ship SEO work do not report to SEO. Standards, working groups and acceptance criteria do the heavy lifting.
- Give every asset a single SEO owner. Separate Heads of SEO per market on one domain fragment standards.
- Hire a senior technical SEO first, a content strategist second and an analyst third, earlier than most companies think.
- Keep strategy, prioritisation and measurement in-house. Buy capacity and specialist skills from agencies.
- Report five metrics to the board: organic revenue, share of demand, AI search visibility, the risk register and roadmap delivery.
In This Post
- What Does an SEO Team Actually Do in 2026?
- The Four SEO Team Structures and When Each Fits
- Single Owner per Asset vs Per-Market Teams
- How to Build an SEO Team: Headcount and First Hires
- Agency vs In-House: Where Does the Line Sit?
- How Do You Get SEO Work Shipped Without Line Authority?
- Executive Reporting: What Should the Board See?
- How AI Changes SEO Team Design
- Common Mistakes When Structuring an SEO Team
- FAQs
- Final Thoughts
- More Resources
Most advice on SEO team structure starts with an org chart.
But in a matrixed company, the org chart is the least interesting thing about how SEO gets done.
The engineers who fix your templates report to a CTO. The editors who write your pages report to a content director. The market managers who decide priorities report to a regional GM.
So who owns organic search? On paper, the SEO team. In practice, everyone and no one.
In this post, you’ll learn which of the four operating models fits your business, who to hire first, where agencies fit, how to get work shipped without line authority, and exactly what a board should see each quarter.
I lead a group SEO function with 10 direct reports and about 300 indirect reports [CONFIRM wording matches LinkedIn], and I’ve managed budgets over half a million a month [CONFIRM wording]. Before that, I worked in teams of 50+ at Wolfgang Digital and The Independent [CONFIRM: led or part of]. This is what I’ve learned about making a matrix work for search.
What Does an SEO Team Actually Do in 2026?
An SEO team owns organic visibility as a revenue channel. That means technical health, content and information architecture, authority and digital PR, measurement, and enabling the teams that actually ship.
In 2026, it also means AI search visibility. Even Google’s own guide to hiring an SEO now lists optimising for generative AI alongside technical advice, content development and training.
The same guide makes a point every exec should remember when a vendor overpromises:
“No one can guarantee a #1 ranking on Google.”
Here’s the catch. In a matrix, the SEO team does very few of those things alone. The table below is the one I use to show leadership who actually holds the pen.
| Capability | SEO team role | Who usually ships it |
|---|---|---|
| Technical health (crawling, indexing, rendering, speed) | Sets standards, audits, writes acceptance criteria | Product engineering, dev agencies |
| Information architecture and templates | Designs, prioritises | Product, UX, engineering |
| Content strategy and briefs | Owns demand research and briefs | Editorial teams, subject matter experts |
| Authority and digital PR | Sets targets and quality bar | PR or outreach teams, specialist agencies |
| Measurement and reporting | Owns questions, definitions and sign-off | Analysts, data engineering |
| AI search visibility | Owns measurement and policy | Content, engineering, legal for crawler policy |
| Enablement and training | Owns and delivers | SEO team |
Key finding: in five of the seven capabilities above, the people who usually ship the work sit outside the SEO team.
That is why structure in a matrix is really a question about influence.
The Four SEO Team Structures and When Each Fits
There is no single best SEO team structure. There is only the one that matches how your company makes money.
Structure follows the business model, not the org chart.
| Model | Best fit | Strengths | Failure mode |
|---|---|---|---|
| Centralised | One product, one main site, one market | Consistent standards, clear priorities, fast decisions | Becomes a ticket queue; far from product squads |
| Hub and spoke | Multi-brand or multi-market portfolios | Shared standards with local market knowledge | Spokes drift if the hub has no authority over standards |
| Embedded | Product-led companies with strong engineering squads | SEO built into the definition of done | Isolated SEOs, inconsistent practice, weak career paths |
| Centre of excellence | Large organisations where many teams publish | Scales through enablement, not headcount | Advises without accountability; nobody owns outcomes |
[IMAGE NEEDED] Four small org model diagrams side by side, built as SVG. (1) Centralised: one SEO team box with arrows to Engineering, Content, Product. (2) Hub and spoke: central hub (standards, tooling, measurement) with spokes to Brand A, Brand B, Market C, each with an SEO lead. (3) Embedded: three product squads, each containing an SEO, dotted line to a Head of SEO. (4) Centre of excellence: small CoE box with "standards, training, tools" arrows to many publishing teams. No names, no headcounts. | Alt: Diagram comparing four SEO team structure models: centralised, hub and spoke, embedded and centre of excellence | Caption: The four SEO operating models. Image created by author, October 2026
1. Centralised
One SEO team sets strategy and standards for everything. It works brilliantly for a single site, and Botify’s Paul Grossi recommends a centralised model, especially when SEO sits inside web product teams.
But it breaks when the business has many brands with different P and Ls, because the central team becomes the bottleneck.
2. Hub and Spoke
The hub owns standards, tooling, measurement and the roadmap framework. The spokes are brand or market SEO leads who apply those standards locally.
This is the enterprise model. What is enterprise SEO? It’s search at a scale where many templates, markets, domains or teams have to work to one standard, so governance becomes as important as tactics.
Conductor’s Patrick Reinhart describes a brand, product, vertical or market structure with one SEO leader overseeing all the teams, plus pods and short-lived cross-functional groups. He puts the stakes bluntly:
“The biggest enemy of enterprise SEO success isn’t an algorithm; it’s disorganization.”
3. Embedded
SEOs sit inside product squads and report day to day to a product lead, with a dotted line to a Head of SEO.
Botify’s Grossi found an SEO engineer embedded in the product team to be the most effective role he’d seen. I agree, with one condition: the embedded SEOs still need a functional home that sets standards and runs their careers.
McKinsey’s work on agile organisations makes the same point in general terms. Its authors describe functions evolving into communities of knowledge and practice that act as a professional home while people work in cross-functional teams.
4. Centre of Excellence
A small expert team that sets standards, builds tools and trains everyone else to do SEO properly.
Think of it as what Matthew Skelton and Manuel Pais call an enabling team in Team Topologies: a team that works alongside others to close skill gaps, then moves on.
The failure mode is predictable. A CoE without accountability for outcomes becomes a library nobody visits.
Tip: Most mature portfolios end up as a hybrid: a hub that owns standards and measurement, spokes with clear ownership per asset, and CoE-style enablement for every team that publishes.
Single Owner per Asset vs Per-Market Teams
This is the structural decision I see go wrong most often in international businesses.
A company launches /uk/, /us/ and /es/ on one domain. Each market gets its own Head of SEO and its own team. Each makes sensible local decisions.
And the domain slowly fragments: different templates, different internal linking rules, overlapping content that cannibalises across folders, and nobody accountable for the whole.
Don’t just take my word for it. GainChanger’s 2026 review of international domain strategies across 13 large affiliate brands observed that teams are often separated within the same site, with a separate Head of SEO and team per market, and concluded this leads to a lack of standardisation; it recommended a single owner per asset. [PERMISSION: GainChanger deck data]
Botify’s Grossi describes the same pattern in siloed structures: competition for developer resources, duplicated testing and weak knowledge sharing.
The single-owner rule: every domain, brand or asset has one accountable SEO owner. Market specialists advise; they do not set competing standards.
That doesn’t mean market expertise disappears. It means market leads own demand research, local content and compliance input, while one owner decides templates, architecture and technical standards for the asset.
[EXAMPLE: Dan to add one structural change he made, for example moving to one owner per asset, and its outcome as a ratio or percentage, such as time to ship SEO tickets or the share of roadmap items shipped. Grandstand data needs comms clearance.]
I go deeper on portfolio-level choices in my post on international SEO strategy at portfolio scale.
How to Build an SEO Team: Headcount and First Hires
How to build an in-house SEO team is less about the number of heads and more about the order you hire them in.
The First Three Hires and Why
Hire 1: a senior technical SEO who can work with engineering. Most organic growth at scale is blocked by templates, rendering, crawling and releases. You need someone engineers respect from day one.
Hire 2: a content strategist. Someone who turns demand data into briefs and information architecture, and who can work with editors and subject matter experts without becoming the bottleneck.
Hire 3: an analyst. This is the hire most companies leave too late.
Here’s why. Without an analyst, the team can’t prove impact, can’t join crawl, log and revenue data, and ends up reporting traffic instead of money. Some data can’t be recovered later, either: Google’s own documentation confirms the Search Console bulk export does not include data from before setup.
I set out the data model that analyst should build in SQL for SEO: the data model my analysts query.
| Phase | Hires | What they deliver | Signal it is working |
|---|---|---|---|
| 0 to 90 days | Head of SEO, senior technical SEO | Audit, risk register, first working group, top ten technical fixes in the engineering backlog | SEO acceptance criteria agreed with engineering |
| 3 to 6 months | Content strategist, analyst | Briefing process, page type segments, a first joined dataset, monthly leadership report | Leadership reads one report, not five dashboards |
| 6 to 12 months | Market or brand SEO leads, outreach or digital PR lead | Hub and spoke ownership, standards and SOPs, agency briefs with SLAs | Roadmap delivery tracked quarterly at board level |
| 12 months and beyond | Specialists by need (international, news, product SEO, AI search) | Depth where revenue justifies it | Headcount requests tied to forecast revenue |
[TEMPLATE LINK: Download the first-hires plan and RACI template.]
Capacity Planning: Sizing the Team
I don’t believe in a formula for SEO headcount. Anyone who gives you “one SEO per X pages” is guessing.
Use a method instead:
- List the assets (domains, brands, markets) and give each a revenue weight.
- List the recurring work per asset: monitoring, audits, release reviews, briefs, reporting.
- Estimate the roadmap work for the next four quarters in days, by capability.
- Subtract what other teams will ship under SEO standards, because in a matrix that’s most of it.
- What’s left is SEO team capacity. Fill the gap with hires where the work is strategic and recurring, and with agencies where it is spiky or specialist.
Simply put, headcount follows revenue weight and roadmap, not site size.
Head of SEO: The Role and the Reporting Line
A Head of SEO owns organic search outcomes across the business, sets the standards every other team works to, and represents search at the leadership table.
Where it reports matters. At Mediahuis, I started as Technical SEO Manager reporting to the COO, before becoming Head of SEO. At Betsperts Media and Technology, as Head of SEO, I reported to the CEO.
Both lines put SEO close to the decisions that actually move organic revenue: product priorities, acquisitions and budgets.
If your Head of SEO sits three layers below anyone who sets the engineering roadmap, you’ve built a structure that asks for permission instead of setting standards.
Agency vs In-House: Where Does the Line Sit?
I’ve managed paid media and technical development agencies, and the rule I come back to is simple.
The key is to keep the thinking in-house and buy the doing.
| Keep in-house | Buy from agencies or contractors |
|---|---|
| SEO strategy and prioritisation | Extra capacity for content production or technical fixes |
| Standards, SOPs and acceptance criteria | Specialist link acquisition and digital PR |
| Measurement definitions and board reporting | One-off audits, migrations support, second opinions |
| Ownership of each asset | Development sprints against a defined brief |
| Vendor management and budget allocation | Niche expertise (a new market, a new platform) |
Manage every agency with three things: a written brief with the business goal, SLAs on turnaround and quality, and a monthly outcome review against the metric the brief named.
[EXAMPLE: Dan to add one anonymised example of managing a paid media or development agency against SLAs, and what changed as a result.]
How Do You Get SEO Work Shipped Without Line Authority?
Christopher Bartlett and Sumantra Ghoshal saw this problem coming decades ago. In their 1990 Harvard Business Review article on matrix management, they argued that many companies were
“organizationally incapable of carrying out the sophisticated strategies they have developed.”
Source: Christopher A. Bartlett and Sumantra Ghoshal, Harvard Business Review, July 1990
Swap “sophisticated strategies” for “SEO roadmap” and you have most in-house SEO teams I’ve ever spoken to.
The fix is not more authority. It’s four habits.
- Tie every request to the other team’s goal. Engineering cares about stability and velocity; content cares about audience; product cares about conversion. Frame the SEO ask in their metric.
- Agree standards once, in a working group. Not ticket by ticket.
- Put SEO acceptance criteria in the definition of done. Then SEO is a quality gate, not a favour.
- Report shipped impact back to the teams that shipped it. Credit buys you the next sprint.
Working Groups With Product, Engineering, Content and Compliance
A working group is a standing forum with a clear remit: agree standards, prioritise cross-team work and unblock releases.
Keep it small. One senior person from SEO, product, engineering and content, plus compliance or legal in regulated markets.
Decision rights matter more than attendance. Bain’s RAPID decision framework separates who recommends, who agrees, who performs, who gives input and who decides, and says ideally only one person decides.
The RACI below is the version I’d start with. Following Atlassian’s guidance on RACI charts, there is exactly one Accountable per row.
| Activity | Head of SEO | Asset SEO owner | Engineering lead | Content lead | Analyst | Compliance | Agency |
|---|---|---|---|---|---|---|---|
| SEO standards and SOPs | A | R | C | C | I | C | I |
| Technical fixes and releases | I | C | A | I | I | I | R |
| Release SEO sign-off | I | A | R | I | C | I | I |
| Content briefs and updates | I | C | I | A | I | C | R |
| Crawler and AI bot policy | A | R | R | I | C | C | I |
| Board metrics and data contracts | A | C | I | I | R | I | I |
| Agency briefs and outcome reviews | A | R | C | C | C | I | I |
[EXAMPLE: Dan to add one working group or SOP adoption example and its effect on output, as a ratio.]
Standards and SOPs: How to Systemise SEO Across a Large Content Team
You can’t train your way to consistency across hundreds of writers. You systemise it.
- Templates over talent: build titles, schema, internal linking modules and canonical logic into templates, so writers can’t get them wrong.
- Briefs with acceptance criteria: every brief states the query, intent, required entities and internal links, and the editor checks them before publishing.
- One SOP per recurring task: launches, redirects, updates, migrations. Short, versioned, owned.
- Audits on a cadence: covered in my post on enterprise SEO audits and governance.
Enablement: Meetups and Roundtables
I run an internal SEO meetup series at Grandstand. It’s the cheapest scaling tool I know, because it turns SEO from a team into a shared practice.
[DATA: Dan to add the meetup cadence, attendance pattern and one output change as ratios, for example the share of teams adopting a new SOP after a session. Needs comms clearance.]
Make no mistake, enablement is not a nice-to-have in a matrix. It’s how you reach all the work your team will never touch directly.
Executive Reporting: What Should the Board See?
Boards don’t want rankings. They want to know whether organic search is growing revenue, whether it’s at risk, and whether the money is working.
The evidence on reporting discipline is striking. In McKinsey’s global survey on organisational redesigns, 45% of successful redesigns tracked key performance indicators, against 8% of failed ones. Redesigns where leaders were fully aligned on objectives succeeded 49% of the time; where they were only slightly or not at all aligned, 1% did.
Different context, same lesson. Agree the metrics up front and measure them relentlessly.
The Reporting Cadence
| Forum | Cadence | Audience | Content |
|---|---|---|---|
| Team stand-up and review | Weekly | SEO team, asset owners | Releases, incidents, backlog, leading indicators |
| Working group | Fortnightly | SEO, product, engineering, content, compliance | Standards decisions, cross-team priorities, blockers |
| Leadership report | Monthly | CMO, CPO, COO or CGO | Five board metrics, trend, decisions needed |
| Board pack | Quarterly | CEO, board | One page: five metrics, risk register, roadmap delivery, investment ask |
The Five Board Metrics
- Organic revenue or conversions, and organic’s share of the total. Lagging, but it’s the one that pays for the team.
- Share of demand captured: non-brand clicks as a share of the addressable demand you’ve defined, by priority market.
- AI search visibility trend: citation or mention share in AI answers for priority topics, plus AI referral traffic.
- Risk register: open high-severity risks such as migrations, algorithm exposure, compliance and crawler policy. A CDN setting can now block search crawlers; Cloudflare’s July 2026 controls mean a crawler like Googlebot can be blocked by customers who block Training.
- Roadmap delivery: share of planned SEO items shipped this quarter, and the share of releases that passed SEO acceptance criteria.
Every one of those metrics needs a data contract behind it: a definition, a source, an owner and a sign-off. That’s where the analyst hire pays for itself, and it’s the backbone of SEO measurement and executive reporting done properly.
[IMAGE NEEDED] One-page board report mock-up. Top row: five metric tiles (organic revenue share, share of demand, AI visibility trend, open high risks, roadmap delivery %) with arrow and quarter-on-quarter change. Middle: one trend chart. Bottom left: risk register (risk, severity, owner, mitigation, date). Bottom right: decisions needed from the board. Placeholder values only. | Alt: One-page SEO board report mock-up with five board metrics, risk register and decisions needed | Caption: A one-page board report for an SEO function. Image created by author, October 2026
How AI Changes SEO Team Design
AI changes the shape of the work more than the structure of the team.
Research, clustering, first-draft briefs, QA checks and reporting prep are increasingly automated. Judgement, standards, prioritisation and the editorial bar are not.
I lead AI and LLM adoption across SEO workflows group-wide, including Claude Projects built per editor voice. The lesson so far: the roles that grow are the ones that design systems and check outputs, not the ones that type faster.
I cover how that works in practice in AI workflows and agent systems for SEO.
Common Mistakes When Structuring an SEO Team
- Copying an org chart from a different business model. A marketplace’s embedded model won’t work for a portfolio of affiliate brands.
- Per-market Heads of SEO on one domain. Standards fragment and nobody owns the asset.
- Hiring the analyst last. You’ll spend year one arguing about numbers instead of acting on them.
- Outsourcing strategy. Agencies are great at doing; they shouldn’t decide your priorities.
- Reporting traffic to the board. Report revenue, risk and delivery instead.
- A centre of excellence with no accountability. If nobody owns outcomes, nobody acts on the advice.
FAQs
What is the best SEO team structure?
There is no single best structure. A centralised team suits one product and one main site, hub and spoke suits multi-brand or multi-market portfolios, and embedded SEOs suit product-led companies with strong engineering squads. Choose based on how many assets you run, where decisions are made, and how much work other teams ship for you.
What does an SEO team do?
An SEO team owns organic search as a revenue channel. It sets technical standards, shapes content and information architecture, drives authority and digital PR, measures commercial impact and enables the product, engineering and editorial teams that ship the work. In 2026 it also measures and improves visibility in AI search answers.
Who should be the first SEO hires?
Usually a senior technical SEO who can work with engineering, then a content strategist who turns demand data into briefs, then an analyst. Hire the analyst earlier than most companies do, because without joined crawl, Search Console and revenue data the team cannot prove impact or prioritise with confidence.
How do you build an in-house SEO team versus using an agency?
Keep strategy, prioritisation, standards and measurement in-house, because they need business context and continuity. Use agencies for capacity, specialist link acquisition, digital PR or one-off audits. Manage every agency with a written brief tied to a business goal, SLAs on turnaround and quality, and a monthly outcome review.
How do you scale an SEO team effectively?
Scale through standards and enablement rather than headcount alone. Document SOPs for recurring tasks, build SEO rules into templates, run working groups with product, engineering and content, train teams through meetups and roundtables, and give every asset a single SEO owner so decisions do not fragment by market.
What should a Head of SEO report to the board?
Five commercial metrics: organic revenue or conversions and their share of the total, share of demand captured in priority markets, AI search visibility trend, a risk register of open high-severity risks, and roadmap delivery. Keep it to one page each quarter, with the decisions you need from the board.
How do you get SEO work shipped without line authority?
Tie each request to the other team’s own goal, agree standards once in a working group rather than ticket by ticket, put SEO acceptance criteria in the definition of done, and report shipped impact back to the teams that delivered it. Clear decision rights, with one accountable owner per activity, prevent stalemates.
Final Thoughts
The best SEO team structure is the one that gets work shipped by people who don’t report to you.
- Match the operating model to the business model: centralised, hub and spoke, embedded or centre of excellence.
- Give every asset one SEO owner.
- Hire technical, then content, then an analyst, sooner than feels comfortable.
- Keep the thinking in-house and buy the doing.
- Run working groups with clear decision rights and SEO acceptance criteria in the definition of done.
- Report five metrics to the board on one page.
If you’re about to hire a VP of Growth or a Head of Organic, share this with your CEO and ask which operating model you actually run today. The answer is usually not the one on the org chart.
More Resources
- Leading organic growth teams
- SEO measurement and executive reporting
- AI workflows and agent systems for SEO
- SQL for SEO: the data model behind exec reporting
- Enterprise SEO audits: cadence, scope and governance
- International SEO strategy at portfolio scale
- About Dan Smullen
References
- Google Search Central, “Do you need an SEO?”. https://developers.google.com/search/docs/fundamentals/do-i-need-seo
- Patrick Reinhart, “How to Build and Structure an Enterprise SEO Team”, Conductor Academy, updated 4 March 2026. https://www.conductor.com/academy/enterprise-seo-team-structure/
- Paul Grossi, Director, Strategic Accounts, “Where Does SEO Live? Tips For Structuring A Successful Enterprise SEO Team”, Botify blog, 29 August 2019. https://www.botify.com/blog/seo-team-structure
- Wouter Aghina, Karin Ahlback, Aaron De Smet and others, “The five trademarks of agile organizations”, McKinsey and Company, 22 January 2018. https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/the-five-trademarks-of-agile-organizations
- Matthew Skelton and Manuel Pais, “Key Concepts”, Team Topologies. https://teamtopologies.com/key-concepts
- Google, “Start a new bulk data export”, Search Console Help. https://support.google.com/webmasters/answer/12917675
- Christopher A. Bartlett and Sumantra Ghoshal, “Matrix Management: Not a Structure, a Frame of Mind”, Harvard Business Review, July 1990. https://hbr.org/1990/07/matrix-management-not-a-structure-a-frame-of-mind
- Bain and Company, “RAPID Decision Making”, 13 October 2023. https://www.bain.com/insights/rapid-tool-to-clarify-decision-accountability/
- Atlassian, “Understanding and using RACI charts”, Atlassian Work Management. https://www.atlassian.com/work-management/project-management/raci-chart
- McKinsey and Company, “The secrets of successful organizational redesigns: McKinsey Global Survey results”, 1 July 2014. https://www.mckinsey.com/capabilities/people-and-organizational-performance/our-insights/the-secrets-of-successful-organizational-redesigns-mckinsey-global-survey-results
- Cloudflare, “Your site, your rules: new AI traffic options for all customers”, Cloudflare Blog, 1 July 2026. https://blog.cloudflare.com/content-independence-day-ai-options/
- GainChanger, international domain strategies review (presentation deck, Key Takeaways), 2026. Unpublished; permission pending, not linked.