Here's a question worth asking on a quiet afternoon: if your web agency disappeared tomorrow, could you still run your website? For a surprising number of businesses, the honest answer is no — and they don't discover it until the day they need to.
Ownership of a website isn't one thing. It's five, and they can each sit in different hands.
The domain name is the most important and the most commonly mishandled. It should be registered to your company, in an account your business controls, with billing on a card you can see. If your domain sits inside an agency's reseller account, you don't own your address. Renewals can lapse, transfers can be slow-walked, and in a bad-tempered parting you can lose email as well as your website. Check the registrant details today; it takes two minutes.
Hosting is second. Ideally the hosting account is in your name and you grant your developer access, rather than the other way round. Agency-managed hosting is fine and often sensible, but you should be able to obtain a full backup on request and know where the site would go if you moved.
Third is the code. Ask whether you receive the source, and whether it lives in a repository you can access. This is where proprietary systems bite. Plenty of agencies build on their own in-house platform, which is excellent while the relationship lasts and worthless the day it ends, because no one else can maintain it. Standard, well-known technology is a form of insurance.
Fourth is the content and data: your copy, images, product information, contact records, form submissions. You should be able to export all of it in a usable format. If your customer list only exists inside a platform, and that platform's export is a mangled CSV, you have a problem waiting.
Fifth is the analytics and marketing accounts. Google Analytics, Search Console, ad accounts, the email platform. These should be owned by a company account with your agency added as a user. Years of historical data have real value, and rebuilding a Search Console history is impossible.
Why does this matter beyond worst-case scenarios? Because ownership determines leverage. If moving is easy, your suppliers earn your business every year on merit. If moving is impossible, you'll be tolerating slow response times and creeping fees for a decade because the alternative is starting from scratch. Ownership also determines speed: when you control the accounts, a change takes an afternoon rather than a support ticket and a week.
There's a cost angle too. Rented platforms price by growth. As your contact list, your traffic or your team expands, the monthly figure climbs, and you have no way to shop around because your entire operation lives inside the thing you'd have to leave. Owning the system costs more honestly at the start and far less over five years.
So how do you fix it without a fight? Start with an audit. List the five categories above and write down, for each one, whose name is on the account. Most people find two or three surprises. Then ask your current supplier, politely and in writing, to transfer ownership and add them back as a user. A good agency will do this cheerfully; we do it routinely, because a client who stays by choice is a better client. Resistance is itself the answer to your question.
If you're commissioning a new site, put it in the brief. State that the domain, hosting, repository, content and analytics accounts will be owned by your company, that the site will be built on standard technology, and that a full export will be provided at the end of the project. Anyone unwilling to agree to that is telling you how the relationship ends.
None of this is about distrust. We've worked with clients for well over a decade, and in that time the ownership question has never once caused friction — because we settled it at the start. Own the asset, choose your suppliers freely, and the relationship stays healthy for the right reasons.