Skip to content
Resume Studioby M2Toolkit

8 role-specific questions

SEO Specialist Interview Questions & Answers

SEO interviews test how search engines work, keyword and intent research, technical audits, content quality, ethical link building, migrations and diagnosing traffic drops.

Free, no sign-up. 61 questions in this role's practice pool, including behavioural, HR and situational questions.

SEO interview questions

Technical SEO, keyword research, content, links, audits, algorithm updates and reporting.

  1. 1.

    Explain how search engines crawl, index and rank pages.

    BeginnerRole knowledge

    What the interviewer is evaluating

    Fundamentals of crawling, indexing and ranking — the basis of every SEO decision.

    Key points a strong answer covers

    • Crawling. Bots discover pages by following links and sitemaps.
    • Indexing. Pages are rendered, understood and stored in the index (or not).
    • Ranking. Ranking orders indexed pages by relevance and quality signals for a query.
    • Blockers. robots.txt, noindex, errors and heavy JavaScript can block crawling or indexing.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Confusing robots.txt (crawling) with noindex (indexing).
    • Thinking submitting a sitemap guarantees indexing.

    Likely follow-up questions

    • What's the difference between a disallow in robots.txt and a noindex tag?
    • Why might a page be crawled but not indexed?
    Example strong answer

    Search engines work in three stages. Crawling: bots like Googlebot discover URLs by following links and reading sitemaps, and fetch the pages — robots.txt controls what they may crawl. Indexing: the page is rendered, including JavaScript, its content understood, duplicates grouped under a canonical, and it's stored — or not, if it's thin, duplicate, or has a noindex tag. Ranking: for each query, indexed pages are ordered by hundreds of signals around relevance to the search intent, content quality and helpfulness, authority from links, and page experience. A common mistake is blocking a page in robots.txt to remove it — that stops crawling, so Google can't even see the noindex tag.

    Practise this question and get feedback
  2. 2.

    How do you do keyword research?

    BeginnerRole knowledge

    What the interviewer is evaluating

    Practical research process.

    Key points a strong answer covers

    • Seed topics from the business. Start from the business and audience.
    • Tools & data. Use tools and Search Console for volume and difficulty.
    • Search intent. Classify by search intent and check the SERP.
    • Prioritise. Prioritise by value, difficulty and long-tail opportunity.
    • Map to pages. Cluster and map keywords to pages to avoid cannibalisation.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Chasing high-volume keywords with the wrong intent.
    • Targeting the same keyword with several pages.

    Likely follow-up questions

    • How do you judge search intent?
    • What is keyword cannibalisation?
    Example strong answer

    I start from the business — products, customers and the problems they solve — and gather seed topics from sales, support and Search Console queries we already appear for. Then I expand them with tools like Ahrefs or Semrush for volume, difficulty and related terms. The most important step is search intent: I look at what actually ranks for each keyword — guides, product pages, comparison lists — because that's what Google thinks people want. I prioritise by business value, realistic difficulty for our site's authority, and long-tail opportunities, then cluster related keywords and map each cluster to a single page, so we don't create several pages competing for the same term.

    Practise this question and get feedback
  3. 3.

    How would you run a technical SEO audit?

    IntermediateRole knowledge

    What the interviewer is evaluating

    Technical depth, and whether you can turn an audit into prioritised fixes.

    Key points a strong answer covers

    • Crawl the site. Crawl the site with a tool like Screaming Frog.
    • Indexability. Check indexability: status codes, redirects, canonicals, robots, sitemaps.
    • Search Console. Review Search Console page indexing and crawl stats.
    • Performance & mobile. Core Web Vitals and mobile usability.
    • Structure & rendering. Internal links, orphan pages, JS rendering, structured data, hreflang.
    • Prioritise fixes. Prioritise fixes by impact and effort.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Delivering a 200-item list with no priorities.
    • Ignoring Search Console data.

    Likely follow-up questions

    • How do you check whether Google can render a JavaScript page?
    • What would you fix first?
    Example strong answer

    I'd crawl the site with Screaming Frog or Sitebulb and compare it with the XML sitemap and Search Console. Indexability first: status codes, broken links and redirect chains, robots.txt rules, noindex tags, canonical tags pointing where they should, and duplicate or thin pages. In Search Console, the page indexing report shows why pages aren't indexed and crawl stats show server issues. Then site structure — internal linking depth and orphan pages — JavaScript rendering using the URL inspection tool, structured data validity, hreflang for multilingual sites, and Core Web Vitals and mobile usability. I finish with a prioritised list based on impact and effort, not a 200-line dump.

    Practise this question and get feedback
  4. 4.

    Organic traffic dropped 30% this month. How do you investigate?

    IntermediateProblem solving

    What the interviewer is evaluating

    Diagnostic method: separating data problems, demand, site changes and algorithm updates.

    Key points a strong answer covers

    • Verify the data. Check it's real in both Search Console and analytics.
    • Seasonality & SERP. Check seasonality, demand and SERP changes.
    • Algorithm updates. Check timing against Google updates.
    • Technical changes. Check releases, migrations, robots/noindex and redirects.
    • Segment pages & queries. Segment by pages, queries, device and country.

    Suggested answer structure

    1. Restate the problem and your assumptions.
    2. Break it into steps and reason out loud.
    3. Check your answer against an edge case.
    4. Summarise the result and what you'd verify next.

    Common mistakes

    • Blaming an algorithm update without checking site changes.
    • Looking only at total traffic.

    Likely follow-up questions

    • How would you recover from a core update drop?
    • How would you check whether AI overviews reduced clicks?
    Example strong answer

    First I'd confirm the drop in both Search Console and analytics, to rule out a tracking problem, and check seasonality by comparing year over year. Then I'd segment: which pages, query types, countries and devices lost clicks, and whether it's impressions — rankings or demand — or click-through rate — perhaps a new SERP feature or AI overview taking clicks. I'd check the timing against site changes — a release that added noindex tags, changed robots.txt, broke canonicals or redirects, or a migration — and against Google's announced updates. If one section lost rankings after a core update, I'd compare our pages with the ones now ranking and improve content quality, rather than making quick technical tweaks.

    Practise this question and get feedback
  5. 6.

    What makes content rank well today?

    IntermediateRole knowledge

    What the interviewer is evaluating

    Understanding of helpful content and E-E-A-T.

    Key points a strong answer covers

    • Matches intent. It matches the search intent and answers the query fully.
    • Helpful & original. Original, helpful content with first-hand experience.
    • E-E-A-T. Experience, expertise, authoritativeness and trust.
    • Structure & UX. Clear structure, good page experience, internal links.
    • Freshness. Kept accurate and up to date.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Writing for keyword density.
    • Producing generic content that repeats what already ranks.

    Likely follow-up questions

    • How do you show first-hand experience in content?
    • How do you handle AI-written content?
    Example strong answer

    Content that ranks today satisfies the searcher better than the alternatives. It matches the intent — if people want a comparison, they get a comparison, not an essay — and answers the question completely and quickly. It adds something original: first-hand experience, real examples, data or expert insight, rather than rephrasing what already ranks. Google's guidance emphasises experience, expertise, authoritativeness and trust, so I show who wrote it and why they're qualified, and cite sources. It's well structured with clear headings, fast and easy to read on mobile, linked from relevant pages, and kept up to date. Keyword density is irrelevant; covering the topic properly matters.

    Practise this question and get feedback
  6. 7.

    How do you report SEO results to stakeholders?

    BeginnerRole knowledge

    What the interviewer is evaluating

    Whether you can communicate SEO value in business terms, honestly.

    Key points a strong answer covers

    • Business metrics. Tie SEO to conversions and revenue, not just rankings.
    • Core SEO metrics. Clicks, impressions, visibility and rankings for priority topics.
    • Context. Context: year-over-year, seasonality and explanations.
    • Actions. What was done and what's next.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Reporting only rankings for vanity keywords.
    • No explanation of changes.

    Likely follow-up questions

    • How do you set realistic SEO targets?
    • How long does SEO take to show results?
    Example strong answer

    I start with what the business cares about: organic conversions, leads or revenue, and how they trend. Then the leading indicators — clicks and impressions from Search Console, visibility for priority topics, and the pages driving growth — with year-over-year comparisons so seasonality doesn't mislead. I explain the why behind changes, and summarise what we did this period and what's next. I avoid reporting a long list of keyword positions, which change daily and don't map to business value. I'm also honest about timescales: SEO work often takes months to show results, so I set expectations upfront.

    Practise this question and get feedback
  7. 8.

    How do you protect SEO during a website migration?

    AdvancedRole knowledge

    What the interviewer is evaluating

    Risk management in technical SEO.

    Key points a strong answer covers

    • Inventory & benchmarks. Crawl and benchmark the old site first.
    • Redirect map. A one-to-one 301 redirect map from old to new URLs.
    • Preserve signals. Preserve content, metadata, internal links and structured data.
    • Test before launch. Test on staging (blocked from indexing) and crawl the new site.
    • Monitor after. Submit sitemaps and monitor errors and rankings after launch.

    Suggested answer structure

    1. State your approach in one sentence.
    2. Walk through the steps or criteria you use.
    3. Give a real example from your work.
    4. Say how you measure whether it worked.

    Common mistakes

    • Redirecting every old URL to the homepage.
    • Launching with staging's noindex still in place.

    Likely follow-up questions

    • How long should redirects stay in place?
    • What would you check in the first 48 hours?
    Example strong answer

    Before migrating I crawl the old site and record benchmarks: rankings, traffic and conversions per page, plus the pages with the most backlinks. Then a redirect map: every old URL with value gets a one-to-one 301 to its closest new equivalent — never everything to the homepage. Content, titles, meta descriptions, internal links, structured data and hreflang are preserved or improved. The new site is tested on staging, blocked from indexing, and crawled to check the redirects and that nothing important is noindexed. On launch day I remove the staging blocks, submit the new sitemaps, and monitor Search Console, 404s, crawl errors and rankings daily for the first weeks. Redirects stay in place for at least a year — ideally permanently.

    Practise this question and get feedback

Behavioural & HR questions you'll also get

These come up in almost every seo specialist interview. Story questions are best answered with STAR — Situation, Task, Action, Result.

  • Tell me about yourself.

    BeginnerHR

    What the interviewer is evaluating

    Whether you can give a concise, relevant pitch that frames your experience around this job.

    Key points a strong answer covers

    • Present. Start with your current role and what you do.
    • Relevant past. Pick the most relevant past experience.
    • Strength / achievement. Include one strength or achievement with evidence.
    • Why this role. Finish with why this role is the next step.

    Suggested answer structure

    1. Present — your current role in one or two sentences.
    2. Past — the experience most relevant to this job.
    3. Proof — one achievement or strength with evidence.
    4. Future — why this role is the logical next step.

    Common mistakes

    • Reciting your whole CV chronologically.
    • Personal life story unrelated to the job.
    • Going over two minutes.

    Likely follow-up questions

    • Why are you looking to leave your current role?
    • What would your manager say is your biggest strength?
    Example strong answer

    I'm a front-end developer with four years' experience, currently at a fintech start-up where I build the customer dashboard in React and TypeScript. Before that I spent two years at an agency building e-commerce sites, which taught me to work fast with lots of different clients. The thing I'm proudest of recently is leading our move to a shared component library, which cut the time to build new screens by about a third. I'm now looking for a role where I can work on a larger product with a strong design system, which is exactly what drew me to this position.

  • Why should we hire you?

    BeginnerHR

    What the interviewer is evaluating

    Whether you understand the role and can match your strengths to its needs with evidence.

    Key points a strong answer covers

    • Role's needs. Show you understand what the role needs.
    • Matching strengths. Match two or three strengths to those needs.
    • Evidence. Back each with evidence.
    • Enthusiasm. Close with genuine enthusiasm.

    Suggested answer structure

    1. Name the two or three things the role needs most.
    2. Match each with your experience and evidence.
    3. Add what makes you different.
    4. Finish with genuine interest.

    Common mistakes

    • Generic claims like 'I'm hardworking' with no evidence.
    • Comparing yourself to other candidates you don't know.

    Likely follow-up questions

    • What would you do in your first 90 days?
    • What's one area where you'd need support?
    Example strong answer

    From the job description and our conversation, you need someone who can take ownership of the customer onboarding process, work with sales and product, and improve the numbers. I've done exactly that for three years: at my current company I redesigned onboarding for new accounts and cut the time to first value from 14 days to 6. I'm comfortable working across teams — I run a weekly session with sales and product on customer feedback — and I'm very data-driven, so I'd measure everything from day one. I'm also genuinely excited about your product, because it solves a problem I've seen customers struggle with.

  • Tell me about a time you disagreed with a teammate. How did you handle it?

    BeginnerBehavioural

    What the interviewer is evaluating

    Handling conflict constructively and keeping relationships.

    Key points a strong answer covers

    • Listened to their view. Show you listened to understand their view.
    • Used facts / common goal. Bring it back to facts or a shared goal.
    • Resolution & relationship. Resolve it and keep the relationship.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Making the other person the villain.
    • A story where you were simply right and they gave in.

    Likely follow-up questions

    • What if you couldn't reach agreement?
    • Have you ever been wrong in a disagreement?
    Example strong answer (a fictional story — use your own)

    On a website rebuild, a senior designer wanted an animated, image-heavy homepage, and I was worried it would hurt mobile load times and SEO. As the developer responsible for performance, I needed us to agree before the sprint started. I asked her to walk me through what she was trying to achieve — she wanted the brand to feel premium. I built two quick prototypes, one with her full design and one with lighter animations, and we tested both on a mid-range phone together. Hers took nearly six seconds to load. We agreed on a version that kept the key animation but lazy-loaded the rest. The page launched loading in under two seconds, and she later asked me to review designs earlier. I learned that testing together beats debating.

  • Tell me about a mistake you made and what you learned.

    BeginnerBehavioural

    What the interviewer is evaluating

    Honesty, accountability and learning.

    Key points a strong answer covers

    • Real mistake owned. Own a real mistake.
    • Fixed it. Show how you fixed it and who you told.
    • Changed behaviour. Show what you changed afterwards.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Choosing a fake mistake like 'I work too hard'.
    • Blaming others.

    Likely follow-up questions

    • How did your manager react?
    • How do you know you haven't repeated it?
    Example strong answer (a fictional story — use your own)

    In my first year as a marketing coordinator, I sent a promotional email to our whole list with the wrong discount code — I'd tested the email but not clicked the code itself. Within an hour customers were complaining that it didn't work. I told my manager immediately, set the wrong code to apply the discount too, and sent a short correction email with an apology. We lost very little revenue, and some customers replied thanking us for the quick fix. Since then I use a pre-send checklist that includes testing every link and code as a customer would, and I asked for a second person to check any campaign to more than 10,000 people.

  • Describe a situation where you worked under pressure or to a tight deadline.

    BeginnerBehavioural

    What the interviewer is evaluating

    Prioritisation, composure and delivery.

    Key points a strong answer covers

    • The pressure. Make the pressure concrete.
    • Prioritised. Show how you prioritised.
    • Communicated. Show how you kept people informed.
    • Delivered. Show the outcome.

    Suggested answer structure

    1. Situation — one or two sentences of context.
    2. Task — what you were responsible for.
    3. Action — what you did, step by step (say “I”).
    4. Result — what changed, with a number if you can back it up.
    5. Reflection — what you learned or would do differently.

    Common mistakes

    • Glorifying working all night as the solution.
    • No mention of prioritising.

    Likely follow-up questions

    • What would you do if it was clear you couldn't make the deadline?
    • How do you stop pressure affecting quality?
    Example strong answer (a fictional story — use your own)

    Two days before a client presentation, our analyst fell ill and I had to finish the market research report she'd been leading. I listed everything left and asked the account director which sections the client cared about most — pricing and competitor comparison. I focused on those, reused verified data from our previous report, and moved the appendix to a follow-up email. I sent a short update each evening so nobody was surprised. We delivered the core report on time, the client approved the next phase, and the appendix followed two days later. I learned to ask early what matters most rather than trying to do everything equally well.

  • What would you do if you realised you were going to miss a deadline?

    BeginnerSituational

    What the interviewer is evaluating

    Transparency and problem solving.

    Key points a strong answer covers

    • Tell people early. Flag it as soon as you know.
    • Assess the gap. Work out how far off you are.
    • Options. Offer options: reduced scope, help, a new date.
    • Prevent repeats. Learn why it happened.

    Suggested answer structure

    1. Clarify the situation and what's at stake.
    2. Say what you'd do first, and why.
    3. Explain who you'd involve and how you'd communicate.
    4. Describe how you'd check the outcome and prevent a repeat.

    Common mistakes

    • Waiting until the deadline to say anything.
    • Promising you'll just work all night.

    Likely follow-up questions

    • What if your manager is unavailable?
    • Has this happened to you?
    Example strong answer

    I'd tell the person depending on it as soon as I realised, not at the deadline. Before that conversation I'd work out how far off I am and why, so I could offer options: delivering the most important part on time and the rest a few days later, getting help from a colleague, or agreeing a new date. Then I'd let them decide what works best for them, and keep them updated. Afterwards I'd look at why it slipped — usually underestimating something — so I plan better next time.

Ready to answer them out loud?

Run a timed seo specialist mock interview, type or speak your answers, and get a score breakdown with what to improve.

Interview questions for related roles