Website Handover When Staff Leave: Keeping the Know-How

A website handover when staff leave is the process of moving every login, renewal and editing routine from the departing person to the business before they go. Without it the site usually keeps running for a while, then fails when a domain lapses, an account locks or nobody remembers how to publish a change.

• Registrars must send renewal reminders about one month and one week before a domain expires, and may cut its website and email for up to 8 days before deletion.
• Google Business Profile makes new owners and managers wait 7 days before they can transfer primary ownership or remove other users.
• A Business Profile has only 1 primary owner, who cannot remove themselves until primary ownership has been transferred to someone else.
• Removing a Search Console owner does not delete their verification token, so a removed owner can re-verify until the token is taken off the site.

What happens to a website when its manager leaves?

Usually nothing at first: the site stays online and looks fine. Problems surface later, when a renewal, a login or an edit needs knowledge that left with the person.

The delay is what makes this risky. A website runs on a set of accounts and renewals that rarely need attention, so the gap stays hidden for months. Then a renewal reminder goes to a closed mailbox, a password reset goes to a personal phone, or a manager asks for a new page and nobody knows where the editor is. By that point the person who knew the answers may be hard to reach.

The most serious failure is a lapsed domain. ICANN's expiry rules mean registrars send reminders before expiry and may interrupt the domain's service for up to 8 days before deleting it, which takes the website and any email on that domain offline. If the reminders went to someone who has left, the first sign may be customers saying your site is down. A deleted name can usually still be restored by the registrant during a 30-day redemption period, but recovery is slower and the registrar may charge a fee to help.

Why does website know-how disappear when people leave?

Website know-how disappears because it lives in one person's head, inbox and password manager rather than in the business's own records. Nobody writes it down while things are working.

The person who set the site up often did so under their own email address, paid with a card they controlled and learned its quirks by trial and error. Each choice was sensible at the time. Together they mean the business depends on one individual for things it legally and commercially owns. This is especially common when a site was built by a contractor or a keen employee years ago and has run quietly since.

The other loss is process knowledge: how to add a page, which sections to reuse, what the services are officially called and who signs off a change. Traditional sites built with custom code make this worse, because the next person has to reverse-engineer how things fit together. A platform where editing happens in the same visible way for everyone reduces the problem, since the process is in the tool rather than in a person's memory. It still helps to write the routine down, because tools do not record who decides what.

Which accounts does a website depend on?

A website typically depends on a domain registrar, a hosting or website builder account, email on the domain, Google accounts and any payment providers. Each needs a business-controlled owner.

Start with the domain registrar, because the domain is the address everything else points to. Next comes the account where the site is hosted or built, which holds the pages and the publishing controls. Email on your domain may sit with the registrar, the host or a separate provider, and it often handles password resets for everything else. Google Search Console and Google Business Profile control how your business appears in search and on maps.

If the site sells or takes bookings, payment accounts matter too. In AI Web Maker, for example, a Store Manager takes online payments through the shop's own Stripe or PayPal account, and a Booking Manager lets visitors request bookings that the owner confirms. Those payment accounts, and the email addresses that receive order and booking notifications, must belong to the business. Add any analytics, social media and directory accounts that link to the site, then record who holds each one.

What should a website handover checklist include?

A handover checklist should cover ownership of every account, renewal dates, recovery details and the editing routine. Work through it before the person's last day, with them present.

The most useful checklists are short enough to complete in a single sitting and specific enough that nothing is left to memory. Do the transfers while the departing person can still approve them, because many services require the current owner to add the new one. Confirm each step by having the new owner sign in, not just by noting that access was granted. Keep the completed checklist with your business records so the next handover starts from it.

1. Domain: registrar name, account login moved to a business email, registrant contact details updated, renewal date and payment card confirmed.
2. Website platform: business owner added with full access, the departing person's access removed after the handover, billing moved to a business card.
3. Email on the domain: admin access moved, the departing person's mailbox forwarded or kept for a set period, recovery phone and email updated.
4. Google accounts: a business owner added to Search Console and Google Business Profile, primary ownership transferred, old verification tokens removed.
5. Payments and tools: Stripe or PayPal, analytics, social and directory accounts listed with owners, and notification emails redirected.
6. Editing routine: how to add and publish a page, which sections to reuse, the style guide and who approves changes.

How do you hand over the domain and hosting safely?

Move the registrar and hosting logins to an email address the business controls, update the registrant contact details and confirm the renewal date and payment method. Do it before the person leaves.

Use a role address such as one for web or admin rather than another individual's personal inbox. That way renewal reminders reach the business whoever is employed, and a future handover becomes a matter of changing who reads that inbox. Check the registrant contact details with the registrar as well as the account login, since the reminders required by ICANN go to the contact on record. Turn on automatic renewal where the registrar offers it, and make sure the card on file belongs to the business and will not expire soon.

Hosting follows the same pattern. On AI Web Maker, going live is $119 a year of hosting with the domain paid separately, so both the hosting plan and the domain have their own renewal to track. Put both dates in a shared business calendar with a reminder well ahead of each. If the departing person paid personally, arrange for the business to take over billing before their card is withdrawn.

How do you hand over Google Search Console and Business Profile?

Add a business-controlled owner to each, transfer primary ownership in Business Profile and remove the departing person's access and verification tokens. Allow for Google's waiting periods.

In Search Console, an owner has full control while full and restricted users can only view and act on data. Google's help explains that verified owners prove ownership with a token placed on the site, and that removing an owner does not delete that token. Check the list of unused ownership tokens and remove the departing person's, taking care not to remove tokens other services rely on. If the only verified owner has already left, the business should verify ownership again to keep or regain access.

Google Business Profile allows several owners but only one primary owner, and the primary owner cannot remove themselves until they have handed that role to someone else. New owners and managers also wait 7 days before they can transfer primary ownership or remove other users. Start this part of the handover at least a week before the person's last day, so they are still around to complete it. Once the new primary owner is confirmed, remove the departing person from the profile.

How do you keep the editing process from being lost?

Write a one-page routine for publishing changes, keep the style guide with it and use a platform where editing works the same way for everyone. The goal is that a new colleague can publish a correct page without a tutorial from the old one.

The routine should say where to sign in, how to duplicate an existing page, which sections to use, how to name pages and who approves changes before they go live. Keep it next to the style guide that lists your service names, tone and main call to action. Ask the departing person to walk a colleague through one real edit using the document, and fix any step that confused them. A document tested this way is far more useful than one written from memory.

The platform matters as much as the paperwork. A builder that holds the design and lets people edit in sections removes much of the hidden knowledge that custom code creates. AI Web Maker builds a complete website from a description of your business, with pages, sections, text and photos that you then edit, so the next person works in the same visible editor rather than in files. This is the same principle behind any plan to maintain a website without a developer: keep the know-how in tools and short documents, not in one person.

What if the person has already left without a handover?

Start with the domain, then the website platform, then Google accounts, using each provider's account recovery and proof that the business owns the asset. Contact the former employee politely as well, since they may still be able to help.

Find out which registrar holds the domain and when it expires, because that deadline sets your timetable. If the registrant email belongs to the former employee, ask the registrar what proof of ownership they need to change it. For Search Console, verify ownership afresh with a new token so you are not relying on the old owner. For the website platform and payment accounts, contact each provider's support with business documents showing you are entitled to the account.

Once access is back, complete the checklist as if it were a normal handover, and change any shared passwords the former employee knew. Then fix the cause by moving every account to a role address and putting renewals in the shared calendar. The aim is that the next departure, planned or not, causes no disruption at all. For a quick check of the site's titles, descriptions and on-page basics after the change, the AI website SEO checker gives a starting list.

Questions owners ask about website handovers

Who should own the website accounts?

The business should, through an email address it controls rather than an individual's personal inbox. Named staff can be added as users with the access they need. That way people come and go without the business losing control.

How long before someone leaves should the handover start?

Start at least a week before their last day, and earlier if they hold the only access to key accounts. Google Business Profile alone imposes a 7-day wait before new owners can take over primary ownership. Leave time to test every login.

What is the biggest risk if nobody takes over?

A lapsed domain, because it takes the website and any email on that domain offline. Renewal reminders go to the contact on record, which may be the person who left. Check the registrant details and renewal date first.

Should we change passwords after someone leaves?

Yes, change any shared passwords and remove their personal access from every account. Also remove their Search Console verification token, since removing the owner alone does not. Do it on their last day, after the handover is confirmed.

A handover plan that outlasts any one person

Every website should be able to survive the departure of the person who knows it best. That comes from three habits: accounts owned by the business, renewals in a shared calendar and an editing routine written down and tested.

Run the checklist once now, even if nobody is leaving, because it will reveal accounts held by the wrong person and dates nobody is watching. Repeat it whenever someone with website access changes role or leaves. With those habits in place, a departure becomes an administrative task rather than a crisis, and the site keeps serving customers throughout.