What Does an SEO Do?
"What does an SEO do?" is a question about a person, not a channel. An SEO is the specialist who decides which search queries a site should answer, then changes pages, content and links until the site answers them better than the alternatives. The job is part analyst, part editor, part project manager. It is not a dashboard, and it is rarely one person doing all three well every single week.
What does an SEO do in a single day, in one answer?
An SEO spends the day on four things: reading data to see what changed, editing pages so they match what people search for, briefing the content or links the site still lacks, and telling the business what it means. The visible output is a short list of decisions plus the pages and briefs that carry them.
One day, four blocks
A day in the seat is less glamorous than the job title suggests, and more measurable than most marketing roles. The pattern below repeats with variations: Monday looks like Thursday, the queries change. If someone cannot describe their week in blocks like this, they are probably managing a calendar rather than a channel. The wider definition of the discipline sits in Whats Is SEO? if you need the vocabulary first.
Read the graph before the inbox
Impressions moving without clicks means the title is wrong for the query. Clicks moving without inquiries means the page is winning the wrong visitor. Indexation drops and new crawl errors get flagged the same morning, not at the end of the month, because a deindexed template can cost more traffic in a week than a quarter of content earns.
Edit the page that is nearly winning
The highest-return hour of the week is usually spent on a page sitting in positions eight to twenty. It already has demand and partial trust. Rewriting the title and the opening paragraph, adding the specification table buyers need, and linking it from two stronger pages moves it faster than publishing a new article on the same topic.
Brief what the site does not have
A page cannot be edited into existence. The afternoon goes to the missing pieces: a content brief for a writer, a page skeleton for a template, or an outreach list for the sites that should be citing the page. A good brief names the query, the intent, the sections in order, the internal links and the next step the reader should take.
Write down what shipped
Changes nobody recorded cannot be attributed later. The last block turns the day into a handoff: what went live, what it should move, which developer ticket is still open, what the owner needs to decide. This is also where a bad week gets admitted early instead of being discovered in the quarterly review.
What an SEO actually produces
The job is judged on artefacts, not activity. These four appear in every healthy engagement, in this order, and each one answers a question the business will ask sooner or later.
| Deliverable | What is inside | Who reads it | Cadence |
|---|---|---|---|
| Demand map | Query clusters, intent, which page answers which cluster, and the gaps | Owner and content lead | Quarterly |
| Audit and fix list | Blocked templates, speed, duplicate titles, orphan pages, priority order | Developer, with dates | Once, then refreshed |
| Page brief or rewrite | Query, outline, entities, internal links, proof, call to action | Writer and designer | Per page |
| Monthly read | Sessions, inquiries, positions by cluster, what changed and why | Owner, in plain language | Monthly |
If only one of the four exists, it is usually the audit, because audits are easy to sell and hard to argue with. An audit on its own changes nothing. The demand map decides what is worth doing, the briefs do it, and the monthly read keeps it honest.
Who an SEO works with, and what crosses the border
Most of the role is translation. An SEO rarely ships a page alone; they hand a decision to someone who can. The interface is where work either survives or quietly dies, so it is worth naming what each side owes the other.
Developer
- Gets
- A ranked fix list with examples and acceptance checks.
- Owes back
- Effort estimate and a shipping date.
- Artifact
- Ticket with before and after URLs.
Writer and editor
- Gets
- A brief with the query, the outline and the proof required.
- Owes back
- A draft that answers the query in the first 150 words.
- Artifact
- Draft, then a tracked edit of the live page.
Designer
- Gets
- The page skeleton: sections, table, comparison, next step.
- Owes back
- A layout that keeps text in HTML, not in images.
- Artifact
- Component spec for the template reuse.
Paid media
- Gets
- Which phrases converted organically, and which pages they landed on.
- Owes back
- Query tests that prove demand before content spend.
- Artifact
- Shared query sheet with cost per inquiry.
Sales and support
- Gets
- Question maps built from real objections and tickets.
- Owes back
- The phrasing buyers actually use on calls.
- Artifact
- Objection list folded into page FAQs.
Owner or marketing lead
- Gets
- One page of decisions: invest, stop, wait.
- Owes back
- A resource ceiling and a named approver.
- Artifact
- Quarterly plan with named owners.
Want the seat filled, not another audit?
Send the site and the target phrases. We will reply with the first four weeks of work, in order.
What an SEO is not
Buying placements in bulk is a transaction with a short half-life. Earning references from sites that already publish in your category is slower and survives an algorithm update.
Editing a title is the visible tip. The work underneath is deciding which page deserves the query at all, which is an editorial decision.
Publishing forty thin pages does not beat one page that answers the question properly. Volume without intent mapping creates pages that compete with each other.
Positions decay while competitors publish. The role is maintenance plus improvement, which is why one audit a year rarely holds.
The first thirty days in the seat
If you are hiring or onboarding, this is the sequence that produces evidence quickly without pretending a quarter has passed.
- Week one, access and baseline. Search Console, analytics, the CMS, and a screenshot of the numbers as they are today, so nobody argues about the starting point later.
- Week one, technical pass. Index coverage, templates, speed, canonicals, internal links from the strongest pages. The result is a fix list ordered by traffic at risk, not by how interesting the bug is. That document is the start of SEO Audit Services in any serious account.
- Week two, demand map. Clusters by intent, mapped to existing URLs, with every gap labelled as edit, merge or build.
- Week three, the first three rewrites. Pages already close to page one. Small edits, fast feedback, visible movement.
- Week four, the reporting rhythm. One page a month, four lines per cluster: what moved, why, what is next, what is blocked.
How to tell a good one in an interview
Ask for a page they improved and the change log behind it. Then ask what they removed. Strong candidates talk about deletions, consolidation and pages they decided not to build, because the job is as much about refusing work as shipping it.
- Which page did you improve last, and what did you change first? A specific page and a specific edit beats a framework.
- What did you decide not to publish? Shows judgment about cannibalisation.
- How do you know a change worked? They should name a window, a metric and a control.
- What do you need from a developer? Reveals whether they can write a ticket instead of an opinion.
- Where does paid search fit? Good answers treat ads as demand research, not a rival.
Questions about the role
Is an SEO the same as a content writer?
No, though the overlap is real. A writer produces the page; an SEO decides which page should exist and what it must answer, then edits it afterwards. Small teams often fold both into one person, which works if the writing is not rushed.
Can one person cover a whole site?
One site of a few hundred pages, yes, if the template work is done once and the content plan is narrow. Past that, the role splits: technical, content and links are different weeks of work.
What does an SEO need from the owner?
A named approver, a realistic publishing ceiling and access to the people who talk to customers. Without the third, the page outlines are guesses.
How do I measure whether the work is real?
Look for a change log with dates, a monthly read that admits what did not move, and inquiries per page trending in the right direction. Positions alone flatter everyone.
Agency or in-house?
In-house wins when the work is continuous and the product changes weekly. An agency wins when you need several specialisms at once and cannot justify three hires. The failure mode either way is nobody owning the change log.
Which tools does the role need?
Search Console, analytics and a crawler cover most of it. Tools speed up diagnosis; they do not decide what to do. A spreadsheet of decisions is worth more than a wall of charts.