Technical SEO interviews can be intimidating.
You might be asked about crawling, rendering, canonicalisation, JavaScript, structured data, redirects, log files, Core Web Vitals, international SEO or a technical problem you've never encountered before.
And unlike some areas of SEO, there isn't always one obvious answer.
That can make candidates feel as though they need to memorise everything before walking into the interview.
You don't.
A strong technical SEO professional isn't someone who has every answer immediately.
It's someone who knows how to investigate a problem, ask the right questions, understand the potential impact and work towards a sensible solution.
That's exactly what you should demonstrate in your interview.
Here's how to prepare.
Start with the Technical SEO Fundamentals
You don't need to memorise every obscure technical SEO scenario ever discussed online.
But you should have a strong understanding of the fundamentals.
Before your interview, make sure you're comfortable explaining:
- Crawling and indexation
- Robots.txt
- XML sitemaps
- Canonical tags
- Redirects and status codes
- Internal linking
- Site architecture
- Duplicate content
- Structured data
- Mobile SEO
- Page speed and Core Web Vitals
- JavaScript rendering
- Hreflang
- Website migrations
Don't simply memorise definitions.
Try to understand how these areas connect.
For example, what happens if an important page is blocked in robots.txt?
What happens if a canonical points towards a redirected URL?
What happens when important pages have no internal links?
Technical SEO interviews often test whether you can apply your knowledge rather than repeat terminology.
Understand Crawling, Indexing and Ranking as Separate Processes
One of the most useful foundations for technical SEO is understanding the difference between crawling, indexing and ranking.
They're related, but they're not interchangeable.
A search engine first needs to discover and crawl a URL.
It then needs to determine whether that page should be indexed.
Only then can an indexed page potentially appear competitively within search results.
When diagnosing technical problems, separating these stages can help you think much more clearly.
If a page isn't appearing in search, ask:
Can Google discover it?
Can Google crawl it?
Is Google allowed to index it?
Has Google actually indexed it?
If it is indexed, is the problem simply that it isn't ranking competitively?
That framework alone can help you work through a surprising number of technical SEO questions.
Know Your HTTP Status Codes
You don't need to memorise every HTTP status code.
But there are several you should understand confidently.
These include:
- 200 – Successful request
- 301 – Permanent redirect
- 302 – Temporary redirect
- 404 – Not found
- 410 – Gone
- 5xx – Server errors
You should understand what these responses mean for users and search engines.
Interviewers may give you practical scenarios.
For example:
"A discontinued product has backlinks. What would you do with the URL?"
There isn't necessarily one answer.
If there's a genuinely relevant replacement product, a redirect might make sense.
If there's no equivalent replacement, allowing the URL to return a 404 or 410 may be more appropriate.
The important thing is explaining your reasoning.
Be Comfortable Talking About Canonicalisation
Canonicalisation frequently appears in technical SEO interviews because it tests whether you understand duplicate and similar URLs.
You should know:
- What a canonical tag does
- When self-referencing canonicals are useful
- How canonicals differ from redirects
- What happens when canonical signals conflict
- Why Google may choose a different canonical
- How parameters can create duplicate URLs
You may be given a scenario involving ecommerce filters, pagination, tracking parameters or duplicated product pages.
Don't rush to recommend canonical tags automatically.
First understand why the duplicate URLs exist and whether users or search engines actually need them.
Understand Robots.txt Versus Noindex
This is another common area of confusion.
Robots.txt controls crawling.
A noindex directive controls whether a page should appear in the index.
Those aren't the same thing.
If you block a URL from being crawled, Google may not be able to access a noindex directive placed on that page.
Being able to explain distinctions like this clearly demonstrates that you understand how search engines interact with websites.
Prepare for JavaScript SEO Questions
You don't need to become a JavaScript developer to work in technical SEO.
But modern websites increasingly rely on JavaScript frameworks, so having some understanding of how this affects search engines is valuable.
You should be comfortable discussing concepts such as:
- Client-side rendering
- Server-side rendering
- Static rendering
- Hydration
- Rendered HTML
- JavaScript-generated links and content
If you're shown a website where important content doesn't appear in the initial HTML, you should know how you might investigate whether Google can access and render it.
You could use tools such as Google Search Console's URL Inspection tool, browser developer tools or crawling software configured to render JavaScript.
You don't need to know how to rewrite the entire application.
Your role may be to identify the SEO problem, explain its impact and work with developers on the solution.
Know How to Investigate Indexation Problems
Imagine the interviewer says:
"We've published 50,000 pages, but only 20,000 appear to be indexed. What would you do?"
Don't immediately jump to a solution.
Start investigating.
You might want to understand:
- Whether all 50,000 pages should actually be indexed
- How the URLs are being discovered
- Whether they're internally linked
- Whether they're included in XML sitemaps
- Whether robots.txt is blocking anything
- Whether
noindexdirectives exist - Whether canonical tags point elsewhere
- Whether pages return the correct status codes
- Whether content is duplicated or very similar
- Whether server issues are preventing crawling
This is where interviewers can see how you think.
The strongest answer isn't necessarily the longest.
It's the one that follows a logical diagnostic process.
Learn How to Approach Website Migrations
Migrations are one of the highest-risk areas of technical SEO.
You should understand the basics of protecting organic visibility when URLs, domains, platforms or site structures change.
Be prepared to discuss areas such as:
- Benchmarking existing performance
- Crawling the existing website
- Mapping old URLs to new URLs
- Implementing redirects
- Preserving important content
- Reviewing internal links
- Updating canonicals
- Updating XML sitemaps
- Checking robots directives
- Testing the staging environment
- Crawling the new website
- Monitoring Search Console after launch
You don't need to have personally led a huge international migration to discuss the process intelligently.
If you haven't done something before, say so.
Then explain how you would approach it.
Get Comfortable with SEO Tools
Interviewers may ask which tools you've used.
Don't simply list every SEO platform you've ever opened.
Explain how you use them.
For example:
Screaming Frog
"I'd use it to crawl the site and investigate things like status codes, redirects, canonicals, metadata, internal linking and indexability."
Google Search Console
"I'd use it to investigate indexing, search performance, crawl-related issues and individual URLs."
Chrome DevTools
"I'd use it to inspect network requests, rendered content, performance issues and JavaScript behaviour."
Depending on your experience, you might also discuss:
- Sitebulb
- Ahrefs
- Semrush
- PageSpeed Insights
- Lighthouse
- Log file analysers
- Looker Studio
Knowing why you use a tool matters more than being able to name 20 of them.
Practise Diagnosing Problems Without Tools
You may not have access to your usual SEO software during an interview.
An interviewer might simply describe a scenario.
For example:
"Organic traffic dropped 40% overnight. What would you check?"
Avoid immediately saying "algorithm update".
Start with the basics.
Did tracking break?
Was the website down?
Were pages accidentally set to noindex?
Did robots.txt change?
Were redirects introduced?
Did the site's URL structure change?
Did the decline affect the entire site or only certain sections?
Was it traffic, rankings, impressions or conversions that actually declined?
When did the change begin?
The goal is to narrow the problem before diagnosing it.
Ask Questions Before Giving an Answer
Technical SEO scenarios are often deliberately incomplete.
That's because interviewers want to see whether you'll ask for more information.
If you're told:
"Traffic to our product pages has fallen. What would you do?"
You could ask:
"When did the decline start?"
"Did it affect all product pages or one category?"
"Did impressions decline as well as clicks?"
"Were there any website changes around that time?"
"Has search demand changed?"
"Are the pages still indexed?"
These questions demonstrate structured thinking.
You aren't avoiding the answer.
You're gathering enough information to provide a better one.
Say What You Would Check First
When faced with a complicated scenario, prioritisation matters.
Listing 30 possible causes may demonstrate knowledge, but it doesn't necessarily demonstrate good judgement.
Instead, explain your order of investigation.
For example:
"First, I'd confirm whether this is actually an SEO performance decline or a tracking problem. Then I'd determine which directories, page types and queries were affected. Once I've isolated the decline, I'd investigate technical changes and search visibility around the date it began."
That sounds considerably more confident than throwing every possible technical SEO issue into the conversation.
Don't Bluff When You Don't Know
You will probably be asked something you don't know.
That's normal.
Technical SEO is enormous.
You might have spent years working on ecommerce websites but have limited experience with international SEO.
You might understand JavaScript rendering but never have analysed server log files.
Don't invent an answer.
A much stronger response might be:
"I haven't personally dealt with that situation before, so I wouldn't want to pretend I know the exact solution. I'd start by confirming X and Y, then I'd review the relevant documentation before making a recommendation."
That demonstrates honesty and problem-solving.
Employers generally don't expect candidates to know everything.
They do expect them to recognise the limits of their knowledge.
Use Documentation as Part of Your Process
Knowing where to find reliable information is a skill.
Google's documentation changes.
Technical standards change.
Platforms change.
Frameworks change.
Trying to memorise every detail isn't realistic.
Good technical SEO professionals know how to research.
Depending on the problem, you might consult:
- Google Search Central documentation
- Search Console documentation
- Web.dev
- Schema.org
- Official platform documentation
- Browser documentation
- Trusted technical SEO resources
Saying you'd verify something before recommending a site-wide change isn't weakness.
It's responsible technical decision-making.
Prepare Examples of Real Problems You've Solved
Before your interview, identify three or four technical SEO problems you've worked on.
For each example, prepare to explain:
The problem
What was happening?
The investigation
How did you identify the cause?
The recommendation
What did you suggest?
The implementation
Did you fix it yourself or work with developers?
The result
What happened afterwards?
Examples might involve:
- Indexation problems
- Redirect issues
- Duplicate content
- Broken internal links
- Crawl problems
- Site migrations
- Core Web Vitals
- Structured data
- JavaScript rendering
- Incorrect canonicalisation
Specific examples make your technical knowledge much more credible.
Explain Your Own Contribution Clearly
Technical SEO projects often involve multiple people.
Perhaps a developer implemented the fix.
That's fine.
You don't need to pretend you wrote the code yourself.
Explain your contribution accurately.
For example:
"I identified that the faceted navigation was creating thousands of unnecessary crawlable URLs. I documented the affected patterns, recommended how they should be handled and worked with the development team to test the implementation."
That demonstrates technical SEO expertise without exaggerating your development skills.
Practise Explaining Technical Concepts Simply
One of the best ways to test whether you genuinely understand something is to explain it without jargon.
Imagine you're explaining canonicalisation to a Marketing Director.
Or JavaScript rendering to a Content Manager.
Or crawl efficiency to a CEO.
Could you explain why the issue matters without turning the conversation into a technical lecture?
Technical SEO roles increasingly involve communication with developers, product teams, marketers and senior stakeholders.
Understanding the problem is important.
Making other people understand it is another skill entirely.
Prepare for Questions Where There Is No Perfect Answer
Some technical SEO questions are designed to test judgement rather than knowledge.
You might be asked:
"Would you redirect this page?"
"Should these filtered URLs be indexed?"
"Would you use canonical tags here?"
"Should this content be rendered client-side?"
The correct answer may depend on context.
Don't be afraid to say:
"It depends."
But don't stop there.
Explain what it depends on.
What is the purpose of the page?
Does it have search demand?
Does it provide unique value?
Does it need to be accessible to users?
How many URLs are involved?
What are the technical constraints?
"It depends" becomes a strong answer when you clearly explain the variables affecting your decision.
Remember That Interviews Test How You Think
A technical SEO interview isn't a pub quiz.
The interviewer isn't simply counting how many definitions you can remember.
They're trying to understand how you approach problems.
Can you identify what information is missing?
Can you separate symptoms from causes?
Can you prioritise?
Can you communicate clearly?
Can you work with developers?
Can you admit when you don't know something?
Can you find the answer?
Those skills often matter more in the real job than recalling an obscure technical detail under pressure.
The Bottom Line
You don't need to know every answer to perform well in a technical SEO interview.
You need strong fundamentals.
You need curiosity.
You need a logical approach to investigation.
And you need enough confidence to say when something falls outside your experience.
Review crawling, indexation, redirects, canonicalisation, JavaScript, structured data, migrations and the other core technical areas.
But don't spend all your preparation time memorising definitions.
Practise solving problems.
Ask questions.
Explain your reasoning.
Think about business impact.
And prepare examples of situations where you've investigated something complicated and helped find a solution.
The strongest technical SEO candidates aren't walking encyclopaedias.
They're people you'd trust to work out what is happening when the answer isn't obvious.
If you're looking for your next opportunity in technical SEO, explore the latest roles on SEO Jobs UK.