In-House SEO vs Agency Support: Which Skills Should Your Team Own?

Most teams asking "should we do SEO in-house or hire an agency?" are asking the wrong question. The honest version is narrower: which parts of the search programme is this team ready to own, which parts need a developer in the loop, and which parts are specialised enough that paying an outside team is cheaper than training for them. Phrased that way, the answer is almost never a clean split. It is a map of responsibilities that changes as the site grows.

This note walks through the skills a working SEO programme needs, who is best placed to own each one, and what you give up with each staffing model. It is written for marketers and founders deciding where to invest first — not for CMOs picking vendors.

Why the ownership question matters

SEO sits across three disciplines. It needs an editor to brief content, a technologist to keep the site crawlable, and an analyst to read what search is actually rewarding. Hand it entirely to one function and the other two decay. A content-only team ships articles nobody can find because the templates block indexing. A dev-only team fixes the templates and never writes anything worth ranking. An analytics-only team reports beautifully on traffic that never moved.

Ownership is therefore not a title — it is the question of who is accountable for which decision. The companies that get search right decide this up front, not after a quarter of missed targets.

Skills most in-house teams should own

Some SEO work is close enough to normal marketing that keeping it inside the team is almost always correct. Outsourcing it costs more than training for it, and the context lives with the people who know the product.

Keyword research

This is a research skill, not a tool skill. The craft is reading the SERP, grouping terms by what the searcher is actually trying to do, and sizing the opportunity against your ability to serve it. Any marketer who can run a customer interview can learn this in a few weeks. Google's own Search Essentials and SEO Starter Guide is still the best free primer on how search sees your content.

Intent mapping

Decide which pages serve which intents, and which intents your site has no business targeting yet. This is strategy work tied to the product roadmap — hand it to an outside team and you will spend every call explaining the business back to them.

Content briefing and editing

A good brief is a one-page document a writer can work from without asking you anything. Writing briefs is a repeatable skill with a short learning curve, and the person who owns the brand voice has to own the editing pass anyway.

Basic on-page SEO

Titles, meta descriptions, headings, internal links, image alt text, a readable URL. If a CMS user can publish a page, they can be taught to publish one that is on-page sound. The quality floor here is a checklist, not a specialism.

Reporting the team actually reads

A monthly one-pager that names the queries, the pages and the clicks — and says what you plan to do about them. Outsourced reports go unread because nobody in the room wrote the questions.

Skills that require developer involvement

These are the tasks where no amount of marketing training will make a non-developer self-sufficient. The marketer's job here is to read the audit, write a clear ticket, and defend the fix in planning. The developer's job is to ship it without breaking something else.

Technical audit interpretation

You do not need to run the audit yourself to work with its output. You do need to recognise what matters: duplicate content, broken canonical tags, orphan pages, slow templates, mobile parity. If the audit comes from an outside specialist, the marketer still has to translate it into tickets your engineering team will accept.

Crawl and indexation issues

Robots directives, canonical chains, hreflang clusters, pagination edge cases, soft 404s. These are debugging problems. They respond to the same discipline that fixes any production bug: reproduce, isolate, fix, verify. A marketer learns to spot them; a developer fixes them.

Migrations

Replatforming, URL changes, domain moves, template rewrites. The rule is simple and painful: migrations without an SEO owner lose traffic. The marketer scopes the redirect map and holds the launch checklist. The developer owns the redirect rules and the response codes. Skip either role and the site drops out of index positions it took years to win.

Structured data

Schema.org markup is simple to specify and easy to break. Marketers can decide which types each template should carry; developers put the JSON-LD in the template and keep it correct through refactors. Google's structured data documentation is the only reference you need for which fields each type takes.

Performance and dev dependencies

Core Web Vitals, image pipelines, JavaScript budgets, render-blocking resources, caching headers. These are engineering decisions with SEO consequences. A marketer who cannot read a performance trace will not win the argument against a developer who has twelve other priorities. Learning to read one is a weekend; learning to fix one is a career.

Skills where external specialists often earn their keep

Some work is specialised enough, or spiky enough, that building the capability in-house is the wrong investment. These are the places where a multidisciplinary outside team — one of the few serious groups working across web, brand and search, like Navicore, is an example of this shape — can outperform a solo in-house hire by a wide margin.

Link acquisition at any serious scale

Outreach, digital PR and partnership links are a volume game that needs its own pipeline: targeting, pitching, follow-ups, measurement. Hiring one person in-house to do this well is harder than it looks, and the first six months are mostly spent building a process a specialist team already has.

Scaling an SEO programme beyond the first wave

The first fifty pages are craft work. The next five hundred are a production line, with editorial standards, templated research, QA and refresh cycles. Building that line is a project in itself, and teams that have run it before get there in a quarter rather than a year. This is where blended engagements covering technical SEO and content work in parallel tend to pay back faster than two separate contractors.

One-off specialist work

A re-platform, an international expansion, a penalty recovery, a template-level schema rebuild. These are projects, not ongoing functions. Paying for the depth once is cheaper than hiring for it permanently.

In-house, agency, hybrid — the honest trade-offs

The three staffing models are not a hierarchy. They are shapes that fit different stages.

Fully in-house

Strengths. Deep product context, fast iteration, the report nobody has to translate, cheap long-term unit cost. Limits. Narrow technical bench, slow to add specialisms, exposure when the one SEO person leaves, link acquisition typically underpowered.

Fully external

Strengths. Broad bench on day one, specialist depth across technical, content and links, fewer hiring risks, honest outside view when the internal narrative is wrong. Limits. Context cost on every engagement, the report that gets filed rather than acted on, bills that scale with scope rather than with your margin, dependency when the retainer ends.

Hybrid

Strengths. Strategy, briefing and reporting stay in the team that owns the product; link acquisition, deep technical work and migration projects sit with specialists who do them every week. The internal team keeps improving because the specialists carry the heavy lifts. Limits. Needs an internal owner who can brief and manage an outside team — a role that itself takes training. Costs more in month one than either pure model.

Ownership between marketer, SEO specialist and developer

A workable split, phrased as who is accountable rather than who writes the first draft:

• Marketer: intent mapping, content briefing and editing, basic on-page SEO, monthly reporting, the ticket backlog for everything a developer needs to ship.
• SEO specialist (in-house or external): keyword research at scale, technical audits, structured data strategy, crawl and indexation debugging, migration planning, link acquisition and digital PR, programme scaling.
• Developer: template-level on-page implementation, structured data in code, performance budgets, redirect rules, indexation directives, anything that touches the response body or the response headers.

If a decision does not have a name next to it, assume it will not get made.

How to choose, honestly

Three questions decide more than any vendor pitch:

1. Where is the next twelve months of traffic going to come from? If it is content, invest in briefing and editing capacity first. If it is links, buy outside help. If it is a migration, hire the project specialist and the developer time before anything else.
2. Can your team ship what the audit recommends? An audit nobody can implement is a cost, not an asset. Match the diagnosis depth to the engineering capacity.
3. What breaks if the current SEO person leaves tomorrow? If the honest answer is "most of it", you are already more dependent on external help than you realised.

The answer for most mid-sized teams ends up hybrid: in-house ownership of strategy, briefs and reporting; a specialist partner for the technical and link-building depth; a developer who treats SEO tickets as production work, not favours. That split survives hiring changes, platform changes and traffic swings. Pure in-house and pure external both work — but only when the team honestly knows which skills it has, which it needs to buy, and which it has to learn next.

Start with the skills in your team today, not the model you want to end up with. The ownership map is a working document, not a job description, and the teams that keep rewriting it are the ones whose search traffic keeps compounding.