← Oleksii Turovskyi

Oleksii Turovskyi

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. This is what I work on and how I go about it.

Українською: про мене.

What I do#

I am currently Full-Stack Developer at Mettevo, working across three things that turn out to be one thing: headless architecture, AI integration into business infrastructure, and agentic SEO. In practice that means enterprise integrations, custom REST APIs and payment gateways on one side, and autonomous agents, custom AI skills and MCP implementations on the other — with the same question underneath both. What has to be true of a system before something else can safely act on it?

Two kinds of work keep coming back. The first is getting a product in front of users quickly, where most of the skill is deciding what not to build. The second is the opposite: a system that already carries real traffic and has grown expensive to change, where the skill is finding which coupling is doing the damage and cutting that one.

The seam between the two stacks is where I spend the most time. A headless WordPress backend feeding a Next.js frontend is a contract, and contracts drift — usually silently, usually on a Friday. A lot of what I ship is the machinery that makes the drift loud instead.

How I work#

I measure before I claim. Most of the writing on this site started as a thing I believed, failed to reproduce, and had to correct — the piece on embeddings changed direction entirely once the numbers came back the opposite way. If something here says a technique works, the article shows what was measured and on what.

I write decisions down. This site keeps its architecture decisions in the repository, next to the code they constrain, because the expensive part of a codebase is not the code — it is reconstructing why it looks like that. The same habit shows up in the plugin pages: each one documents the trade-off, not just the feature.

I prefer the smallest thing that removes a class of bugs. A build that fails on a too-long meta description is worth more than a checklist asking a reviewer to remember. A test asserting a status code is worth more than a comment explaining why the status matters.

What this site is#

It is a portfolio, and it is also the reference implementation for the things I write about. Every AEO technique described in the articles is live here: the machine-readable .md mirror of every page, llms.txt, structured data, a WebMCP tool surface for in-browser agents. When I claim a technique is cheap to adopt, this site is the evidence — you can read its markdown, its structured data and its source.

The Chrome extension I ship audits pages for exactly these signals, so the site and the tool check each other.

Where to find me#

The full résumé lives at /resume.json as JSON Resume and at /profile.md as markdown, both for machines that would rather not parse a page.