+60%
Website traffic
Lift from technical SEO, performance, and structured content, not vanity tweaks.
Impact
I focus on outcomes that survive launch: traffic, rankings, performance, stable systems, and handoffs that teams can operate without guesswork.
+60%
Lift from technical SEO, performance, and structured content, not vanity tweaks.
#2
Page one placement for core commercial terms after schema, hreflang, and on page discipline.
Production grade
Multiple launches with full documentation so teams operate without chasing you for basics.
Clear
Runbooks, API notes, deployment context, and decisions documented so teams can keep moving.
Metrics are only useful if they tie to something a business cares about: revenue, leads, trust, or time saved. I start from the outcome, then work backward through the stack: content, SEO, performance, and the operational side of shipping and maintaining software.
Same person, different lenses. Here is how I tend to split the work when we are trying to move something measurable.
Structured data, hreflang, clean IA, and pages that answer intent. I optimize for what people actually search for, not just what looks good in a sitemap export.
Core Web Vitals, image and asset discipline, and honest performance budgets. Fast sites rank better and convert better, so I treat speed as a product requirement, not a nice to have.
Readable PRs, API contracts, deployment notes, and decisions documented clearly enough for the next engineer or stakeholder to keep moving.
Not every project needs every metric. These are the ones I reach for when we are trying to prove something changed or stayed healthy.
Want the story behind the numbers? Each project write-up on the work page includes context, constraints, and what shipped.
See case studies