Grow organic search traffic with a Search Console driven SEO loop

A solo developer ran Claude Code as a rule-bound SEO engineer wired to Search Console and reports 407K Google clicks in six months, with daily clicks rising from about 3,000 to over 9,000.

Done withClaude Code· Nov 20, 2026

What they did

Mofidul Islam, a solo developer with a full-time job, connected Google Search Console to Claude Code through an MCP server and worked on his app's website in the evenings. Instead of asking for a page per keyword, he gave the agent written rules. Before any new page, it queries Search Console for the keyword and variants, lists URLs that already get impressions, and must choose create, improve existing, or reject. It then audits the work with SEO skills (intent, titles, canonicals, internal links, thin content, unsupported product claims), runs a pre-deploy checklist that blocks failing pages, checks the live HTML after deploy, and later marks each change keep, iterate or revert from the data.

How it went

He reports 407,000 clicks and 3.25 million impressions over six months at a 12.5% click-through rate and average position 8, with 131,000 clicks in the last 28 days. Daily clicks went from about 3,000 at the start of November to over 9,000 by mid-November, up from a few hundred six months earlier. No ads, agency or content team. The production check caught pages whose source looked right but whose served HTML was wrong.

Worth knowing

The numbers are self-reported in a Medium post and the screenshot was not included in the text we read. The app and site are not named. Search Console access through MCP is the piece that makes the loop work; he warns against publishing new pages in reaction to a traffic drop.

Try it

With Claude Code· 4 parts to fill in

Act as the SEO engineer for [my site]. You have Search Console access through [MCP server]. Before proposing any page for [target keyword], query Search Console for it and close variants, list every URL on the site already getting impressions, and output one decision: CREATE, IMPROVE EXISTING or REJECT, with the data behind it. For anything you build, audit intent, title, meta description, H1, canonical, internal links, sitemap and claims against [product facts]. Do not deploy if any check fails. After deploy, check the live HTML, not the source. Stop after one change and wait for me to approve before starting the next.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related