Every few months a call comes in with a version of the same sentence: “We need to move our website, but we are not sure who has the keys.” It is rarely a crisis at first. A credit card expires. A developer moves on. An agency folds. The volunteer who set everything up in 2019 stops answering email. Then something ordinary needs doing, a redirect, a switch to better hosting, a new mail provider, and the ordinary thing turns out to be impossible, because nobody in the building can log in to the account that controls it.
Twenty years of taking over other people’s WordPress installs has taught us that this is the most common hidden defect in a small organization’s web setup. It is not a design problem. It is not a speed problem. It is an ownership problem, and it stays invisible right up to the week it costs you real money.
Here is the check we run on every site we inherit. You can run it yourself in an afternoon, and you do not need a developer to do it. There are five accounts. For each one the test is the same: can you log in right now, by yourself, without asking anyone for permission? Not “we have the password somewhere.” Not “our guy handles that.” You, logged in, today.
1. The domain registrar
This is the deed to the property. The registrar is the company where your domain name is registered and renewed, and whoever controls that account controls where your web address points. Everything else on this list can be rebuilt in a week. A domain you do not control can take months to recover, if you recover it at all.
Log in and check three things: the account is in your organization’s name, the billing card is one your organization actually holds, and the administrative contact email is an address your organization will still read in three years. That last one matters more than people expect. A domain whose contact address is a former employee’s personal inbox is a domain nobody will be able to verify when the renewal notice goes unanswered.
2. Whoever answers for your DNS
DNS is the switchboard. It takes your domain name and decides which server shows the website and which one receives the email. The catch is that DNS very often does not live at the registrar. It gets moved to a host, a security service, or a performance service during some earlier project, and the move is almost never written down.
This is the single most frequent source of the sentence “we changed it and nothing happened.” People edit records in the old place while the internet reads the new one. Find out which service is actually authoritative for your domain, confirm you can log in there, and write it down somewhere other than a developer’s memory.
3. The hosting account
Hosting is the building the site sits in. You want owner level access, not a sub-account somebody created for you, and not a login that is shared with four other websites belonging to other clients of the same person. A shared arrangement is not automatically bad, but you should know it exists, because it determines whether you can move out on your own schedule or have to negotiate for it.
While you are in there, find out whether backups are running, where they are stored, and whether anyone has ever restored one. A backup nobody has tested is a belief rather than a safety net, which is a separate problem we have written about at length.
4. Your own WordPress administrator account
Not the site’s admin account. Yours. There should be an administrator user in WordPress that belongs to a named person at your organization, with its own email address and its own password.
What we usually find instead is one login called “admin” that five people share, including two who no longer work there. That arrangement fails in both directions: you cannot tell who made a change, and you cannot remove one person’s access without resetting everyone. Give every person who needs access their own account at the lowest level that lets them do their job, and keep at least one administrator that the organization itself controls.
5. The mail room
This is the one nearly everybody forgets. Your contact form has to hand its message to something that delivers mail, and your website probably also sends password resets, receipts, and notifications. That delivery usually runs through a separate service with its own account, its own sending domain, and its own monthly limit.
If you do not know what that service is, you have no way to find out why a form submission never arrived, and no way to prove whether the problem was the form or the delivery. Find the account. Confirm the sending address still belongs to you. Then send yourself a test and watch it land.
Four mistakes we keep finding
Everything registered to one person’s personal account. Usually the founder, sometimes a board member, occasionally a nephew. It works perfectly until that person is unreachable, and then the organization has no standing to ask anyone for help.
The agency holds the domain “for convenience.” Some shops do this with no bad intent, as a service. It still means your single most valuable digital asset is in someone else’s name. Convenience is a fine reason to let a partner manage a domain. It is not a reason to let them own it.
Access granted by password sharing instead of by invitation. Nearly every service on this list can invite a separate user with its own credentials. Sharing one password instead is how access quietly outlives the relationship it came from.
No written record of what lives where. This is the mistake that converts all of the above from a nuisance into a project. The information exists, scattered across four inboxes and one person’s recollection, and reassembling it is the first and most expensive hour of any handover.
What a clean handover actually looks like
We think this is just plain dealing, and we set it up the same way on every build. Accounts in the organization’s name, with the organization’s billing details. One owner level login per service that the organization controls, plus individual accounts for everyone else who needs in. A one page record of which service holds the domain, which holds DNS, which holds hosting, and which delivers mail. Renewal dates on a calendar someone actually looks at.
None of that is technically difficult. It is just work that gets skipped when a project is racing to launch, and nobody misses it until the day it is the only thing standing between you and a decision you need to make.
Run the five checks. Write down what you find, including the gaps, especially the gaps. If the list comes back clean, you have lost an afternoon and gained something worth having, which is certainty. If two or three accounts come back as “we are not sure,” that is the real scope of your next web project, and it is better to know before you commission anything else.
Your next step
Bring your completed list to a scope conversation. Our services and pricing page sets out what a defined project includes, including the written scope and the clear handover of credentials at the end, and every engagement starts with a short conversation before any work begins. Send us the five answers and the gaps, and we will tell you plainly whether recovering access is a one hour job or the first phase of a larger one. If you would rather just ask the question first, get in touch and say “ownership check” so we know what you are after.