One of the easiest ways to convince yourself you’re not ready for an SEO job is to read the job description too literally.
You open a vacancy that sounds interesting.
Then you get to the requirements.
Two years of experience.
Technical SEO.
Content.
Link building.
GA4.
Search Console.
Screaming Frog.
Semrush.
Ahrefs.
WordPress.
Shopify.
Reporting.
Client communication.
AI.
Suddenly, an “SEO Specialist” vacancy looks like they’re searching for someone who has mastered the entire internet.
If you’re trying to land your first SEO role, it’s very easy to close the tab and think:
I’m not ready for this.
I think that’s often the wrong conclusion.
Job descriptions tell you what an employer would like to find. Your job as an applicant is to understand what they’re really asking for, identify which gaps actually matter, and decide whether you could reasonably grow into the role.
You don’t need to tick every box before you’re allowed to apply.
Start by Separating Responsibilities From Requirements
This is one of the first things I’d do when reading an SEO vacancy.
There is a difference between:
What will you be doing?
and:
What do we need you to know already?
Job descriptions don’t always make that distinction particularly clear.
Take a line like:
“Creating structured roadmaps based on audit findings.”
That can sound intimidating if you’ve never created an “SEO roadmap”.
But strip away the corporate language.
They’re essentially saying:
Can you find SEO problems, decide which ones matter most, and organise your recommendations into a sensible order?
That’s much easier to understand.
Maybe you’ve never called it a roadmap.
But perhaps you’ve audited your own website and noticed:
- Some pages have missing title tags;
- Several important pages aren’t internally linked very well;
- Images are unnecessarily large;
- There are broken links;
- A few pages target the same topic;
- Important pages aren’t receiving impressions.
You decide to fix the technical problems first, improve the pages second, and work on content opportunities after that.
Congratulations.
You’re beginning to think in roadmaps.
A lot of intimidating SEO terminology becomes less intimidating once you translate it into the actual task.
“2–3 Years of Experience”
This is probably where many people stop reading.
A vacancy asks for two years of experience.
You have six months.
Or you’ve spent a year learning SEO but haven’t worked professionally yet.
Should you apply?
Sometimes, yes.
I’m not saying experience requirements are meaningless. If a company needs someone to independently manage major client accounts from day one, experience matters.
But years are often used as a shortcut for capability.
The better question is:
What do they expect someone with two years of experience to be able to do?
Read the rest of the job description.
If they’re expecting you to develop enterprise SEO strategy, lead migrations, manage a team and present to senior executives independently, you’re probably looking at a genuinely experienced position.
But if most of the responsibilities involve audits, keyword research, on-page optimisation, reporting, CMS updates and using common SEO tools, you might be closer than the number of years suggests.
Don’t automatically reject yourself because you have 18 months and they asked for two years.
Let them decide whether your experience is enough.
“Strong Understanding of the Three Pillars of SEO”
This sounds bigger than it is.
They’re probably not expecting you to have discovered a new way of understanding Google’s ranking systems.
They want you to understand the major areas of SEO.
Generally, that means being comfortable with things like on-page/content SEO, technical SEO and authority/off-page SEO.
For an entry-level candidate, I would want you to understand the purpose of each.
Can you explain why keyword research matters?
Do you understand search intent?
Can you optimise a title tag without stuffing it with keywords?
Do you know why internal links matter?
Do you understand what a backlink is?
What happens when a URL returns a 404?
What’s a redirect?
What’s a canonical tag?
What’s the difference between crawling and indexing?
You don’t need ten years of experience to start understanding these things.
More importantly, you don’t need to know every possible SEO problem.
You need enough foundational knowledge to recognise the problem and start investigating it.
Don’t Be Intimidated by the Tool List
SEO job descriptions love tool lists.
You might see something like:
“Experience using SEO tools such as Semrush, Screaming Frog, Ahrefs, GA4 and Search Console.”
A beginner can read that and think they need professional-level mastery of five different platforms.
I wouldn’t interpret it that way.
I’d ask what each tool is actually being used for.
Search Console helps you understand how a website performs in Google Search.
GA4 helps you understand what people do after reaching the website.
Screaming Frog helps you crawl and analyse websites.
Semrush and Ahrefs can help with things like keywords, competitors, rankings and backlinks.
Once you understand the purpose, you can learn the interfaces.
And tools change anyway.
I’ve worked with enough SEO platforms over my career to know that learning the buttons is rarely the hardest part.
Understanding why you’re opening the tool in the first place matters more.
If you’ve learnt keyword research on one platform, you can learn it on another.
If you understand crawling, moving between crawling tools becomes easier.
Don’t confuse knowing software with knowing SEO.
The Same Applies to CMS Platforms
A job might mention:
“Experience with Webflow, WordPress, Shopify and HubSpot.”
Do you need professional experience with all four?
Probably not unless the vacancy specifically says so.
What I’d want as a beginner is basic confidence working with websites.
If you’ve used WordPress, that’s useful.
Can you edit a page?
Change a title?
Add content?
Create an internal link?
Change image alt text?
Understand where a URL comes from?
Recognise headings?
Install or work around plugins?
If you understand how websites and content management systems work, learning another CMS becomes easier.
This is also why I encourage people learning SEO to build a website.
You learn differently when you’re responsible for the thing you’re optimising.
Break something.
Fix it.
Change a URL.
Create a redirect.
Publish an article.
Connect Search Console.
Submit a sitemap.
Watch what Google does.
That experience counts.
“Proactive Mindset” Doesn’t Mean Knowing Everything
Here’s another common requirement:
“Proactive mindset — identifying issues and providing detailed recommendations.”
That sounds like you need to walk into the company on Monday and immediately identify SEO problems nobody else has noticed.
I read it differently.
They’re telling you they don’t want someone who waits to be given every individual task.
That’s a skill you can start developing before your first SEO job.
Instead of asking:
“What should I do next?”
Start asking:
“What does the data suggest I should investigate next?”
If impressions suddenly fall, investigate.
If an important page isn’t indexed, investigate.
If a page ranks at position eight with lots of impressions but poor CTR, investigate.
If a crawler suddenly reports hundreds of broken links, investigate.
You won’t always know the answer.
That’s okay.
Being proactive doesn’t mean magically knowing the solution.
Sometimes being proactive is saying:
“I noticed this. I don’t know exactly what’s causing it yet, but here’s what I’ve checked and what I think we should investigate next.”
That’s a valuable habit at every level of SEO.
“Keep Up With SEO News and AI”
I actually like seeing this in entry-level job descriptions.
SEO changes constantly.
AI is changing search.
Google changes its SERPs.
New tools appear.
Old tactics become less useful.
Algorithms change.
Search behaviour changes.
You don’t need to wake up every morning and memorise every Google update.
But curiosity matters.
Follow a few reliable SEO publications.
Read Google’s documentation.
Follow experienced SEOs.
Experiment.
When something changes, try to understand why people are talking about it.
And don’t just repeat whatever you saw on LinkedIn.
Ask questions.
Test things.
Curiosity will take you surprisingly far in SEO.
Client Ownership Is a Bigger Requirement
There are some phrases I would pay more attention to.
For example:
“Taking ownership of account performance.”
That’s different from knowing how to use Semrush.
If an agency expects you to own client accounts, they’re probably looking for someone who can do more than execute tasks.
You may need to:
understand the client’s business, develop recommendations, prioritise work, communicate performance, explain problems, work with account managers and take responsibility when results aren’t going as expected.
That’s where experience starts to matter more.
If you’ve never worked with clients, don’t pretend that you have.
But again, look for transferable experience.
Have you presented university projects?
Worked in customer service?
Managed stakeholders?
Explained technical concepts to non-technical people?
Worked in another marketing discipline?
Managed your own projects?
Communication skills don’t suddenly appear when your LinkedIn title changes to SEO Specialist.
What I’d Actually Want an Entry-Level SEO to Know
If you asked me what someone preparing for their first SEO job should concentrate on, the list would be much shorter than many job descriptions suggest.
I would focus on:
- How search engines basically work: crawling, rendering, indexing and ranking.
- Keyword research and search intent: understanding what people are actually looking for.
- On-page SEO: titles, headings, content, URLs, images and internal linking.
- Basic technical SEO: status codes, redirects, canonicals, robots.txt, sitemaps, indexability and common crawl issues.
- Off-page SEO: what backlinks are, why authority matters and why not every link is a good link.
- Search Console and analytics: enough to investigate performance rather than just screenshot graphs.
- Basic website/CMS knowledge: ideally get comfortable using WordPress or another CMS.
- An SEO crawler: learn what a crawl tells you and how to investigate the results.
- Basic reporting: explain what changed, why you think it changed and what should happen next.
- Communication and curiosity: arguably two of the most underrated SEO skills.
You don’t need to be an expert in all ten.
You’re applying for an entry-level position because you’re still learning.
Build Evidence Instead of Waiting for Experience
There’s an annoying problem with entry-level jobs.
You need experience to get the job.
But you need the job to get experience.
Fortunately, SEO is one of the easier careers to practise outside formal employment.
Build a website.
It doesn’t have to become successful.
In fact, I’d argue that a website that struggles can sometimes teach you more.
Do keyword research.
Publish pages.
Optimise them.
Connect Search Console and GA4.
Crawl the website.
Create a basic SEO audit.
Track rankings.
Improve internal linking.
Make mistakes.
Wait for Google to crawl your changes.
Look at the data.
Then document what happened.
Now, when an interviewer asks:
“Have you used Google Search Console?”
You don’t have to say:
“I completed a Search Console module in a course.”
You can say:
“I connected Search Console to my own website and used it to identify pages getting impressions but very few clicks. I then reviewed their queries and changed some of the titles.”
That’s an entirely different conversation.
Prepare Stories, Not Just Definitions
This approach is one thing I’d strongly recommend before an SEO interview.
Knowing what a canonical tag is matters.
But employers will often learn more from hearing how you think.
Prepare examples of things you’ve actually done.
A page you optimised.
A technical problem you found.
Keyword research you completed.
A website you built.
A time something went wrong.
A recommendation you made.
A result you achieved.
Even small projects can become useful interview examples.
The point isn’t to make yourself sound more experienced than you are.
The point is to demonstrate that you’ve moved beyond watching SEO tutorials and have started applying what you’re learning.
You Are Allowed to Say “I Don’t Know”.
I still encounter things in SEO that I don’t immediately know how to solve.
That’s not unusual.
SEO overlaps with web development, analytics, content, UX, servers, JavaScript, data, local search, AI and plenty more.
Nobody knows all of it.
An entry-level candidate definitely shouldn’t be expected to.
If you’re asked something in an interview that you don’t know, don’t panic and invent an answer.
Explain what you do know.
Then explain how you would investigate what you don’t know.
I’d much rather hear:
“I haven’t worked with that before, but here’s how I’d approach learning it.”
than listen to someone confidently make something up.
Knowing how to find an answer is part of the skill.
Someone Once Took a Chance on Me
I can say all of this because I’ve been on the other side of it.
When I applied for an SEO role at Wishpond, I didn’t perfectly match the job description.
I didn’t have all the years of experience they were looking for. There were also tools and platforms I hadn’t worked with before. Shopify, for example, wasn’t something I had much experience with at the time.
It would have been easy to look at those gaps and decide I wasn’t qualified enough to apply.
Thankfully, someone else saw it differently.
Guillermo Reynoso, who was the SEO Lead at Wishpond at the time, took a chance on me.
He didn’t expect me to arrive knowing everything.
When there were things I needed to learn, he pointed me toward tutorials and resources that could help. Our one-on-one meetings gave me opportunities to ask questions, understand where I needed to improve, and gradually become more confident in the role.
That experience has stayed with me.
Because sometimes the difference between the candidate who meets 100% of the requirements and the candidate who meets 70% isn’t potential.
It’s simply exposure.
You may not know Shopify because nobody has given you a Shopify website to work on yet.
You may not know Screaming Frog because your current role has never required it.
You may not have agency experience because nobody has hired you at an agency yet.
Those are gaps, but they’re also gaps you can learn from.
There’s an important difference between not knowing something and not being capable of learning it.
Guillermo could have looked only at what was missing from my CV. Instead, he gave me an opportunity to learn the things I didn’t know.
I’m grateful that he did.
And it’s one of the reasons I’d tell someone starting out in SEO not to eliminate themselves from an opportunity simply because they don’t match every line of the job description.
Sometimes you need someone to take a chance on you.
But first, you have to take a chance on yourself and apply.
Don’t Let the Job Description Reject You Before the Company Does
I’m not suggesting you apply for every SEO vacancy you see.
If a company wants five years of enterprise SEO experience and you’ve just learned what a title tag is, that’s probably not the right opportunity yet.
But don’t go to the other extreme.
Don’t see:
“2 years experience”
and immediately close the page.
Don’t see five SEO tools when you’ve only used three and decide you’re unqualified.
Don’t see Shopify when you’ve only worked with WordPress and assume you can’t learn it.
Don’t see “technical SEO” and imagine they’re expecting you to rewrite Google’s crawler.
Read the responsibilities.
Translate them into actual work.
Separate the things you already understand from the things you can reasonably learn.
Identify the genuine gaps.
Prepare examples of what you’ve done.
Then apply.
One of the strange things about starting a career is that you often don’t feel ready until long after you’ve already become capable enough to begin.
SEO is no different.
You don’t need to know everything.
You need the fundamentals, curiosity, evidence that you’re willing to learn, and enough confidence to give someone the opportunity to say yes.
Don’t reject yourself on the employer’s behalf. Apply and let them make that decision.
