I'm Victor Ijomah. I embed with in-house teams for defined engagements: three to six months, shipping the technical SEO and AI Search work you do not have time to ship internally. Based in the UK, available now.
The role, as I see it
An In-House SEO Consultant embeds with your team for a defined period to ship the work that is currently blocked, missing, or stuck in someone's backlog. Not a presentation. Not a slide deck. Actual work, written up so the team can run with it after I leave.
In practice, that looks like:
The mode of working is different from a permanent role. I am there to ship, transfer, and exit. The best consulting engagements end with the team being able to do what I came to do, without me. That is the goal.
What I bring
No three-month warm-up. I work in your tools, your rhythms, your sprints from week one. By the end of week two there should already be shipped work to point at, not just an audit document waiting for sign-off.
llms.txt, AI crawler management, entity optimisation, schema for citation. These are the standards moving fastest right now, and most in-house teams have not started on them. I bring this workstream in-house with practical work and clean documentation.
My deliverables are merged pull requests, shipped schema, fixed crawl issues, validated llms.txt files. Reports exist to document what was done, not to sit on a shared drive untouched. Most consulting engagements over-index on findings and under-deliver on fixes. Mine do not.
Everything I build is written up so the in-house team can run with it after I leave. Technical SEO Library habits applied internally: clear audits, replicable processes, onboarding-ready handover docs. Critical when the engagement is finite by design.
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.
This work is moving fast enough that waiting six months to find the perfect permanent hire is a strategic mistake. Consulting fills the gap. Get the work shipped now, recruit the permanent hire properly, hand it off cleanly.
Engaging me as a consultant means buying capacity at the moment you need it most. I can be in your tools next week, shipping the work that compounds, while you take your time getting the permanent hire right.
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
Three to six months, four days a week embedded with your team, working in your tools and rhythms. We define the scope upfront with clear deliverables and a written exit plan that includes documentation handover and (where relevant) onboarding the permanent replacement.
Within two weeks of an agreed scope and signed engagement letter. No notice period for consulting work.
No. I hold right to work in the United Kingdom. No sponsorship required.
Open to all three. Most engagements work well as primarily remote with on-site days for kickoff, key reviews, and final handover.
Shipped work, not slide decks. Schema implementations live on the site, crawl issues resolved and validated, AI crawler rules deployed, technical SEO docs written for the team. The audit report is a starting point, not the deliverable.
Yes, and this is one of the strongest reasons to engage me. I can run the function while the permanent hire is being recruited, then spend the final weeks transferring everything I built and the context around it. Better than a cold start for the permanent hire.
Yes. Several have led to permanent conversations. Open to that if it makes sense for both sides, but I do not enter consulting engagements with that as the agenda. The goal is to ship great work first.
Engagement-based, scoped to outcomes rather than hours where possible. Day rates and project pricing are discussed during the scoping conversation.