I'm Victor Ijomah. I lead SEO end-to-end: strategy across technical, content, and discoverability, plus the team and stakeholder work that holds it together. Based in the UK, available now.
The role, as I see it
An SEO Manager owns the SEO function: the strategy across technical, content, and discoverability, the team that delivers it, the reporting that proves the case, and the relationships with engineering, product, content, and leadership that keep the work moving.
In practice, that looks like:
It is the role where you stop being measured on a single audit and start being measured on the whole organic growth picture. That requires breadth, depth, and the patience to play a quarter-by-quarter game.
What I bring
Many SEO Managers came up through the content or keyword research route. They cannot lead a Technical SEO directly because they cannot meaningfully review the work. I can. That changes what kind of technical projects you can take on as an organisation, and how quickly engineering trusts SEO recommendations.
llms.txt, AI crawler management, entity optimisation, schema for citation. These are the levers that decide who gets cited in ChatGPT, Perplexity, and Claude. I have been building for this since the standards started emerging, while most SEO Managers are still working out what AI Search means for them.
At my consultancy I lead a small team across development specialisms. I scope projects, prioritise work, review deliverables, and hold the line on quality. The same approach scales to an SEO team with mixed skill sets across technical, content, and analytics.
Comfortable in a leadership review on Monday and reviewing a schema implementation on Friday. The combination matters because SEO Manager work flips between those modes constantly, and the depth of the tactical work changes the quality of the strategic decisions.
The stack
Selected work
Where this role is heading
Classical SEO had one consumer of structured data: Googlebot. AI Search adds GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, and a growing list of crawlers that read sites with different rules and produce different outputs.
Each one needs technical accommodation: schema that survives different parsers, llms.txt that declares intent, log analysis that distinguishes them from each other, crawl rules that allow the ones you want and block the ones you do not.
An SEO Manager who cannot have these conversations with engineering at depth becomes a bottleneck. An SEO Manager who can becomes disproportionately valuable, because they can both make the case to leadership and direct the team that ships the work.
This is the work I have been building for. Hiring me means hiring an SEO Manager who can lead both the technical and the content sides of AI Search readiness, not someone who can only direct one half.
Continuous learning
So I completed every major SEO course in the field. Each one verifiable.
Tech SEO Pro
Academy Certification
SEO Essentials
Academy Certification
SEO 2
SEO 1
Plus broader marketing credentials: Google Fundamentals of Digital Marketing, Google Online Marketing Fundamentals, HubSpot Inbound Marketing.
Recommendations
Victor took our crawl efficiency issues seriously and shipped fixes inside two weeks that previous consultants had told us would take months. The reporting was clear and the team trusted him from day one.
Laura Mitchell
Head of Growth, B2B SaaS Platform
Working with Victor on our SSR rollout was rare. He understood our codebase, knew exactly what SEO needed, and translated between the two without friction. Most marketing people slow engineering down. He sped us up.
Marcus Tate
Senior Engineer, SaaS Platform
We brought Victor in for a schema migration on our editorial platform. Six weeks later we were being cited in ChatGPT responses for the first time. Specific, technical, gets the work done.
Rachel Adeyemi
Editorial Director, Content Publication
Victor publishes some of the clearest writing I have read on llms.txt and AI crawler management. I have sent his posts to clients more than once when explaining what is coming next in search.
Tobi Adekunle
SEO Consultant, Independent
Recommended reads
Full walkthrough of the emerging standard for declaring AI crawler intent. Syntax, validation, common mistakes, and how to ship it.
Read articleA contrarian look at default Yoast configuration choices that block GPTBot, ClaudeBot, and CCBot without flagging it to site owners.
Read articleBeyond basic Article schema. What entity structures, sameAs links, and citation-friendly markup actually surface in ChatGPT, Perplexity, and Claude responses.
Read articleCommon questions
Four weeks notice from my current role. Available to begin within four weeks of an accepted offer.
No. I hold right to work in the United Kingdom. No sponsorship required, now or in future.
Open to all three. Currently based in the UK. Comfortable with travel for on-site days where the role requires it.
Yes. I currently lead a small team across full-stack, UI/UX, and frontend development at my consultancy. The mix of skill sets translates well to managing an SEO team that combines technical, content, and analytics work. Formal performance management is the addition I would build into a permanent role.
They are not opposing investments. Technical SEO is the foundation that makes content investment pay off. Content SEO is what fills the foundation with value. The balance question usually comes from leadership wanting a single answer, but the honest answer is: invest in both, sequenced by what is broken now. If indexation is the problem, technical first. If indexation is fine, content first.
Both. Permanent is my preferred path for the next two-plus years. Open to contracts of six months or longer where the work is the right fit.
Hands-on enough to stay credible. I will still write schema where useful, run the occasional audit, and review work that team members produce. Most of my time goes to strategy, team, and stakeholder work, but I do not stop doing the craft.
Yes. The recommendations above are a preview. Full references with direct contact details are available on request after an initial call.