What Is an SEO in Marketing? The Seat, the Reports, the Output
An SEO in marketing is a person, not a channel. The phrase names a seat on the team: someone who owns how the site earns unpaid search traffic, reports into marketing leadership, and delivers a specific set of artifacts that other people can use. That is different from "we do SEO," which describes an activity, and from "SEO is our best channel," which describes a result. When a job listing says "an SEO," it is describing headcount with a remit, a reporting line and a handoff to content, paid and engineering. Confuse the seat with the tactic and you end up hiring a report instead of a person, or a writer when you needed an analyst.
We can staff the seat, fill it temporarily or hand it over.
What Does "an SEO" Mean on a Marketing Team?
An SEO is the person who owns how a site is found in unpaid search. They sit in marketing, report to whoever owns demand or growth, and deliver a small set of reusable artifacts: a query map, a technical fix list, briefs that writers can follow, and a monthly read on what search is producing. They are a translator between commercial intent and page markup.
The Seat Card: What It Actually Says
Think of the role as a place card at a table. It tells everyone where the person sits, what they are responsible for and who they talk to. Four items belong on it, and a hiring process that skips any of them usually produces a frustrated first year.
The first item is the remit: organic search performance for a defined set of pages and markets. The second is the reporting line: who this person escalates to when a decision needs authority. The third is the output: the artifacts other teams consume. The fourth is the boundary: what this seat does not own, such as paid media budgets, brand voice or development sprints.
Write those four lines before writing the job description. A description built from a list of tools attracts people who know tools. A description built from a remit attracts people who can move a site.
Where the Seat Sits in the Org Chart
There is no universal position, but there are three common placements, and each one changes what the person can actually get done. The diagram shows the pattern that works most often for small and mid-sized B2B teams: the seat sits beside content and paid, under one demand owner, with a dotted line to engineering.
Solid lines are reporting. Dashed lines are cooperation that needs a written request, not a favour.
The three placements
Under a marketing director, the seat has a clear commercial owner and usually a fixed budget for content. Under a growth or demand lead, the seat is closer to paid and tends to get faster experiments and better attribution. Under a founder in a small company, the seat is often a fractional consultant who reports directly and has no internal peers, which is fast but lonely.
Placement determines the hardest part of the job. Reporting to marketing makes content easy and engineering hard. Reporting to a product or engineering lead makes deployment easy and messaging hard. Pick the reporting line based on which bottleneck you currently have, and revisit it when the bottleneck moves.
What the Seat Delivers
The deliverables are the part of the role that survives a change of personnel, so they matter more than the job title. A person who produces these five things is doing the job even if their title says something else. A person who produces none of them is not, regardless of seniority.
| Deliverable | Shape of the artifact | Cadence |
|---|---|---|
| Query map | Which query clusters belong to which page, which pages compete with each other, and which queries are conceded. | Quarterly |
| Technical fix list | Ranked list of crawl, index, speed and duplicate issues with the exact URL and the expected effect. | Monthly |
| Page briefs | A one-page brief per new or rewritten page: intent, outline, internal links, proof required. | Per page |
| Search performance read | What earned impressions, what converted, what changed and why, in plain language. | Monthly |
| Market and competitor notes | Which competitors appear on which queries, and what they publish that we do not. | Quarterly |
| Launch checklist | The pre-deploy list used by engineering so no new page ships without titles, links and markup. | Per release |
Notice that only one of these is a report. The rest are instruments: things other people use to make decisions. That is the practical test of whether a seat is real. If the person spends the whole month assembling dashboards that nobody reads, the seat has been installed as a monitoring service rather than an owner of outcomes.
The Three Interfaces
An SEO seat is defined as much by its handoffs as by its tasks. These are the three relationships that decide whether the role produces anything.
With content
Brief in, draft outThe seat supplies intent and outline; the writer supplies voice and proof. The handoff fails when the brief is a keyword list instead of an argument.
Rule: no brief ships without a stated intent and three competitor examples.
With paid
Query data both waysPaid sees which phrases convert before a page ranks; organic sees which queries bring free traffic after. Sharing both makes the budget argument factual instead of tribal.
Rule: one shared query sheet, reviewed every two weeks.
With development
Ticket in, deploy outEngineers need a reproducible defect, not a principle. The seat translates "our pages are slow" into a specific URL, a measurement and an acceptance test.
Rule: every ticket includes a before-and-after check.
What the Job Is Not
- Not a content factory. If the seat is expected to write every page alone, the team has hired a writer with an SEO label and will lose the analytical half of the role.
- Not an emergency ranking hotline. Nobody can move a position on request. The seat can explain what is missing, and it can build the conditions, but it cannot dial a rank.
- Not a tool administrator. Licences and dashboards are overhead. If the calendar is full of exports, the seat is doing reporting work rather than search work.
- Not a solo owner of growth. Search depends on product, pricing and sales follow-up. A seat that is blamed for all demand will leave within a year.
How to Hire for the Seat
The interview should test judgment about pages, not recall of acronyms. Four questions separate candidates who can hold the seat from candidates who have read about it.
Ask them to fix a real page
Give them one of your URLs and the query it should win, with thirty minutes and no tools beyond a browser. Listen for what they check first. Strong candidates look at whether the page is indexed, what the first paragraph promises, and whether a competing page on your own site says the same thing.
Ask what they would stop
A candidate who can name three things your team should stop doing has a point of view. A candidate who lists forty things to start has a backlog. The seat needs the first kind of judgment, because the constraint is usually attention rather than ideas.
Ask about a failure
Search work fails often: a migration loses traffic, a rewrite does not move, a link campaign goes nowhere. What you want to hear is how they detected it, what they told stakeholders, and what they changed. Evasion here is a warning sign.
Ask who they would talk to first
The answer reveals whether they understand the interfaces. Good answers mention the person who can deploy changes, the person who writes, and the person who talks to customers. Bad answers mention a tool.
When to Fill the Seat From Outside
Most companies under about fifty pages do not need a full-time hire. They need a defined block of specialist time, a query map and a working relationship with whoever deploys the site. That is a fractional arrangement, and it works because the artifact is what matters, not the attendance.
We take that seat on a retained basis: the query map, the fix list, the briefs and the monthly read, delivered as if we were internal but without the headcount. For teams whose main market is a city or a region, the seat often starts with Whats Is SEO?, because the query set is closer to purchase and the feedback loop is faster.
If you are still working out the vocabulary before the organizational question, read Local SEO For Small Business first. It covers the practice; this page covers the person who holds it. Most hiring mistakes come from mixing the two, and most of those are avoidable with one clear job description.
A Short Example
A software company hired an SEO into a content team and gave the seat a remit of "grow organic traffic." Six months later, traffic had grown eight percent and pipeline had not moved. The seat was producing four blog posts a month, all well written, none of them about the queries buyers ask before a demo.
The problem was the placement, not the person. Content reported to a brand lead who measured output volume, and engineering requests went through a product manager who had never met the SEO. The seat had no interface with sales, so the query map was built from keyword tools rather than from call transcripts.
Three changes fixed it. The seat moved under the demand owner, the monthly read switched from sessions to demo requests from organic pages, and a standing twenty-minute call with two sales reps was added. The blog cadence dropped to one post a month and the rest of the time went into comparison pages. Pipeline from organic search was measurable within two quarters.
Same person. Different card at the table.
Need the Seat Filled, Not Just Advised?
Tell us the remit and the reporting line you have in mind. We will tell you whether it is a hire, a fractional seat, or a problem that a rewrite would solve.