The role, drawn as a card
What's an SEO? A Real Persona Card for the Search Role
When someone asks what's an SEO, they are almost never asking about the acronym. They are asking what kind of person holds that job, what the days actually look like, and how you can tell a careful one from a confident one. Short answer: an SEO is the person who makes a website legible to search engines and genuinely useful to the people typing the queries, then proves the traffic earned is worth having.
What's an SEO, in one sentence?
An SEO is a search specialist who improves a site's technical health, content and authority so it ranks for the queries its buyers type, and who measures the result in qualified organic sessions rather than vanity positions. The role sits between engineering, editorial and marketing, and it is judged on traffic quality and revenue, not on rankings alone.
Replies usually within one business day. No sales script, just questions about your site.
Fig. 1 — the five fields that define the role
Field notes
The card, field by field
A persona card is a briefing tool, not a job description. It answers the five questions a hiring manager, a founder or a freelancer really needs answered before money changes hands: what is this person responsible for, what do they touch each day, what do they have to be good at, who do they depend on, and how will anyone know the work is going well. Below, each field is unpacked in plain language.
Job title: organic search strategist
Job boards use many labels: SEO specialist, organic growth lead, search strategist, technical SEO. They describe the same discipline with different weighting. A technical-leaning title means schema, crawl paths and Core Web Vitals occupy most of the week. A content-leaning title means briefs, editorial calendars and internal linking dominate. Ask which weighting a specific role has before you compare candidates, because two people with identical titles can spend their weeks in completely different files.
A normal day, honestly
Mornings usually start with monitoring: index coverage, a rank sample, error logs, and whatever a developer shipped overnight. The middle of the day is research and writing: turning a messy keyword list into intent clusters, then into briefs a writer can actually use. Afternoons are the handoff hours, where recommendations become tickets, screenshots and acceptance criteria instead of slide decks. Very little of the job is a dramatic reveal. Most of it is small, checkable changes repeated for months.
Skills that actually matter
Three skills carry most of the weight. First, reading a log file or a crawl report well enough to know which pages deserve attention. Second, writing a brief so precise that a non-specialist can produce a page that answers a query. Third, explaining a technical fix to a developer without implying their architecture is stupid. Everything else, including tool fluency, is learnable in a fortnight. Judgement about which twenty tasks to skip is what separates a senior operator from a busy one.
Who they collaborate with
The role has no direct authority over the pages it must improve, so influence is the real currency. Developers control rendering and page speed; designers control template hierarchy; writers control whether the answer appears in the first paragraph; sales controls which queries are worth winning. A good operator brings evidence to those conversations, which is why a structured Whats Is SEO? engagement is often the first thing they run. An audit converts opinion into a ranked list everyone can agree on.
How the work gets judged
Three signals matter more than anything in a dashboard: whether the pages that should be indexed are indexed, whether organic sessions are converting at a rate close to your other channels, and whether non-brand impressions are rising quarter over quarter. Brand impressions can flatter a report, because they mostly prove people already knew the name. A serious review asks what share of organic revenue came from queries the business did not rank for a year ago. If nobody can answer that, the measurement layer needs fixing before the content layer does.
Fig. 2
A day in the workflow
The timeline below is a composite of a mid-level in-house role at a company with a real product and a modest content budget. It is not glamorous, and that is the point: the visible output of a good day is usually three decisions and one clarified ticket, not a new campaign.
Fig. 2 — a composite working day, not a job advert
What the timeline hides is the waiting. Search results move on a lag measured in weeks, and most of the job is keeping decisions consistent while that lag plays out. Someone who cannot hold a plan steady for ninety days will keep restarting it, and restarts are the most expensive thing in the discipline.
If you are hiring, ask a candidate to walk through this exact day and name what they would cut. The answer tells you more than any certification, because prioritisation is the actual skill being bought.
Fig. 3
Five questions that reveal a real practitioner
These five questions work in an interview, in a contractor call, or in your own head when you are deciding whether to trust a proposal. None of them can be answered well with a memorised statistic. Each one forces a description of a decision.
A candidate who answers all five with examples from their own projects is worth a second call. A candidate who answers with tools and definitions is probably reciting a course.
Calibration
Four things people get wrong about the role
Mistake 1: treating them as a traffic vending machine
Organic search is a compounding channel, and the first ninety days are mostly groundwork with unremarkable numbers. Hiring someone and then judging them at day thirty by sessions is like judging a foundation by the number of walls. Set the review window before the contract starts, and agree on what the first month is supposed to produce: an audit, a fixed indexation baseline, a query map, five briefs. Those are real deliverables even when the chart is flat.
Mistake 2: confusing activity with leverage
Publishing forty thin posts is activity. Rewriting one category page that already earns impressions but converts badly is leverage. The second kind of work is harder to put in a weekly report, which is why it gets skipped. A useful habit is to ask, for any proposed task, which existing URL it improves. If the answer is none, the task is probably a new page nobody needs.
Mistake 3: assuming the role is junior because the tools are cheap
The software is genuinely affordable now, which makes the job look entry-level. But the expensive part is never the crawl; it is the judgement about which crawl findings matter for this particular business this quarter. That judgement takes years and is not sold in a subscription.
Mistake 4: skipping the definition conversation
Half the friction in a first engagement comes from two people using the same words differently. Spending twenty minutes on what search optimisation actually covers prevents that, and a plain explainer such as SEO Audit Services is a faster way to align a stakeholder group than a kickoff slide. Once everyone means the same thing, the plan gets shorter.
Our side of the card
What we bring to that role
We are not a marketplace of freelancers. The person who audits your site is the person who briefs the content and the person who sits on the developer call, which removes the handoff where most recommendations quietly die. Engagements usually start with a two-week teardown: crawl and index review, template-by-template intent mapping, and a ranked fix list with effort estimates attached.
From there we run a monthly cycle of briefs, on-page work and internal linking, with a short written readout that names the decision taken and the metric it should move. If your team writes in-house, we can operate as the review layer instead of the production layer. If you have no writer at all, we cover production end to end, including the technical queue and the briefs that feed it.
What we will not do is promise a position. Nobody controls the index. What we can promise is a documented plan, a predictable cadence, and numbers you can audit yourself.
Want a second opinion on your current organic setup before you hire?
Quick answers
Questions people ask about the role
Is an SEO a job or a service?
Both. Inside a company it is a role with a salary and a manager. Outside, it is a service you buy by the month or by the project. The work is the same; the reporting line is not. Deciding which shape fits you depends on whether you have someone who can hold the plan steady between agency calls.
Do I need an SEO if I already run paid ads?
Only if you want a channel that gets cheaper over time. Paid buys impressions now and stops when the budget does. Organic builds a set of pages that keep earning after the invoice clears, which is why most mature advertisers eventually fund both.
How long before the work shows up?
Technical fixes can move indexing within days. Content and authority work usually read clearly in eight to sixteen weeks, and the compounding part takes two or three quarters. Anyone quoting a two-week ranking timeline is guessing or selling.
Can one person cover technical and content?
Often yes, at small scale, if they are senior enough to delegate production. The failure mode is a single generalist who is excellent at one half and avoids the other. Ask which half they avoid; every honest practitioner has one.
What should a first month look like?
A baseline you trust, a query map tied to real buying language, a ranked fix list, and one or two changes shipped to production. If the first month is entirely a slide deck, the engagement is already behind.
How is success reported?
One page, three numbers: qualified organic sessions, organic-assisted revenue, and index health. Everything else is context for those three. If a report cannot fit on one page, it is usually hiding the answer.