Field note 07 · what the job looks like
What Does a SEO Do? A Working Day, Block by Block
What does a SEO do all day? Mostly five things, in roughly this order: read the numbers, repair a page, write a brief, fix internal links, and log what changed. The job is not a mysterious growth ritual. It is a production schedule with a diagnostic habit attached, and every block leaves a document behind that someone else can use.
FIRST
What does a SEO actually do in a day?
A SEO diagnoses why pages are not being found, changes the pages that are wrong, writes briefs for new ones, connects them with internal links, and measures the result. The day produces documents, not promises: a diagnosis, a change list, a brief, a link map and a log entry.
The shape of the day
Most people imagine the job as one long stretch of keyword research. In practice the keyboard time splits into five short blocks, and the blocks are ordered by dependency: you cannot rewrite a page before you know which page is failing, and you cannot measure a change you did not record.
Two things are worth noticing in that picture. First, more than half the day is spent producing something another person needs — a developer, a writer, a client. Second, no block is longer than two hours, because the attention that search work requires degrades quickly when it runs uninterrupted for a whole morning.
09:00 to 17:30, block by block
Diagnose before touching anything
The first block is reading, not writing. Search console queries, crawl reports, pages that lost impressions this week, pages that gained them. The question is narrow: which three pages deserve attention today, and what is broken about them?
A useful diagnosis separates three causes. Is the page not indexed? Is it indexed but ranking for the wrong query? Or is it ranking and failing to convert? Each cause leads to a completely different block of work, and confusing them is how teams spend a month on the wrong page.
By the end of the block there is one page of notes naming the pages, the evidence and the suspected cause. No adjectives, no scoring, no dashboard screenshots.
Repair the page that is closest to working
This is the block most people picture when they ask what does a SEO do: editing a page. Not redesigning it. The title gets the query in the first four words. The first heading restates it. The opening paragraph answers it in plain language. A table replaces a paragraph that was doing a table's job.
Occasionally the repair is structural: a category page that lists products with no explanation of the class, or a set of forty near-identical pages that should be one page and thirteen variants. Those are the days when the output is a merge plan rather than an edit.
The work is shipped as a change list with before and after, so a developer can apply it without a meeting and a reviewer can see exactly what moved.
Write a brief someone else can execute
New pages need a brief, and a brief is not a keyword plus a word count. It names the query, the reader, the decision the reader is trying to make, and the questions that must be answered before the page can end. It also names what to leave out, which is the part most briefs skip.
A good brief includes the internal links the page should receive and the two or three pages it should link out to. That detail saves an hour of rework later, when the article is finished and nobody remembers where it belongs in the structure.
Writers should be able to start without asking a single clarifying question. If they cannot, the brief is not finished — it is a topic.
Wire the pages together
Internal links are the part of the job that gets skipped when the calendar is full, and they are usually the cheapest source of movement on an existing site. The block starts with the orphan list — pages with no internal links pointing at them — and works through the three or four that matter.
Each link needs a reason: this page answers a question the other page raises. Anchor text describes the target page, not "click here". Links that go nowhere useful get removed, because a navigation menu with forty items distributes attention across forty pages and none of them win.
The output is a map of source URL, target URL and anchor, which doubles as the change list for whoever edits the template.
Look at the numbers and write the log
The last half hour is bookkeeping, and it is the block that makes the other four measurable. Each change gets a line: date, URL, what changed, what should happen, and the date to check. Without that line, next month's diagnosis starts from memory.
The check is also where the job stays honest. A change with no effect is information. A change with a negative effect is more information. A change nobody recorded is a rumour.
Tomorrow's queue gets written before the laptop closes, three items at most, so the next morning starts with a decision instead of a search for one.
The five things the day actually produces
If you are hiring, briefing or evaluating this work, ask for the artefacts rather than the activity report. Five documents cover almost everything a working day should leave behind.
| Output | What it looks like | Who uses it | What makes it good |
|---|---|---|---|
| Diagnosis note | One page: three URLs, the evidence, the suspected cause | You, and whoever approves the work | It names pages, not themes |
| Change list | Field, before, after, reason, owner | Developer or template editor | It can be applied without a meeting |
| Content brief | Query, reader, outline, exclusions, links | Writer, editor, reviewer | A writer can start with no questions |
| Link map | Source URL, target URL, anchor text | Anyone with template access | Every link has a stated reason |
| Log entry | Date, URL, change, expected effect, check date | Future you, and the monthly report | It makes the next diagnosis possible |
None of these five documents is impressive on its own. Together they are the difference between a job that compounds and a job that restarts every quarter with a new theory about why traffic fell.
What five of those days look like as a week
Friday afternoon is when the individual blocks become a report. This is a template we use with clients: four working days that produce changes, one day that reads them. It fits on a single page and takes twenty minutes to fill.
The Friday row is the one people skip. Reading a week of changes and deciding what to drop is the actual management of search work; without it, the next week inherits every unfinished idea from the last one and the queue grows faster than the site does.
Four things the job is not
01 It is not one big project with an end date
There is no moment when a site is "done", because pages decay, competitors publish and queries shift. The work is a schedule, not a sprint. A project framing is useful for a template migration and misleading for everything else.
02 It is not a solo activity with no dependencies
Almost every change needs a developer, a writer, a designer or a founder to approve it. The person doing the work spends a real share of the day waiting, explaining and re-prioritising. Any description of the job that leaves that out is a job advert, not a reality.
03 It is not the same as writing content
Writing is one block of the day. Choosing which page should exist, what it must answer, and which page should link to it is separate work that happens before the writing starts. When those decisions are skipped, the writing is wasted effort with good grammar.
04 It is not measured by position alone
A top-three position for a query nobody buys from is a vanity number. The day is measured by pages receiving entrances and enquiries attributed to organic entry, with position used only to explain why those two moved.
How to tell whether the day is working
Leading signals, visible in weeks
- More pages receiving at least one organic entrance each week
- Fewer orphan pages in the crawl
- Queries where the page ranks 8 to 20 starting to move
- A log with an entry for every shipped change
Lagging signals, visible in quarters
- Enquiries attributed to organic entry
- Revenue influenced by pages that existed before the work
- Share of the category query set where you appear at all
- Cost per enquiry compared with paid search
Judge the person by the leading column and the programme by the lagging one. Confusing the two is how a good month of work gets cancelled three weeks before it would have shown up.
Where our day starts
We begin with the 09:00 block, because a diagnosis is the only honest way to decide what to change. That is the substance of Whats Is SEO?: a crawl, a query review, a page-by-page cause, and a change list ordered by effort rather than by enthusiasm.
If the vocabulary is still new, the plain-language primer on SEO Audit Services explains what the work is for before it explains how it is done.
Want to see the log before you commit?
Ask for a sample week: the diagnosis, the change list and the Friday read. It is the fastest way to judge how someone works.
One week that changed a site's quarter
A furniture component manufacturer had been paying for "SEO" for eight months and could not name a single change made to the site. There was no log, no brief, no link map: only a monthly PDF of positions.
We ran the five blocks for one week. Monday's diagnosis found 47 pages with no internal links and 19 pages competing for three phrases. Tuesday merged six of them. Thursday adopted the orphans from the category pages. Friday's read produced three items for the following week.
Questions about the job
Is this the same every day?
The blocks repeat; the content does not. One day the repair is a title, the next it is a category structure. The rhythm is deliberate, because it keeps diagnosis ahead of editing instead of letting enthusiasm choose the work.
How much of the day is meetings?
In-house, roughly a fifth, usually with developers and content owners. Agency-side it is closer to a third, because the explanation is part of the deliverable. Anyone claiming zero meetings is either very senior or not shipping changes.
Can one person do all five blocks?
Yes for a site under a few hundred pages. Past that, the brief and the links split off first, because they are the two blocks that scale with page count. The diagnosis should stay with one owner, or it stops being consistent.
What should I ask for in a weekly update?
Three things: which pages were changed, what the change was, and when it will be checked. A weekly note with those three answers is worth more than a dashboard with forty metrics and no decisions.
Does the job change with AI tools?
The drafting gets faster; the diagnosis and the judgement do not. Tools help produce variants of a title or an outline. Deciding which page deserves the work, and which pages should be merged away, is still a person reading evidence.