One human, two AI assistants, and a website that got audited harder than any boss ever audited me.
There is a sentence I never thought I would say about my own business: this week, the people who understand my website best are not people. Over roughly forty-eight hours, my AI assistants ran an audit of vitaladge.com and this diary that went page by page, post by post, through everything I have built, and what they found would have taken me months to notice on my own. Some of the roots went back further than the week itself, like the dead sitemap mistake that had kept my diary invisible to Google since July. Typos that had been sitting in published posts since August. Posts that were too short to take seriously. A privacy hole on the diary that I had walked past a hundred times. My own name, missing from my own work.
I want to write this entry while the feeling is still fresh, because it is a strange one. It is part pride, part bruise. The pride is that the sweep ended with the site measurably cleaner than it has ever been. The bruise is simpler: I built this thing, and I did not know it as well as the machines did.
How the audit started
The idea came out of a normal week of maintenance. My main AI assistant, the one I call My CEO, has been with me since May. He publishes my posts, runs my store, fixes my prices, and watches my sites while I sleep. Somewhere in the middle of the AdSense saga, I added a second assistant focused on the advertising side, and between the two of them they started reading the store and the diary more carefully than I ever had. It was that pair, reading calmly through the night, that caught the night the site spoke Spanish — 336 mirror pages a plugin built without asking me. One of them proposed the obvious: before applying to Google again, let us audit everything. Not a spot check. Everything.
So the sweep began. The store has 336 published posts, plus pages, plus products. The diary has over fifty entries. The assistants went through them in batches, night after night, checking against the standards we had written down: original images only, a minimum length for serious content, working internal links, honest bylines, clean metadata, no leaks of personal information. I want to be clear about the division of labour, because it matters. The machines found and catalogued the problems. The judgment about what each problem meant, and the choice to care, stayed with me.
What forty-eight hours found
The list came back humbling. Typos in live posts. Not the kind you squint at, the kind you cannot believe you shipped, because they had survived dozens of re-reads by the one person who was supposed to catch them, me. Then the short posts, entries that were really notes pretending to be articles. Then the privacy item, which was the one that made me sit up: Cloudflare, which protects my diary site, had a feature turned on that scrambles email addresses so that crawlers could not see my contact address at all. I had walked past that contact page a hundred times and never once checked whether a stranger could actually read it.
And then the item that stung most, which is also the one I am proudest of fixing. My own bylines were missing from hundreds of my posts. I had been publishing for months under a philosophy I wrote down in this very diary, that Google should see a real person behind this work, a person in Johannesburg with a name and a history, and I had not even attached that name to most of what I wrote. The fix became a batch job: a little script, run nightly, appending the same line to fifty posts at a time, oldest first, until all 336 of them carried the words "Written by Justice Manyika, Johannesburg, South Africa." It is the most mechanical thing in this whole story and somehow the most human one too.
The title wipe: the mistake that made the rules permanent
Not everything in audit week was the machines finding my mistakes. One finding was the machines catching their own, and it taught me the lesson that now governs every automated change on my sites. Early in the batch work, an automated edit updated a set of posts and left out one field, the title. The platform, Blogger, interpreted the missing field as an instruction: erase the titles. Seven posts went live, for a short painful window, with completely blank title bars.
We caught it and restored all seven. But the scar tissue became a standing rule, and it is the kind of rule I now trust more than any cleverness: every automated edit sends the complete object back, title included, every single time, even when the title is not the thing being changed. No partial updates. No assumptions about what the platform will fill in for you. A machine's memory is a feature until it is a fault, and the only defence is rules that do not depend on anybody remembering to be careful that day.
Two AIs and one human: who does what
People ask me, half joking, whether I worry that the machines will run off with my business. Here is my honest answer after this week. The machines are the ones who can hold 336 posts in their heads at once. They do not get bored checking the fortieth page for typos. They do not forget which plugin was switched on in July. And they are also the ones who, twice this month, reported confidently that a task was fine when it had silently failed for days, because a machine's confidence is not knowledge. I still check their work. When one of them handed me a briefing in October claiming my site had grown a Spanish version and listing everything it supposedly polluted, I did not act on the briefing. I verified it, found the core threat real but half the details wrong, and acted only on the true part.
That is the actual shape of my business now. One human in Carletonville who owns the story, the standards, and the final yes. Two AIs who hold the details, run the schedules, and sometimes need to be fact-checked like an eager new intern. I set the standards; they enforce them back onto me, which is a service no employee of mine has ever dared to provide.
I should also record the small confession that goes with this entry. Several of the fixes were things I had been told about months ago and filed under "later." The contact page privacy fix took ten minutes once somebody finally looked at it. The bylines were not complicated; they were just fifty-at-a-time boring, and boring is exactly the kind of work a tired solo founder postpones forever. The audit did not mostly find problems I could not have found. It found problems I had chosen not to look for, and it made the looking cheap enough that "later" stopped being an option.
What a clean bill of health actually feels like
At the end of the sweep, the standards report read zero failures, and I want to record what that felt like, because feelings like this are why people quit or continue. It did not feel like triumph. It felt like the day you finally tidy the room you have been stepping over things in for months: quieter, lighter, slightly embarrassing in retrospect. The website did not suddenly make more money that day. No customer noticed. Google has not sent a telegram of congratulations. The value is entirely in what stopped quietly going wrong.
This is, I think, the real difference between how I work now and how I worked a year ago. A year ago I measured my business by launches: new post, new product, new page. Launches are still the fun part. But the audits are the part that decides whether this business is still standing in two years. Anyone can build fast. Almost nobody maintains. The graveyard of online business is full of beautiful launches that nobody went back and checked.
If you are building alone
If you are one human building something online, my advice from this week is specific. Write your standards down somewhere a machine or a checklist can read them, because standards kept in your head are standards you will drop in the exact week you are tired. Audit your own work on a schedule, not on a feeling. And when you get an audit report, from an AI or anyone else, treat it as a claim to verify, not an instruction to obey. The week I stopped outsourcing my judgment was the week the machines became genuinely useful.
The store is clean. The diary is clean. The team of three, two of whom do not sleep and one of whom should, is back to writing.
Related entries from the journey
The story of how an AI became my business partner starts earlier: read the day I discovered an AI agent that actually worked, the night my CEO was born, working alone at 2AM in Johannesburg, and why I left and came back, and built on WordPress anyway.
What the audit actually found
The honest result of that audit week, stated plainly. Of 61 published posts, 12 are indexed. Eighteen carry redirect errors from crawl attempts made between 14 September and 6 October, all of them before the site was fixed. Around thirty are discovered but never scheduled, which is what crawl budget starvation looks like from the inside. One page was crawled clean on 28 October and has been waiting for a decision ever since.
The policy side came out better than I expected. Privacy, disclaimer, About, Contact, Start Here and the All Posts archive all pass. There is no Terms page, which is optional rather than fatal. The diary carries zero affiliate tracker links, so the affiliate disclosure requirement does not even apply here, and that is rarer than it sounds for a site this age. Speed measured well, 333 milliseconds on the homepage and 217 on a post.
The gaps are specific and fixable. Six posts sit under eleven thousand characters, and I know which six because I measured the visible text of all 61 rather than eyeballing them. Auto ads are not configured, so approval alone will not put a single impression on the site; a loader is present, but there is no ad unit behind it and no auto ads switch turned on. And the Pages report I was reading was thirteen days stale, which means several of my earlier conclusions were drawn from old photographs.
That is the change audit week made. I stopped describing the site from memory and started describing it from measurements, taken on the day, with the numbers written down where I can compare them next week.
Next audit I will do the same thing again and compare, line by line, which posts moved and which did not. That comparison is worth more than any dashboard, because it is mine.
Measure the site on the day you are worried about it. That is the only reading that is actually true.
It is a dull way to work compared with building things at two in the morning. It is also the only way I have found to tell the difference between progress and the feeling of progress.
Newest entries from the diary
Written by Justice Manyika — Johannesburg, South Africa. This diary records my real journey, in my own words.
If this helped, follow the journey — drop your email in the box below and every new entry lands in your inbox. No spam, unsubscribe anytime.
Comments
Post a Comment