A new website arrives. It looks good on a phone. The colours belong to the business. Someone has finally removed the photograph of the office you left three years ago. Lovely. Now for the less glamorous question: if the person who built it becomes unavailable, can you still get in?
A website is more than the page people see. Behind it sit a domain name, hosting, email, a few business accounts, perhaps a booking tool and increasingly an AI assistant that can help change things. Each has its own access, bills and recovery arrangements. Paying one invoice does not tell you how those pieces are controlled.
You do not need to become your own IT department. You do need a clear answer to who holds the keys, what you can take with you and how the business keeps moving if something changes. This is a practical buying and handover checklist, rather than a demand that everyone learn to enjoy server administration. There are limits to a reasonable afternoon.
A timely nudge, rather than a new panic
The Australian Cyber Security Centre’s 1 October update calls this Cyber Security Action Month. Its 2026 message is to turn awareness into practical action, with steps including updates, backups and stronger account protection. It is a useful prompt to check the everyday arrangements behind your website, rather than simply share a cautionary graphic and continue guessing where the password lives.
The platform guidance points to the same practical issue from different directions. auDA explains how a .au registrant is recorded. Google distinguishes business-profile owners from managers, and Search Console owners from other users. These are existing administrative distinctions, not newly announced website rules. My view is that they belong in the buying conversation, alongside design, content and price.
First, know which key opens which door
The domain is the address. Hosting is where the site runs. Business email may be supplied elsewhere again. A Google Business Profile is a separate public listing, while Search Console reports information about Google Search. Being able to edit a sentence on the homepage does not establish control of those other services.
Ask for a short account map. It should name the service, its purpose, the business account holder, who manages it, how renewal is handled and where recovery information is kept. Keep the map somewhere the business can reach independently of the website. It should identify where secrets are stored securely, rather than become a spreadsheet full of passwords.
This is an administrative handover, not an invitation to change settings at random. The useful outcome is knowing who to contact and what you can recover. A clear map can be one page. A collection of screenshots with no explanation is usually just a more colourful mystery.
Check the domain record, not just the invoice
For .au names, auDA describes the registrant field as the legal name of the entity that registered the domain name. Its WHOIS guidance distinguishes that registrant from contacts and the registrar. The practical check is that the record reflects the intended business or eligible holder, rather than assuming that whoever paid the invoice must be recorded correctly. Other domain endings have their own arrangements; the .au guidance does not automatically apply to them.
auDA also says its domain-password recovery service sends information to the registrant contact email recorded in the registry. An out-of-date contact can therefore matter at an inconvenient moment. Ask the provider to explain the recorded contact and recovery route before there is a problem. Keep that contact current through the proper provider process.
Be precise about language. A .au domain is held under a licence. That is different from owning a piece of property forever. If the record needs correcting, the business is being sold or eligibility is unclear, use the registrar’s process and appropriate advice. Do not try an improvised transfer because a blog made it sound easy.
Give helpers access without giving away the whole business
Google Business Profile supports owners and managers using their own Google Accounts, so they do not need to share one password. Its guidance says a profile can have several owners but only one primary owner. An arrangement that lets someone maintain opening hours is not the same thing as making them the only person who controls the listing.
Search Console makes another distinction: a verified owner proves control with a verification method, while other access can be delegated. Google warns that removing a user alone may not remove their ability to verify ownership again if their verification tokens remain. That is a reason for a considered handover with the provider, rather than an enthusiastic round of deleting accounts.
My recommendation is to keep an appropriate business-controlled owner route and give each helper the access their work requires. Record the people and roles. Review them when the work or the relationship changes. A capable supplier should be able to explain the arrangement in plain English, including any platform restriction. Delegation should reduce your workload without making the business dependent on a single personal login.
A proper handover includes a way back in
The ACSC’s website guidance recommends multi-factor authentication for administrator accounts, appropriate access privileges, regular backups and attention to domain renewal. Those are useful foundations. They do not remove every risk, and a tidy checklist is not a security certification.
Add recovery to the demonstration. Can the authorised business owner reach the real sign-in page? Where does a legitimate password-reset email go? Who can help if the usual person is absent? Agree how recovery material is protected and who can use it. Do not run a surprise lockout test on the live system while customers are trying to book.
A backup also needs an explanation. What is included: pages, photographs, database records, configuration, or only some of those? Who keeps it, how current is it and who can restore it? Ask for evidence of a safe restore exercise or an agreed way to test one. A file called final-final-backup is a promising name, but it is not much of a recovery plan.
Managed does not have to mean trapped
There is nothing inherently wrong with paying someone to host and maintain the site. There is also nothing inherently virtuous about being handed a pile of code you cannot use. The useful question is whether the arrangement is clear, proportionate and workable for your business.
A managed platform may be an excellent fit. A custom build may offer the flexibility you need. Neither label answers what can be moved. Ask what happens to your domain, content, original artwork, enquiry records and other business information if you leave. Some platform features may need rebuilding elsewhere; some purchased assets have licensing limits. Have those boundaries explained before treating every export as a complete portable website.
Get the practical exit terms in writing: what is supplied, in what form, any agreed notice or handover charge, and the work required to move. Clarify rights to commissioned work and third-party materials in the agreement; this article cannot determine them for a particular contract. A straightforward relationship should not depend on either party remembering an optimistic phone conversation from last spring.
You can hand over the technical work without handing away your ability to leave.
An AI editing window needs its own sensible boundaries
An assistant that helps draft website changes can be useful. The design question is what happens after the chat. Can you see the proposed change? Is the conversation retained appropriately? Does an authorised person review the result? Is there a way to recover the previous version? Those questions are more useful than whether the chat bubble looks reassuringly clever.
For a small-business editing tool, my preferred starting point is narrow: help with agreed content, show a preview and keep a clear route to review and recovery. Changing a heading and changing who can access the hosting account deserve different controls. An assistant should not acquire billing, domain or account-management powers simply because it can help write a service description.
That is a design recommendation, not a claim that every chatbot supplies these controls. Ask for a demonstration of the actual product. Keep credentials and private customer information out of casual prompts, and agree who can see saved conversations. Useful assistance should make responsibility clearer, rather than move it into a very confident paragraph.
A fictional handover: the cafe that wants to change its hours
Imagine a cafe with a small website, a booking link and active social pages. This is a hypothetical example, not a client story. The owner wants to adjust summer hours without rebuilding the internet. A good handover would show the agreed editing route, explain whether the booking provider has separate hours, and identify who updates the Google listing.
It would also explain what the owner cannot change through that editing screen. If a booking service has its own account, updating the website’s text may not update that service. If a social post contains an old screenshot, it will not correct itself because the homepage has changed. A small account map and one worked example make those boundaries understandable.
The lesson is not that the owner should do every task. It is that the business should know which task it is asking for, who can carry it out and how to continue if the usual helper is unavailable. That is a calmer form of independence than pretending nobody will ever need support.
Seven questions to put beside the quote
Use these before a new build, at renewal or when reviewing an existing arrangement. You do not need perfect answers on the spot. You need a shared understanding and a short list of gaps to resolve before they turn into an urgent Friday afternoon.
- Which entity is recorded for the domain, and which business-controlled contact receives renewal and recovery messages?
- Which accounts are ours, which are managed for us, and who has owner or administrator access?
- What can we change ourselves, and can you demonstrate that route with a harmless example?
- How do sign-in recovery, staff changes and provider changes work without sharing one master password?
- What is backed up, who can restore it, and what evidence shows that recovery works?
- If we leave, what content, files and records can move, and what fees, licences or rebuilding limits apply?
- If an AI assistant is involved, what can it change, what needs review and where can we undo a mistake?
The useful next step is small
Ask the person who looks after your website for the account map and one calm handover conversation. Start with the domain contact, the owner’s sign-in route and a clear description of the backups. Resolve one gap at a time through the proper provider process. Do not respond by changing every password, moving the domain and cancelling hosting on the same afternoon.
At Quietly Better, I want the conversation about a website to include how the business will use it after launch. The visual work matters. So does being able to update a useful detail, get help and understand the arrangement. You should be able to choose ongoing care because it helps, with the practical terms made clear before work is agreed.
A better website is not only the one that makes a good first impression. It is one the business can understand well enough to keep using. The front door should look considered. The keys should not be a mystery.
Sources and further reading
Platform statements are linked to primary sources. The practical examples, recommendations and interpretation are Richard's analysis; they are not promises of reach, rankings or sales.
- ACSC — Take a second to stay secure this Cyber Security Action MonthPublished 1 October 2026; checked 26 October. Current news context, not a new mandatory website standard.
- auDA — How to use the .au WHOIS toolChecked 26 October 2026. Explains registrant, contact and registrar fields for .au names; other endings have different arrangements.
- auDA — Additional .au domain servicesChecked 26 October 2026. Domain recovery information is sent to the recorded registrant contact email.
- Google — Manage Business Profile owners and managersChecked 26 October 2026. Individual Google Accounts, owner/manager roles and one primary owner.
- Google — Managing Search Console owners, users and permissionsChecked 26 October 2026. Verified/delegated owners and verification-token considerations during removal.
- ACSC — Secure your websiteChecked 26 October 2026. Administrator MFA, least-necessary access, renewal, updates and backups.


