Hire a website maintenance service when updates are being skipped, and keep ownership of the accounts while you do it. People ask when do you need a website maintenance service once they are the only person willing to click update, and they have stopped clicking. A firm that will not share access is not maintaining your site. You will know what access to keep in the business's name.
Takeaways
- Hire when updates sit unrun because nobody wants to be the person who clicks.
- Hand off the updates and the small edits, and keep an owner login for every account that controls the site.
- Refuse a firm that will only work if the business does not hold the login. That is custody, not maintenance.
- The order is initial contact, then a detailed discussion, then implementation. It is not an uptime promise.
Hire When Updates Are Being Skipped
The signal is simple. There is an update, and the only person who might run it is you, and you are not going to. The reasons feel practical: the last update broke a page, you do not know what the plugin does, the host's screen is unfamiliar. The result is the same. The site is drifting into a condition that is harder to repair. That is when a maintenance service is the right hire, not when you want a badge.
Website Maintenance covers updates, backups, and the small edits that keep a site from quietly rotting. If you only buy the edits, the software still sits. If you only buy the updates, the sentences still lie. Hire for the set. A service that will click update and will not change a retired offer has sold you half the habit. A service that will change sentences and will not touch the software has sold you the other half.
You do not need to wait for an outage. Skipped updates are already the trouble. A site that cannot be updated is already in trouble, even while it still loads. The hire is how you stop being the single reluctant click. It is not how you outsource worry in the abstract. If the updates are current and the edits are happening, you may not need anyone. If they are not, you do.
Keep Ownership of the Accounts
Hand off the work without handing off the ownership. The business should be able to log in as an owner to every account that can take the site away, change where the name points, or lock you out of the editor. A maintainer needs access to do the updates. They do not need to be the only owner. A firm that will not share access is not maintaining your site. They are holding it.
This is the lesson people learn when a freelancer disappears. The updates were happening, until they were not, and the login left with the person. Hire the next firm with the opposite arrangement from the start. You hold the owner role. They have a login of their own, which you can remove. If they need a moment of deeper access, it is temporary and it ends with you still inside.
Say this in the first conversation, before any work starts. A surprised vendor is better than a locked account. If their process "requires" that clients not hold admin, their process is the problem. Plenty of careful people can update a site they do not solely own. The ones who cannot are telling you that control matters more to them than the habit you came to buy.
Access That Stays in the Business's Name
"In the business's name" means the recovery path does not depend on a vendor's goodwill. The email address on the account should be one the business controls. The owner user should be one you can still use if the relationship ends on a bad day. Shared passwords written on a single person's laptop are not this. An owner role, in an inbox the company keeps, is.
You will know what access to keep in the business's name if you ask one rude question: if we part ways tomorrow, what can we still open? The list of things you can still open is the list that was actually yours. Everything else was borrowed. Maintenance should add to the first list, not to the second. A vendor login is fine on the second list. Your ownership is the first.
Ask them to show you the owner screen, not a promise in a proposal. Log in yourself during the conversation if you can. A screenshot they email later is weaker than a login you just used. If you cannot get in, the first task of the engagement is recovery of access, before any update. Updating a site you cannot enter is how the dependency deepens.
Keep a second person in the business who knows where these logins live. Sole ownership by you is better than sole ownership by a vendor, and it is still a single point of forgetting. Maintenance includes the accounts staying findable when you are away. A password safe the company controls is enough. A memory is not.
What a Firm Should Not Hold Alone
There are pieces a firm should never hold alone, even if holding them would make their job easier. The domain registration. The host account. The owner role in the editor. The billing identity that, if it lapsed, would take the site down with their credit relationship rather than yours. Convenience is not a reason. You can give them the ability to act without giving them the ability to disappear with the keys.
They should also not hold the only copy of the backup. A backup that lives only in their account is not a backup you could restore if they are gone. Ask where a copy can sit that you can reach. You do not need to become the person who runs restores. You need to not be stranded. A firm confident in its work will not fear you having a copy.
Be wary of a setup that adds their own license, their own builder, or their own host as the only way the site runs, without saying what happens at the end. That can be a legitimate platform. It can also be a lock. Ask the end in plain words before implementation. If leaving means rebuilding because they will not export, you should hear that while the decision is still cheap.
None of this requires distrust as a personality. It requires the same clarity you would want for a door key. The people who maintain the place need a key. The owner of the place needs a key too. A service that argues with that picture is maintaining its own position, not your site.
| Account | Keep in the business's name | A vendor may have |
|---|---|---|
| Editor or admin | An owner user on an inbox you control | Their own user, which you can remove |
| Host | The account and its recovery email | Access to do the work, not the only ownership |
| Domain registration | The registration and its recovery details | A login to help, without being the sole owner |
| Backups | A copy you could reach if they left | The working copy they use for updates |
The Login You Must Not Lose
If you are the only person willing to click update, you are also at risk of being the only person who knows the password. Hiring does not fix that if the password stays a secret you might forget and they might monopolize. Move the secret into a place the business owns as part of the handoff. Do it before they run the first update, so the habit starts from a login you have already seen.
Watch them work once. Not to grade their clicking, but to see that an update is a sequence you could recognize: backup, update, look at the pages that matter. A service that will not show you is asking for faith. Faith is a weak operating plan. A short demonstration is enough to make the later months boring, which is what you wanted.
Small edits belong in the same handoff. Tell them how you will send a sentence that became untrue, and who on your side is allowed to ask. If every edit needs you personally, you have remained the bottleneck in a different chair. Pick a second person. The service should accept their word on ordinary corrections and refuse only the changes that are really new projects.
How the Handoff Should Work
Use initial contact, then a detailed discussion, then implementation. The order keeps access from being an afterthought. It is not a promise of uptime, of a particular response on a bad day, or of traffic. It is how you confirm they will share the keys before they start clicking.
Initial contact is the skipped update and the login question. You tell them what you are afraid to run. You ask whether the business will keep owner access. Their answer is the fit test. A detailed discussion is optional only if that answer is already a refusal. You can end the conversation there, politely, and keep looking.
The detailed discussion lists the accounts, the backup, the small edits you already know about, and what is out of scope. Implementation then runs one update with you able to log in, documents the restore in words you understand, and corrects the stale sentences you brought. You should leave with the owner role still working. If implementation ends with you locked out and them "set up," the handoff failed in the only way that matters.
Bring this to the first conversation:
- The update you have been skipping, and what happened the last time one ran.
- The accounts you know about: editor, host, and domain registration.
- Whether you can log in as an owner today, and which inbox recovers the account.
- The stale sentences you already want changed.
- The name of a second person in the business who should be able to request an ordinary edit.
Questions
Do You Need Help If You Are Simply Busy?
You need help if busyness has turned into skipped updates or sentences you know are false. Being busy while the list still gets done is not the same problem. Hire when the click is being avoided. Do not hire a logo because the calendar feels full and the site is actually current.
Should the Vendor Hold the Only Admin Login?
They should have their own access, and the business should keep an owner login it can use if the relationship ends. A firm that will not share that access is not maintaining your site. It is holding it, so make the split a condition before any update runs.
Which Accounts Should Stay in the Business's Name?
The editor, the host, and the domain registration, plus a backup you could reach without them. Recovery email addresses should be ones the business controls. A vendor login can sit beside those. It should not replace them, and it should not be the only key to the billing that keeps the site online.
What Order Should the Handoff Follow?
Initial contact, then a detailed discussion, then implementation. Contact tests whether they will share owner access, the discussion lists accounts, backups, and edits, and implementation runs an update you can still log in after. The order is not a promise about uptime.
How Do You Know the Service Is Real After a Month?
An update happened, you can still log in as an owner, and a small edit you sent is visible on the page. A note that says everything is fine, without those three, is a footer logo in email form. Ask to see the list. You hired the habit, not the reassurance.
Conclusion
Hire when updates are being skipped, and keep ownership of the accounts. A firm that will not share access is not maintaining your site. You will know what to keep in the business's name: the owner logins, and a backup you could still reach.
If you want help handing off the updates and the small edits without losing the login, Speak With Us.
