01 · search that machines trust

Technical SEO & AI search

Google still matters. So do the answer engines quoting whoever they can parse. I make sites legible to both — crawlable, fast, structured, and cited — then prove it with instruments, not decks.

the discipline behind campaigns for Pitney Bowes and Urban Outfitters — and the engine this site grades itself with · scroll — the instrument is live ↓

the instrument — live crawl waterfall — this page auditing itself

abstracted from this site's real route table

crawl — this site's route map, drawing itself

bars abstract · status real


/200
/services/200
/services/technical-seo/200
/services/ai-systems/200
/work/200
/writing/200
/feed.xml200
/about/200
/contact/200
/lab/200

the work — manifest

  • w-01

    Deep technical audits that end in shipped fixes, not backlogs — crawl architecture, rendering, indexation, Core Web Vitals to green.

  • w-02

    AI-search readiness: structured data as a connected entity graph, llms.txt, clean machine-readable mirrors, citation-worthy page anatomy.

  • w-03

    Migrations without casualties — URL inventories frozen, redirect maps generated and tested, rankings watched through the flip.

  • w-04

    Ecommerce at catalogue scale: faceted-navigation control, canonical discipline, feed and category architecture that pulls the long tail into search.

  • w-05

    Performance rescue: server response, caching layers, render paths — found at the root, fixed at the root.

  • w-06

    Measurement that tells the truth: Search Console, server logs, and answer-engine visibility read together.

method — how it runs

01

read the machines' view

crawl the site the way each reader does — Googlebot, citation bots, agents — and reconcile what robots.txt promises against what the server actually serves.

02

find the root, not the symptom

rankings drop for reasons that live in server configs, render paths, and information architecture. The diagnosis names the mechanism, with evidence.

03

ship the fix personally

the same hands write the recommendation and the commit — templates, redirects, schema, server rules. Nothing waits in a backlog.

04

watch it hold

search console, logs, and vitals monitored through the change. If it moves the wrong way, it's caught in days, not quarters.

manifest — what lands on your desk

jm/technical·01

  • 01

    a prioritised technical audit that reads like an engineer wrote it

  • 02

    shipped fixes — commits, configs, schema, redirects

  • 03

    a frozen URL inventory + tested redirect map on migrations

  • 04

    an entity graph + llms.txt for the machine readers

  • 05

    a measurement baseline you can hold future work against

signed — one operator, no handoffs

05 items

proof — on the record

pitney bowes — named engagement

named

a full technical SEO campaign behind the franking-machine offering in the UK and US.

the file

urban outfitters — named engagement

named

a complex technical SEO campaign for the ecommerce store — architecture, crawl, and indexation.

the file

verified readout

verified

a UK tile retailer's server response taken from 2.2 s to 47 ms — plotted live on the work page.

watch it plot

self-audit

agent-ready grader

live

run it at /lab

mcp tools

04

public — /api/mcp/

corpus

222→0

retired into the field

build

p5

hardening pass

your visit — measured on you, just now

ttfblcpinpawaiting inputcls

compiled from c2660ba · 2026-08-26 16:14 utc · push = ship


Jamie McKaye — technical SEO, AI systems, full-stack build, technical writing. One person, no handoffs.