Solo founder flips 13 impressions/day into 1.54M in 90 days

The Case: 1.54M impressions, 12.9K clicks, 1.2K AI referrals/mo

What he does. Runs Agensi.io, a marketplace where developers download plug-and-play "skills" — instruction files that teach AI coding agents (Claude Code, Cursor, Codex CLI, +20 others) new workflows.

Backstory. AI coding agents went mainstream in late 2025, and every developer suddenly needed reusable instruction files to make them useful. There was no canonical directory. He shipped one before Google finished figuring out what "AI agent skill" even means. The window is now — while the vocabulary is still forming.

Product. - 700+ community-listed skills with structured metadata - One-click install into 20+ AI coding agents - Automated 8-point security scan before publish - 100+ SEO articles answering exact developer queries - Creator-driven catalog, free to browse

Pricing. Free to browse. The operator did not disclose revenue — this case is a distribution playbook, not a monetization one. Read it as such.

Key numbers. - Day 1 baseline: 13 impressions/day - Day 90 peak: 50,000 impressions on a single Sunday - Total impressions in 90 days: 1.54M - Total clicks: 12,900 (CTR 0.84%) - Daily active users: 1,000+ - Registered users: 1,500+ - Domain rating: 43 - AI referral sessions/mo: 1,200 (ChatGPT, Gemini, Perplexity, Claude, Kagi + 7 more) - Articles published: 100+ (one per day) - Programmatic landing pages: 700+ (one per skill)

Stack. Claude, Google Search Console, Lovable, Claude Code, FAQ + Article + Product schema on every page.

Why this works (and what most readers will miss)

1. The catalog is the SEO engine, not the blog. 100 articles is nothing. 700 skill pages is a substrate. Every creator who uploads a skill hands him another indexable page for free. His suppliers are unpaid SEO labor. Most operators run programmatic SEO as a one-time script. He turned it into a two-sided flywheel.

2. Schema-first, not copy-first. Every page ships FAQ, Article, Product, Breadcrumb, and Organization schema. That is why ~30% of his non-direct traffic comes from AI assistants citing him. AI search does not reward vibes. It rewards machine-readable answers with clean canonical structure. Schema is the new backlink.

3. He is writing the dictionary for a category that does not have one yet. This is the one nobody in the thread caught. When "AI agent skill" becomes a standardized term in 2027, whoever defined the taxonomy, the naming conventions, and the schema will be cited by every downstream tool. He is not building a marketplace. He is writing the reference index.

The Distilled Read

The product is not the marketplace. It is the answer to a developer's stuck moment. He did not build a directory and then hunt for users. He watched what Claude Code developers typed into Google — "where are Claude skills stored," "how do I install skills in Codex CLI" — and wrote 100 answers over 100 days. Each answer is a doorway. The marketplace waits behind the door. Boring, sequential, unfashionable. It works because the pain was already there. You do not create demand. You meet it at the search bar.

The catalog is the template, and the community is the printer. 700 skill pages come from one landing-page template with dynamic metadata. Each creator upload becomes another long-tail page for "[specific workflow] Claude Code skill." He built the pattern once. The community reprints it forever. That is the entire trick of programmatic SEO in 2026 — you do not scale content, you scale surface area, and you get somebody else to fill it. Two products from one playbook: the marketplace serves developers, the index serves search engines.

Score this as a bet, not a business. Capital at risk: 90 days of solo time. Time to first traffic: two months of flatline before the curve bent. Asymmetric upside: category ownership at the moment a category is forming. Decay risk: real — Google could de-rank, AI search could route around him, a bigger player could clone the schema in a weekend. This is a 1-in-20 wager. Nineteen of these die when the platform shifts. The one that lives owns a taxonomy. You should be running three of these bets at once, not staking your year on one.

Distribution was not a growth hack, it was inevitability. The audience already existed. Cursor's Discord has 40K+ members. r/ClaudeAI has hundreds of thousands. The pain — "where do I find good skills for this thing" — was being posted daily. He did not cold-DM. He did not buy ads. He built the URL Google would send those people to when they gave up asking humans and typed the question into a search bar. Distribution stopped being a channel and became a physics problem: pain × search intent × indexed answer = clicks.

Now the part nobody in the comment thread saw. The 1,200 monthly AI-assistant referrals are not a metric. They are the entire game. Every founder in that thread was arguing about CTR, core updates, and whether his impression count is sustainable. They are grading him on the 2019 scoreboard. The real scoreboard is different: AI assistants are becoming the front page of the internet, and they cite pages with strong schema and canonical structure. He is not competing with Google anymore. He is teaching Claude, ChatGPT, and Perplexity what "AI agent skills" means. Every citation reinforces his terminology in the models' next training pass. In 18 months, the moat is not 700 pages. It is that his vocabulary — his slugs, his taxonomy, his schema fields — will be how AI models describe this category to the next 10 million developers. That is owning the language of a market before the market has a name.

Steal-the-Playbook

1. Pick one narrow wedge, not the category. Not "AI tools" — something like "instruction files for Claude Code users" or "prompt packs for real-estate agents." One noun, one user, one stuck moment.
2. Pull 50 exact stuck-moment queries. Use People Also Ask, Reddit search on r/ClaudeAI and r/CursorAI, and GSC from week two onward. Cluster into 100 article ideas.
3. Ship one article per day for 90 days. Draft with Claude, edit hard, add screenshots, publish. FAQ + Article schema on every one. No thought-leadership. Only answers.
4. Build one templated landing page per artifact in your niche. Skill, prompt, template, plugin, dataset — whatever. One template, dynamic metadata, all schema types. Let creators upload the content.
5. Every Monday, export GSC to CSV, hand it to Claude, ask "what's broken." Fix 10 things: duplicate schema, redirect chains, truncated titles, indexation errors. Boring. Compounding.

Stack: Claude ($20/mo), Google Search Console (free), Next.js or Astro with schema routes, Lovable ($20/mo) for the landing template. Setup: one weekend. Ongoing: 15-20 hrs/week for 90 days.