I'm Victor Ijomah. I run technical SEO as a function: strategy, team, delivery, and the stakeholder work that holds it together. Based in the UK, available now.
The role, as I see it
A Technical SEO Manager owns the technical SEO function: the strategy, the people, the roadmap, and the relationships that keep the work shipping. The role is half strategic, half operational, zero spectator.
In practice, that looks like:
It is the role where you stop being measured on the work you personally do and start being measured on what the team ships. That requires depth to make the right calls, judgement to set the right priorities, and the people management work that most technical SEOs avoid for too long.
What I bring
I think about technical SEO as a function with strategy, headcount, roadmap, and stakeholder management, not as a series of one-off audits. That mindset turns the technical SEO team into something a business plans around, not something it calls when something breaks.
llms.txt, AI crawler management, entity optimisation. I have been working on these since the standards started emerging. Most SEO teams are still catching up. I bring this work in-house ready to go, with a team plan to scale it.
At my consultancy I run a small development team across full-stack, UI/UX, and frontend. I scope projects, prioritise work, review deliverables, and hold the line on quality. The same approach scales to a Technical SEO team with formal performance management on top.
I still write schema, debug crawls, and analyse logs myself. That keeps me close enough to the work to spec it accurately, train people through it, and spot when an engineering pushback is real versus when it is a dodge.
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.
A team without a Technical SEO Manager building strategy and headcount for this layer gets cited less, ranks less, and loses ground quarter after quarter as AI Search captures more search behaviour. A team with one builds a structural advantage that compounds.
This is the work I have been building for. Hiring me means hiring someone who can build the team, set the strategy, and ship the work in this new layer, not someone learning to manage it.
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 at my consultancy, operating on a per-project basis. I handle scoping, prioritisation, deliverable review, and the quality bar. Managing a Technical SEO team would scale that pattern with the addition of formal performance management, hiring, and headcount planning.
Judgement first, depth second. Most technical SEO skills are teachable to someone curious and rigorous. Judgement is not. I look for people who can explain why a decision was made, not just what was done. I also look hard at written communication. A Technical SEO who cannot write a clear audit report struggles in the role regardless of technical skill.
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 myself, and review code that engineering team members push. 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.