At first glance, SEO and cybersecurity probably don’t look like obvious companions.
One focuses on helping websites become more visible.
The other focuses on keeping systems, networks, and information secure.
So why am I, after building a career in SEO, spending my spare time learning about cybersecurity?
Curiosity is part of the answer.
But the more I learn, the more I realise the two worlds aren’t as far apart as I thought.
Working with websites eventually exposes you to security
I’ve spent years working with websites.
When you do that long enough, you encounter problems that aren’t neatly labelled “SEO”.
A website gets hacked.
Thousands of strange URLs suddenly appear in Google.
A security change prevents scripts from loading.
Tracking stops working.
A staging environment accidentally becomes publicly accessible.
A developer mentions HTTP headers, DNS, server configurations or permissions, and suddenly you’re having a conversation that stretches well beyond keywords and rankings.
I don’t need to become a cybersecurity professional to recognise that understanding more about what happens underneath a website could make me better at my own job.
That was one of the things that pushed me towards cybersecurity.
SEO taught me to look at websites differently
Before SEO, I mostly thought about websites from the perspective of building them.
SEO changed that.
I started thinking about how Google accesses a website, what happens when a browser requests a page, why different status codes appear, how redirects work and how JavaScript can affect what search engines see.
Cybersecurity takes some of those familiar ideas and asks completely different questions.
Who should have access?
What happens if someone exploits this?
How is information moving between systems?
What could go wrong?
How would we know if something had gone wrong?
I find that fascinating.
It’s like looking at an environment I’ve worked around for years through a completely different lens.
A hacked website is also an SEO problem
This is probably the most obvious crossover.
Security incidents can become search problems very quickly.
If someone compromises a website and creates thousands of spam pages, those pages can end up being crawled and indexed.
Important pages can be changed.
Users can be redirected somewhere they shouldn’t be.
A site can develop reputation problems.
Cleaning up the SEO impact afterwards isn’t always as simple as deleting a few URLs.
For an SEO, understanding what happened — even if you’re not the person responsible for fixing the security vulnerability — makes collaboration with developers and security teams much easier.
I’m also becoming more interested in how the internet actually works
This might be the bigger reason.
As careers progress, I think it’s easy to become increasingly specialised.
You become very good at your particular corner of technology.
There’s nothing wrong with that.
But I’ve found myself wanting to understand more of what’s happening underneath the tools I use every day.
Networks.
Protocols.
Linux.
Authentication.
Permissions.
Threats.
Logs.
How machines communicate.
How attackers think.
I’m still learning all of this.
Some concepts make immediate sense because of my existing experience. Others remind me very quickly that I’m a beginner.
I like that.
Being a beginner again is uncomfortable
In SEO, I have years of context to rely on.
I can look at a problem and usually have some idea of where to start.
Cybersecurity removes that comfort.
I encounter terminology I’ve never seen before.
I have to look things up.
I occasionally finish a lesson convinced I understand something, only for the next lesson to prove otherwise.
That’s part of why I’m documenting this journey.
I’m not writing about cybersecurity because I want to present myself as a cybersecurity expert.
I’m writing about what it’s like to learn something new after becoming experienced in something else.
There’s a difference.
It might make me better at SEO
I’m already seeing connections.
Technical SEO becomes more interesting when you understand more about servers and networks.
Website migrations make more sense when you understand the infrastructure involved.
Security headers aren’t simply mysterious instructions from a development team.
Logs become interesting for reasons beyond understanding how Googlebot crawls a website.
Python, which I’m also learning, starts connecting automation, SEO, data and security in ways I’m still exploring.
I don’t expect every cybersecurity lesson to have an SEO application.
It doesn’t need to.
Not everything needs to become a career move
There’s pressure in professional life to justify everything you learn.
If you’re studying something, people want to know what certification you’re getting.
What job are you targeting?
Are you changing careers?
What’s the salary?
What’s the plan?
Right now, I don’t have some dramatic announcement about leaving SEO for cybersecurity.
I enjoy SEO.
I’ve spent years building my career in it, and there’s still plenty I want to learn.
Cybersecurity is simply another area of technology that has captured my attention.
Maybe it becomes a bigger part of my career one day.
Maybe it makes me a more technically capable SEO Manager.
Maybe it simply teaches me more about how the technology I’ve worked with for years actually works.
All three outcomes sound useful to me.
Curiosity got me here in the first place
There’s also something familiar about all of this.
My journey into SEO started with curiosity.
I was working with websites and wanted to understand what happened after we put them online.
How would people find them?
That question eventually became a career.
Now I’m asking different questions.
What happens when those websites are attacked?
How do networks stay secure?
How do you identify something suspicious?
What’s actually happening when all these systems communicate with each other?
I don’t know where those questions will take me.
I’ve learned not to worry too much about that.
Sometimes you don’t need a five-year plan for learning something.
Sometimes “I want to understand how this works” is a good enough reason to start.
