What's an SEO? The Person Behind the Roster Card
Ask what's an SEO and the useful answer is a seat, not a channel. In hiring language, an SEO is the person who decides what a site should say, gets it built, and proves the gain in search. They sit between marketing and engineering, ship small changes weekly, and are measured on qualified organic demand rather than on traffic alone. The title confuses people because it names a channel, not a craft.
If you are hiring, the roster card below is the job description you actually need.
Full time · hybrid
- Role
- Owns organic search as a channel, not as a task list
- Reports to
- Head of growth or marketing, with a dotted line to engineering
- Daily output
- Tickets, drafts, briefs, one decision per day
- Scorecard
- Qualified organic demand, shipped-fix rate, assisted pipeline
What's an SEO in one line?
An SEO is a practitioner who chooses which pages a site should have, makes those pages findable, and measures whether the right people arrive. They brief writers, file tickets with developers, read search data, and defend trade-offs. The deliverable is not a report — it is a set of changes that stay changed.
Why the title confuses everyone
Search engine optimisation names a channel, so the title reads like "email" or "social". Channels are places; roles are sets of decisions. That mismatch is why one job ad asks for a writer, another for a developer, and a third for a data analyst, all under the same heading.
The practical consequence is bad hiring. Teams interview for tool knowledge, then discover after three months that the hire cannot get anything shipped, because the real bottleneck was never knowledge of tools.
There is a second confusion: many people doing the work are not called SEOs. Content leads, product marketers and front-end developers all make search decisions daily. The title is a job family at best, and a specific seat at worst.
So when someone asks what an SEO is, the honest answer describes a seat: a person with a scope, a reporting line, a weekly output and a scorecard. That is what the rest of this page sets out.
The roster card, field by field
Four fields decide whether the seat works. Fill them in that order, and the interview writes itself.
Role
Owns the organic channel end to end: what gets published, what gets fixed, what gets measured. Not "helps with SEO". If the seat cannot say no to a page, it is not a role, it is a queue of favours.
Reporting line
Most often growth or marketing, with a real working relationship to engineering. If the seat reports somewhere with no access to release cycles, every technical ticket will lose to feature work.
Daily output
Briefs, drafts, tickets, one clear decision. The visible output is small and specific. Anyone claiming to "do strategy" all week without artefacts is describing meetings, not work.
Scorecard
Qualified organic demand, share of planned fixes shipped, assisted pipeline. Traffic alone rewards the wrong pages; position alone rewards the wrong keywords.
One week on the calendar
The shape of the week matters more than the job description. This is a realistic split for an in-house seat at a site with a weekly release.
Roughly half the hours are making things; the other half is deciding what to make and proving it worked. Candidates who cannot describe that split have usually done one half only.
How the seat is measured without gaming it
Traffic is the easiest number to move and the least useful on its own. A page about a broad concept can triple sessions and sell nothing. A single comparison page can convert steadily on a thousand visits a month.
So the scorecard pairs a demand measure with a delivery measure. Demand asks whether the right queries are growing. Delivery asks whether the planned work actually shipped, because that is the part the person controls week to week.
Three numbers we like: impressions on commercial-intent queries, share of planned fixes that reached production, and assisted pipeline attributed to organic landing pages. All three are readable from tools you already own.
Add one qualitative check: can the person explain last month's movement in one paragraph, with a ticket number as evidence? If not, the scorecard is being read by people who cannot interpret it.
Four questions that sort the candidates
Ask these in order and listen for specifics. A strong candidate names pages, tools, dates and outcomes. A weak one stays at the level of principles.
- Show me a page you changed and what happened after.Looking for: the before state, the specific edit, the wait, the result. Vague answers usually mean the person reported on work rather than did it.
- How do you decide what not to publish?Looking for: a filter. Anyone can generate twenty ideas; the seat exists to kill eighteen of them for a reason.
- What do you do when a developer says the fix cannot ship this quarter?Looking for: a negotiation with a smaller version attached, not escalation. The best answer is usually a partial fix that still passes acceptance.
- Which number would you refuse to be measured on, and why?Looking for: judgement about incentives. A candidate with no answer has not thought about how the role gets gamed.
Three things this seat should not own
Every channel's copy
If the same person writes ads, emails and landing pages, search becomes the leftover hour. Scope it to the pages that earn organic demand.
Paid media budget
Blending paid and organic under one owner hides which lever moved. Keep the budgets separate even when one person advises both.
Web releases
Owning deployment turns the role into operations. Better to sit in the release review and file checks than to be on call for it.
None of this is about seniority. It is about whether one person can be accountable for a channel while three other teams change the product underneath them.
Hiring the seat, or renting it
If you are building the team, use the roster card as the brief and the four questions as the filter. Expect a six to ten week search for a good mid-level hire, and budget for the first month to be mostly reading.
If the title still feels abstract, Whats Is SEO? explains the discipline the seat belongs to, in the same plain terms.
If hiring is not realistic this year, rent the seat. We run the weekly cadence for teams without a search hire, including the briefs and the acceptance checks, and we hand over the roster card so an internal hire can take it later.
Either way the work is concrete: decide what a page should say, make it findable, and show the change in the data. Our On-Page SEO Services cover the middle of that sentence, which is where most seats spend their week.
Need the seat filled this quarter?
Send us the page you are proudest of and the one you cannot fix. We will tell you what the role would actually do in your first ninety days.
Questions hiring managers ask
Is an SEO the same as a content marketer?
Overlapping, not identical. Content marketers own a narrative and a calendar; an SEO additionally owns indexability, page structure and query mapping. In small teams one person holds both, which works until publishing volume rises.
Do they need to code?
Not full-stack, but they must read HTML, understand status codes, canonicals and rendering, and write a reproduction step a developer can act on. Without that, every technical conversation becomes a handover.
How senior should the first hire be?
Senior enough to say no to stakeholders and to run a queue alone. That is usually mid-level plus three years. A junior hire without a senior above them tends to produce volume and very little ranking movement.
What should the first thirty days look like?
Crawl the site, read three months of search data, meet the release owner, and publish nothing. The first output should be a prioritised list of ten changes, not a content plan.
Can this be a part-time seat?
Yes, for sites under a few hundred pages with a stable template. Below twenty hours a month the work becomes reactive, and reactive search work rarely compounds.
How do we know the hire is working out?
Look at shipped-fix rate and at whether the person can explain movement with evidence. Ranking gains take a quarter; delivery pace tells you in a month whether the seat is functioning.
Should the role sit in marketing or product?
Marketing if the site is mostly content. Product if the site is an application with templates and releases. The deciding factor is who controls the pages, not where the budget sits.