Church Digital

For churches · Lost access

Your church web volunteer left. Here is how to get your website back.

Recovery steps · domain ownership · prevention

It is one of the most common ways a church loses its website: the person who built it moved, got busy, or passed away, and the domain, the hosting and the login were all in their name. Here is the order to work in.

Step one

Find out who owns the domain

The domain (yourchurch.org) is the one asset that matters most, because everything else can be rebuilt behind it. Look it up on any public WHOIS lookup tool: the registrar (GoDaddy, Namecheap, Google Domains, Squarespace Domains) is usually visible even when the owner's name is private.

If the registrant email is the church's, you can recover the account through the registrar's standard password reset. If it is the volunteer's personal email, contact them first; most registrars will also transfer a domain to an organization with proof of the church's legal name, but it is slower. Check the renewal date while you are there. An expired domain can be bought by anyone.

Step two

Recover the site and the hosting

  • Identify the platform

    The site footer usually says it: "Powered by The Church Co," "Made with Squarespace," a WordPress login at /wp-admin. Each platform has an account-recovery path that starts with the billing email.

  • Follow the money

    Whoever pays the bill can recover the account. Check the church's card statements for the monthly or annual charge; the vendor name tells you where the account lives.

  • Export everything you can

    Once in, export the pages, the sermons and any form data before changing anything. If the account cannot be recovered, save the public pages by hand: the copy and photos are what you will rebuild from.

  • Check the other accounts too

    Google Business Profile, Google Analytics, the giving platform, Facebook admin, the church email. They are usually in the same person's name.

Step three

Make sure it never happens again

  • Church-owned accounts

    Domain, hosting, and site login on a church email address (office@ or web@), with the password in a place two people can reach.

  • A second admin on everything

    Every platform allows more than one administrator. Add the pastor or the office manager to each one today.

  • Decide who owns the website

    A named person, or a company. A site nobody owns goes stale within a year and gets lost within five.

  • Consider taking the risk off a volunteer entirely

    This is the situation Church Digital is built for: we run the site, hosting and updates for $120 a month flat, no setup fee, no contract, and the founding rate makes the first 6 months $60 a month. Your domain stays in your account, and when a volunteer leaves, nothing changes.

Common questions

Questions churches ask

Our web volunteer left and we have no logins. What do we do first?
Find the domain registrar with a WHOIS lookup and confirm the domain is not about to expire. Then identify the site platform from the footer and recover that account through its billing email. Export your content before you change anything.
How do we find out who owns our church domain?
Use any public WHOIS lookup: it shows the registrar and, unless privacy is on, the registrant. If the registrant is a former volunteer, ask them to transfer it; if they cannot be reached, registrars can transfer to an organization with proof of the church's legal name.
Can we just start a new website on a new domain?
You can, but you lose the Google history attached to the old domain and every link pointing to it. Recover the old domain if there is any way to; a new site can live on it.
How do we stop this from happening again?
Church-owned accounts for the domain, hosting and site, two administrators on each, and a clear owner for the website. Or move the site to a service that runs it for you so no single volunteer is the point of failure.

In this situation right now

Send the site address and we will tell you what shape it is in

A free five-minute walkthrough of the homepage as it stands, plus a straight read on whether to recover and refresh it or rebuild. No pitch, no call required.

Go deeper

Related reading