The setup
segeo sells a daily blog. The obvious question from anyone evaluating it is whether the output is actually worth publishing — and the obvious way to answer that is to point it at our own website and leave the results up, unedited, for anyone to read.
So segeo.net's blog is written by segeo. Same pipeline, same guardrails, same daily cron as a paying customer's site. There is no separate "marketing" mode and no human editing pass.
How it was configured
Setup took the same path a customer takes: a business profile (what we do, who we serve, the keywords we care about), a brand-voice profile, and a publishing connection. Topic selection runs off live news and trend data rather than a fixed content calendar, and every topic is checked against the previous 30 titles so the blog builds coverage instead of circling one idea.
What it has produced so far
- 3 posts published, growing by one per day on an 11:00 UTC cron.
- 1,385–1,550 words each — long enough to answer a question properly, short enough not to pad.
- $0.04 in model cost per post, on average. That is the whole marginal cost of a post.
- 5 internal links placed automatically between posts, in context, where one post genuinely covers something another raises.
Every post also links our own name once in the body and once in the closing call to action, and nothing else — the writer is only allowed to use URLs it has been handed, so it cannot invent a link that 404s.
What we are not claiming
We are not going to show you a traffic chart. This blog is days old; any ranking or traffic number we put on it right now would be noise dressed up as evidence. Search results take months to move, and we would rather say that plainly than publish a percentage you cannot check.
What you can check today is the output itself. Read the blog and judge whether these are posts you would be happy to have on your own site. That is the part we can prove now, and it is the part that decides whether the rest is worth waiting for.
Why this is the first case study
Because it is the only one where we control every variable and owe nobody's permission. Customer stories go up here as customers agree to them and as there is enough history to say something meaningful — with the source of every figure named underneath. Until then, this page has one entry rather than five invented ones.