skip to content

about — the operator

One person. No handoffs.

I'm Jamie McKaye — a technical consultant who ships. Nineteen years across search, systems, and production code, run as a deliberate one-person practice: the person who scopes the work is the person whose commits you can read.

in practice since 2007 · four disciplines · one operator

act i — the practice: four disciplines, one pair of hands

04 parts

01

technical seo

nineteen years reading how machines read.

02

ai systems

the new readers — agents, answer engines, pipelines.

03

full-stack build

the fix shipped as production code, not a deck.

04

technical writing

the reasoning written down, sourced, published.


assembled — the same hands at every layer

no handoffs, by design

act ii — the provenance: how a packet of chewing gum led here

ch.00

early 2000s · a supermarket in surrey

The checkout.

Before any of it, there was a till at Safeway and a teenager bored enough to invent a game: sell the customers something they hadn't come in for. The stakes were a packet of chewing gum at a time.

One of the customers who took the gum ran a large SEO agency. She'd just watched a checkout kid engineer a sale out of nothing, for fun — and she knew an early version of the trade when she saw it. That conversation was the door.

It's still the cleanest definition of search work I know: the right thing, in front of the right person, at the exact moment they'll take it. Everything since has been that, at scale, with better instruments.

ch.01

2007 — 2011 · a digital marketing agency, uk & europe

Sold it, then learned it.

Started in sales; left as Director of Search Marketing. The route between those two roles is most of what I know about how search agencies actually work — pitching, scoping, contracts, then project-managing the delivery I'd just sold.

By the end I ran the search function: reseller partnerships, consultant hiring and training, the deep-end technical work, and an early content-marketing playbook before that phrase existed.

The job that turned someone who sold SEO into someone who could actually do it.

underneath it: bsc (hons) marketing, first-class honours — university of bath, 2004–2007

ch.02

2011 — 2017 · a multi-national full-service agency, london

The systems game.

Head of Search. Built the SEO practice from seven consultants to sixty-three across the UK, Europe and offshore delivery — serving FTSE 100 brands, blue-chip retail, fintech, and ambitious SMEs.

Owned the technical function end to end: site migrations, log-file analysis, Core Web Vitals before they had a name, JavaScript-rendering audits before frameworks made it a sport. Link programmes audited at C-suite level. CRO stood up as a practice line. SOPs and training that ramped consultants in weeks, not quarters.

The era that taught me search is a systems game, not a tactics game.

the practice, built

763

consultants · uk, europe & offshore

client range

FTSE 100

to seed-stage

ch.03

2008 — now · independent

The independent thread.

Running through all of it, then becoming all of it: hundreds of engagements as auditor, fractional head of search, and embedded technical lead — deep technical SEO across ecommerce, travel, and local; migrations, rebuilds, recoveries; seed-stage to multi-national. Every client arrived with the same brief, and the standard answers had stopped working.

I worked through every era that was declared the death of the job: the update that ended link-buying and content farms overnight, the panic of mobile-first, the shift from keywords to intent, the answer box quietly decoupling rank one from the click — and now assistants answering the questions that used to be searches.

Each shift was real. Each one minted an industry of certainty around it. And when the dust settled, the fundamentals were still standing: be genuinely useful, be technically sound, be the source worth trusting.

Nineteen years didn't teach me search. It taught me to distrust anyone who claims they've got it figured out.

among the files — unsealed with permission · the rest stay sealed

ch.04

2026 · the instrument

Build, don't just advise.

The independent years ended the backlog era for good: I stopped posting recommendations into other people's queues and started shipping the fix myself, in the code — full-stack by necessity at first, then by preference. Production engineering alongside search: WordPress estates, Next.js builds, hosting operations, measurement stacks that tell the truth. Then I went further and built the reference.

Four products of my own run in production, and this site is the working proof — two hundred and twenty-two posts retired into the particle field behind these words, thirty-one recordings brought back in my own voice, a grader that scores this site in public, machine surfaces any agent can read.

You cannot bluff Core Web Vitals, crawl economics, schema, or how an AI system parses a page when your own software lives or dies on exactly those things. That's the whole argument for hiring a consultant who ships.

2007

2011

2015

2020

2024

2026

every shift was sold as a revolution · every shift, the fundamentals survived

operating principles — how the work runs

01

proof over promises

claims on this site are instrumented, and the site itself is the portfolio piece.

02

small surface area

few clients, deep ownership, direct line. No account managers because there's no account to manage.

03

reversible first

freezes, inventories, and rollback paths before anything irreversible ships.

04

plain reporting

what happened, what it cost, what moved. If something failed, it says failed.

the direct line

The person reading your brief is the person who ships it. Start there.