Six question sets built for the employer side: 45+ questions on diagnosis, technical SEO, keywords, analytics, and risk, each with why it is worth asking and what a good answer contains, plus a scorecard. Download as DOCX.
The hardest part of hiring an SEO analyst is that you probably cannot grade the answers. I have sat on the employer side of this interview, and the uncomfortable truth is that the subject rewards fluency: a candidate who names tools confidently and talks about algorithm updates sounds identical to one who has actually diagnosed a traffic collapse at two in the morning. The candidate knows you cannot tell. That asymmetry is the whole problem.
So this page is not a list of questions to memorize. It is a set of questions with a stated reason each one is worth asking and a note on what a good answer contains, so you can listen for a shape of reasoning instead of for correct vocabulary. You do not need to learn SEO before the interview. You need to notice whether the candidate diagnoses before they prescribe.
At FirstHR, we build for small businesses that hire without an HR department, where the owner runs the whole search alone. Below are six downloadable question sets, a 1-to-5 scorecard with an eight-item red-flag checklist, and the one paid exercise that settles this hire faster than any second interview. Pair it with the SEO analyst job description if you are still writing the posting.
TL;DR
Interview an SEO analyst on five things: diagnosis, technical understanding, keyword and intent judgment, measurement honesty, and risk awareness. Ask what they would check before they recommend, make them tie traffic to leads, and ask which tactics they refuse to use. Then confirm with a short paid work sample on real data. National pay for the closest federal classification runs a median of $78,760 (BLS OEWS, May 2025). Six question sets and a scorecard below, downloadable as DOCX.
What to Assess in an SEO Analyst
Assess five competencies: diagnosis, technical understanding, keyword and intent judgment, measurement honesty, and risk awareness. Knowledge of SEO is table stakes and easy to fake in conversation. Judgment about messy data and murky causation is the actual job, and it is what separates an analyst who earns their salary from one who produces monthly charts nobody acts on.
Diagnosis comes first because it is the most testable. Ask why a page might be missing from search and a strong candidate checks whether it is indexed before proposing anything. A weak one starts recommending keywords. You do not need to know the right answer to hear the difference between verifying and guessing, which is why this is the competency to lead with.
Measurement honesty is the one most owners skip and later regret. An analyst who reports impressions and average position as wins can show you six months of upward charts while the leads stay flat. Ask which metric they refuse to report on its own, and listen for whether they volunteer the limits of their own data before you ask for them.
The Five Question Categories
The questions below are grouped into five categories plus a scorecard. Each targets a different failure mode, so a candidate who is strong on technical questions and vague on measurement is telling you something specific about how the job would go. Ask across all five rather than staying where the conversation is comfortable.
Core Analyst Questions
Ask every candidate
Diagnosis, first ninety days, and the honesty questions. Tests whether the candidate reasons about organic search or only describes it. Start here.
Technical and Indexing
Site, migrations, tickets
Canonicals, redirects, migrations, and index control, plus how they write a ticket a developer will accept. Weight it when the role touches the site.
Keywords and Intent
Where the money is won
Whether they pick winnable terms and read the results page as an intent signal, or chase a famous keyword that will not pay for a year.
Analytics and Reporting
Can you trust the report?
Traffic versus outcomes, attribution limits, and what goes in your monthly one-pager. The easiest set for a non-technical owner to grade.
Risk and Communication
What they refuse to do
Link quality, generated content, and whether they push back on an unrealistic ask in the interview instead of in month three.
Scorecard and Red Flags
Score, do not guess
A 1-to-5 rubric across six competencies plus an eight-item red-flag checklist, so the decision rests on evidence. The asset most question lists skip.
Weight the Sets to the Job You Are Actually Filling
Every candidate gets the Core set and the Analytics set, because diagnosis and measurement honesty matter regardless of the role. Add Technical when the analyst will file tickets to a developer or you have a migration coming. Add Keywords when they will steer what gets written. Add Risk for every finalist without exception, since that is where the expensive damage hides. Finish with the Scorecard, which is what keeps a persuasive interview from making the decision on its own. If the role is closer to implementation than analysis, weight Technical and read the SEM and SEO specialist posting instead.
45+ Questions and a Scorecard to Download
Download all six as a single Word document, or copy the sets you need. Each follows the same structure: when to use it, the questions with a stated reason for asking and what a good answer contains, what to listen for, and space for notes. The last file is the scoring rubric and red-flag checklist, and every other role in the hiring templates library follows the same shape.
Download All 6 SEO Analyst Question Sets
Core, technical, keywords, analytics, risk, and a 1-to-5 scorecard with red flags. All in one DOCX.
Set 1: Core SEO Analyst Questions
The set to ask every candidate. Diagnosis, first two weeks, honest limits, and what they need from you. Tests whether the candidate reasons about organic search or only describes it.
Core SEO Analyst Questions
CORE SEO ANALYST INTERVIEW QUESTIONS
Candidate: __
Business: __
Interviewer: __
Date: _
HOW TO USE THIS SET
This is the set to ask every candidate, whatever else you add. It tests whether
the candidate diagnoses organic search or only describes it. Ask 6 to 8 of these,
listen against the "good answer" notes, and score on the rubric in Set 6. You do
not need to be an SEO to run this. You need to hear specific reasoning.
QUESTIONS
1. Explain crawling, indexing, and ranking to me as if I have never heard the
terms.
(Why ask: it is the fastest test of real experience, and the analyst will be
explaining exactly this to you every month.
Good answer: three separate stages. A page can be crawled and not indexed,
or indexed and not ranked, and those are different problems with different
fixes. Uses plain language without talking down.)
2. One of our pages is not showing up in search at all. Walk me through the first
thirty minutes of finding out why.
(Why ask: this is the request you will actually make, probably in your first
month.
Good answer: checks whether the URL is indexed before theorizing. Then works
down a list: robots.txt, a noindex tag, a canonical pointing somewhere else,
a redirect, thin or duplicate content. Separates "not indexed" from "indexed
but ranking on page nine," which is a completely different problem.)
3. Our organic traffic dropped 30 percent last month. How do you find the cause?
(Why ask: a drop is when you will need this person most.
Good answer: asks what changed on our side first, deploys, redesigns,
migrations, before blaming an algorithm update. Segments the drop by page,
by query, and by device rather than looking at one total. Checks whether
tracking itself broke.)
4. What would you look at in the first two weeks on our site, and in what order?
(Why ask: it reveals whether they have a method or a checklist they downloaded.
Good answer: business first, what we sell and who buys, then measurement
integrity, then indexation, then the pages that already earn money. A
candidate who opens with a 200-point technical audit is optimizing for
looking thorough.)
5. Tell me about a recommendation you made that did not work.
(Why ask: search work fails often, and you want someone who notices.
Good answer: a specific project, a specific reason it failed, and what they
changed. Ownership rather than "the algorithm changed.")
6. How do you decide what to work on when everything looks broken?
(Good answer: ranks by expected impact against effort, and can say out loud
which fixes they would skip. Names a page or a page type, not a metric.)
7. What do you need from us to do this job well?
(Why ask: a good analyst has requirements. A candidate with none has probably
never had to ship anything.
Good answer: analytics access, developer time, subject-matter input for
content, and a decision-maker who can approve changes.)
8. What would make you say we should not invest in SEO right now?
(Why ask: it is the honesty question. Search is not right for every business
or every timeline.
Good answer: names real conditions, a brand-new domain with a two-month
sales target, a product nobody searches for, a site nobody can change.)
WHAT TO LISTEN FOR
•Diagnosis before recommendation
•Plain language, not tool names used as answers
•Willingness to say "I do not know, here is how I would find out"
•Business framing: leads and revenue, not just traffic
NOTES
__
__
Set 2: Technical SEO and Indexing Questions
Canonicals, redirects, migrations, index control, and how they write a ticket a developer will accept. Weight this set when the role touches the site or a domain move is coming.
Technical SEO and Indexing Questions
TECHNICAL SEO AND INDEXING QUESTIONS
Candidate: __
Business: __
Interviewer: __
WHEN TO USE THIS SET
Use this set when the role touches the site itself: a large catalog, a recent
or planned migration, a site with an existing traffic problem, or any case where
the analyst will be filing tickets to a developer. Skip or shorten it when the
role is purely content and reporting, and say so in the job posting instead of
testing for skills the job will never use.
QUESTIONS
1. What is a canonical tag, and when would you use one?
(Good answer: it tells search engines which version of near-duplicate content
is the one to index. Gives a real case: filtered category pages, tracking
parameters, printer versions. Knows it is a hint, not a command.)
2. What is the difference between a 301 and a 302, and why does it matter to us?
(Good answer: permanent versus temporary. A 302 where a 301 belongs can leave
the old URL as the indexed one. Mentions redirect chains as a real cost.)
3. We are moving to a new domain next quarter. What is on your list?
(Why ask: a botched migration is the single most expensive SEO event a small
business can suffer.
Good answer: a full URL inventory and a one-to-one redirect map before
launch, Search Console set up for the new property, internal links updated
rather than left to redirect, and a monitored comparison after launch. A
candidate who says "just redirect everything to the homepage" has told you
everything you need to know.)
4. How would you audit a site with twenty thousand URLs when most of them are
near duplicates?
(Good answer: crawls it, groups by template rather than by URL, and decides
which templates should exist at all. Talks about consolidation and index
control, not about fixing every page.)
5. How do you decide a page should be noindexed rather than improved or deleted?
(Good answer: has a rule. Pages that serve users but should not compete in
search get noindexed; pages that serve nobody get removed and redirected.)
6. Our developer has four hours a month for you. What do you spend them on?
(Why ask: at a small business this is the actual constraint.
Good answer: picks the changes that unblock everything else, and batches
requests instead of trickling tickets.)
7. How do you write a technical ticket a developer will actually accept?
(Good answer: the change, the affected URLs, the expected result, and how to
verify it. Does not send a tool export and call it a ticket.)
8. What is the relationship between site speed and rankings, honestly?
(Why ask: it is a good honesty filter, because the popular answer overstates
it.
Good answer: speed is a real ranking input and a much bigger conversion
input, but it will not rescue a page that does not deserve to rank.)
WHAT TO LISTEN FOR
•Verifies before recommending
•Understands redirects and canonicals precisely, not approximately
•Budgets developer time as the scarce resource it is
•Writes for the developer, not for the audit report
NOTES
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Set 3: Keyword Research and Search Intent Questions
Whether they pick winnable terms and read the results page as an intent signal, or chase a famous keyword that will not pay for a year. This is where most of the budget is won or wasted.
Keyword Research and Search Intent Questions
KEYWORD RESEARCH AND SEARCH INTENT QUESTIONS
Candidate: __
Business: __
Interviewer: __
WHEN TO USE THIS SET
Use this set for any SEO analyst role, and weight it heavily when the analyst
will steer what gets written. Keyword judgment is where most of the money is won
or wasted, and it is the area where a confident candidate is hardest to tell from
a competent one. The questions below are written to force a specific answer.
QUESTIONS
1. Build me a starting keyword list for this business. Talk me through it out
loud.
(Why ask: it is a live work sample that costs you five minutes.
Good answer: starts with the business, what we sell, who buys it, what they
call it, what problem precedes the purchase. Pulls seed terms from sales
calls and support tickets before opening a tool. A candidate who starts by
naming a tool has skipped the only part you can judge.)
2. How do you decide a keyword is worth targeting?
(Good answer: four things together, search volume, difficulty relative to
our site's current authority, intent match, and what the current results
actually look like. Any one alone is a trap.)
3. A keyword has ten thousand searches a month and we rank nowhere. Should we
chase it?
(Why ask: the wrong answer here costs a year.
Good answer: usually no, not first. For a small site, a cluster of lower
volume, higher intent terms wins revenue sooner and builds the authority
that makes the big term reachable later. A candidate who says yes without
qualification is selling you a vanity project.)
4. The top ten results for a term are all listicles. What does that tell you?
(Good answer: the results are the intent signal. If every result is a
comparison list, a product page will not rank there no matter how good it
is. Match the format or pick a different term.)
5. How do you tell informational intent from commercial intent, and why do you
care?
(Good answer: informational terms build audience and links; commercial terms
produce leads. A small business usually needs commercial terms first and can
afford informational ones once revenue is coming in.)
6. Which keywords would you deliberately not target for us?
(Why ask: a candidate who wants every keyword has no strategy.
Good answer: names categories, terms we cannot win, terms that attract the
wrong buyer, terms owned by a marketplace or a directory.)
7. How do you group keywords into pages, and how do you avoid two of our pages
competing for the same term?
(Good answer: one page per intent, not one page per keyword. Recognizes
cannibalization and describes consolidating rather than adding.)
8. How would you find what our competitors rank for that we do not?
(Good answer: describes a gap analysis and, more importantly, says which
gaps are worth closing and which are not our business.)
WHAT TO LISTEN FOR
•Starts with the business, not with a tool
•Reads the results page as evidence of intent
•Prefers a winnable cluster over a famous keyword
•Can name what they would refuse to chase
NOTES
__
Set 4: Analytics, Attribution, and Reporting Questions
Traffic versus outcomes, attribution limits, and what belongs in your monthly one-pager. The easiest set for a non-technical owner to grade, because the wrong answers are wrong in plain English.
Analytics, Attribution, and Reporting Questions
ANALYTICS, ATTRIBUTION, AND REPORTING QUESTIONS
Candidate: __
Business: __
Interviewer: __
WHEN TO USE THIS SET
Use this set with every candidate. The word "analyst" is in the title, and this
is the part of the job that decides whether you can trust the monthly report.
It is also the easiest set for a non-technical owner to grade, because the wrong
answers are wrong in plain English.
QUESTIONS
1. Our organic traffic went up 40 percent and our leads stayed flat. What
happened?
(Why ask: this is the most common and most expensive reporting illusion in
the job.
Good answer: does not guess. Checks which pages and which queries grew, and
whether the growth is branded traffic, informational traffic with no buying
intent, bot traffic, or a tracking change. Ends with a hypothesis and a way
to test it, not with a reassurance.)
2. How do you separate an SEO result from a seasonal swing or an ad campaign
that was running at the same time?
(Good answer: year over year comparison for seasonality, segmentation by
channel and landing page, and honesty about what cannot be cleanly
attributed. A candidate who claims perfect attribution is overselling.)
3. What would go in a one-page monthly report for me, and what would you leave
out?
(Why ask: you are the audience. The answer tells you whether the reports will
be useful or decorative.
Good answer: a small number of outcome metrics tied to revenue, what changed
and why, and what happens next. Leaves out rank screenshots and vanity
charts. Volunteers to explain the misses, not just the wins.)
4. We currently measure almost nothing. What do you set up in week one?
(Good answer: verified Search Console, analytics with real conversion
tracking on the actions that make us money, and a baseline recorded before
any changes ship.)
5. How do you know a change you made actually caused the result?
(Good answer: talks about baselines, holdouts or staged rollouts where
possible, and the limits of a single-site before-and-after. Comfortable
saying "correlated, not proven.")
6. Which metric do you refuse to report as a success on its own?
(Good answer: impressions, average position, or raw sessions. Explains why
each moves without any business result behind it.)
7. Walk me through the last dashboard you built. What decision did it change?
(Why ask: it separates people who make charts from people who inform
decisions.
Good answer: a specific decision, made by a specific person, because of a
specific number.)
8. Our tracking has been broken for three months and nobody noticed. How do you
respond?
(Good answer: says so immediately and in writing, marks the affected period
as unreliable in the reporting, rebuilds the baseline, and adds a check so
it does not repeat. Concealing a measurement gap is a fireable habit.)
WHAT TO LISTEN FOR
•Distinguishes traffic from outcomes without prompting
•Volunteers the limits of the data
•Reports the misses as readily as the wins
•Ties a dashboard to a decision, not to a meeting
NOTES
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
What they refuse to do and why, how they judge a link, how they use generated content, and whether they push back on an unrealistic ask in the interview instead of in month three.
Risk, Ethics, and Communication Questions
RISK, ETHICS, AND COMMUNICATION QUESTIONS
Candidate: __
Business: __
Interviewer: __
WHEN TO USE THIS SET
Use this set with every finalist. An SEO analyst can do lasting damage to a small
business with tactics that look like progress for two quarters and then collapse,
and the owner is usually the last person to find out. These questions test whether
the candidate protects the business and whether they can explain themselves to
someone who is not an SEO. Both are part of the job.
QUESTIONS
1. What SEO tactics would you refuse to use, and why?
(Why ask: the refusals tell you more than the recommendations.
Good answer: names specific practices they will not touch, bought link
networks, mass unedited generated pages, doorway pages, cloaking, and can
explain the business risk rather than reciting a rule. A candidate with no
refusals has either never seen the downside or does not mind it.)
2. How do you evaluate whether a link is worth having?
(Good answer: relevance to our business, whether the linking page has real
readers, and whether the link would exist if search engines did not. Vague
answers about "high authority sites" usually mean a paid network.)
3. How do you use AI writing tools in your work?
(Why ask: the honest answer is somewhere between "never" and "for
everything," and you want to hear where.
Good answer: describes research, outlining, and first drafts with real human
editing and subject-matter input, plus a clear view of the risk of
publishing large volumes of unreviewed content. Names what they would not
automate.)
4. How would you explain a technical fix to a developer who does not care about
SEO?
(Good answer: leads with the user or business impact, gives the exact change
and the affected URLs, and makes it verifiable. Does not appeal to authority
or forward a tool report.)
5. Explain to me, in plain language, why a change you want will take four months
to show a result.
(Why ask: you will need this explanation for yourself, and possibly for a
partner or a board.
Good answer: no jargon, an honest mechanism, and a stated checkpoint before
the four months are up.)
6. What would you do if I asked for a result you thought was impossible in the
time I gave you?
(Good answer: says so directly, in the interview, right now. Offers what is
achievable in that window instead. A candidate who agrees to your
unrealistic timeline in the interview will agree to it again in month three
and then miss it.)
7. Tell me about a disagreement with a manager or client about SEO strategy.
(Good answer: a real disagreement, a specific argument made with evidence,
and a professional outcome either way.)
8. How do you keep up with changes in search?
(Good answer: names primary sources and, more importantly, describes testing
on real sites. Following commentary is not the same as knowing.)
WHAT TO LISTEN FOR
•Has refusals and can justify them commercially
•Explains without jargon when asked to
•Pushes back on an unrealistic ask in the interview itself
•Treats generated content as a tool with a risk, not a strategy
NOTES
__
Set 6: SEO Analyst Scorecard and Red Flags
A 1-to-5 rubric across six competencies, an eight-item red-flag checklist, and a line for the work-sample score, so the decision rests on written evidence rather than on who interviewed best.
SEO Analyst Scorecard and Red Flags
SEO ANALYST SCORING RUBRIC AND RED-FLAG CHECKLIST
Candidate: __
Business: __
Interviewer: __
Date: _
HOW TO SCORE
Score each area from 1 to 5 immediately after the interview, while it is fresh.
Anchor every score to something the candidate actually said. If more than one
person interviews, each scores independently before anyone discusses, so the
loudest opinion does not set the group's. Use the same rubric for every
candidate, and keep the completed sheets.
Rating scale:
5 = Strong, specific evidence 4 = Solid evidence 3 = Some evidence
2 = Weak or mixed evidence 1 = No evidence or red flags
SCORING AREAS
Diagnosis: finds causes methodically instead of guessing
Strong answers share one property: the candidate establishes a fact before proposing a fix. Weak answers skip to the recommendation, because recommendations are what candidates rehearse. Three of the highest-signal questions are worked through below, with what each answer should and should not contain.
One of our pages is not showing up in search. Where do you start?
Strong answer: Checks whether the URL is indexed before theorizing about anything else, then works down a short list: blocked in robots.txt, a noindex tag, a canonical pointing elsewhere, an accidental redirect, or content too thin to earn a place. Separates “not indexed” from “indexed but ranking on page nine,” because those are different problems with different fixes.
Weak answer: Jumps straight to recommendations. Suggests adding keywords, building links, or rewriting the page before establishing whether the page is even in the index.
Our organic traffic rose 40 percent but leads stayed flat. What happened?
Strong answer: Refuses to guess and says what they would check: which pages and queries grew, whether the growth is branded, whether the new traffic has any buying intent, and whether conversion tracking changed. Finishes with a hypothesis and a way to test it.
Weak answer: Treats the traffic increase as the win and the flat leads as someone else's problem, or explains it away with “SEO takes time” without proposing a single check.
What SEO tactics would you refuse to use?
Strong answer: Names specific practices they will not touch and explains the commercial risk in plain terms: bought link networks, mass unedited generated pages, doorway pages. A strong answer connects the refusal to what it would cost you, not to a rule they were taught.
Weak answer: Says “I only do white-hat SEO” and stops. No specifics, no risk, and no sign they have ever had to decline a tactic that was working in the short term.
Push on every answer with the same two follow-ups: how would you check that, and what would change your mind? A strong candidate has a method for both. A weak one repeats the original answer more slowly. The signals below are what to watch for across the whole conversation.
Diagnosis signals
Verifies a fact before recommending a fix
Segments a change by page, query, and device
Says “I do not know” and then says how to find out
Measurement honesty
Separates traffic from leads without prompting
States the limits of attribution out loud
Reports the misses as readily as the wins
Communication
Explains indexing without jargon on request
Writes tickets a developer will accept
Ties every number to a decision you have to make
Red flags
Guarantees a ranking or a date
Answers with tool names instead of reasoning
Accepts an unrealistic timeline without a word
One more habit worth adopting: ask the candidate to explain something back to you in plain language, and mean it. If they cannot make indexing understandable in the interview, they will not make the monthly report understandable either, and you will end up approving work you do not follow. Read the broader interview red flags alongside the role-specific ones.
The Paid Work Sample That Settles It
One short paid exercise tells you more than a second interview, because analytical judgment shows up in written work and almost never in conversation. Interviews reward fluency; this job rewards care. Give every finalist the same task, pay for the time, and grade it against criteria you wrote before the first submission arrived.
Give everyone the same file
One export of real or realistic search data, with a deliberate flaw left in it: a broken tracking period, a duplicated page, or a branded query inflating the totals.
Cap it at two to three hours
Say the cap out loud and pay for the time. A longer exercise filters for who is unemployed, not for who is good.
Ask for a written recommendation
Not a dashboard. One page: what they see, what they would do first, and what they would need from you to do it.
Grade against criteria set in advance
Did they find the flaw, did they prioritize by impact, and could you follow the reasoning without asking a question? Score it before you look at the next one.
The deliberate flaw is the whole point. Leave a broken tracking period, a duplicated page set, or a branded query inflating the totals somewhere in the data, and see who notices without being told to look. A candidate who reports confidently on a broken dataset has shown you exactly how the next twelve months of reporting will go.
What the submission shows
What it tells you
Found the flaw unprompted
Verifies before reporting; the single best predictor in this role
Prioritized by impact, named what to skip
Can work inside a small budget instead of listing everything
Wrote one page you could follow
Will produce a monthly report you actually act on
Stated what they would need from you
Has shipped work before and knows the constraints
Delivered a polished dashboard, no recommendation
Optimizes for looking thorough; a common and costly pattern
Keep the scope to two or three hours and say the cap out loud, because a longer exercise filters for who has free time rather than who is good. Treat the result as one input on the same evaluation form you use for the interview, not as a separate verdict that overrides everything else.
Fair, Legal, and Structured Interviewing
A fair interview and an accurate one are the same interview. Asking every candidate the same job-related questions, scored on the same rubric, keeps you inside employment law, reduces bias, and produces a better hire at the same time. For a subject as easy to bluff as SEO, structure is also your only real defense against a persuasive candidate.
Ask about the job, not the person
Federal anti-discrimination law, enforced by the EEOC, prohibits basing a hiring decision on protected characteristics, and questions that probe them create risk even when they are asked as small talk. Keep away from age, race, religion, national origin, sex, pregnancy or family plans, disability, and genetic information. Marketing interviews drift into personal territory easily because the conversation is casual by nature, so watch for the friendly traps: where are you originally from, do you have kids at home, how long have you been in the field. Every question on this page is written to stay on the work. This is general information, not legal advice.
Ask every candidate the same core set
A structured interview, where every candidate answers the same prepared questions and is scored on the same rubric, predicts on-the-job performance better than a free-flowing conversation, and it makes the decision far easier to defend. For an SEO hire this matters more than usual, because the subject rewards confident talkers and most owners cannot grade the technical content themselves. Write the core questions before you meet anyone, ask them in the same order, and take notes as you go. The kits on this page are built to be used exactly that way, unchanged, across every candidate.
Score independently, then discuss
When two or more people interview, each should fill in the scorecard alone before the group talks. This stops the most senior or most enthusiastic voice from anchoring everyone else, which is one of the most reliable ways a weak candidate gets talked into a job. Compare the written evidence first, then discuss where the scores disagree, because the disagreements are the useful part. For an owner interviewing alone, the scorecard still earns its place: it forces you to write down what the candidate actually said before your memory smooths it into an impression.
Keep a work sample job-related and consistent
If you use a paid exercise, and for this role you should, treat it as a selection procedure: give every finalist the same task, the same data, the same time, and grade it against criteria written before you see the first submission. EEOC guidance on employment tests and selection procedures is built around exactly that principle, that a test must be job-related and applied consistently. Pay for the time, keep the scope to two or three hours, and do not use candidate work in production unless you have paid for it and said so. This is general information, not legal advice.
Same Questions, Same Rubric, Better Decisions
A structured interview, where every candidate answers the same prepared questions scored against a consistent rubric, predicts on-the-job performance more reliably than an open-ended conversation, and asking the same job-related questions of everyone also keeps you within the EEOC rules against basing decisions on protected characteristics. If you add a work sample, EEOC guidance on employment tests and selection procedures asks that it be job-related and applied consistently, which is the same discipline for a different reason.
Keep every question tied to the work and avoid the friendly small-talk traps about age, family, origin, or religion. This is general information, not legal advice.
Hiring an SEO Analyst Without an HR Department
A large company puts an SEO candidate in front of a marketing director who can grade the technical answers cold. A small business puts them in front of the owner, who cannot, and who is making this call between everything else. That is not a reason to hire worse. It is a reason to change what you grade and to insist on evidence you can read yourself.
You cannot grade the answers, and the candidate knows it
This is the defining problem of hiring an SEO analyst without an HR department or a marketing lead. The subject is technical enough that an owner cannot tell expertise from fluency, and the candidate is aware of that from the first minute. Confident vocabulary wins interviews it should lose. The fix is not to learn SEO before the interview. It is to change what you are grading: every question in these kits comes with a note on what a good answer contains, so you are listening for a specific shape of reasoning rather than for correct terminology. Ask the question, listen for whether they diagnose before they prescribe, and write down what they said.
A bad SEO hire looks fine for two quarters
Most bad hires announce themselves quickly. This one does not. An analyst who buys links, publishes unreviewed generated pages, or reports impressions as growth can produce charts that go up for six months before the traffic collapses or the leads never arrive, and by then you have paid a salary and lost a year of compounding. That delay is why the risk questions and the red-flag checklist matter as much as the technical ones. Ask what they refuse to do, ask where links come from, and insist that the monthly report ties to leads. An analyst who volunteers the limits of their own data is worth more than one who never has a bad month.
The interview alone will not settle it, and the offer is its own job
For this role, a short paid work sample tells you more in two hours than a second interview does in one, so budget for it and give every finalist the same task. Once you choose someone, the work turns into hiring them properly: a written offer, the new hire paperwork, system and analytics access, and a first ninety days with a defined first deliverable. FirstHR covers that people side for a small business: send the offer for e-signature, run the onboarding workflow and paperwork, set up the access tasks, and keep the signed documents and interview records on the employee profile. FirstHR is an onboarding and HR platform, not an SEO or analytics tool, so pair it with those. Applicant tracking is coming soon to FirstHR.
The role title matters here too, because analyst and specialist are different hires that get advertised interchangeably. Decide which one you actually need before you interview, and say it in the posting. The comparison below is the practical version of that split.
Responsibility
SEO Analyst
SEO Specialist
Owns keyword research and competitor analysis
Runs audits and diagnoses traffic changes
Builds the monthly report and the recommendations
Implements on-page and technical changes weekly
Writes or edits the published content
At a small company one person often does both, and that works fine as long as you say so in the posting and interview for both. What fails is hiring an analyst and then expecting weekly implementation, or hiring a specialist and then asking why nobody can explain the traffic drop. Applicant tracking is coming soon to FirstHR.
What SEO Analysts Are Paid
There is no dedicated federal wage category for SEO analysts, so benchmark against market research analysts and marketing specialists, the classification that contains search marketing roles. Use the federal band as your reference point, then place your role inside it by seniority rather than averaging to the middle.
Needs supervision and a defined scope; often non-exempt
In-house SEO analyst
$78,760 (median)
The standard role; adjust for metro and industry
Senior or specialized analyst
$108,310 (75th percentile)
Measurement depth, ecommerce, or a large catalog
Top of the band
$155,480 (90th percentile)
Usually a lead or manager title, not an analyst
Publish a real range where pay transparency laws require one, and consider publishing it everywhere else too. Analysts research compensation professionally, and a posting with no number reads as an employer hoping to underpay. FirstHR is an onboarding and HR platform, not a payroll provider, so pair it with payroll for the compensation side.
From Interview to Onboarding
The interview is step one. Once you choose someone, the job becomes hiring them properly: a written offer, the new hire paperwork, analytics and site access on day one, and a first ninety days with one named deliverable rather than a vague ramp. For an analyst, day-one access is the difference between a fast start and three weeks of waiting on logins.
Prepare the same question set
Pick the kits that match the role, then ask the same core questions of every candidate so the comparison is fair and the notes are comparable.
Score on the rubric
Fill in the 1-to-5 scorecard right after each interview with evidence, and have every interviewer score alone before the group discusses.
Run the paid work sample, then offer
Give finalists the same short exercise, grade it against criteria set in advance, then confirm role, pay, and start date in writing with e-signature.
Onboard with access and a first deliverable
Analytics and site access on day one, a baseline recorded before any changes ship, and one named deliverable inside the first ninety days.
An offer letter template handles the offer, and an onboarding template gives the new analyst a structured first month. FirstHR connects the offer, e-signature, paperwork, access tasks, and onboarding workflow in one place, and keeps the signed documents and interview records on the employee profile, so a small business can run the whole hiring-to-onboarding path from one system. Applicant tracking is coming soon to FirstHR.
If the search turns up an adjacent fit rather than an analyst, the analytics manager and marketing specialist kits follow the same format, with the same scorecard discipline behind them.
Key Takeaways
Assess five competencies: diagnosis, technical understanding, keyword and intent judgment, measurement honesty, and risk awareness.
You are grading the reasoning, not the SEO: a strong candidate verifies a fact before recommending a fix.
Make every candidate tie traffic to leads, and ask which metric they refuse to report as a success on its own.
Ask what tactics they refuse to use; a candidate with no refusals will use whatever works this quarter and leave you the bill.
Run one short paid work sample on real data with a deliberate flaw in it, and see who notices unprompted.
Score six competencies from 1 to 5 with written evidence, independently, before anyone discusses the candidate.
Benchmark pay against market research analysts and marketing specialists: a median of $78,760 a year (BLS OEWS, May 2025).
Frequently Asked Questions
What questions should I ask an SEO analyst candidate?
Ask questions that force diagnosis rather than description. The strongest openers are: explain crawling, indexing, and ranking as if I have never heard the terms; one of our pages is not showing up in search, walk me through the first thirty minutes of finding out why; our organic traffic went up 40 percent and leads stayed flat, what happened; and what SEO tactics would you refuse to use. Each one has a right shape of answer that an owner can recognize without knowing SEO: the candidate verifies a fact before recommending a fix, segments the data instead of quoting one total, and ties traffic to leads. Add technical questions on canonicals, redirects, and migrations if the role touches the site, and keyword questions if the analyst will steer what gets written. This page gives you six full sets with answer guidance and a scorecard.
How do I evaluate an SEO analyst if I do not know SEO myself?
You are not grading the SEO, you are grading the reasoning, and that is something any owner can do. Three patterns separate a strong candidate from a fluent one. First, they diagnose before they prescribe: asked why a page is missing from search, they check whether it is indexed before suggesting keywords or links. Second, they tie every number to a business outcome without being prompted, and they volunteer the limits of their own data. Third, they have refusals, specific tactics they will not use, with a commercial reason. Every question in these kits carries a note on what a good answer contains so you are listening for that shape rather than for correct vocabulary. Then confirm with a short paid work sample on real data, which reveals judgment far better than a second conversation.
What is the difference between an SEO analyst and an SEO specialist?
An SEO analyst measures and diagnoses organic search, while a specialist mostly implements. The analyst owns keyword research, audits, competitor analysis, reporting, and the recommendations that come out of them; the specialist executes the on-page changes, the content briefs, and the technical fixes. In practice the line blurs at small companies, where one person often does both, and that is fine as long as you say so in the job posting and interview for it. If you need someone to tell you what is wrong and what it is worth fixing, interview for analysis, using the diagnosis and analytics sets on this page. If you need someone to ship changes every week, weight the technical set and add a practical exercise. Hiring an analyst and then expecting weekly implementation is a common and avoidable mismatch.
What are the biggest red flags in an SEO analyst interview?
The clearest red flag is a guarantee: a promise of a number-one ranking or a specific traffic figure by a date. Nobody can guarantee either, so the promise tells you the candidate either does not understand the mechanism or is willing to say anything to close you. Close behind: cannot separate crawling, indexing, and ranking; reports traffic with no line to leads or revenue; is vague about where links come from or who writes the content; blames an algorithm update for every past result; answers questions with tool names instead of reasoning; and accepts an unrealistic timeline without pushing back, which almost always repeats in month three. A candidate with no refusals at all, who would use any tactic that works this quarter, is the most expensive version of this hire. The downloadable scorecard includes the full checklist.
Should I give an SEO analyst candidate a test or work sample?
Yes, and for this role it is the single highest-value step. Analytical judgment shows up in twenty minutes of written work and almost never in an hour of conversation, because interviews reward fluency and this job rewards care. Give every finalist the same export of real or realistic search data with a deliberate flaw left in it, a broken tracking period or a branded query inflating the totals, and ask for a one-page written recommendation rather than a dashboard. Cap it at two to three hours, say the cap out loud, and pay for the time. Grade against criteria you wrote before the first submission arrived: did they find the flaw, did they prioritize by impact, and could you follow the reasoning unaided. Treat it as a selection procedure and apply it consistently to every finalist.
How many interview rounds does an SEO analyst hire need?
Two conversations and one paid exercise is enough for most small businesses. Round one is a short screen, thirty minutes, using the core questions to confirm the candidate diagnoses rather than describes and can explain search in plain language. Then send the work sample to your two or three finalists. Round two is a sixty-minute conversation built around their submission, plus the analytics and risk sets, which is a far better use of the hour than repeating general questions. Score after each stage rather than at the end, while the answers are still fresh, and use the same rubric throughout. Adding a third and fourth interview rarely improves the decision and regularly loses good candidates, who are usually talking to two or three other employers at the same time.
How much should I pay an SEO analyst?
There is no dedicated federal wage category for SEO analysts, so benchmark against market research analysts and marketing specialists, the classification that contains search marketing roles. The Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025) puts that group at a median of $78,760 per year, or $37.87 per hour, with the lowest 10 percent under $43,390 and the highest 10 percent above $155,480. Place your role inside that band by seniority rather than averaging to the middle: a junior analyst sits near the 25th percentile of about $58,350, an experienced in-house analyst near the median, and a specialized measurement or ecommerce role toward the 75th percentile of about $108,310. Adjust for your metro and industry, and publish a real range, because analysts benchmark compensation for a living.
Are these SEO analyst interview questions legal to ask?
Yes. Every question here is about the work: how the candidate diagnoses a ranking problem, what they would check, which keywords they would target, what they report, and which tactics they refuse to use. Job-related questions asked consistently of every candidate are exactly what employment law asks for. The caution is general to all interviewing rather than specific to this role: avoid questions that touch protected characteristics such as age, race, religion, national origin, sex, pregnancy or family plans, disability, or genetic information, including as casual small talk. If you use a paid work sample, give every finalist the same task and grade it against criteria written in advance, since a selection procedure should be job-related and applied consistently. For specifics, consult EEOC guidance or a qualified advisor. This is general information, not legal advice.
