SEO Specialist Interview Questions (2026) and How to Answer

Behavioural questions (1–10)

How you've handled real situations. Answer each with one true story, in STAR order.

1. 1.Tell me about an SEO change that led to a measurable traffic increase.

   What they're really asking: Can you tie your work to a result, not just an activity?

   Answer outline (STAR)

   • SituationA site with flat or declining organic traffic in a specific area.
   • TaskFind and fix the highest-impact issue.
   • ActionAudited crawl data and search console, found thin or duplicate pages cannibalizing a key term, consolidated and rewrote them.
   • ResultThe traffic and ranking change, measured over a defined period.

   Full sample answer (fictional example)

   A B2B software client had three blog posts all loosely targeting the same core term, each ranking on page two and splitting traffic between them. I audited the pages in Search Console, confirmed they were cannibalizing each other, and consolidated the strongest content from all three into one comprehensive page, 301-redirecting the other two. I rewrote the headers around the core term and its related questions, and updated internal links to point to the surviving page. Within six weeks it moved from page two to position four, and organic traffic to that URL increased by 85 percent over the prior combined traffic of the three pages.

2. 2.Tell me about a time you had to convince engineers to prioritize an SEO fix.

   What they're really asking: Can you get technical work prioritized against competing deadlines?

   Answer outline (STAR)

   • SituationA site speed or indexing issue that engineering didn't see as urgent.
   • TaskGet the fix scheduled without overstating the risk.
   • ActionQuantified the issue's cost in lost traffic or crawl budget, proposed the smallest fix that solved it, joined the sprint planning to answer questions directly.
   • ResultThe fix shipped, and the metric that improved afterward.

   Full sample answer (fictional example)

   Our e-commerce site's category pages were taking over six seconds to load on mobile, and engineering had it backlogged behind feature work. I pulled Search Console and analytics data showing the pages' indexing rate had slowed and mobile bounce rate was 22 percent higher than desktop. Instead of asking for a full rebuild, I proposed the smallest fix: lazy-loading product images, which their estimate showed was a two-day job. I joined their sprint planning to answer questions directly rather than just filing a ticket. It shipped the following sprint, and mobile load time dropped to under three seconds, with category page traffic up 18 percent over the next month.

3. 3.Describe a time you had to explain a technical SEO issue to a non-technical stakeholder.

   What they're really asking: Can you translate crawling, rendering or indexing into business language?

   Answer outline (STAR)

   • SituationA stakeholder confused about why a redesign hurt organic traffic.
   • TaskGet buy-in for the fix without a technical argument that lost the room.
   • ActionUsed a simple analogy, showed the actual lost pages and traffic in dollars, proposed a phased fix.
   • ResultApproval secured, and the stakeholder's understanding going forward.

   Full sample answer (fictional example)

   After a site redesign, organic traffic to our resources section dropped sharply, and the marketing director wanted to know why in a meeting that afternoon. I avoided terms like 'canonical tags' and instead showed her a before-and-after screenshot: the old URLs returned content, the new ones returned a 'page not found' because redirects were never set up during launch. I translated the lost traffic into estimated lost lead volume per week using our usual conversion rate, which made the urgency concrete. She approved an emergency fix that day. I also proposed a pre-launch SEO checklist so future redesigns wouldn't repeat it.

4. 4.Tell me about a time an SEO recommendation of yours was ignored, and what happened.

   What they're really asking: Can you handle being overruled, and were you right to raise it?

   Answer outline (STAR)

   • SituationA content or technical recommendation that leadership chose not to act on.
   • TaskMake the case clearly, then respect the decision.
   • ActionDocumented the recommendation and expected impact, let the decision stand, tracked the outcome anyway.
   • ResultWhat happened to the metric, and whether it changed minds later.

5. 5.Tell me about diagnosing a sudden drop in organic traffic.

   What they're really asking: Can you work through a traffic-drop investigation methodically under pressure?

   Answer outline (STAR)

   • SituationA sharp week-over-week organic traffic decline with no warning.
   • TaskFind the cause fast and recommend a fix.
   • ActionChecked Search Console for manual actions or indexing issues, checked recent site changes and a competitor or algorithm update, then isolated by page and query.
   • ResultThe cause found, and the recovery timeline once it was fixed.

   Full sample answer (fictional example)

   Traffic to our main product pages fell 30 percent week over week with no warning. I checked Search Console first and ruled out manual actions or a spike in indexing errors. Next I checked our deployment log and found a robots.txt change pushed three days earlier that accidentally blocked the product directory. I confirmed it by testing a URL in the URL inspection tool, which showed it was now excluded from indexing. I got the robots.txt reverted within the hour and requested re-indexing for the affected pages. Traffic recovered to its prior level within about ten days, once Google re-crawled and re-indexed the pages.

6. 6.Tell me about a time you found a technical SEO issue nobody else had noticed.

   What they're really asking: Can you spot problems proactively, not just when told to look?

   Answer outline (STAR)

   • SituationA site that looked healthy on the surface but had an underlying crawl or indexing problem.
   • TaskCatch it before it caused real damage.
   • ActionRan a routine crawl, noticed an unusual pattern in indexed-page counts, traced it to a faceted navigation generating infinite URLs.
   • ResultThe fix applied, and the crawl budget or indexing improvement that followed.

7. 7.Tell me about collaborating with a content team on an SEO-driven content plan.

   What they're really asking: Can you work with writers without just handing them a keyword list?

   Answer outline (STAR)

   • SituationA content calendar built around keyword opportunities.
   • TaskGet content that served search intent and read well.
   • ActionShared not just keywords but the intent and questions behind them, reviewed drafts for structure, not just keyword placement.
   • ResultThe content's ranking and traffic performance, and what the writers said about the process.

8. 8.Tell me about a time you had to recover rankings after a Google algorithm update.

   What they're really asking: Can you respond to things outside your control without guessing wildly?

   Answer outline (STAR)

   • SituationA core algorithm update that caused a ranking or traffic drop.
   • TaskUnderstand the likely cause and respond appropriately.
   • ActionCompared affected pages for common patterns, checked Google's own guidance on the update, avoided over-reacting with unrelated changes.
   • ResultWhat recovered, over what timeframe, and what you learned about the update's focus.

9. 9.Tell me about presenting SEO results to someone skeptical of SEO's value.

   What they're really asking: Can you earn credibility with someone who doesn't trust the discipline?

   Answer outline (STAR)

   • SituationA stakeholder who saw SEO as unmeasurable or slow.
   • TaskShow concrete, attributable impact.
   • ActionPicked one clear before-and-after case tied to revenue, avoided jargon, invited questions about the methodology.
   • ResultWhether their view changed, and what they asked for next.

10. 10.Tell me about a time you had to say an SEO tactic wouldn't work, even though someone wanted it to.

    What they're really asking: Will you be honest about limits instead of promising results you can't control?

    Answer outline (STAR)

    • SituationA request for a tactic that was outdated or against best practice.
    • TaskRedirect effort toward something that would actually help.
    • ActionExplained why the tactic had stopped working, with evidence, and proposed an alternative aligned with current guidance.
    • ResultWhat was done instead, and the result compared to what was originally hoped for.

Technical and role-skill questions (11–22)

Can you do the work itself? Think out loud and name the trade-offs.

1. 11.Walk me through how you'd diagnose a sudden drop in organic traffic.

   What they're really asking: Core diagnostic skill, asked in nearly every SEO interview.

   Answer outline

   • Check Google Search Console first for manual actions, security issues or indexing drops.
   • Check for recent site changes: a migration, robots.txt edit, template change or redesign.

   Full sample answer (fictional example)

   I start in Google Search Console to rule out the two most serious causes: a manual action under Security & Manual Actions, or a sudden jump in indexing errors. If those are clean, I check whether anything changed on the site recently, like a deployment, a robots.txt edit, a template change, or a migration, since those cause a large share of sudden drops. If nothing changed on our end, I check the date against known algorithm update rollouts. Then I segment the drop by page, query and device to see if it's site-wide or concentrated, which usually points toward the cause. I report findings with a confidence level, not just a guess.

2. 12.What's the difference between crawling, indexing and ranking?

   What they're really asking: SEO fundamentals that separate serious candidates from keyword-stuffing enthusiasts.

   Answer outline

   • Crawling is Google discovering a page; indexing is storing it for retrieval; ranking is ordering indexed pages for a query.
   • A page can be crawled but not indexed, for example if it's marked noindex or seen as low-value duplicate content.

   Full sample answer (fictional example)

   Crawling is Googlebot discovering a URL and downloading its content. Indexing is Google deciding to store that page so it can be retrieved later, which doesn't happen automatically just because a page was crawled; a page marked noindex, or seen as low-value duplicate content, can be crawled but never indexed. Ranking is the separate process of ordering all indexed pages for a given search query based on relevance and other signals. I mention this distinction often in audits, because teams sometimes focus entirely on ranking factors for a page that was never indexed in the first place, which makes the ranking work pointless until indexing is fixed.

3. 13.How do you decide which keywords to target for a new piece of content?

   What they're really asking: Can you prioritize by opportunity, not just search volume?

   Answer outline

   • Combine search volume, competition and the searcher's intent, not volume alone.
   • Check what's currently ranking to judge whether you can realistically compete.

   Full sample answer (fictional example)

   I don't rely on search volume alone, since a high-volume term with intense competition and low commercial intent can be a poor use of time. I look at volume alongside competition, estimating realistic ranking potential by checking who currently holds the top results and whether we could credibly compete with them. I also weigh searcher intent: whether they want to buy, compare, or just learn, which should match the page type we're building. Where several related keywords share the same intent, I group them into one strong page rather than writing several thin pages that would end up competing with each other.

4. 14.How would you approach a technical SEO audit of an unfamiliar site?

   What they're really asking: Structured thinking under an open-ended request.

   Answer outline

   • Start with crawlability and indexing: robots.txt, sitemap, crawl errors in Search Console.
   • Check site speed, mobile usability, and whether key pages render correctly for Googlebot.

5. 15.What's your view on link building, and what tactics do you actually use?

   What they're really asking: Do you understand links as a lagging trust signal, not a game to be gamed?

   Answer outline

   • Prioritize earning links through content worth citing over buying or spamming them.
   • Digital PR, original data or tools, and competitor backlink gap analysis are common legitimate tactics.

6. 16.How do you measure the success of an SEO campaign beyond rankings?

   What they're really asking: Can you connect SEO to revenue, not vanity metrics?

   Answer outline

   • Track organic traffic, conversions from organic traffic, and revenue or leads attributable to it.
   • Rankings are a leading indicator; traffic and conversions are what the business actually cares about.

7. 17.How does structured data (schema markup) help a page's search performance?

   What they're really asking: Practical knowledge of a commonly underused technical lever.

   Answer outline

   • It doesn't directly boost rankings, but it can earn rich results like star ratings or FAQ snippets.
   • Use JSON-LD, validate it, and apply the schema type that actually matches the page's content.

8. 18.What's the difference between a 301 and a 302 redirect, and when do you use each?

   What they're really asking: A fundamental that trips up less experienced candidates.

   Answer outline

   • A 301 signals a permanent move and passes most ranking signals to the new URL.
   • A 302 signals temporary, and search engines may keep indexing the original URL.

9. 19.How does Googlebot render JavaScript-heavy pages, and what problems can that cause?

   What they're really asking: Increasingly important as sites move to JS frameworks.

   Answer outline

   • Google crawls, then renders JavaScript in a second wave, which can delay indexing.
   • Content injected client-side may not be seen if rendering fails or times out.

10. 20.What's your approach to fixing duplicate content issues?

    What they're really asking: Can you resolve cannibalization instead of just flagging it?

    Answer outline

    • Identify whether duplicates are near-identical pages or genuinely overlapping topics.
    • Use canonical tags, 301s or consolidation depending on whether the pages should merge or simply point search engines to one version.

11. 21.How do Core Web Vitals affect search performance, and how do you improve them?

    What they're really asking: Tests your practical knowledge of how page experience affects search performance.

    Answer outline

    • They're a ranking factor among many, and a stronger signal for user experience than for rankings alone.
    • Improve Largest Contentful Paint with image optimization and faster server response; improve Cumulative Layout Shift by reserving space for dynamic elements.

12. 22.How would you build an internal linking strategy for a large site?

    What they're really asking: Can you use a lever most sites underuse?

    Answer outline

    • Identify your most important 'hub' pages and link to them generously from related content.
    • Use descriptive anchor text rather than generic 'click here' links.

Take-home or live exercise: tips

SEO interviews often include a live or take-home audit of a real page or small site, or a traffic-drop case study with a dataset to diagnose.

• State your diagnostic order out loud (Search Console, recent changes, algorithm updates, segmentation) so the interviewer sees your process, not just your conclusion.
• In a live audit, check crawlability and indexing before judging on-page content, since content fixes are pointless on an unindexed page.
• Quantify findings where you can, even roughly, rather than listing issues with no sense of priority.
• End with a short, ranked list of recommendations, not an exhaustive list of every minor issue found.

Situational questions (23–30)

Scenarios that test judgement: say what you'd do first, and why.

1. 23.A site migration is planned and nobody has mentioned SEO. What do you do?

   What they're really asking: Can you get ahead of a classic traffic-loss risk?

   Answer outline

   • Raise it immediately: migrations are one of the most common causes of major traffic loss.
   • Insist on a redirect map, URL structure review and pre/post-launch crawl comparison.

   Full sample answer (fictional example)

   I raise it immediately, since migrations are one of the most common causes of major, sometimes permanent, traffic loss when SEO isn't involved early. I'd ask for the full list of old and new URLs so I can build a redirect map before launch, and review whether the new URL structure preserves the site's existing hierarchy and keyword-relevant paths. I'd also run a full crawl of the current site to document its baseline, so I can compare against a post-launch crawl. After launch, I'd monitor indexing and rankings closely for several weeks and keep a rollback plan for redirects in case something was missed.

2. 24.Marketing wants to publish ten thin pages targeting keyword variations of the same topic. How do you respond?

   What they're really asking: Will you push back on a tactic likely to hurt rather than help?

   Answer outline

   • Explain the risk of cannibalization and thin-content issues.
   • Propose one strong page covering the topic with clear sections for each variation instead.

   Full sample answer (fictional example)

   I'd explain the risk clearly: ten thin pages on close keyword variations often end up competing against each other, splitting both links and relevance instead of building one strong, authoritative page. I'd propose consolidating into a single comprehensive page with clear sections addressing each variation, which tends to perform better in search and is easier for users to navigate too. If marketing has a real reason to keep pages separate, like genuinely distinct audiences, I'd ask to see that reasoning and adjust my recommendation. Usually, once I show a competitor example ranking well with the consolidated approach, the team agrees to combine them.

3. 25.You have a limited budget and could invest it in content or technical fixes. How do you choose?

   What they're really asking: Can you prioritize with judgment, not just whichever is trendier?

   Answer outline

   • Look at what's actually capping performance: is content missing, or is technical debt blocking what's already there from ranking?
   • Fix any severe technical blockers first, since content can't outrank what isn't indexed well.

4. 26.A competitor suddenly outranks you for your most valuable keyword. What do you do?

   What they're really asking: Can you respond to competitive pressure with analysis, not panic?

   Answer outline

   • Analyze what changed on their page and site, not just that they moved up.
   • Check if your own page lost something (content freshness, links, technical issue) rather than assuming they simply did better.

5. 27.You discover the site has a manual penalty in Search Console. What do you do?

   What they're really asking: Can you handle a serious, time-sensitive issue correctly?

   Answer outline

   • Read the specific violation Google cited rather than guessing at the cause.
   • Fix the underlying issue completely before submitting a reconsideration request.

   Full sample answer (fictional example)

   First, I read the specific violation Google cited rather than assuming I know the cause, since manual actions can range from unnatural links to thin content, and the fix is different for each. For a links-based penalty, I'd audit the backlink profile, identify the violating links, request removal where possible and disavow the rest. I wouldn't submit a reconsideration request until I was confident the issue was fully resolved, since a rejected request can slow recovery further. I'd document everything done, since Google expects to see the remediation steps clearly in the request, not just a promise it won't happen again.

6. 28.Leadership wants to see ranking improvements within one month of a new SEO hire. How do you manage expectations?

   What they're really asking: Can you set a realistic timeline without sounding like you're avoiding accountability?

   Answer outline

   • Explain which fixes act fast (technical, indexing) versus which take longer (content, authority building).
   • Propose a quick win alongside the longer-term roadmap so there's visible progress early.

7. 29.A new CMS migration is about to launch without SEO review. What do you do?

   What they're really asking: Will you escalate a high-risk situation in time to prevent damage?

   Answer outline

   • Raise the risk immediately to whoever can delay launch if needed.
   • Request a staging-environment crawl comparison before go-live.

8. 30.You find that a competitor is using tactics that violate search engine guidelines and it's working for them. What do you do?

   What they're really asking: Will you chase short-term gains or protect the site long-term?

   Answer outline

   • Don't copy the tactic just because it's currently working.
   • Explain the risk of a penalty to stakeholders tempted to imitate it.

Red flags to avoid in your answers

Each one is quick to fix before the day.

1. Talking only about rankings, never traffic, conversions or revenue.

   Connect every example to a business outcome, not just a position change.

2. Recommending risky link-building or content tactics without acknowledging the risk.

   Show awareness of search engine guidelines and the cost of a penalty.

3. Treating SEO as purely technical or purely content, never both.

   Show you can work across technical, content and off-page levers depending on what's actually capping performance.

4. No clear process for a traffic-drop diagnosis, just guessing at causes.

   Walk through a structured framework: data checks first, then site changes, then external factors.

How to prepare for a SEO specialist interview in 7 days

An hour or two a day is enough; the order matters more than the length.

1. 1

   Day 1: Audit the target company

   Run a basic crawl and Search Console-style review of the company's own site and note two or three real issues you could discuss.

2. 2

   Day 2: Traffic-drop framework

   Rehearse your diagnostic order out loud: Search Console checks, recent site changes, algorithm updates, segmentation.

3. 3

   Day 3: Technical refresher

   Review crawling, indexing, redirects, canonical tags, structured data and Core Web Vitals until you can explain each in plain language.

4. 4

   Day 4: Case study prep

   Prepare one detailed case study: the problem, your diagnosis, the fix, and the measured traffic or revenue result.

5. 5

   Day 5: Software comfort check

   Spend an hour in Google Search Console and one other tool (Screaming Frog, Ahrefs or similar) refreshing your fluency with core reports.

6. 6

   Day 6: Keyword drills

   Write four STAR stories: a traffic win, convincing engineering, explaining a technical issue simply, and a recommendation that was ignored.

7. 7

   Day 7: Practice block

   Do a mock interview with a live audit exercise and two technical questions, then rest.

Questions to ask the interviewer

Pick two or three; the answers tell you whether you want the job.

1. What tools does the team use for tracking rankings, technical issues and analytics?
2. How closely does the SEO function work with engineering and content teams here?
3. What's the biggest technical or content gap holding organic traffic back right now?
4. How is SEO success measured and reported to leadership?
5. What did the last major SEO project look like, and what was the outcome?

Preparation tips

• Review the company's site beforehand and note two or three real technical or content issues you noticed.
• Rehearse a traffic-drop diagnostic framework out loud: Search Console checks, site changes, algorithm updates, segmentation.
• Bring one case study you can walk through in detail: the problem, the fix, and the measured result.
• Brush up on at least one SEO tool's core reports (Search Console, Screaming Frog, Ahrefs or similar).

Prepare the general questions too: tell me about yourself, why do you want to work here? and why are you leaving? Afterwards, send a thank-you email; when the offer comes, negotiate the salary.