SEO interview questions are the questions a hiring manager uses to find out whether a candidate can move organic traffic, not only describe how SEO works. Unlike the 100-question lists that rank for the term, which are written for candidates cramming definitions, a useful set tests judgment: what the person would fix first, how they diagnose a drop, and what they would refuse to do.
The short version for founders and marketing directors: ask fewer questions, make them about your site, and decide in advance what a good answer sounds like.
According to Google Search Central (2026), site owners should interview a potential SEO, ask to see examples of previous work, and find someone else if the SEO guarantees first place in search results.
According to Semrush’s analysis of 3,900 US SEO job listings on Indeed (November 2025), specialist titles made up only 15% of open SEO roles, while senior leadership roles accounted for 59%.
Search for Hire’s study of 1,175 US SEO job listings (April 2025 to March 2026) found that 54.9% of job descriptions mentioned AI.
Why most SEO interview questions test the wrong thing
Look at what ranks for “SEO interview questions” and you find the same format: 50, 100 or 108 questions with model answers. What is a meta description. What is a canonical tag. What is the difference between dofollow and nofollow. Several of the top results were first published between 2017 and 2023.
Those questions were weak filters before AI tools. In 2026 they are useless. Any candidate can generate a perfect definition of crawl budget in ten seconds, and the ones who prepared from those lists will recite them word for word. You end up hiring the best memoriser, not the best SEO.
What separates good SEOs from average ones is not knowledge. It is diagnosis, prioritisation and the ability to say no. Semrush’s job listing study found communication in 39.4% of non-senior SEO roles, and Google Analytics in 47.7%. Employers already know they need someone who can read data and explain it. The interview has to test exactly that.
In my experience auditing sites, the damage from a weak SEO hire rarely shows up as a penalty. It shows up as a year of busywork: hundreds of tool warnings “fixed”, a blog calendar nobody reads, and no change in qualified traffic.
12 SEO interview questions that reveal judgment
Group your questions into four areas. You do not need all twelve. Pick two or three per area that match the role, and write down what a strong answer looks like before the first interview.
Questions about ownership and results
“Walk me through one result you personally owned, from the problem to the number.” A strong answer names the starting situation, the change they made, how long it took and how they measured it in Search Console or analytics. A red flag is “we” for the whole story with no clear part that was theirs.
“Tell me about an SEO project that did not work.” Good candidates have one ready and explain what they learned. Someone with fifteen projects and no failures either has little experience or is not being straight with you.
“Which Google update affected a site you worked on, and what did you do?” This shows whether they follow the field and whether they react with analysis or panic.
Questions that test diagnosis
“Organic traffic dropped 30% last month. What do you check, in order?” Listen for a sequence: tracking and data first (did the analytics tag break?), then Search Console by page and query, then indexing, then known updates, then competitors. A strong candidate asks whether the drop is in impressions, clicks or both before guessing a cause.
“Here is our Search Console performance report. What do you notice?” Share a real screenshot. You learn more in five minutes than from an hour of theory.
“How would you find out whether two of our pages compete for the same query?” This tests practical knowledge of keyword cannibalization and whether they check data before merging pages.
Questions about priorities and trade-offs
“You have 40 developer hours this quarter. What do you spend them on, for our site?” Give them the site in advance. The best answers rank three or four items by expected impact and explain what they are deliberately leaving out.
“An audit tool shows 2,000 warnings. Which ones do you ignore?” A candidate who treats every warning as urgent will burn developer goodwill within a quarter. You want someone who knows most warnings change nothing.
“Should we write more content or improve what we have?” There is no single right answer. The right answer depends on the site, and a good candidate says so and asks for data.
Questions about business sense and ethics
“How would you report SEO results to our CEO?” Strong answers connect organic search to leads, pipeline or revenue, not to rankings alone. A red flag is a report built around domain authority or keyword counts.
“What would you refuse to do, even if I asked?” Buying links at scale, mass-producing AI pages with no editing, or promising a timeline they cannot control. Google’s guidance is explicit that guaranteed rankings are a reason to look elsewhere.
“How are AI answers changing the work, and how would you measure our visibility in them?” In 2026 this is a fair question for any SEO role. A good answer mentions that AI systems draw on the same index and signals, and proposes a practical way to track citations rather than a vague promise.
How to run an SEO interview: a five-stage process
A structured process beats a brilliant question list. Here is the sequence I recommend for a first in-house SEO hire.
- Define the bottleneck before you write questions. Decide whether the role is mainly technical, content or authority. The SEO specialist job description guide explains the three archetypes. Your questions should weight the one you are hiring for.
- Run a 20-minute screening call. Use two questions only: the result they owned and the traffic drop diagnosis. This filters out most of the list-memorisers quickly.
- Hold one structured interview with a written scorecard. Every interviewer asks the same core questions and scores each answer from 1 to 5 before discussing the candidate. Scoring separately stops the loudest person in the room from deciding.
- Set a short paid test task on your own site. Give two to four hours of work, for example: “Find the three issues costing us the most organic traffic and explain how you would fix them.” Pay for it. Unpaid tasks put off exactly the experienced people you want.
- Check references with specific questions. Ask past managers what the candidate shipped, how they handled disagreement with developers, and whether they would hire them again. Google recommends checking an SEO’s business references for the same reason.
A technical SEO specialist needs a heavier test task than a content hire. For technical roles, ask them to review a crawl export or a set of rendering issues. For content roles, ask for a brief for one page that should rank but does not.
Scoring SEO interview answers: a simple rubric
A rubric is what turns interview questions into a decision. Without one, you end up remembering whoever told the best story. Score each answer from 1 to 5 against four criteria:
| Criterion | 1 (weak) | 5 (strong) |
|---|---|---|
| Specificity | Generic, textbook answer | Names real sites, numbers and dates |
| Diagnosis | Jumps to a cause | Checks data in a logical order |
| Prioritisation | Wants to fix everything | Ranks by impact and explains trade-offs |
| Communication | Jargon a CEO could not follow | Clear enough to repeat to your board |
Add the scores and compare candidates only after everyone has scored. If two people disagree by more than two points on the same answer, discuss the evidence, not the impression.
Watch for three red flags that should end the process regardless of score: guaranteed rankings or timelines, an answer about link building that starts with buying packages, and no questions at all about your business. Google makes the same point: a good SEO should ask what makes your business unique, who your competitors are and how your customers find you.
SEO interview questions for consultants and agencies
If you are hiring outside help rather than an employee, the questions shift from skills to working model. You are buying a result and a way of working, not a person’s time. Good freelancers sell exactly that: one defined fix with a scope, a price and a deadline.
Google’s own list is a solid base. It suggests asking for examples of previous work, whether they follow Google Search Essentials, what results they expect and in what timeframe, how they measure success, and whether they will explain every change they make. Add three of your own:
- “Who will actually do the work, and how senior are they?”
- “What do you need from my team each month for this to work?”
- “What would make you tell me SEO is not worth it for us?”
The last one matters most. A good consultant will tell you when the budget is better spent elsewhere. For a full vetting checklist, see the guide on how to hire an SEO consultant, and before you sign anything, compare the proposal against the points in how to evaluate an SEO proposal. Price matters too: Ahrefs’ pricing survey found freelance SEOs averaged $71.59 per hour, and my own SEO pricing is published openly so you can compare.
When you grant access for a trial audit, follow Google’s advice: read access to Search Console only, no write access at that stage.
When interviewing is the wrong first step
Sometimes the problem is not finding the right person. It is that nobody in the company knows what the role should achieve. If you cannot say whether your bottleneck is technical, content or authority, every candidate will sound plausible and you will have no way to tell them apart.
In that case, get a diagnosis first. An SEO audit shows where the traffic is being lost, and a few months of SEO consulting can set the strategy and help you write the job description and the interview questions with real priorities behind them. Search for Hire’s data puts the mid-level median salary at $73,000 a year in the US, so a bad hire costs far more than a diagnosis.
The best SEO interview questions are the ones only a good candidate can answer well, because they are about your site, your data and your constraints. Ask fewer of them, score them against the rubric, and pay for a real test.
Frequently Asked Questions
What are the 5 main interview questions?
The five main questions in an SEO interview are: walk me through a result you owned, diagnose this traffic drop, what would you fix first on our site, how do you measure success, and what would you refuse to do. Together they test ownership, diagnosis, prioritisation, business sense and ethics. Definitions are easy to memorise, so a strong interview spends most of its time on these five.
What does SEO involve?
SEO involves making a website easy for search engines to crawl, understand and trust, so its pages appear for the searches its customers make. In practice that means technical work (crawling, indexing, speed, site structure), content built around search intent, and earning links and mentions from other sites. In 2026 it also covers visibility in AI answers, which draw on the same signals.
What are the four types of SEO?
The four types of SEO usually listed are on-page, off-page, technical and local SEO. On-page covers content and page elements, off-page covers links and mentions, technical covers how search engines crawl and index the site, and local covers maps and location searches. In an interview, the better question is which of the four is the bottleneck for your site right now.
What are the 5 best SEO tools?
The five SEO tools most practitioners rely on are Google Search Console, Google Analytics 4, a crawler such as Screaming Frog, a backlink and keyword platform such as Ahrefs or Semrush, and PageSpeed Insights for performance data. Search Console is the only one that shows how Google itself sees the site. A candidate who names paid tools but cannot explain what Search Console’s reports tell them is a weak hire.
What are the three C’s of SEO?
The three C’s of SEO are most often given as content, code and credibility, although there is no official Google definition. Content is what the page says, code is whether search engines can crawl and render it, and credibility is the links and reputation that make it trustworthy. Ask a candidate which C is weakest on your site and why: the answer tells you more than the definition.