Blog
By Published 10 min read

Do I Own My Website? What to Check Before You Pay

Do you own your website after an agency builds it? Check domain access, source files, platform limits and handover terms before paying or switching providers.

Working through a similar problem? Tell us what you want to build.

Legacies is an independent digital product brand based in Bucharest, Romania, founded by Horia Stan and Alexandru Tălnaci, building websites, landing pages and web apps for businesses worldwide.

Our short answer to “Do I own my website?” is: payment alone does not tell us which rights, accounts or files come with a project. We need to check the agreement, the account holders and what the platform actually lets us move. A useful buying test is whether another provider could keep the site working using the materials and permissions supplied.

Quick answer

  • We recommend checking the domain, website files, content rights, hosting and business accounts separately.
  • We distinguish permission to edit a site from the ability to move it to another provider.
  • We ask for a written handover list, including export limits, ongoing charges and cancellation steps.
  • We treat a working backup and recovery access as practical evidence of control.

What does owning a website actually mean?

We break website ownership into three practical questions: what can we use, what can we control and what can we move?

A business might control its domain and copy while using a subscription platform that cannot run elsewhere. Another might receive custom source code but have no access to the account that publishes it.

We would use this checklist before comparing proposals:

Website elementWhat we would checkEvidence to request
DomainRegistrant details, renewal and recovery accessRegistrar account and registration details
Copy and imagesPermission to publish, edit and reuse themOriginal files and licence records
Custom design and codeRights granted under the agreementWritten ownership or licence terms
Website platformEditing permissions and export limitsAccount roles and a sample export
Hosting and databaseAccess, backups and transfer processHosting details and restore instructions
Search and analyticsBusiness access independent of the supplierAccount permissions
Connected servicesBilling, access and dependenciesService inventory and renewal schedule

We would avoid treating “full ownership” as a complete answer. The useful detail is what that phrase covers and what happens when the relationship ends.

For rights in commissioned work, we would have the agreement reviewed in the relevant jurisdiction. WIPO’s website-development guidance recommends addressing ownership or sufficient licensing rights, including continued use after the development agreement ends.

Start with the domain and recovery access

We recommend keeping domain registration under an account the business controls, with appropriate registrant details and a recovery method that survives a staff or supplier change.

The agency can still manage technical settings through suitable access. We do not need to share one password to collaborate.

ICANN explains domain registration as an agreement between a registrant and a registrar. We would therefore check the registration details and account access rather than assume that paying a website invoice settles domain control.

Our practical checks are simple:

  1. Can the business sign in to the registrar?
  2. Who receives renewal and recovery messages?
  3. Is the payment method current?
  4. Who can change DNS settings?
  5. Is there a documented recovery process?

We would also record where email runs. Moving website hosting should be planned around existing email settings, particularly if the same provider manages both.

A domain and a website are separate purchases. We can change where a domain points without necessarily transferring the registration, and we should establish which change a migration actually requires.

Can we move the website to another host?

We would ask this before choosing a platform. “We can export it” needs a follow-up: export which parts, in what format, and with which features still working?

Build approachWhat we would verify before buyingPotential handover work
WixAccount transfer options and external-hosting restrictionsRebuilding on another platform
WebflowExport eligibility and excluded featuresReplacing hosted functionality
Self-hosted WordPressComplete files, database, media and licencesRestoring and testing elsewhere
Custom website or appRepository, data, build steps and service accessDeployment and dependency setup

Wix: account control and hosting portability differ

Wix states that its sites must run on Wix’s infrastructure. Its documentation distinguishes ownership of content from the ability to host the functioning site elsewhere.

We would choose that arrangement when the convenience suits the business and the exit implications are acceptable. If independent hosting is a firm requirement, we would resolve that before commissioning the design.

Webflow: code export has boundaries

Webflow’s export documentation says code export requires a paid Workspace plan; a Site plan alone does not include it. Exported code excludes CMS database content and ecommerce functionality, while hosted forms and site search do not continue working.

We would request a feature-by-feature migration plan for a dynamic site. A downloaded design can be useful without being a complete replacement for the running website.

WordPress: content export is only part of a handover

WordPress’s Tools Export feature produces an XML file containing content such as posts, pages and categories. We would not use that file alone as proof that the whole site can be restored.

For a full move, we would request the relevant database, uploads, themes, plugins and configuration, then test the restored result.

Our WordPress vs Next.js comparison covers broader platform choices. Here, the buying question is narrower: can we reproduce the agreed website elsewhere?

What should a website handover include?

We would make the handover list part of the project scope. That gives both sides something concrete to deliver and check.

Our baseline list would cover:

  • Business-controlled account access and recovery details.
  • Source files or the agreed platform transfer.
  • Original copy, images and relevant licence records.
  • Database and media exports where applicable.
  • A list of hosting, email and connected services.
  • Build, deployment and backup instructions.
  • Recurring charges and renewal responsibilities.
  • A record of any features that cannot transfer.

We would keep passwords and secret keys out of an ordinary shared document. The handover should identify a secure transfer method and which credentials need replacing afterward.

For a custom app, we would also ask how another developer starts it, tests it and publishes an update. A repository link is useful, but missing database access or deployment instructions can still block a takeover.

This is where project scope matters. We build websites, landing pages and web apps with a fixed price and a clear process for the agreed work. When comparing a proposal with ours, we recommend discussing account control and handover alongside pages, features and launch requirements.

What does a cheap quote leave out?

We would compare the build price with the cost of running, changing and eventually moving the website.

There is no useful universal “ownership fee.” Instead, we would ask each supplier to complete the same cost breakdown:

Cost categoryQuestion we would ask
Initial buildWhich pages, features, revisions and launch work are included?
Recurring servicesWhich subscriptions continue after launch?
MaintenanceWhat work is included, and what is billed separately?
LicencesWhich renewals belong to the business?
HandoverWhat is delivered when the agreement ends?
MigrationWhich features require replacement or rebuilding?

As a hypothetical example, imagine two proposals for the same five-page site. One includes a documented handover; the other includes hosting but leaves cancellation and exports undefined.

We cannot compare their long-term cost until we know what happens when the business changes supplier.

For the broader budgeting question, our business website cost guide is the better starting point. We would then use this checklist to compare what each quote actually buys.

Keep Google accounts and search continuity in the plan

We recommend giving the business its own access to Search Console and analytics, with the supplier added through appropriate permissions.

Google’s Search Console documentation distinguishes owners from users. Owners can manage permissions, and a property needs at least one verified owner for users to retain access. We would verify the business’s access before removing an outgoing supplier.

For a move, we would also record existing page addresses, important content and redirects. Ownership of files does not automatically preserve the way visitors and search engines reach them.

Our website redesign SEO checklist covers that work in more detail.

For AI search, we would focus on accessible, useful pages and sound technical foundations. Google’s guidance for its AI search features connects eligibility to Search requirements, including indexing and snippet eligibility, while making clear that inclusion is not guaranteed.

We would not accept promised rankings or AI citations as evidence of ownership or a complete handover.

What if an agency already controls everything?

We would start by documenting the current arrangement and requesting the agreed access. A migration is easier to assess with an inventory than with assumptions about what is missing.

First, we would collect the contract, invoices and known account details. Next, we would request a written handover list and identify dependencies such as email, booking systems or payment services.

Before cancelling hosting, we would arrange backups and a tested replacement where necessary. If rights or release obligations are disputed, we would separate that contractual question from the technical migration plan.

We would also avoid assuming a rebuild is necessary. Sometimes the task is an account transfer, better documentation or a missing backup process.

Our free website audit can provide a first look at public Google readiness. We would treat ownership, private account permissions and contractual rights as a separate review requiring the relevant records.

When to handle it yourself and when to bring in help

We would handle a simple account inventory internally when the business already has access and the platform meets its needs. Recording renewals, testing recovery and collecting original assets can be straightforward administrative work.

We recommend technical help when a move involves databases, customer logins, payments, email dependencies or important search traffic. We would seek legal review when ownership or licensing terms are unclear.

For a new build, we would settle the required portability before choosing the platform. Our services page is the next step for discussing a website, landing page or web app. For an existing site, we suggest starting with the free audit, then deciding what work is actually needed.

Frequently Asked Questions

Do I own my website if I paid an agency to build it?

We would check the agreement and delivered materials before answering. Payment alone does not establish which rights, accounts, files or licences are included. We recommend confirming each part separately and obtaining jurisdiction-specific advice if the contract is unclear.

Should my web designer register my domain?

We recommend a business-controlled registrar account with appropriate registrant details and recovery access. A designer can help configure the domain through suitable permissions. If registration already sits with the designer, we would ask for the account and registration arrangement in writing.

Can I move my Wix website to another host?

We would plan for a rebuild if external hosting is required. Wix’s documented architecture requires its websites to operate on Wix infrastructure. Keeping the domain and original content accessible can help with a replacement, but does not make the running Wix site portable.

Does a Webflow export include the whole website?

We would not assume so. Webflow documents exclusions affecting CMS content and hosted features such as forms and search. We recommend checking the current export requirements and identifying which functions need replacement before agreeing to a migration.

What files should an agency give me at handover?

We would request the materials specified in the agreement, including applicable source files, content, media, database exports, licence records and operating instructions. For a hosted builder, an account or project transfer may be more relevant than source files, so we would define the deliverable before work begins.

Can I change agencies without rebuilding my website?

We would first check account access, platform transfer options, rights and technical dependencies. A rebuild may be unnecessary when another provider can maintain the existing setup. We recommend confirming that with a practical handover review before cancelling services or commissioning a replacement.

Web DesignBusinessWebsite Ownership
Business websites we buildProjects we have builtFree website auditAbout Legacies