10+ years building for real users
Long-term product work across themes, plugins, and tools that had to hold up in production.
WordPress development first
I build websites that work — and fix the ones that don't. (yes, even yours)
I build and fix WordPress websites, improve performance, solve technical issues, and handle the SEO details that support a better build. I also take on selected Shopify troubleshooting work when a business needs it.
10+ years building WordPress products. 20+ plugins maintained or contributed to. Technical SEO experience from real production sites, migrations, and rebuilds.
WordPress-first SEO-aware Selected Shopify work
Credibility
Developer proof that points back to WordPress work.
Years of product work, plugin maintenance, and community contribution carry more weight here than generic “full-service” language ever will.
20+ plugins maintained or contributed to
Shipped code that lives beyond one client project and gets used across the wider WordPress ecosystem.
WordPress.org contributor
Plugins, themes, translations, events, support, photos, and the other places where real WordPress work tends to leave a trail.
WordCamp speaker and organizer
Not just building in the ecosystem, but showing up in it and contributing back in public.
The working style
Less “just add a plugin.” More “why is this failing?”
01
Inspect
Start with the stack, the failure point, and the real source of the problem instead of guessing from symptoms.
01.5
Trace the constraint
Confirm whether the blocker lives in the theme, plugin stack, hosting, workflow, or business logic. It usually is not just one thing.
02
Implement
Build the simplest maintainable fix, whether that means code, cleanup, or undoing a clever workaround.
03
Stabilize
Leave the site faster, cleaner, and easier to work on the next time somebody has to touch it.
Services
WordPress development leads. SEO supports it. Shopify comes in where it helps.
The main work is building, fixing, and improving WordPress sites. Technical SEO supports the build. Shopify is a smaller but useful part of the mix.
“The site is slow.”Could be code, hosting, images, plugins, or tracking. Usually all five. They've formed a union.
“SEO is stuck.”Sometimes content is fine. The crawl path, templates, redirects, or signals are not. That is usually a build problem wearing an SEO name tag.
“Shopify almost works.”Usually a workflow problem hiding behind a theme, app, or checkout limitation. The last 10% takes 90% of time. Shopify guarantees this.
Primary focus
WordPress Development
Custom themes, plugin work, rebuilds, performance improvements, migrations, maintenance, and long-term WordPress problem solving.
Supporting skill
Technical SEO Support
Crawlability, redirects, schema, indexing, site structure, and technical cleanup that supports the build instead of fighting it.
Selected work
Shopify Troubleshooting
Theme fixes, storefront issues, tracking cleanup, workflow gaps, app conflicts, and practical help when Shopify gets awkward.
Additional capability
Custom Integrations
Middleware, automation, and system-to-system connections when WordPress or Shopify needs help talking to the rest of the business.
Case studies
Real problems, practical fixes.
A few examples of the kinds of problems I've worked through.
When the API did not exist
- Problem
- A business needed systems to talk to each other, but no direct API path existed.
- Solution
- Built a middleware layer to process, transform, and route data reliably.
- Impact
- Reduced manual work and created a cleaner operational flow.
Shopify workflow blocker
- Problem
- A Shopify limitation was affecting day-to-day business operations.
- Solution
- Diagnosed the workflow, adjusted theme and app behavior, and simplified the process.
- Impact
- Improved reliability and reduced repeated manual fixes.
Technical SEO cleanup
- Problem
- Years of site changes had created structure, redirect, and indexing issues.
- Solution
- Audited crawlability, redirects, metadata, schema, performance, and site structure.
- Impact
- Built a cleaner foundation for organic visibility and future content growth.
The Plugin That Should Not Exist
- Tag
- WordPress · Plugins
- Problem
- A client had installed eleven separate plugins to do one thing.
- Solution
- Replaced all eleven with twelve lines in functions.php.
- Impact
- Client immediately asked about adding three more plugins.
Experience
Built in product teams. Sharpened through client problems.
WordPress product experience building themes, plugins, and tools shipped to real users at scale.
Catch Themes
WordPress product experience building and maintaining themes, plugins, and production-ready tools used by real users.
Outpace
Client problem-solving across WordPress, Shopify, SEO, integrations, and business-critical technical workflows.
10+years WordPress product experience
20+plugins maintained or contributed to
8WordPress.org contribution areas
3+years client delivery and troubleshooting
Blog
Development notes from real projects.
Mostly WordPress, then technical SEO where it affects the build, plus the occasional Shopify problem worth writing down.
WordPress ACF vs SCF in 2025: what changed and what it means for your builds
Secure Custom Fields forked from ACF. Here is what changed and how it affects existing WordPress sites.
Technical SEO Why your canonical tags are wrong (and how to actually audit them)
Most canonical issues are not plugin bugs. They are logic problems. Here is the audit process I run on client sites.
Shopify Structured data on Shopify without an app: a Liquid walkthrough
Most guides stop at Product markup. This one covers collections, breadcrumbs, and FAQs in native Liquid.
Have a website problem that needs more than a quick patch?
Tell me what's going on. I'll help figure out what the actual problem is.