Nobody Owns Your Second Website
Published by: Erick Olivares
Date published: August 12, 2026
You have more than one website. Most companies your size do.
There is the main one. Then there is the campaign site somebody spun up for a product launch three years ago. Maybe a store on a different platform. Maybe a portal a vendor built and then stopped answering email about. Maybe a microsite for a location, an event, or a brand you acquired.
They were built at different times, by different people, on different systems. They do not share a design system, a login, or a maintenance schedule. And if someone asked you today who is responsible for all of them, the honest answer is that you are, sort of, but nobody actually is.
That is the second website problem. It is quieter and more expensive than it looks.
It only shows up when something goes wrong
A website nobody owns works fine right up until it doesn’t.
Nothing about it feels urgent. The main site gets attention because it gets traffic. The second, third and fourth get attention when someone notices they are broken, and by then whatever broke has usually been broken a while.
The moments it surfaces are predictable:
Someone leaves. The person who set up the campaign site moves on, and with them goes the hosting login, the plugin decisions, and the reason it was built that way in the first place.
Something breaks. A form stops delivering. A checkout throws an error. A certificate expires. On the main site you would know within hours. On the second one you find out when a customer tells you, or when you notice the enquiries went quiet.
A rebrand starts. New logo, new colours, new messaging. Now there are four sites to update, and no clear list of what exists, where it lives, or who can change it.
You get compromised. Worth naming plainly. Neglected installs are the ones that get hacked, because nobody is applying updates. And the site that gets hacked is almost never the flagship.
Why it never gets fixed
Because it is nobody’s job.
The website is one of about fifteen things you are responsible for, and none of them is your specialty. It competes with a supplier problem, a hiring gap, and a system that needs replacing. It becomes urgent when it breaks, and the moment it is fixed it goes back to the bottom of the list.
There is a structural reason too. Agencies are built to sell projects. A project has a start, an end and an invoice. “Keep an eye on these four sites indefinitely” does not fit that shape, so it rarely gets offered, so it rarely gets bought.
The result is that the work most likely to prevent a disaster is the work least likely to be anyone’s responsibility.
The real cost is not money
It is that you are the single point of failure.
You are the only person who knows all four sites exist. You are the one who remembers the store is on a different platform and the portal has its own login. You cannot fully hand any of it off, because there is no document, no owner and no shared history. It lives in your head.
Which means you cannot take two weeks off without a small background hum of worry. And every time you bring in help, you start by explaining the whole situation from scratch.
That is the cost. Not a line item. Something you carry.
What good looks like
One owner across every property. Not a ticket queue, not whoever is free that day. Someone who already knows the store is on Shopify, the portal has a custom form, and the campaign site was built in a hurry.
Shared hours you can spend wherever they are needed. Some months everything happens on the flagship. Some months it is all the store. Splitting attention into fixed per-site buckets guarantees you have hours sitting in the wrong place.
One agreement, one invoice, one number to call. So nobody has to ask which site you are calling about.
A regular pass across all of them. Updates, backups, monitoring, and someone actually looking at the ones you have not thought about in six months.
Most of our longest-running clients arrived with two to four properties built at different times by different people. That is not the exception. It is the normal condition of a company that has been operating for a while.
Four questions
Before deciding whether this is a problem worth solving, answer these honestly:
- Can you list every website your company owns, right now, without checking?
- If the second one went down on a Saturday, how would you find out?
- When was the last time anyone applied updates to the one you think about least?
- If you left the company next month, who would know all of this?
If the fourth question made you uncomfortable, that is the actual problem. Everything else is a symptom.
