Interview questions

SEO Interview Questions

17 SEO interview questions on crawling, indexing, technical SEO, content, links and measurement, with model answers for candidates and hiring managers.

SEO Interview Questions

What's here

17 SEO interview questions, grouped into 4 areas: how search works, technical seo, content, keywords and links and measurement and communication. Each one comes with why it is worth asking and what a strong answer contains, so the same question can be scored the same way by different interviewers.

  • Give a real or anonymised Search Console export and ask the candidate what they notice
  • Ask a myth-busting question (robots.txt to deindex, E-E-A-T as a ranking factor) to see whether they rely on primary sources
  • Use a traffic-drop scenario to test method rather than asking for definitions
For hiring teams

Cohesyve finds, contacts and tests SEO candidates on the real work, then ranks them for these interviews. 14-day free trial for 10 candidates, not charged until it ends.

Preparing for this interview yourself? Practise it free →

SEO roles range from specialist and executive to manager, and most interviews test the same foundations: how search engines crawl and index pages, technical SEO, content and search intent, links and authority, and how to measure and explain results. These SEO interview questions follow Google's own documentation where facts are involved. Each question comes with what a strong answer contains, so hiring managers can score consistently and candidates can prepare with confidence.

How Search Works

The foundations every SEO candidate should explain clearly.

  1. 1

    Explain the difference between crawling, indexing and ranking.

    Why ask it

    The basic model behind every SEO decision.

    What to look for

    Crawling is discovering and fetching pages; indexing is processing and storing them so they can be shown; ranking is ordering indexed pages for a query. Strong answers explain how problems at each stage look different in data (not crawled, crawled but not indexed, indexed but not ranking).
  2. 2

    If you want to keep a page out of Google's results, should you block it in robots.txt?

    Why ask it

    A common misconception that tests real understanding.

    What to look for

    No. Google says robots.txt is not a mechanism for keeping a page out of Google; it controls crawling. To keep a page out of the index, use a noindex directive (and let Google crawl the page to see it) or password-protect the page.
  3. 3

    What is a canonical URL, and does Google always follow rel=canonical?

    Why ask it

    Duplicate content handling is a core technical skill.

    What to look for

    The canonical is the representative URL Google chooses from a set of duplicate or very similar pages. You can signal a preference with rel=canonical, redirects and sitemap inclusion, but Google treats it as a hint, not a rule, and may choose differently when signals conflict.
  4. 4

    What is E-E-A-T, and is it a ranking factor?

    Why ask it

    Tests whether the candidate repeats myths or reads primary sources.

    What to look for

    Experience, expertise, authoritativeness and trustworthiness, with trust the most important. Google states that E-E-A-T itself is not a specific ranking factor; its systems use a mix of signals that can identify content showing these qualities. Good answers connect this to people-first content.
For hiring teams

Before the SEO interviews, see who can do the work

Cohesyve finds and contacts SEO candidates from your job description and tests each one on an AI job simulation of the role, so these questions go to a ranked shortlist. 14-day free trial for 10 candidates, not charged until it ends.

Technical SEO

How the candidate finds and fixes problems that stop pages performing.

  1. 5

    What are the Core Web Vitals, and what counts as a good score?

    Why ask it

    A standard technical question with precise answers.

    What to look for

    Largest Contentful Paint for loading (good within 2.5 seconds), Interaction to Next Paint for responsiveness (good under 200 milliseconds; it replaced First Input Delay in 2024) and Cumulative Layout Shift for visual stability (good under 0.1). Strong answers note that Google describes them as aligned with what its ranking systems reward, rather than overstating their weight.
  2. 6

    How does hreflang work, and what mistakes do you see most often?

    Why ask it

    International sites depend on it.

    What to look for

    Hreflang tells Google which pages are language or regional versions of the same content, using HTML link tags, HTTP headers or sitemaps. Each version must list itself and all others; if pages do not point to each other, the annotations are ignored. x-default sets a fallback. Common mistakes: missing return links, wrong codes, pointing to non-canonical URLs.
  3. 7

    Walk me through how you would run a technical audit on a site you have never seen.

    Why ask it

    Shows method and prioritisation.

    What to look for

    A crawl to find status codes, redirects, broken links, duplicate titles and thin pages; Search Console for indexing and coverage issues; checks on robots.txt, sitemaps, canonicals and structured data; page speed; and rendering for JavaScript-heavy sites. Then prioritising fixes by impact and effort.
  4. 8

    How do you protect search traffic during a site migration?

    Why ask it

    Migrations are high-risk projects.

    What to look for

    Mapping every old URL to its new equivalent with permanent redirects, keeping content and internal links consistent, updating canonicals and sitemaps, testing on staging, benchmarking traffic and rankings before launch, and monitoring crawl errors and traffic closely afterwards.
  5. 9

    What problems can JavaScript-heavy sites create for SEO?

    Why ask it

    Many modern sites render content in the browser.

    What to look for

    Content or links that only appear after scripts run may be discovered late or missed; rendering takes extra resources. Solutions include server-side rendering or prerendering, real links in the HTML, and checking rendered output with URL inspection tools.

Measurement and Communication

How the candidate proves value and handles setbacks.

  1. 15

    Organic traffic dropped sharply last week. How do you investigate?

    Why ask it

    A realistic scenario that tests method under pressure.

    What to look for

    Confirming the drop is real (tracking changes, seasonality), segmenting by page, query, device and country, checking Search Console for indexing or manual action issues, reviewing recent site changes and deploys, and checking for known search updates. Then a clear explanation and plan.
  2. 16

    Which metrics do you report to leadership, and why?

    Why ask it

    SEO value has to be explained in business terms.

    What to look for

    Organic traffic and conversions or revenue from organic, visibility for priority topics, and leading indicators such as indexed pages and rankings for target terms. Strong candidates avoid vanity metrics and explain the time lag in SEO results.
  3. 17

    How do you get developers to prioritise your SEO fixes?

    Why ask it

    SEO depends on other teams.

    What to look for

    Clear tickets with the problem, evidence, expected impact and acceptance criteria, grouping small fixes, building relationships with the engineering team, and following up with results so the next request is easier.

Running the interview well

  • 1Give a real or anonymised Search Console export and ask the candidate what they notice
  • 2Ask a myth-busting question (robots.txt to deindex, E-E-A-T as a ranking factor) to see whether they rely on primary sources
  • 3Use a traffic-drop scenario to test method rather than asking for definitions
  • 4Ask for an example of a result they drove and how they isolated their impact
  • 5Match the depth to the role: technical SEO roles need more crawling and rendering questions, content roles more intent and editorial questions
  • 6Check how they explain SEO to non-specialists; most of the job involves persuading other teams

Common questions

What are the most common SEO interview questions?

Expect questions on crawling, indexing and ranking, robots.txt versus noindex, canonical tags, Core Web Vitals, hreflang, technical audits, site migrations, keyword research and search intent, link building, internal linking, and diagnosing traffic drops.

How should I prepare for an SEO interview?

Review Google's Search Central documentation on the basics, prepare two or three examples of results you drove with numbers you can back up, and practise a traffic-drop diagnosis out loud. If you have no job experience, run SEO on a personal site or a volunteer project and talk through that.

What are the Core Web Vitals?

Google's Core Web Vitals are Largest Contentful Paint (loading, good within 2.5 seconds), Interaction to Next Paint (responsiveness, good under 200 milliseconds) and Cumulative Layout Shift (visual stability, good under 0.1).

Does robots.txt remove a page from Google?

No. Google says robots.txt controls crawling and is not a way to keep a page out of its results. Use a noindex directive or password protection instead.

What tools should an SEO candidate know?

Google Search Console and an analytics platform are close to essential. Most roles also expect familiarity with a site crawler and a keyword research tool. Interviewers usually care more about what you do with the data than which paid tools you have used.

For hiring teams

Save these questions for the SEO candidates who can do the work

Cohesyve takes your SEO job description, finds candidates, reaches out to them and runs an AI job simulation of the real work, then returns a ranked shortlist.

1,500+

assessments completed

50%

faster time-to-hire

5 min

from JD to assessment

14-day free trial · 10 candidates · Not charged until the trial ends

For job seekers

Preparing for an SEO interview yourself? Practise on an AI job simulation of the role. 3-day free trial, cancel anytime.

Practise an SEO interview free →

See Cohesyve in action

Free 30-min walkthrough

See it on your role