Does Your Church Website Say What You Believe?

Short answer first: if a visitor can’t find your statement of beliefs in two clicks and read it on their phone, your website isn’t saying it. It might be written down somewhere. That is not the same as being said.

This page is about finding and reading. It is not about what your church should believe or what the statement should say. That belongs to your pastor and your church, and I stay out of it.

Why does this matter before anyone visits?

Most people check a church’s website before they ever drive over. They are looking for service times, where to park, and what kind of church this is.

The “what kind of church” part is the one a lot of sites leave to guesswork. A visitor who can’t find what you teach has to either guess, call, or skip you. Most won’t call.

A clear, findable statement of beliefs does something quiet and useful. It lets a person who agrees with you feel at home before they arrive. It also lets a person who doesn’t agree find that out kindly, on their own time, with no awkward conversation at the door.

The three ways it goes wrong

I see the same three problems again and again, on sites of every size:

• It’s hidden. It exists, but only on a page you reach by clicking through three menus, or only inside a long “About Us” page with no heading.
• It’s locked in a file or a picture. A PDF that downloads slowly, or a photo of a printed page. On a phone it is tiny, can’t be searched, and a screen reader can’t read it aloud.
• It’s written for insiders. Fine for members, but a first-time visitor hits unexplained terms and gives up. (What the words are is your church’s call. Whether a newcomer can read the page without help is a website question.)

The two-minute check: run it on your own site

Use your phone, because that is what most visitors use.

• 1. Start on your homepage. Pretend you’ve never heard of your church.
• 2. Find your statement of beliefs in two taps or fewer. Look at the menu and the footer. If you have to guess which menu it’s under, a visitor will too.
• 3. Check that it’s real text on the page, not a PDF or a photo. Try pinching to zoom. Text should reflow and stay readable.
• 4. Read the first paragraph out loud. Would a first-time visitor understand it, or would they need someone to translate?
• 5. Check the page title. The browser tab or search result should say something plain like “What We Believe,” not “Page 7.”
• 6. Search for it. Type your church name and “beliefs” into Google. Does your own page come up?

If you got through all six without frustration, you pass. If you got stuck on any, that is the thing to fix, and it is usually a small fix.

What does good look like?

• One clear link in the main menu or footer, labeled in plain words.
• Real text on its own page, with a heading, short paragraphs and room to breathe.
• Easy on a phone, with no pinching and no sideways scrolling.
• Nothing that expires. If it mentions a date or a name that changes, someone owns keeping it current.

Notice what’s not on that list: any opinion about the content. That is yours.

Who should own it?

Somebody on your team should be named as the person who keeps this page current, even if that is one volunteer or the pastor’s assistant. A statement that hasn’t been looked at in years can quietly drift away from what your church actually says out loud on Sunday.

What this check does not tell you

• It doesn’t judge the statement itself. I’m checking whether people can find and read it, not whether it’s right.
• It isn’t a full accessibility review. Readers who use screen readers or need larger text deserve their own check.
• It doesn’t guarantee more visitors. It removes one reason for a newcomer to leave.

How I run this on church sites

This is the check I run on every church site I build, before I hand it over.

Your turn: pull out your phone, start at your homepage, and see how long it takes you to find what your church believes.