I'm Victor Ijomah. I lead the technical layer of search end-to-end: setting priorities, partnering with engineering, shipping the work that compounds. Based in the UK, available now.
The role, as I see it
A Senior Technical SEO sets the direction of the technical work, not just executes it. The role sits between the engineering team and the broader marketing organisation, translating each side into the other's language and making the calls that get the work shipped.
In practice, that looks like:
It is the role where you stop waiting for someone to tell you what to do and start telling them. That requires depth, judgement, and the ability to say no when something is not going to work.
What I bring
I am used to operating without daily direction. Whether through agency client work, in-house collaboration, or my own consultancy, I scope problems, design solutions, and ship the result. That mode translates directly into Senior responsibility.
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.
Four-plus years working in the weeds: schema implementation, render issues, crawl debugging, log file analysis, AI crawler management. Pattern recognition for the problems that come up most.
I publish weekly at the Technical SEO Library. Internal audits, stakeholder reports, and team-wide documentation come naturally because I do the equivalent work on my own time.
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 Senior Technical SEO setting direction 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 set technical direction in this new layer, not someone learning to navigate 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 run a small development team at my consultancy (full-stack, UI/UX, frontend specialists), scoping projects, prioritising work, and reviewing deliverables. The same mode translates into a Senior role mentoring junior SEO team members or partnering with engineering peers.
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.
I write code where it helps. Schema markup, configuration files, small scripts, frontend tweaks. For deeper engineering work I partner with developers, but I do not need to be one to spec the work properly.
Yes. The recommendations above are a preview. Full references with direct contact details are available on request after an initial call.
Yes. A two-week paid sprint on a specific Technical SEO problem works well as a fit-test for both sides.