Running a Hundred Sites Without Losing Your Mind
The instinct that works at one site and breaks at scale
When you run a single site, checking on it feels like care. You open the dashboard, read a comment, nudge a headline, notice a broken image and fix it right then. That instinct, the urge to look closely and respond immediately, is what makes a first site good. It is also the first thing that has to change once there is more than one.
I learned this the slow way, treating every site the way I treated the first one: as something to watch. Watching does not scale. The moment a second site exists, then a third, checking in on each one individually stops being diligence and starts being the thing quietly eating your week. The fix is not to care less. It is to express that care through structure instead of presence, so a site can sit untouched for a stretch and still be doing its job.
"Just check on it" is not a system
Somewhere early in this work I noticed I was using the phrase "I'll just check on it" as if it were a plan. It is not. A system tells you what to look at, when, and what counts as a problem worth stopping for. Just checking tells you none of that. It is a vague promise to your future self, and future you is already busy running everything else.
The difference shows up the moment something actually breaks. Without a real signal, you find out about a dead form or a broken redirect whenever you happen to stumble across it, days or weeks later. With a system, something tells you within hours: an alert, a scheduled check, a simple beacon confirming the page is alive and behaving the way it should. That layer is what lets you finally ignore everything else on purpose instead of by accident.
Rituals instead of heroics
Heroics feel good and do not scale. A late night spent fixing six things at once, congratulating yourself the next morning, is satisfying and useless as a strategy. It relies on you noticing the mess, having the energy to deal with it, and being available exactly when it happens. Over a large enough portfolio, at least one of those three will fail on any given week.
Rituals are the boring alternative, and they are the ones that hold. A short recurring pass through the same checklist, on the same cadence, regardless of how the week is going, catches the site that quietly needs attention. The value is not in any single instance of the ritual. It is in the fact that it happens whether or not you feel like it, which is exactly why the sites I trust most are run by people with unremarkable weekly routines.
The maintenance work nobody sees
Nobody writes a case study about the domain renewal that happened on time, or the broken image swapped out before a visitor saw it. That is the nature of maintenance: when it works, it is invisible, and invisibility gets mistaken for unimportance. This is the part of the work that tests you emotionally more than technically.
You can spend an afternoon on unglamorous plumbing, renewing a certificate, tidying a sitemap, checking that a form still delivers mail, and have nothing to show for it except the continued, unremarked existence of things that were already working. I have made peace with this by changing what counts as a win. A quiet week across the portfolio is not nothing. It is the entire point.
Leaving good enough alone
This one goes against instinct. A site that is working, reads well, loads fast, and converts at a reasonable rate does not need to be reopened every month for a redesign. The urge to keep polishing something that is already doing its job is not diligence. It is often restlessness wearing diligence as a costume.
Every time you touch a live page you introduce a small chance of breaking something that was fine, and that risk multiplies across a portfolio. The operators who keep quality high over time are not the ones endlessly tinkering. They are the ones who know how to leave a good page alone and spend that saved attention where it is genuinely needed. Restraint is a skill here, and it has to be practiced on purpose.
Telling real care apart from thin mass production
The honest tension in doing this at any scale is that it can resemble, from a distance, the exact thing it is trying not to be. A large number of sites and a philosophy of not tinkering constantly can look like a content farm if you squint. The difference is not visible in the count of sites.
It is visible in whether each one was built for a real reader, with a real point of view, held to a standard that does not bend just because other sites exist alongside it. Mass production optimizes for output and treats every unit as disposable. Care at scale optimizes for a standard and applies it consistently, which happens to make output possible as a side effect rather than the goal. I would rather run fewer sites well than many sites carelessly.
| The instinct with one site | The system you need at scale | |
|---|---|---|
| Publishing a new page | Write it, publish it, admire it, move on whenever it feels right | A repeatable structure and a fixed checklist so every page meets the same bar before it goes live, regardless of mood or day |
| Checking analytics | Refresh the dashboard out of curiosity, several times a day | A brief look on a fixed cadence, with an alert doing the watching in between so curiosity is not the only safeguard |
| Renewing a domain | Trust yourself to remember the date | A calendar entry or automatic renewal set months ahead, because memory is the least reliable part of any large operation |
| Fixing a broken template | Patch the one site where you noticed it | Fix the shared source so every site using it heals at once, then confirm the fix actually held |
How do you keep quality consistent across many sites?
Through templates and standards decided once, in a calm moment, rather than improvised under pressure on each site individually. A shared checklist for what a page needs before it counts as finished, a consistent editorial voice, and a small set of non negotiable technical basics. Consistency comes from the system doing the remembering, not from personal vigilance repeated many times over.
Isn't running this many sites just spam?
It can be, if the sites exist only to fill space and rank for a keyword. That pattern is real, and it deserves the skepticism it gets. The distinction I hold myself to is whether a given site is a genuine, standalone thing built for an actual reader with a real point of view, or whether it is a thin page wrapped around a link and nothing else. Scale is not the problem. Building without care and calling it scale is the problem.
What breaks first when a portfolio grows?
Attention and consistency, almost always before anything technical does. The infrastructure tends to hold up fine on its own. What slips first is smaller: a voice that used to feel consistent starts to drift, a standard that used to be automatic gets skipped once, then again. The fix is catching that drift early through rituals, not waiting for it to become visible to a reader.
I write these notes as the operational picture becomes clearer, not on a fixed schedule. If you want the next one when it lands, there is a small, low-noise way to hear about it at the bottom of the homepage.