My First SEO Internship Interview: Questions I Was Asked and How I Prepared
When I applied for my SEO internship at Shaligram Infotech, I was nervous – I had theoretical knowledge from my BBA but very little hands‑on experience. The interview turned out to be less scary than I expected, mostly because I prepared systematically.
This post shares the actual questions I was asked, how I answered them, and how you can prepare for your own SEO internship interview.
The Interview Format
- Duration: 30 minutes (first round, followed by a small task)
- Interviewer: SEO team lead + one senior analyst
- Mode: In‑person (but the same principles apply for video calls)
- Focus: Technical understanding, problem‑solving, and attitude
5 Real Questions I Was Asked
1. “Explain SEO in simple words to a business owner who knows nothing about the internet.”
My answer (paraphrased):
“SEO makes your website show up higher when people search for what you sell. When someone searches ‘best cafe in Ahmedabad’, SEO helps your cafe appear on the first page instead of page 5. It includes things like fixing your website speed, using the right words, and getting other websites to mention you.”
Why it worked: I avoided jargon and focused on the outcome (more customers). The interviewer later told me this is what they look for: can you talk to clients, not just to other SEOs.
How to prepare: Practice explaining SEO without using terms like “backlinks”, “crawl budget”, or “indexation”. Use an analogy (like a library, a map, or a shop window).
2. “What free SEO tools have you used? Show me one thing you learned from them.”
My answer:
“I’ve used Google Search Console, PageSpeed Insights, and Ubersuggest. For example, in Search Console, I discovered that my portfolio had 3 pages with ‘Crawled – currently not indexed’. I added more content to those pages and requested re‑indexing. Within two weeks, all three were indexed.”
Why it worked: I didn’t just list tool names – I described a specific action and a result.
How to prepare: Pick 2–3 free tools. For each, have one concrete example of a problem you found and how you fixed it (even if it was on your own site).
3. “What’s the difference between a 301 redirect and a 302 redirect?”
My answer:
“301 is permanent. You use it when a page has moved forever – like when you change a URL or delete a product page and want to send users and link equity to the new page. 302 is temporary – for A/B testing or a short‑term promotion where you plan to bring the old page back.”
Why it worked: I knew both the technical meaning and the practical use case.
How to prepare: Study the most common HTTP status codes (200, 301, 302, 404, 503) and why they matter for SEO.
4. “A client says they’ve been doing SEO for 6 months but see no results. What do you do?”
My answer:
“First, I’d ask what they expected – sometimes expectations are unrealistic. Then, I’d check their Google Search Console and Analytics to see if traffic is actually zero or if they just missed it. I’d look for technical issues (blocked pages, broken sitemap) and basic on‑page errors. Finally, I’d check if they were tracking the wrong keywords – maybe they target broad terms instead of local, low‑competition keywords.”
Why it worked: It showed I could troubleshoot without blaming the client or giving up.
How to prepare: Think of a step‑by‑step diagnostic flow: verify data → check indexing → review technical basics → reassess keyword strategy → set up a small test.
5. “What’s a Google algorithm update you know about, and how should a business react?”
My answer:
“The Helpful Content Update. It penalises sites that write for search engines first and people second. A business should focus on answering real customer questions, not stuffing keywords. Also, don’t panic and make sudden changes – wait for data and then improve content quality.”
Why it worked: I named a specific update and gave a calm, measured reaction (which interviewers like).
How to prepare: Know 2–3 recent updates (Helpful Content, Core Web Vitals, Product Reviews) and the principle: “Make good content for people, and Google will eventually reward it.”
How I Prepared (The Week Before)
| Area | What I Did |
|---|---|
| Technical basics | Watched a 20‑min YouTube recap of SEO fundamentals (crawling, indexing, ranking). |
| Tool practice | Spent 1 hour exploring Google Search Console on my own portfolio. Took notes on 3 insights. |
| Client scenarios | Wrote down answers to 5 “what would you do” questions (e.g., traffic drop, no backlinks, duplicate content). |
| My portfolio | Practised explaining my cafe case study in 60 seconds (problem → action → result). |
| Questions for them | Prepared 3 questions to ask at the end (e.g., “What does success look like for an intern here?”). |
The Task I Received After the Interview
I was asked to perform a mini technical audit on a sample website: find 3 issues, explain why each was a problem, and suggest fixes. I submitted a one‑page report within 24 hours. That report convinced them to hire me.
Takeaways for You
- You don’t need to know everything. Saying “I don’t know, but I’ll learn” is acceptable if you then describe how you’d find the answer.
- Show, don’t just tell. Mention concrete examples from your own portfolio or practice projects.
- Prepare stories. Use the STAR method (Situation, Task, Action, Result) for at least 2 experiences.
- Ask thoughtful questions. It shows genuine interest and critical thinking.
Final Advice
Your first SEO interview is not a test of mastery – it’s a test of foundational knowledge, problem‑solving attitude, and communication skills. Build a small portfolio (even just 2 case studies), practice talking about it, and you’ll be ahead of 80% of candidates.
Have your own interview experience or question? Connect with me on LinkedIn.
📘 Check my SEO On‑Page Playbook for technical optimisation tips.