What an SEO specialist does: a competency map
What an SEO specialist is and does: a competency map across technical, content, data and communication, with three levels and the questions to ask when hiring.
By Roozbeh Nazari · CEO
The short answer to "what is an SEO specialist" is: the person who plans, measures and improves how findable a website is in search engines and, increasingly, in AI search surfaces. The long answer is about how loosely the title is used. The same words can describe someone with three years of technical audit experience at an agency, or the person at another company who "also looks after SEO" alongside social media. This article builds a competency map you can use when hiring an SEO specialist or choosing an agency: four axes, three levels on each, and a question that makes each level visible. We covered what SEO consulting includes as a service in what SEO consulting is; here we look at the person and the competence, not the service.
An SEO specialist is not a title but a four-axis skill set
In practice, the best answer to the question is where a person stands on four axes. The first is technical: crawling, indexing, site architecture, speed and structured data. The second is content: reading search intent, building topic clusters, seeing what is missing at page level. The third is data: reading Search Console and analytics, finding the cause of a drop, turning a hypothesis into something measurable. The fourth is communication and prioritisation: writing a request a developer can act on, explaining to a manager why this work comes first. Few people are expert on all four, and they do not need to be; what matters is knowing which axes the job requires and seeing honestly where the candidate sits on those.
The technical axis: crawling, indexing, architecture
At entry level, a person can read the page indexing report in Search Console, understands robots.txt and canonical logic, and can explain in basic terms why a page is not indexed. At intermediate level, they crawl a site end to end with a crawler, read log files, find redirect chains and hreflang errors on multilingual sites, and can say which Core Web Vitals metric is failing in field data. At advanced level, they test what the crawler actually sees on JavaScript-rendered sites, plan a site migration without losing rankings, and speak the developer's language: which header, which status code, which build step. The question that separates the levels is "How would you find out why pages on this site are not indexed?" Entry level names tools; advanced level describes a diagnostic sequence.
The content axis: intent, clusters and page-level gaps
At entry level, content work means looking at keyword volume and writing title tags. Intermediate level understands why different pages answer the same query, builds a topic cluster as a pillar with subpages, and sees which questions existing content leaves unanswered. Advanced level knows the sector's sensitivities such as YMYL, can say which sentence cannot be written in a regulated field like healthcare, and explains which content format AI search surfaces need in order to cite you as a source. The distinguishing question here is not "why isn't this page ranking?" but "which question is this page trying to answer, and is that answer already given better on another page?"
The data axis: finding the cause, not reading the report
The data axis is the most overstated and least tested one in candidates. Entry level reads the traffic and click graph. Intermediate level separates whether a drop came from an algorithm update, a technical change or seasonality by comparing dates and segments, and connects organic traffic to conversions. Advanced level questions the measurement setup itself: is the conversion event defined correctly, is locale-based reporting in place on a multilingual site, what are the limits of the attribution model. The test is simple: give the candidate a real Search Console export and ask them to describe what they see in fifteen minutes. Report readers and cause finders separate here.
The communication axis, and how much one SEO specialist can carry
The fourth axis is missing from most competency lists, yet it determines the outcome more than any other. Nothing an SEO specialist finds produces a result unless a developer implements it and a manager prioritises it. Entry level lists findings; intermediate level ranks them by impact and effort and writes each as a task; advanced level defends a challenged recommendation with evidence, or accepts a valid objection. This brings us to a frequent question: can a single SEO specialist carry a company's entire SEO need? On a small or mid-sized, single-language site, one person at intermediate level on the technical and content axes carries most of the work; developer support and content production come from other resources. On a multilingual site in a regulated sector, or a large e-commerce site, advanced level on all four axes is rarely found in one person; that is where a team or a properly scoped external partner comes in. We handled the choice between an agency and an individual consultant in agency or SEO consultant with a decision matrix.
What certificates, titles and portfolios prove
When using the competency map, separate three kinds of evidence. A certificate shows that the basic concepts of a tool or platform are known; an analytics certificate is meaningful on the data axis, but a crawler certificate on the technical axis does not prove someone can diagnose a site. A title usually reflects the company's naming policy rather than seniority; a two-year "senior" and an eight-year "specialist" can appear in the same job listing. A portfolio is the strongest evidence, but only when the person's own contribution can be isolated: which decision did they make, which finding did they find, which result did they measure. Cross these three kinds of evidence with the four axes and you have a framework that genuinely tests a candidate before the interview.
How to use the competency map
Using the map takes three steps. First, distribute your need across the four axes: a new site build weights the technical axis, stalled content production the content axis, traffic without revenue the data axis. Second, write the level you need on each axis and prepare the question that makes that level visible; the sections above give one example per axis. Third, match answers to evidence: Google's own guidance recommends asking for references from previous work when choosing an SEO specialist or agency, and staying away from anyone who guarantees rankings; we add asking what the candidate's own contribution was to the work they show. We describe how we work as a team and which axes sit with which roles on our approach page, and the scope of each service on our services page. The right question is not "who is the best SEO specialist" but "which level on which axis does this job need, and who can prove it".