Back to Perspectives Behind the Build

Content Creation Automation: How We Run Our Own SEO

Everyone talks about AI. We wanted to run our growth on it, in the open, without faking a number. So we aimed the automation we build for clients at our own worst problem: SEO for a small bootstrapped site in a loud category. No content team. No guessing. Two rules: decisions come from data, and claims have to be true.

Content Creation Automation: How We Run Our Own SEO

We Started With Data, Not Keywords

We didn't start with content. We started with a command center. Every Search Console export gets saved, dated, and compared to the last one, so we know what actually changed instead of guessing. It caught things instinct would miss: impressions rising weeks before any clicks, German cost queries quietly converting, a stack of posts Google found and ignored. Same rigor we bring when we build automation for clients, pointed at ourselves.

SEO COMMAND CENTERCLICKS (12 mo)55IMPRESSIONS6,294+282NOT INDEXED94DAILY IMPRESSIONSTOP QUERIESprivacy first ai683ki automatisierung kosten91ai operations98
The command center: one view of clicks, impressions, indexing, and the queries doing the work.

Intent Before Keywords

Then we sorted every query the site ranks for, all 247, by what the person wanted: learn, compare, or buy. A page on the first results page with zero clicks doesn't need a new keyword. It needs a better headline. Most "AI content engines" skip this and just spin up pages around keywords. We start from intent, build the page to match, and make sure someone still owns it after it ships.

Striking 33CTR fix 13Transactional 45KEYWORDINTENTOPPORTUNITYPRIprivacy first aiInformationalConverting410your next automation...InformationalCTR fix248ki automatisierung kostenTransactionalConverting68privacy first ai platformCommercialStriking60ai operationsInformationalDeep39
247 queries, sorted by intent and opportunity. The work queue.

We Fixed What Was Actually Broken

The problem was plumbing, not prose. Dozens of posts were orphaned, reachable only from the blog index, so Google never bothered to index them. The cause was almost silly: a "related articles" box showing the same three posts on every page. We rebuilt it so every post links from at least two others, added real links inside the writing, and checked it live. That diagnosis is exactly what an AI audit does for a client site.

BEFOREAFTER~40 posts orphanedevery post linked 2x+
Before: the same 3 related posts everywhere. After: every post linked at least twice.

The Engine Runs Weekly

With the plumbing fixed, the loop got boring, which is the point. It reads the latest Search Console data, finds something just off page one, drafts a piece with real facts and the right links, and sends it for review. A person signs off on every word. For a real business making real claims, that isn't a bottleneck. It's the whole point.

The Honest Results So Far

We're early, and here's exactly where we stand. Impressions went from about 3,000 to just over 6,000 as the system compounded, across 138 pages and 247 tracked queries. Clicks are still catching up to position, which always happens right before they break. Small numbers, but a real direction, and every one is checkable.

Daily impressions, 30 Jun to 12 Jul 20266/307/77/87/97/107/1293284
Real Search Console numbers. Visibility climbing ahead of clicks, the pattern right before they follow.

That's the deliverable: not a traffic screenshot, but a system we can run again next week. And a rule we hold ourselves to first. If we won't put a number in our own post without proof, we won't do it in yours.

Key Takeaways

  • Start with data, not keywords. Save every Search Console export and compare it.
  • Sort by intent first. A first-page result with no clicks is a headline problem, not a keyword one.
  • Automate the fetching, scoring, and drafting. Keep a human signing off on every word.

Conclusion

None of this is magic, and none of it runs itself. Search Console data, an honest read on intent, fixed linking rules, and a person who checks before it ships. The result is consistency without invention.

Want it pointed at your site? Start with an AI audit. Curious who keeps it running after? That's AI operations, the difference between a system that rots and one that pays you back.

Don't miss the next one

One email when a new piece goes live. No spam, unsubscribe anytime.

More perspectives

AI Operations: Who Runs Your AI After It Ships? AI Strategy

AI Operations: Who Runs Your AI After It Ships?

Why 70% of AI Projects Fail Analysis

Why 70% of AI Projects Fail

AI Automation Cost & ROI Benchmarks 2026 Analysis

AI Automation Cost & ROI Benchmarks 2026