SEO Job Description

An SEO job description is the document where most hiring mistakes start. I have reviewed dozens and the good ones share one thing: they define the problem before the task. A job description that begins with 'we need to improve our organic visibility' sets a different expectation from one that opens with 'perform keyword research'. The first attracts problem-solvers; the second attracts task-doers. You want both, but the framing determines who applies.

When I write a job description now, I start with one sentence of context: 'Our website gets 50,000 organic visits a month and we want 80,000 in twelve months.' Then I list the responsibilities that directly tie to that goal: research queries that drive revenue, fix technical barriers like slow load times, coordinate with the content team on briefs, and report weekly to the head of marketing. Responsibilities are concrete, not abstract.

The role also requires a specific mix: analytical (analyse search volumes, click-through rates), technical (crawl depth, schema), and communication (convince a developer to change a URL structure). I have seen job descriptions that list ten tool names and no outcome. That is a red flag. If you are hiring an [SEO Specialist](/seo-specialist/), give them a problem, not a tool list. If the role is [client-facing](/client-seo/), include stakeholder management. The best job descriptions I have read are those that let a candidate imagine their first week. They answer 'what will I actually be doing?' and 'how will I know I am succeeding?'.

An SEO job description stops being a generic HR document and becomes a decision tool in three situations.

First, when you are hiring your first SEO person. If the company has never had an SEO role, the job description is the only thing screening candidates. I have seen startups write 'must know everything about SEO' — that gets no one good. Instead, write what the business needs most: is it content-driven SEO for a blog, or technical cleanup for an e-commerce site? Pick one. My rule: if the job description is shorter than 300 words, you have not thought hard enough.

Second, when the role is for an agency versus in-house. Agency SEO usually means managing multiple clients, each with different goals, and presenting monthly reports. In-house means owning one site deeply and collaborating with product and engineering. If you write a hybrid description, you attract candidates who are good at neither. I would write two separate descriptions if you are unsure. Link to [SEO Consultant](/seo-consultant/) for agency roles, and [SEO Manager](/seo-manager/) for in-house strategy leads.

Third, when you are scaling from one SEO to a team. Now you need separate job descriptions for different levels. A junior SEO executes tasks; a senior SEO plans strategy; an SEO manager leads people. I made the mistake of using the same template for all three and ended up with a junior who expected to set strategy. The job description must differentiate scope and autonomy. For example, a junior might have 'assist with keyword research', while a senior has 'own the content roadmap'. A counter-argument: some companies prefer flexibility and cross-training. That works for a team of three, but when you have five, clarity prevents overlap.

Two mistakes I made when writing SEO job descriptions.

First, I over-emphasised tool proficiency. My early job descriptions listed 'Ahrefs, Moz, Screaming Frog, Google Analytics required'. I thought that showed rigor. What it actually did was filter out excellent candidates who had used different tools but could learn quickly. I now list tools as 'familiarity with one SEO tool suite' and spend the word count on strategic tasks. The best SEO hire I ever made had never used Ahrefs before; she learned it in a week and taught me three workflows I did not know.

Second, I ignored the communication dimension. SEO is not a solo role. You need to coordinate with content writers, developers, product managers, and sometimes sales. If a job description only covers technical audits and reporting, you will hire someone who cannot explain their recommendations to a non-technical stakeholder. I once hired a technically brilliant SEO consultant who could not articulate why a site migration needed redirects to the CTO. The project stalled for three months. Now I include 'explain technical concepts to non-technical audiences' as a key responsibility. Link to [outsource SEO](/outsource-seo/) if you think communication is not your team's strength — sometimes it is better to hire an agency who already has that process.

Third, I assumed SEO was a junior role. It can be, but senior SEO professionals exist and command higher salaries. Job descriptions should reflect the level: an [SEO freelancer](/seo-freelancer/) may own their process, while an entry-level SEO follows instructions. I used to write generic descriptions that attracted only those who did not know their own value. Now I am specific about experience and expectation.