The content engine that never guesses
A system that keeps a blog in sync with what people actually search for — connecting search data, trends and a knowledge base of its own into accurate drafts, instead of guessing. And writes texts that are actually correct.
Most things are written on gut feeling; what the author finds interesting. Not what readers are actually looking for or want.
The result is content that is never found, and search data that disappears into a dashboard nobody opens. Not an entirely unfamiliar situation.
Somewhere there is a login to Google Search Console and Google Analytics, but who has it is unclear, so that opportunity is lost too. Even if you knew, it is not certain you would understand what to use the two for, or how to read them. I admit, neither did I when I started, so I built a system that does it for me.
One that connects the search console, analytics and trend data to a knowledge base of its own, so that every new post is grounded in what is actually being asked for — not a guess. In short: true and relevant, for both SEO and AEO. Not the same thing: SEO is showing up in the list of links. AEO is becoming the sentence the AI quotes outright — without anyone clicking through.
It is fast, too. The search data is read every week, the gap is found automatically, and on request a complete draft is written the same day — research and wording that would otherwise have taken half a working day. We are talking minutes from start to publication.
Best of all, nothing in a draft is left hanging. Every figure and conclusion can be traced to a source — the knowledge base, or external reports from authorities and research that are fetched and cited on request. No AI guess is allowed to stand unchecked.
The system never presses publish itself. Its job is to flag gaps and suggest priority; the user's job is to keep the knowledge base up to date and actually read through and correct what is proposed before it goes live. The tool makes the research faster — it does not replace judgement.
Today it runs one day a week, for a public blog, with four prioritisation principles: quick win, real gap, AI-answer first, and timing. I have two tasks — keep the database up to date and actually read through what I push out.
