A/B Testing for Gutenberg
An A/B Test block for the WordPress block editor — cache-friendly, cookie-free, with built-in click + dwell-time analytics.
I build headless WordPress and Next.js systems, AI agents on MCP, and the tools that make websites readable to answer engines.
Next.js front ends over a WordPress back end that serves content through REST or GraphQL, with the contract between the two written down and tested, so a schema change fails a build instead of a page.
Notes from production ↗Custom plugins and blocks built to survive real traffic and full-page caches. Three of my own are published here, each with its architecture and trade-offs written up next to the download.
The plugins ↗Agents that act on a system rather than just read it: custom skills, Model Context Protocol servers and tools. This site exposes its own WebMCP tools to in-browser agents.
Browser tooling ↗Making pages that AI answer engines can fetch, parse and quote: clean HTML, structured data, llms.txt and Markdown mirrors. Measured on a sample of real search results before it is recommended.
Start with AEO ↗An A/B Test block for the WordPress block editor — cache-friendly, cookie-free, with built-in click + dwell-time analytics.
12 profiling tabs for WordPress — from PHP lifecycle checkpoints to autoloaded bloat, render-blocking assets, and outbound HTTP calls.
One-click AEO audit for the page you're on — score, per-check pass/warn/fail, instant remediation list.
Keyboard shortcuts, smoother zoom and pan for NotebookLM mindmaps — explore your knowledge graph instead of dragging it.
App Router front ends, server components and edge-rendered pages. This site runs on it.
Headless or classic, Gutenberg blocks, ACF, WooCommerce, and plugins built for full-page caches.
End to end, with the API contract typed once and shared by both sides of the seam.
Services and integrations on Fastify: payment gateways, webhooks, REST and GraphQL APIs.
Model Context Protocol servers and custom skills, so an agent can act on a system safely.
GA4 exports, server-side tagging and the measurement that decides what gets built next.
The audit this site runs on itself, in a Chrome extension anyone can install. How it scores a page ↗
A 0-100 AEO score for the page you are on, weighted across nine checks.
Every warning comes with the concrete fix and the article behind the signal.
Shows whether the page exposes tools that in-browser AI agents can call.
I build web systems end to end, usually WordPress and Next.js at the same time, and usually at the seam where the two have to agree. Two kinds of work keep coming back: getting a product in front of users quickly, and making a system that already carries traffic cheap to change again. More about me ↗
Find which coupling is doing the damage before touching any of it. Most of the skill is deciding what not to build.
The smallest change that removes a whole class of bugs: a failing build beats a checklist, a test beats a comment.
Decisions are written down next to the code they constrain, so the next person does not have to reconstruct why.
Nothing is claimed before it is measured. When the numbers come back the other way, the article changes, not the data.
Full-cycle design of web systems and enterprise-level AI solutions. The work spans three disciplines: scalable headless architecture, AI integration into business infrastructure, and agentic SEO.
Made a significant contribution to a key phase of the project's technical transformation, working on the migration of a large-scale SPA platform to a modern Headless stack. My responsibilities covered the full development cycle, from architectural design to final implementation.
Led a comprehensive refactoring and modernization of the codebase for the blog section of a high-performance SaaS platform. Eliminated accumulated technical debt by transitioning the project from a legacy procedural implementation to a modern object-oriented architecture.
Marketing Tools Integration: Google Analytics 4 (with BigQuery synchronization), GTM (client-side and server-side tagging), Google Retail, Google Merchant Center, Airtable, Klaviyo, HubSpot.
Developed WordPress websites from scratch, creating custom themes and plugins.
Let's build it
A product to get in front of users, or a system that has grown expensive to change. Tell me which one.
Get in touchNext.js and React on the front, WordPress on the back, often both at once as a headless setup where WordPress serves content over REST or GraphQL. TypeScript and PHP day to day, Node.js and Fastify for services, and MCP when an AI agent has to act on the system rather than just read it.
Yes. Custom plugins and Gutenberg blocks have been part of my WordPress work since 2019, and three plugins of my own are published on this site with their architecture and trade-offs written up next to the download.
Answer Engine Optimization is making a page readable and quotable by AI answer engines such as ChatGPT, Perplexity, Claude and Google's AI Overviews, not just rankable. The quickest check is AEO Checker, my free Chrome extension, which scores the page you are on from 0 to 100 and lists what to fix. The AEO section of this site explains each signal it measures.
Yes, all of them are free. The Chrome extensions install from the Chrome Web Store. The WordPress plugins ship under GPL-2.0-or-later, and each plugin page gives you a signed download link without an account.
Kyiv, Ukraine, on Kyiv time (UTC+2, UTC+3 in summer). I have worked remotely with teams in Norway and Israel.
Write to me directly at alexturik@gmail.com or through this form.