Website ownership after launch: who is responsible?

A website launch has a clear end point. You decide what the site needs to do, sort out the structure and content, design it, build it, test it and put it live. Then the project ends and everyone moves on.

The business doesn’t. Services change, priorities shift, new customers arrive and the way you talk about what you do moves on. Pages get added. Marketing creates landing pages. Someone changes the navigation. Someone else rewrites part of the homepage.

None of that is unusual. The problem is when nobody is responsible for the website as a whole.

That’s different from maintenance. It’s website ownership: noticing when the site and the business are moving apart, looking at the evidence, deciding what matters and getting the right work done.

Maintenance isn’t ownership

Most established businesses have some way of keeping their website running. An agency might handle hosting and updates, marketing publishes content, and a developer steps in when something breaks.

That covers maintenance and delivery. It doesn’t answer the bigger questions.

Does the website still reflect the business? Are the right people finding it? Can they understand what you offer? Are marketing campaigns sending people to pages that do their job? Are new pages helping, or slowly making the site harder to use?

Most importantly: out of everything you could change, what’s actually worth doing?

Without someone owning those questions, website work becomes reactive. Sales wants another case study. Marketing needs a landing page. SEO research suggests another piece of content. A new service needs adding. Each request makes sense on its own, so somebody deals with it.

Over time, the site becomes the sum of those decisions. Similar pages start doing the same job, old messages sit next to new ones and the important stuff gets harder to find.

That has a cost. You can spend money on SEO to attract more people while the pages they arrive on are unclear. You can put an advertising budget behind an offer the website doesn’t explain properly. Or you can commission another redesign when the real problem sits in the proposition, structure or customer experience.

More activity doesn’t fix a problem you haven’t understood.

I’ve written before about what happens when a business outgrows its website. It doesn’t automatically mean it’s time for another redesign. The first job is to work out what has changed, where the problem actually sits and what deserves attention.

The hard part is deciding what matters

There’s no shortage of possible website work. Rewrite the service pages. Improve SEO. Add case studies. Fix the navigation. Improve the forms. Create landing pages. Sort out accessibility. Redesign the homepage.

Data makes that list longer. Analytics, Search Console, customer feedback, search research and conversion figures will all give you things to investigate. They won’t tell you which ones matter most.

I use three questions:

• What is the business trying to achieve?
• What is getting in the way?
• What evidence do we have that changing this will help?

That rules out quite a lot.

A page losing traffic isn’t automatically an SEO problem. Search behaviour might have changed, another page might now be doing the job instead, or the traffic might not have been useful in the first place.

The same applies to conversion. A weak conversion rate doesn’t necessarily mean changing buttons and forms. The problem might be the audience, the offer or something much earlier in the experience.

This is where priorities matter. The job isn’t to keep producing a backlog of improvements. It’s to decide which changes are worth the time and money, which can wait and which shouldn’t be done at all.

Sometimes the brief isn’t the problem

Locale originally approached me about a rebrand.

After reviewing what they had and talking to the team, I came to a different conclusion. The business had moved on and the positioning needed work too. Simply changing the visual identity would have left a more fundamental problem untouched.

It was really the same set of questions. What was the business trying to achieve? What was getting in the way? A new identity was part of the answer, but it wasn’t the whole answer.

That changed the scope of the work. We addressed the positioning alongside the brand and website, then continued looking at the site after launch rather than treating it as finished.

One of the next opportunities was organic search. Working alongside SEO expertise, I restructured key product pages around customer intent and commercial searches, and developed dedicated pages around specific problems and solutions.

Over time, average Google search position across the site improved from around 24 to 11, while daily organic search impressions roughly doubled. Several of the solution pages reached the first page of Google, with others appearing across thousands of relevant searches.

The useful part wasn’t simply continuing to work on the website. It was being able to change what we were doing as the evidence changed: first positioning and the website itself, then search visibility, product pages, conversion and other parts of the experience.

That’s the difference between maintaining a website and continuing to think about what it needs to do.

Staying involved also lets you spot things nobody asked for

I saw the same thing over several years working on digital tools for fleet managers and drivers moving towards electric vehicles.

One was a vehicle comparison tool. I saw a need for people to compare electric and conventional vehicles more directly, mocked up an approach and tested the idea with the team. It became part of the product.

Another was much smaller. An internal tool held information that the sales team needed elsewhere, so I suggested adding a CSV export. It removed manual work and saved the sales team time.

Neither example is dramatic. That’s the point. Useful digital work often comes from understanding what people are trying to do, spotting something that could work better and deciding whether it’s worth changing.

You can’t do that particularly well if every interaction starts with a new brief.

So who should own the website?

The business should.

If you have a strong marketing, digital or product lead with the time and authority to do this, give them clear responsibility for it. You don’t need another person sitting alongside them.

The gap is more common in owner-led and growing businesses where the website matters commercially but doesn’t justify a full-time senior digital role.

Marketing is busy generating demand. An agency is running campaigns or development. The founder knows the business but doesn’t have time to keep reviewing the website. Everyone has part of the picture, but nobody is responsible for joining it together.

That’s where I provide stewardship rather than ownership. There still needs to be someone inside the business who makes the calls — often the founder or another senior lead. Decisions stay with you. My job is to make sure they’re informed, challenge them when needed and follow through on what we agree.

What website stewardship looks like

Website Stewardship means having someone senior who keeps looking at the website with you over time, rather than waiting for the next project or problem.

The arrangement is built around what the business is trying to achieve rather than a fixed block of time. We agree how we’ll work together, how often we need to review direction and priorities, what’s worth monitoring and where my involvement starts and stops. For some businesses that will need more attention than others.

There’s a regular direction and priorities meeting, and I keep track of the opportunities we’ve identified, decisions we’ve made and things we’ve agreed to watch. Between meetings there’s one place for questions and advice, so we don’t have to wait for another project to talk about something that’s changing.

What we monitor depends on the goals. It might be search performance, enquiries, conversion, important pages or a particular problem we’re trying to understand. The point isn’t to produce another report. It’s to know when something deserves attention.

Small changes can be included where we’ve agreed them. Larger pieces of work are separate. I might do them, your existing agency might do them, or we might need somebody else.

There’s an obvious overlap there: I’m advising on what needs doing and I can also be paid to do some of it. I don’t think pretending that conflict disappears makes the relationship more impartial. Substantial work is a separate decision, and Stewardship shouldn’t depend on me finding more things for Bold Wise to build.

It doesn’t need constant improvement

A good website should be given time to do its job. Changing it constantly creates its own problems, and sometimes the sensible decision is to leave something alone.

If your agency already understands the business, challenges requests and gives you good senior advice, you may have this covered. The same is true if somebody internally is looking across the website, interpreting the evidence, setting priorities and following decisions through.

Website Stewardship is for the gap: the website matters enough to need continuing senior attention, but nobody has the time and remit to provide it.

I obviously have a commercial interest in suggesting that businesses need this. Not all of them do. If your team already owns the website well, keep it there.

But if nobody is really asking what the website needs next, that’s worth fixing. You can read more about Website Stewardship, or start with a Website Review if the more immediate question is what needs attention now.