AI-Powered Content Engine
Automated blog pipeline that proved programmatic SEO works, even at baseline quality.
I run admocker.com and thought it had room to pick up organic traffic, but writing blog posts isn’t my favorite work, and I was curious how Google would actually respond to AI-assisted content on a real, indexed domain rather than a test property. So I built the smallest possible pipeline that could take a topic and ship a published post end-to-end, with no manual step in between.
Topic generation from sitemap gaps
The pipeline starts by reading the site’s current sitemap to see what’s already covered, then identifies the gaps: topics adjacent to existing content that nothing on the site addresses yet. It asks the model for a batch of SEO-relevant title candidates against those gaps, so every post starts from an actual hole in the site’s coverage instead of a topic picked at random.
Drafting and sourcing imagery automatically
Once a title is chosen, the post is generated through the ChatGPT API against a structured prompt and a fixed format the site already uses, so output is consistent post to post rather than reinventing structure every time. A light NLP pass over the title extracts keywords, which drive a call to the Unsplash API to pull relevant photography. Credits are attributed automatically, no manual image search or licensing check required.
Publishing pipeline
The finished post is saved as a static page and committed straight to the site. There’s no CMS, no draft-review queue, no human gate between generation and publication. That’s deliberate: the whole point of the experiment was measuring what happens when the content surface area exists, not building an editorial workflow around it.
Doubled organic traffic
After the AI-assisted pages were indexed, impressions and clicks on the domain roughly doubled. A domain with thin content gets meaningfully more search visibility once the content surface area exists at all, even at a baseline quality bar. The content being AI-written mattered less than the content existing in the first place: more indexed pages addressing more specific queries beat fewer, thinner pages every time.
The code lives on GitHub.
When programmatic SEO is the right tool
This only works because admocker.com had genuine coverage gaps, not because automation is a substitute for having something to say. A domain that’s already thin loses far more from having ten pages than from having one bad page, since search engines reward topical coverage as much as they reward any single piece being excellent. The pipeline is intentionally narrow for the same reason the rest of my side projects are: it does one job, close a specific content gap on a specific domain, and doesn’t try to be a general-purpose CMS.