Website Ownership Checklist: Make Sure You Truly Own Your Website

On this page

1. 1. Domain name
2. 2. DNS
3. 3. Hosting account
4. 4. WordPress administrator access
5. 5. Technical access
6. 6. Business email
7. 7. Premium themes and plugin licences
8. 8. Analytics and Google accounts
9. 9. Design files and brand assets
10. 10. Backups
11. 11. Put it in writing
12. Keep a secure record

Many business owners discover too late that their domain, hosting or website admin is registered in a developer's or agency's name. If that relationship ends badly, getting control back can take weeks. Use this checklist to make sure you own what you've paid for.

1. Domain name

• Registered in your business name, with your email as the owner contact
• You have the registrar login
• Auto-renew on, with a payment method you control

Domain stuck in someone else's account? See how to transfer a domain safely.

2. DNS

You know where DNS is managed (registrar, host or a service like Cloudflare) and have access. DNS controls your website and email routing; see domain, hosting and SSL explained.

3. Hosting account

• The account is in your name, or you have full access if a developer manages it
• You know the renewal date and cost

4. WordPress administrator access

You have your own Administrator account, not just an Editor account. Developers should have their own separate logins that you can remove.

5. Technical access

You know how to get SFTP and database access, or at least have the hosting login that provides it.

6. Business email

Email accounts are under your control, with the admin login in your name.

7. Premium themes and plugin licences

Paid licences should ideally be bought in your name. Otherwise, you may lose updates if the developer's licence lapses.

8. Analytics and Google accounts

• You're the owner of Google Analytics, Search Console and Google Business Profile, and add developers as users
• Same for Meta Business, ad accounts and tag managers

9. Design files and brand assets

You have your logo files (including vector formats), brand colours and fonts, and any design files for the website.

10. Backups

Backups are stored somewhere you can access, not only inside a developer's account.

11. Put it in writing

Your contract or agreement should state that you own the website, content and accounts once paid. See the website brief template for planning the project.

When a project finishes, use the website handover checklist to confirm you have received everything.

Keep a secure record

Store all logins in a password manager, and update it whenever access changes.

Already locked out? See how to regain access from an old developer.