SEO Manager
Structured interview questions for SEO Manager, with what a strong answer surfaces for each one.
BehavioralAnalytical thinking Describe the last time an algorithm update visibly hit your organic traffic. What was the diagnosis, what did you change, and how long did recovery take?
What a strong answer surfacesThe ability to frame an update as a diagnostic exercise and not a natural disaster. Concrete steps: identified affected URLs, used log files or Search Console data to narrow it down, formulated a hypothesis (content quality, E-E-A-T, technical issue, backlink profile), prioritized the fix. Bonus: the candidate describes what they changed structurally to weather future updates better. Anyone who cannot name an update experience or only answers Google does that sometimes rarely has real SEO practice and tends toward confirmation bias when analyzing.
BehavioralAnalytical thinking Tell me about the last time you had an SEO hypothesis that turned out to be wrong after checking the data. What was the hypothesis, what did the data show, and how did you react?
What a strong answer surfacesThe ability to work data independently (SQL, spreadsheet, Search Console API, log-file analysis) and to communicate an inconvenient result without going defensive. Bonus: the candidate describes how they originally framed the hypothesis (competitor observation, industry dogma, gut feeling) and how the validation changed their process. Anyone who only takes data from Sistrix or Ahrefs and presents it without validating against Search Console or GA4 is too weak for this role.
BehavioralTechnical SEO craft Describe the last time you solved a technical SEO problem the engineering team initially did not want to prioritize. How did you go about it?
What a strong answer surfacesA structured approach: a business case computed with traffic and revenue impact, an honest assessment of technical complexity (not played down), alternatives shown (full solution versus interim fix). Bonus: the candidate describes talking to the tech lead directly instead of escalating via tickets, or reducing engineering effort through their own implementation (e.g. schema markup via GTM, an hreflang patch in the CMS). Anyone who describes running into the wall of the engineering team without reflecting on their own part shows a cross-functional weakness.
SituationalContent and funnel strategy You take over an SEO role at a B2B SaaS SMB with 60 employees, 4 M€ ARR, 80,000 monthly organic sessions, but only a 1.2 % conversion rate on organic. Management wants to raise the value to 2.5 %. What do you do in the first 30 days?
What a strong answer surfacesAudit before action: a funnel diagnosis per landing-page type (blog traffic with pre-intent versus solution pages with buying intent), a qualitative assessment of the top-20 conversion pages and the top-20 traffic pages without conversion, identification of the two or three highest-leverage bottlenecks (wrong intent, weak CTA, missing conversion logic on top-of-funnel pages). Only then hypotheses, only then experiments. Candidates who jump straight to we build more content show an execution bias without diagnosis. Bonus: the candidate questions the premise (is 2.5 % realistic for our segment? what benchmark data exists?).
SituationalTechnical SEO craft A competitor domain has ranked consistently above yours for 3 months on one of your most important keyword clusters. You have more content, more backlinks and a better technical setup. What do you check first?
What a strong answer surfacesA nuanced diagnosis instead of blindly extending content: check intent match (does the competitor cover the search intent more precisely?), compare page experience and Core Web Vitals, analyze internal linking and link-juice distribution, check E-E-A-T signals (author info, sourcing, update date), check SERP features (does the competitor win the featured snippet or a People-Also-Ask position). Bonus: the candidate names a hard-to-measure factor (brand authority in the topic area, semantic depth) and how it can still be validated indirectly. Anyone who immediately answers more backlinks or even more words has no modern SEO posture.
SituationalContent and funnel strategy Management proposes using an AI tool to generate 200 blog articles per month to scale organic traffic quickly. How do you react?
What a strong answer surfacesA clear stance against scaling spam: explaining the risks (Helpful Content Update, manual action, long-term loss of domain reputation), but without an anti-AI attitude. A nuanced proposal: AI as an assistant for research, outline and first draft, with human editing, expertise input and fact-checking at a ratio of 30 min of human work per article hour. Bonus: the candidate names the limit (10 to 30 high-quality articles per month are sustainable; 200 are not) and proposes a pilot of 10 articles with a 90-day visibility measurement. Anyone who agrees without question or answers AI is spam in a blanket way lacks the nuance.
TechnicalKeyword strategy and research How do you prioritize a list of 200 keyword opportunities from a research run? Describe your framework concretely and work an example out loud.
What a strong answer surfacesA structured methodology: clustering (semantically related keywords together), scoring per cluster by search volume, competition (KD or difficulty score), intent match to the funnel stage, expected click rate from the SERP layout (featured snippet, knowledge panel, ads-heavy). Bonus: the candidate names the weakness of popular scores (Ahrefs KD is a heuristic, not a truth claim) and describes a correction mechanism (manually checking the top-10 SERP, comparing the backlink profiles of the top 3). Anyone who only answers search volume times difficulty, without accounting for intent and SERP layout, has a one-dimensional model.
TechnicalTool and data competence Describe your ideal SEO stack for a B2B SaaS SMB with 50 employees and 5 M€ ARR. Justify each tool and name the two or three connections that break the fastest.
What a strong answer surfacesA lean, coherent stack: Search Console (mandatory), Sistrix or Ahrefs (visibility tracking, keyword research, backlink analysis), Screaming Frog or Sitebulb (crawler), GA4 (conversion tracking), a log-file analysis tool (Botify, OnCrawl or Screaming Frog Log Analyzer for an SMB), a schema validator (Google Rich Results Test plus Schema.org validator), a CMS with good SEO integration (or a headless stack with Astro, Next, Sanity). Bonus: the candidate identifies the fragile connections (exporting Search Console data into BigQuery for deeper analysis, schema markup on CMS updates) and names concrete pitfalls.
TechnicalTool and data competence Which SEO analysis do you regularly run yourself in SQL, a spreadsheet or a notebook, without asking an analytics team? Describe a concrete recent analysis with data source, question and result.
What a strong answer surfacesOperational data autonomy: the candidate describes a concrete log-file analysis, Search Console export analysis (top movers, query cannibalization, CTR analysis per position), crawl-diff analysis or content-decay analysis they did themselves, ideally in SQL or a structured notebook. Bonus: mentions a validation loop (cross-checking the result with the content team or engineering) before communicating it. Anyone who can only work in tool UIs (Sistrix dashboard, Ahrefs Site Explorer), having never done a raw-data analysis, quickly hits a wall at an SMB because the analytics team usually does not even exist.
ValuesCross-functional collaboration Tell me about a time you worked closely with the engineering team on a technical SEO project. How was the collaboration?
What a strong answer surfacesA partnership posture with engineering instead of a demanding attitude. The candidate describes shared hypotheses, jointly defined success criteria, a shared review process. Bonus: mentions a technical project the engineering team built against the SEO person's initial wish (showing they understand the technical logic and do not practice pure wishing without system understanding). Anyone who describes the engineering team as the-team-that-blocks-my-tickets starts at an SMB with the wrong posture.
ValuesCross-functional collaboration How do you take difficult feedback from the content or product team that exposes a gap in your SEO work (e.g. unclear briefs, keyword targeting without conversion logic)?
What a strong answer surfacesA learning posture: the candidate describes not only hearing the feedback but integrating it and changing their practice. Bonus: shared what they learned with the rest of the team or documented a new process (a shared briefing template, a shared intent key per keyword cluster). Anyone who describes explaining their own logic instead of accepting the observation shows a coachability weakness that becomes a bottleneck in a cross-functional role like SEO.
ValuesCross-functional collaboration Describe the marketing or SEO team where you felt most comfortable. What defined the culture?
What a strong answer surfacesReflective clarity about their own ideal environment. The answer should be specific enough that they either fit your culture or not (speed, data focus, technical depth, content-quality standards, learning cadence). Bonus: the candidate names something missing in previous teams that would be a deal-breaker. Anyone who feels comfortable everywhere rarely has clear preferences and tends to re-quit quickly when reality does not fit.
CasePosture and motivation Why are you applying with us specifically and not with one of our competitors looking for similar profiles?
What a strong answer surfacesConcrete research on the company's product, market and stage. The candidate names two or three specific aspects (market positioning, growth phase, domain maturity, content inventory, team) that attract them. Bonus: the candidate also identifies a difficulty or risk of the role (low domain authority, competition with aggregator sites, a long SEO cycle to visible results) and explains why it is still the right choice. Anyone who answers in generalities (I love SEO, the mission speaks to me) has not prepared specifically and will move on again after 6 to 12 months when the next logo beckons.
CasePosture and motivation What do you specifically want to learn in this role that you cannot learn in your current position?
What a strong answer surfacesSpecific learning goals beyond more responsibility: a concrete technical lever (JavaScript SEO, international scaling, edge rendering), a concrete funnel stage (conversion optimization on solution pages, pricing-page SEO), a concrete market (DACH specifics, international expansion with hreflang). Bonus: the candidate describes an attempt to learn what they want in their current job, and why it was not possible there (showing an active learning attitude, not just a move motivation). Anyone who cannot name specific learning goals is usually just looking for a salary bump or a better logo.
CasePosture and motivation In 18 months, what would be the best possible outcome of your work with us, and how would you measure it?
What a strong answer surfacesA concrete, measurable vision anchored in the company's business goals: quantified organic-traffic and pipeline contributions, improved SERP visibility on strategic keyword clusters, an established content cadence, raised technical SEO hygiene. Bonus: the candidate names both output metrics (what was generated) and system metrics (which processes, tools, team posture were established). Anyone who answers only very generically (I want to have an impact) has no clear career idea or has not engaged with the specific role.
Evaluation playbook
The SEO Manager role reveals itself across four evaluation stages. The work sample (stage 3) is central: without it, it is hard to distinguish who can really build technical diagnoses and keyword strategies from profiles who only cite audit-tool outputs.
Stage 1: CV review
Look for: consistent tenure (at least 18 months on previous SEO roles, ideally with the same project through two years of visibility building), company context (an SMB or scale-up between 10 and 300 employees, not exclusively an agency with simultaneous account management), a stack covered across multiple levers (technical SEO, content strategy, off-page, analytics). Negative: 100 % content-SEO specialization without technical understanding, or conversely pure tech profiles with no content and conversion view. Save the cited visibility curves (I grew organic traffic by X %) for the interview; those numbers are usually worthless without context on the starting point, competition and algorithm updates.
Stage 2: Structured interview (90 min)
Work through the 15 questions below, alternating behavioral, situational, technical, values and case. On the technical question about keyword prioritization, ask the candidate to reason out loud. At least two interviewers (ideally the Head of Marketing plus someone from product or data), independent scoring before the debrief.
Stage 3: Work sample (90 min, see Work Sample)
A technical SEO audit plus a content-cluster proposal on a sample domain. The candidate gets a fictional domain with Sistrix or Ahrefs screenshots plus a crawl report, identifies the three biggest technical levers, proposes a content cluster of 5 to 8 pages with keyword reasoning, and prioritizes by expected visibility over 6 to 12 months. A 30-min presentation with 30 min of Q&A. This stage weighs heavily in the final decision. Candidates who cite audit-tool outputs without prioritization, or propose vanity keywords with no conversion intent, are eliminated here.
Stage 4: References (structured check)
Call two references: a former direct manager (ideally Head of Marketing or management) and a former peer from content, product or engineering. Ask both the same four questions: What is she/he strongest at? Which technical SEO problem did she/he solve against expectations, and how? Would you hire them again tomorrow, why or why not? A concrete example of how the person handled an algorithm-update drop? The fourth question delivers the most signal about the SEO posture.
How to recognize a great hire
| Trait | Below bar | On bar | Above bar |
|---|---|---|---|
| Analytical thinking | Reads Sistrix or Ahrefs dashboards passively, without forming hypotheses. Accepts the first number without validating against Search Console or GA4. Cannot compute CTR per position, click loss from SERP features, or organic funnel contribution without a spreadsheet. | Forms testable hypotheses from data. Validates numbers across two sources (Sistrix plus Search Console, Ahrefs plus GA4) before communicating them. Works SEO math (expected traffic lift, pipeline contribution, CTR correction per position) out loud operationally. | Builds data models independently (SQL, spreadsheet, notebook) to investigate open questions. Recognizes biases (cannibalization, filter bubble in logged-in search) in SEO data and corrects the analysis accordingly. Can defend an inconvenient analysis with numbers in front of management. |
| Technical SEO craft | Knows SEO audit tools but cannot prioritize audit outputs. Does not understand crawl budget, JavaScript rendering, hreflang or canonical logic in depth. Hands everything to the engineering team without computing a business case. | Diagnoses the common technical bottlenecks independently (crawl errors, duplicate content, Core Web Vitals, hreflang conflicts, schema errors). Creates prioritized tickets with a business case and a technical description. Can implement schema markup or hreflang in the CMS themselves when no engineering effort is needed. | Understands rendering pipelines (SSR versus CSR versus ISR), edge caching, log-file signals on bot behavior, JavaScript rendering diff (what Googlebot sees versus what the browser sees). Can discuss performance budgets and rendering strategies with engineering as an equal. Establishes an SEO gate in the deployment process (automated checks before release). |
| Keyword strategy and research | Uses a single keyword-tool output as ground truth. Prioritizes by search volume without intent match or SERP-layout analysis. Writes content for all high-volume keywords without forming clusters. | Forms keyword clusters by semantic relatedness and funnel stage. Prioritizes by search volume times intent match times realistic ranking chance (benchmarked against domain authority). Manually checks the top-10 SERP for top candidates. | Establishes a repeatable keyword system: a prioritized cluster backlog, central documentation per cluster (brief, target keywords, internal linking, expected conversion logic), continuous evaluation of their own estimates. Can transfer the system to the content team and freelancers and coaches others in the keyword craft. |
| Content and funnel strategy | Thinks of SEO as a pure traffic exercise, without conversion logic. Writes top-of-funnel content with no CTA or path to pipeline. Measures success by traffic numbers instead of organic pipeline contribution. | Thinks end to end: knows which page types serve which funnel stage (blog for awareness, solution pages for consideration, pricing and comparison pages for decision). Allocates content effort accordingly. Defines the conversion logic per cluster. | Steers SEO as a pipeline contribution: coordinates with product, sales and customer success, anticipates content decay before the revenue effect, establishes shared SEO-pipeline metrics across functions. Recognizes structural limits (market TAM, intent bottleneck) beyond pure SEO mechanics. |
| Tool and data competence | Operates only the UI surfaces of the common tools (Sistrix dashboard, Ahrefs Site Explorer). Cannot process API exports, run a log-file analysis, or do an SQL or notebook analysis. | Exports data from Search Console, Sistrix and GA4 into spreadsheets or notebooks, validates numbers across at least two sources, builds reusable analysis templates. Runs simple log-file analyses with Screaming Frog Log Analyzer or similar. | Writes their own SQL queries on a Search Console export in BigQuery, builds notebook-based analyses (content decay, CTR anomalies, query cannibalization, crawl diff), automates recurring reports. Understands the limits of the tools used (sampling, filter quirks) and compensates for them. |
| Cross-functional collaboration | Defends their own function without dialogue with engineering, content or product. A defensive attitude toward feedback. No shared vocabulary across functions. | Shared definitions (intent key, conversion logic per cluster, technical SEO acceptance criteria) with the adjacent teams. A regular cadence (weekly 30 min with content, monthly with engineering). Takes qualitative feedback and integrates it. | Establishes shared dashboards, shared rituals and shared language across functions. Spots weak signals from other functions before escalation. Coaches their environment in SEO data competence and SEO mindset without falling into the role of the lecturer. |
30 / 60 / 90 day success plan
By day 30
- Full SEO audit: technical audit (crawl, Core Web Vitals, hreflang, schema, log-file sample), content inventory by funnel stage, keyword visibility per cluster, backlink-profile diagnosis
- 1:1 with every key stakeholder (management, Head of Marketing, engineering lead, content lead, product lead) to clarify expectations and points of friction
- Identify the two or three highest-leverage SEO bottlenecks, documented with a data argument and first hypotheses
- Search Console connection to BigQuery (or a comparable data setup) established for deeper analysis
By day 60
- Prioritized SEO backlog for the quarter (technical plus content), shared with management, engineering and the content team
- First technical tickets in progress with engineering, a documented business case and success measurement
- First content cluster (5 to 8 pages) briefed, production started with internal authors or freelancers
- Steering cadence set: weekly 30 min with content, monthly 60-min SEO review with management, quarterly technical sync with engineering
By day 90
- First significant improvement on the top bottleneck demonstrated (e.g. plus 10 to 20 % organic sessions on the target cluster, or a documented technical-lever solution with expected lift over the coming 90 days)
- SEO roadmap for the next quarter written: quantified visibility and pipeline goals, content backlog, technical backlog, dependencies on engineering and content
- Two to three keyword clusters actively being built or expanded, each with a clear visibility comparison against baseline
- Established content cadence: at least 4 high-quality articles per month plus 2 solution or comparison pages per quarter, with a documented briefing process