What I do, and how deep it goes
Search work and engineering usually sit in different teams that blame each other. I have done both for twenty years, which is why a finding here arrives with the fix already written rather than thrown over a wall.
Technical SEO audits
A full read of what is stopping the site from ranking, ordered by what will move first.
Crawl and index coverage, site architecture and internal linking, Core Web Vitals, structured data, and entity consistency. The deliverable is a prioritised list with the reasoning attached, not a 90-page export from a tool. Where a fix is a development task, it comes with the implementation.
What it covers
- Crawl, index, and coverage analysis
- Site architecture and internal linking review
- Core Web Vitals and PageSpeed diagnosis
- Schema.org and entity audit
- Search Console and GA4 configuration review
- Competitor and search intent analysis
AEO & GEO implementation
Being cited by answer engines and generative search, not only ranked by the classic one.
Classic search returns a list of links. Answer engines return a claim. Generative engines synthesise from whatever they can parse and attribute. Those are three different retrieval problems, and content that wins one can be invisible to the others. This is structured data as a connected graph, answer-shaped sections that extract cleanly as standalone responses, consistent entity naming across every page and every node, and an llms.txt that states plainly who you are and what you do.
What it covers
- Connected JSON-LD @graph, not disconnected islands
- Answer-shaped content that extracts as a standalone response
- Entity and topical authority modelling
- llms.txt and AI crawler policy
- Citation and visibility monitoring across AI surfaces
Full-stack & WordPress builds
Designed and built in one pass — fast and machine-readable from the first commit.
Twenty years of full-stack work, the last decade concentrated in WordPress, PHP, and JavaScript. Custom plugins and themes rather than page-builder sprawl, WooCommerce where commerce is involved, REST API integrations to whatever the business already runs on. Cloudflare, DNS, SSL, and CDN configuration included, because performance is an infrastructure question as much as a code one. The interface is designed as part of the same job rather than handed off — every project on this site was designed and built by the same person, which is why the type, spacing, and component decisions survive contact with the code.
What it covers
- Interface design and design systems, carried through to the build
- Custom WordPress themes and plugins
- WooCommerce and secure payment processing
- REST API and third-party integrations
- Cloudflare, DNS, SSL, and CDN configuration
- Core Web Vitals and PageSpeed optimisation
- Docker-based environments and deployment
AI workflow & multi-agent automation
Systems where several models and tools cooperate on real work, running in production.
Multi-agent systems for backend processing and content generation, retrieval-augmented pipelines over your own data, MCP implementations, n8n workflow automation, and custom GPTs. Local models run and evaluated as part of client builds where data cannot leave the building. The distinction that matters: this is building the AI systems, not only optimising for them.
Grounded against Claude Watch, private tooling that keeps a curated wiki of vetted sources so the agents read facts rather than recall them.
What it covers
- Multi-agent systems for backend processing
- RAG pipelines over proprietary data
- MCP server implementation
- n8n workflow automation
- Custom GPT development and prompt engineering
- Local model deployment and evaluation
The combination is the point.
Any one of these is a role someone else can fill. Together they are rare: search architecture that survives contact with a real codebase, engineering that accounts for how a thing gets found, and AI systems built rather than bought. Based in Lawrenceville, GA, open to metro Atlanta or remote.