Marco Patzelt
Back to Overview
February 11, 2026

Agentic SEO Results: 109K Impressions in 11 Days, Full Data

109K impressions and 1,786 clicks in just 11 days using agentic SEO. Full case study with real trajectory data, CTR patches, agent costs, and what worked.

Everyone writing about agentic SEO talks about what it could do. This is what it did.

Google Search Console: 109K Impressions, 1,786 Clicks in 11 Days

109,333 impressions. 1,786 clicks. Average position 6.3. Zero ad spend. One engineer, one terminal, eleven days.

This is not a pitch for a platform. This is my Google Search Console. The blog you are reading right now. Every number is verifiable, every article indexed, every click organic.

The Starting Point

Eleven days ago this blog had single-digit daily impressions. I had published a handful of articles about agentic architecture and middleware engineering. Google barely knew the domain existed.

I started using Claude Code as my entire SEO system. Not as a writing assistant that suggests headlines. As an agent that reads my Search Console data, identifies content gaps, writes articles targeting those gaps, optimizes existing pages, and publishes everything to Supabase through the terminal.

The result: a hockey stick that started around January 27th and has not stopped climbing.

What Actually Drove the Numbers

The growth did not come from one viral article. It came from a system that compounds.

I started publishing articles on topics I know. Within two to three days, articles already started ranking. That is when the system kicked in.

Claude Code pulled my GSC data every morning. It saw which articles formed content clusters. It found gaps: linking opportunities between related articles, queries where I ranked but had no dedicated page, meta titles that did not match what people were actually searching for. Every day it generated a report within minutes. I reviewed it, said "go through everything you found and fix it," and Claude Code went in and fixed it all.

After about 30 minutes of clicking enter, a month of manual SEO work was done. Title rewrites, internal link restructuring, content gap fills, meta description patches. All based on real search data, not guesses. And because the agent works on data, every optimization had a reason behind it. The more data came in, the more the agent found to improve. It compounds.

The Agent Team Audit

The inflection point was spawning a team of AI agents to audit the entire blog. Four specialists running in parallel: content quality, search data analysis, intent matching, competitor gaps. The report came back with over twenty issues I had not seen.

Newsletter

Weekly insights on AI Architecture. No spam.

The agent fixed them in ten minutes. New meta titles, rewritten sections, restructured internal links. Then I built a landing page for a keyword cluster the team had discovered. Next day: rank one, six thousand views.

That was not optimization. That was a system finding opportunities faster than I could think about them.

The Trajectory

The GSC screenshot shows 90 days of data. The first 79 were flat. The last eleven produced virtually all of the 109K impressions.

PeriodImpressions/DayClicks/DayAvg Position
Before agentic setup~5-500-220-30+
Day 1-5 (Jan 27-31)2,000+50+8
Day 6-11 (Feb 1-8)10,000-18,000180-3276.3

The jump is not gradual. The blog crossed a threshold where Google started trusting the domain enough to rank content on page one for competitive queries. That trust came from topical depth and publishing velocity, not domain age.

CTR Patches: The Quick Wins

Three articles were bleeding impressions with near-zero CTR. The agent identified the mismatch between search intent and title promise.

ArticleImpressionsCTR BeforeWhat Changed
Qwen3-Coder2,0890.2%Title rewritten to match "review" intent
Best AI for Coding1,6360.1%Added model names and year to title
Is OpenClaw Safe1,1320.2%Added "CVE" and "Fix" for trust signal

Each patch took about a minute. The agent rewrote the title, I approved, done. Total time for three CTR fixes: three minutes.

The Cost

Claude Max subscription: $90/month. That covers everything. Article writing, SEO audits, agent team runs, content optimization, Supabase publishing.

No enterprise platform subscription. No agency retainer. No ad spend. The agent runs locally, connected to all my endpoints, and acts in its environment to produce value.

What These Numbers Prove

Agentic SEO is not a concept paper. It is a measurable system with a daily workflow that produces verifiable results. The trajectory from 5 impressions per week to 18,000 per day is documented in Google Search Console, not in a slide deck.

The question is not whether this works. The screenshot answers that. The question is what happens when the people paying thousands per month for enterprise SEO platforms realize they can get comparable results from Claude Code and a $90 subscription.

That conversation is just getting started.

Newsletter

Weekly insights on AI Architecture

No spam. Unsubscribe anytime.

Frequently Asked Questions

A workflow where an AI agent reads your real search data, identifies what to fix or write, and executes the changes. It speeds up the process but does not replace strategy, domain expertise, or good content.

No. You still need a domain, real expertise in your topic, and content worth ranking. You cannot write about anything and expect results. The agent accelerates what already works, it does not create authority from nothing.

It reads your Google Search Console data, finds patterns like CTR mismatches or content gaps, and executes fixes faster than you could manually. It is a boost when you have data to work with, not a magic tool.

$90/month for Claude Max. But cost is not the main barrier. You need a domain, hosting, content expertise, and the willingness to follow a logical process. The agent helps you move faster, not skip steps.

Currently yes. You need to understand APIs, Claude Code workflows, and how to connect the agent to your data. Once set up, the agent handles the execution, but the initial setup requires engineering knowledge.

Let's
connect.

I am always open to exciting discussions about frontend architecture, performance, and modern web stacks.

Email me
Email me