Hiring Guide

How to Hire an SEO Specialist

Hiring an SEO specialist starts with naming your actual problem: a site search engines struggle to crawl and understand, or pages nobody has a reason to rank. Then run an audit exercise on a real site with planted issues and ask for the fixes ranked by impact against effort. Anyone promising specific positions by a date is guessing.

Where do you find SEO specialists worth hiring?

Agency-side consultants have seen dozens of sites and know which fixes actually moved something, which is exactly the pattern recognition an in-house team lacks. In-house specialists from content-heavy or retail sites bring depth on one property and usually know how to work with developers. The rarest and most useful profile is the developer who drifted into technical work on crawling, rendering and site structure, because they can implement rather than only recommend. This field has a very loud public layer, so treat published case studies as claims to verify rather than evidence, and always ask what the person personally changed. Describe the stack and the mandate in the [SEO specialist job description](/job-descriptions/seo-specialist).

What should the job posting tell a specialist about the site?

The technical reality and the route to shipping. Name the content management system, the framework, whether pages are rendered in the browser or on the server, and how often you deploy. Say who writes code, how a change gets into a release, and how much developer time the role can count on. State whether the mandate is technical, content-led or both, whether they own the content calendar or advise it, and what your position is on paid links so nobody arrives with the wrong playbook. List what has already been tried and failed. Specialists judge a role almost entirely on whether their recommendations will ever ship, and if you are also fixing job pages, say whether the [careers page builder](/careers-page-builder) is in scope.

How do you screen an SEO specialist?

Give them a real site to audit, ideally a staging copy with planted problems: a blocked path in the robots file, a canonical tag pointing at a redirect, duplicate title patterns generated by a template, thin pages produced at scale, and important pages with almost no internal links pointing at them. Ask for a prioritised list with impact against effort, what they would measure, and what they would need from a developer. The signal you are reading for is prioritisation and business reasoning, not detection. Strong candidates ask about the business goal before recommending anything and put the template-level fix above the one-page fix. Weak candidates return an unedited tool export with severity labels attached.

What does the interview process look like?

Four stages with a developer involved early. A screen on mandate and stack. The audit review, with an engineer in the room to test whether the candidate can explain a change precisely enough to be implemented. A search-intent conversation: given this query, what kind of page should exist, what does the results page tell you about what readers expect, and what would you not build. Then an expectations conversation about what they would commit to in the first quarter, which should be about diagnosis, fixes shipped and content published rather than positions. Ask about a site migration that went badly, since anyone experienced has one. Keep the [SEO specialist interview questions](/interview-questions/seo-specialist) tied to the audit they submitted.

How long does it take to hire, and how do you close them?

The applicant pool is wide and quality varies enormously, so the written audit is not optional and it will do most of your filtering. Expect to review many superficially similar profiles before two or three separate themselves. What closes a good specialist is evidence that work will actually ship: your deploy cadence, a developer who will take their tickets, and a content budget. They will also want to know whether leadership understands that organic results build over months rather than weeks. Say it out loud in the offer conversation. The same discipline applies to finding them, so treat your own [candidate sourcing software](/candidate-sourcing-software) searches as a targeted exercise rather than a broad job advertisement.

The hiring process for a SEO Specialist

  1. 1
    Name the problem first Decide whether the site has a technical crawling and structure problem, a content and demand problem, or both, because that decides who you hire.
  2. 2
    Check the route to shipping Confirm developer time, deploy cadence and content capacity before hiring, since recommendations that never ship drive specialists away fast.
  3. 3
    Source across agency and in-house Approach agency consultants for breadth and in-house specialists for depth, and treat developers with search experience as a rare find.
  4. 4
    Run a planted-issue audit Give a staging site with template-level and page-level problems and grade the prioritisation rather than the length of the findings list.
  5. 5
    Put a developer on the panel Have an engineer judge whether the candidate can specify a change precisely enough for somebody to implement it.
  6. 6
    Set honest expectations Agree what the first quarter delivers in fixes, content and diagnosis, and refuse any candidate who commits to specific positions.

What to look for

  • Prioritises by business impact rather than by the severity labels a tool assigned
  • Explains a required change precisely enough for a developer to implement it
  • Separates a crawling and indexing problem from a lack of genuine search demand
  • Reads intent from what already ranks rather than from search volume alone
  • Has run or repaired a site migration and can describe what broke
  • Measures by page type and segment instead of one sitewide trend line
  • Declines to promise positions and states what they will commit to instead

Red flags to avoid

  • !Commits to specific search positions by a specific date
  • !Audit is an unedited tool export with no prioritisation or business reasoning
  • !Recommends buying links or using private link networks
  • !Attributes every fluctuation to an algorithm update with no further analysis
  • !Cannot say which changes on a cited case study were theirs
  • !Has never filed a ticket or worked directly with a developer

Hiring a SEO Specialist? See the ATS built for it

FAQ

Frequently asked questions

Should I hire a technical or a content-focused SEO specialist? +
Diagnose first. If pages are slow to be discovered, duplicated by templates or invisible to crawlers, hire technical. If the site is healthy but has nothing worth ranking, hire content-led and pair them with writers. Many candidates claim both and are genuinely strong in one. The audit exercise usually reveals which side they actually think in.
Is an agency better than an in-house hire? +
An agency gives breadth and immediate capacity, which suits a one-off audit, a migration or a fixed project. An in-house specialist builds context, sits in planning conversations and fights for the fixes to be prioritised, which is where most long-term value comes from. Many teams use both: an in-house owner with agency support for specialised work.
How long before organic results appear? +
Months rather than weeks, and it varies with competition, the site's existing authority and how quickly fixes actually ship. Technical corrections can show up faster; new content competing against established pages takes considerably longer. Judge the early period on diagnosis quality, fixes released and content published, and be suspicious of anyone offering a firm timeline.
How do I verify a candidate's case studies? +
Ask what the site was doing before, which specific changes they made, who implemented them, what else changed at the same time and how they measured the result. Then look at the site yourself. Vague answers about strategy paired with a rising chart usually mean they were adjacent to the work rather than responsible for it.
Should the SEO specialist own the content calendar? +
They should shape it, and someone should own it. Handing full editorial control to a search specialist tends to produce pages built for queries rather than for readers. Excluding them entirely produces content nobody finds. The workable arrangement is joint topic selection, with search input on structure and demand, and editorial judgment on whether the piece deserves to exist.
Built for recruiters & hiring teams

See how much faster your team could hire

Get a personalized walkthrough of Pitch N Hire on your own roles and workflow. No slides, no obligation.

Prefer to talk? Book a demo · View pricing

Free 1-user plan · No credit card · Talk to a real hiring expert

One Hiring Infrastructure.
Zero Tool Chaos.

Demos are consultative. We respect privacy and enterprise
governance. No lock-ins.

Start free Book demo