Why this matters
Scrap and start over only when the foundation is broken: the site does not load on a phone, is not on HTTPS, or the person who built it is gone and no one can log in. Everything else, wrong photos, an old service time, a give button no one can find, is a fix, not a rebuild. Running this check first saves you from paying for a full redesign that changes the paint but leaves the same problems for a first-time guest.
Most church sites we look at do not need to start over. When you rebuild without diagnosing first, you spend months and a real chunk of the budget rebuilding the parts that already worked, and the parts that were actually broken often come back in the new build too.
At a glance
- A rebuild is worth it only when the foundation is broken; most sites need three or four targeted fixes instead.
- Run the six-step check in about an hour, on your own phone, before you call anyone.
- Score five areas out of five. A low total means fix in place; a foundation failure means rebuild.
- The most common wasted rebuild replaces a site that just needed a current service time and a visible give button.
The framework: a six-step rebuild-or-fix diagnosis
Run these in order. Use your phone, not your office computer, because that is how most first-time guests arrive.
1) Phone load check (10 minutes)
Open the homepage on your phone over cell data, not office wifi. If it does not load in a few seconds, or the text is tiny and you have to pinch to read, note it. As of 2026, 93.4% of small church websites have a mobile viewport tag, per our 2026 State of Small Church Websites study, an audit of 2,000 church websites. If yours is in the small group without one, that is a real foundation issue.
2) Security and access check (10 minutes)
Look for the padlock and "https" in the address bar. Our 2026 study found 94.3% of small church sites serve over HTTPS, so a missing padlock puts you in the failing minority. Then confirm someone on your team can actually log in and edit. A site no one can access is a rebuild whether you like it or not.
3) First-time guest facts check (10 minutes)
Can a stranger find your service times, your address, and what to expect in under 30 seconds? Service times are findable on 83.9% of small church sites in our 2026 study, so this is table stakes. If the basics are buried or wrong, that is content, and content is a fix.
4) Give path check (5 minutes)
Try to give a dollar as if you were a guest. If you cannot find the button or the link is broken, flag it. Only 64.2% of small church sites have a working online giving path in our 2026 study. A broken give path is almost always a fix, not a reason to rebuild.
5) Freshness check (10 minutes)
Look for anything that dates the site: last year's Christmas banner, a staff member who left, an event from two summers ago. Stale content makes a live church look closed. This is editing, not rebuilding.
6) Who can maintain it check (5 minutes)
Ask honestly: can your volunteer keep this updated, or does every change require an outside developer and a wait? If the platform fights the person who maintains it, that is the one content-side reason a rebuild can pay off.
Scoring worksheet
- Phone load and mobile readability: 0 to 5
- Security and edit access: 0 to 5
- Guest facts (times, address, what to expect): 0 to 5
- Give path works: 0 to 5
- Freshness and maintainability: 0 to 5
Score each area honestly. If security and edit access or phone load scores a 0 or 1, that is a foundation failure and a rebuild is on the table. If those two pass but your total is low elsewhere, fix in place first; you will get most of the benefit for a fraction of the cost.
This week action plan
- Day 1: Run all six checks on your phone and write down the score.
- Day 2: Fix the give path and update service times if either failed.
- Day 3: Remove stale banners and departed staff.
- Day 4: Confirm at least two people can log in and edit.
- Day 5: If foundation checks failed, price a rebuild; if not, close the ticket.
Common mistakes
- Rebuilding to fix content problems that a 20-minute edit would solve.
- Judging the site on the office desktop instead of a phone on cell data.
- Starting over without confirming the old site's broken parts won't return in the new one.
Frequently asked questions
Is a rebuild worth it for a small church?
A rebuild is worth it when the foundation is broken: no HTTPS, no mobile support, or no one who can log in to edit. If those pass and the problems are outdated content or a hidden give button, a fix costs far less and lands the same result for a first-time guest.
What is the best church website builder to start over on?
There is no single best church website builder; the right one is whichever your volunteer can actually keep updated without waiting on a developer. The median visible platform spend for small churches was $16/mo software-only in our 2026 study, so you do not need an expensive platform to have a working site.
How do I know if my church website is just outdated versus truly broken?
Outdated is a stale banner, a wrong service time, or a departed staff member; those are edits. Truly broken is a site that will not load on a phone, is not secure, or that no one can access to change. Run the six-step check above and the difference becomes obvious.
Where this connects in our work
- A homepage review for a second set of eyes on whether yours needs a rebuild or a fix.
- Our 2026 research for the numbers behind what most small church sites get right and wrong.
- Examples for what a working first-time-guest homepage looks like.
Next step
Run the six-step check this week, then decide.