This is serpguy — a practitioner's archive on how search actually works.
A blog publishing expert content on SEO, GEO & AEO, Growth, and Vibe Coding. Written from real client work and production deployments — not conference stages, not recycled LinkedIn posts.
What serpguy covers — and what it refuses to cover.
Technical SEO
Crawling, indexing, log-file forensics, Core Web Vitals, JavaScript rendering, schema — the underneath layer most content teams never look at.
GEO & AEO
Generative Engine Optimization and Answer Engine Optimization. How to stay visible as ChatGPT, Perplexity, and AI Overviews absorb the top of the funnel.
Growth
Acquisition, retention, and conversion. Practical tactics that survive contact with a P&L — backed by experiments, numbers, and a fair share of failures.
Vibe Coding
Building SEO infrastructure with AI-assisted tools. Fast, lean, opinionated — how one person ships production workflows without a full engineering team.
Six rules that decide whether something ever ships on this site — no exceptions.
One writer.
Ten years in search.
Sr. Growth Manager · SEO & founder of Sealed.agency. Based in Istanbul. Writes here on Thursdays, consults the rest of the week, and breaks more things in staging than he ships to production.
serpguy is a one-person archive. There is no editorial team, no content calendar filled by freelancers, no "head of content" rebranding B2B listicles as thought leadership.
The byline is the practitioner. If a case study runs on this site, it's because the writer ran the project. If a code snippet appears in an essay, it's because the writer shipped it. This is the single non-negotiable principle the whole archive is built on: the person writing about the work is the person who did the work.
That constraint is also why posts are weekly, not daily. A longread that meets this bar takes between 10 and 30 hours of writing, editing, and production. The math doesn't support a higher cadence, and nobody's helped by one.
If you've read something here that moved your work forward, that's the entire point. If you disagree loudly with something you've read — even better. The inbox is open.
How we got here — the short version.
First agency seat, first technical audit
Learned to read server logs before learning to read keyword research. Which turned out to be the right order.
In-house SEO lead at a mid-market e-commerce brand
Three years, four replatforms, one very long section on migration checklists that still informs the current Technical SEO archive.
Founded Sealed.agency
Boutique growth consultancy — SEO, GEO, and growth engineering for B2B and e-commerce clients. Deliberately kept to a roster of 6–8 clients at a time.
Launched serpguy
The archive you're reading. Started as an internal write-up habit, then became a public one. Same writer, same standard.
Read one essay. Decide for yourself.
The fastest way to know if serpguy is for you is to spend 14 minutes on the latest field note.