Who owns your website? You paid for a website. You assume that means you own it: the design, the code, the domain, all of it. Then you try to switch agencies, or your current one stops answering emails, and you find out how much of “your” site was never actually yours to take with you.
This isn’t a rare edge case. It’s one of the most common reasons a business ends up stuck with an agency it wants to leave. Not because the contract was malicious, but because nobody spelled out what “your website” actually included until it mattered.
Ownership isn’t one thing. It’s at least seven separate things, and an agency can be completely upfront about some of them while staying vague on the rest, not necessarily out of bad faith, just because nobody asked. Here’s what to check, what usually goes wrong, and what a proper handover actually includes.
The seven things “ownership” actually covers
Design files and source assets. The Figma or XD files, the layered graphics, anything used to produce the final design. If your agency worked directly in a page builder with no separate design file, that’s fine, but it means the “source” is the live site itself.
The site files and database. The actual WordPress installation: theme files, plugins, uploads, and the database that holds your content. This is the part most people assume they automatically get, and usually do, once the project is paid off. It’s also the easiest to verify. Ask for a full export and see how quickly, and how completely, you get one.
Domain registration. Whose name is on the registration, yours or the agency’s? This is the single biggest point of leverage an agency can hold over you, intentionally or not.
Hosting account. Is your site on your own hosting account, or living on an agency reseller plan alongside dozens of other clients? The second setup isn’t automatically a problem, but it means your site’s uptime depends on a relationship you may no longer have.
Premium plugin and theme licences. Page builders, form plugins, security tools: most serious WordPress sites run on several. Licences are usually held one of two ways, yours or the agency’s, bundled into what you’re paying them.
Content, copy, and imagery. Words and photos have the same ownership questions as code. If your agency wrote your copy or supplied stock photography, check whether that’s licensed to you specifically or to the agency’s account.
Third-party accounts. Analytics, Google Search Console, ad accounts, form and booking tools. These often get set up under an agency’s login during the build and never get transferred, which means your data history stays with them even after you leave. Losing years of Search Console history isn’t just an inconvenience. It’s the record that shows how your site has actually performed over time, and it doesn’t come back once it’s gone.
Where it usually goes wrong
The pattern is consistent: a domain registered under the agency’s account instead of yours, hosting on a reseller plan with no separate login for you, a proprietary page builder or theme that breaks or disappears the moment a licence lapses, stock images licensed to the agency rather than to your business, and no access to your own analytics history because the account was never in your name.
None of this is necessarily malicious. Reseller hosting and bundled licences are normal parts of how agencies keep costs down for you, and most agencies aren’t trying to trap anyone. The problem shows up only when nobody told you, and you find out at the worst possible time: when you’re trying to leave, mid-argument, or both.
The proprietary page builder issue deserves a specific mention. A site built on a custom, in-house framework that only the original agency’s developers understand isn’t technically “locked,” but it functions that way in practice. Any new developer has to reverse-engineer how it works before they can safely touch it, which costs you time and money that has nothing to do with the actual redesign work you wanted done.
Plugin licences specifically
This is the part most FAQs skip, so it’s worth its own section. Agencies buying unlimited-site licences for premium plugins and covering clients under them is completely standard practice, and it’s often cheaper for everyone than every client buying individually.
What matters isn’t whether the agency holds the licence. What matters is whether you’re told up front, and given a clear answer to “what happens if I leave.” A plugin under an agency licence doesn’t stop working the day you go, but it stops receiving updates, which turns into a security problem over time rather than an immediate one. Reasonable agencies will tell you which plugins are agency-licensed and roughly what it costs to pick up your own licence if you leave. As a rough guide, premium plugin licences for a typical business site run somewhere in the low hundreds of dollars per year, combined. Ask your agency for the specific list rather than budgeting blind.
What a clean handover looks like
A proper handover, whether you’re leaving on good terms or bad ones, includes:
- A full export of your site files and database: not screenshots, not a zipped folder missing the uploads directory, an actual complete export.
- The domain either already registered in your name, or transferred to you without delay and without a surprise “administrative fee” attached.
- A written list of which plugin and theme licences are agency-held, so you know exactly what needs replacing and roughly what it will cost.
- Credentials for any third-party accounts set up on your behalf, handed over rather than reset.
- A reasonable window, a few weeks is typical, where your next developer can ask the outgoing agency direct questions about how the site was built.
None of this should require a fight. If it does, that tells you something about the agency more than it tells you about the process. A studio confident in the value of its work doesn’t need to make leaving difficult in order to keep you.
Questions to ask before you sign
Ask these before the contract, not after the invoice:
- Is the domain registered in my name or yours?
- Whose hosting account will the site live on?
- Which plugins and themes are licensed to me, and which are licensed to you?
- What do I get if I leave: files only, or a full database export?
- Will I have my own login to Analytics, Search Console, and any ad accounts?
- If I stop paying for maintenance, does anything stop working immediately?
- Do you retain any rights to reuse my design or code elsewhere?
- Is there a handover process, and how long does it take?
A vague or defensive answer to any of these is worth noting. A specific one is a good sign, regardless of which agency you’re talking to. Most of these questions take thirty seconds to answer if the agency actually knows their own setup. Hesitation is usually the more telling response than the answer itself.
It’s also worth asking these again partway through a long project, not just at the sales stage. Setups change. A domain that started in your name can end up transferred during a rebuild if nobody’s paying attention, and the person who answered these questions during the sales call isn’t always the person who ends up managing the technical side of your account.
How we handle it
You own the design, the content we produced for you, and the site files outright once final payment clears. We retain the right to display the work in our portfolio and case studies unless you ask us not to. What we don’t hand over is our own internal tooling: our reusable code libraries and site-build framework, because that’s not part of your site, it’s how we build it. If you ever leave, we’ll provide a full export and answer reasonable questions from your next developer during a handover window.
If you’re evaluating agencies and want a broader list of questions beyond ownership, our guide to choosing a website designer and questions to ask freelance developers cover the rest of the vetting process. And if a low quote is part of what’s driving this, it’s worth reading why cheap web design usually costs more later before you decide based on price alone. If licensing costs are the sticking point, our take on whether Elementor Pro is worth it walks through how that specific licence works.
One more thing worth knowing: in Canada, copyright doesn’t automatically transfer to you just because you paid for the work. Under the Copyright Act, an independent contractor or agency is the default first owner of anything they create for you, unless the contract explicitly assigns those rights to you in writing. The Canadian Intellectual Property Office confirms this directly, so “we built it, you paid for it” isn’t enough on its own. Make sure your contract actually says the rights transfer to you, in plain language, rather than assuming it’s implied by the invoice.
This matters more than it sounds like it should. A verbal agreement or a handshake understanding that “obviously” you own what you paid for carries no legal weight if it isn’t in writing, and it’s a strange thing to discover only after a relationship has already gone sideways and you need the leverage that a clear assignment clause would have given you.
