Most church websites are written for the people who already come.

The visitor looking you up on a Saturday night has a different set of questions than the member checking Wednesday's schedule, and the visitor rarely gets answered. We build church sites that serve both, keep the service times from going stale, and hand the whole thing over in a way that survives the volunteer who built the last one moving away.

We are in East Canton and we work with churches and nonprofits across Northeast Ohio, using the same web design process as our commercial work.

Two people use your website, and they want opposite things

The member, on a Wednesday

What time is youth group, is the potluck still on, who do I email about the nursery schedule, where is the bulletin.

A calendar that someone on staff can actually update, a bulletin or announcements page, and a short staff and ministry contact list. This audience forgives a plain design and does not forgive stale information.

The first-time visitor, on a Saturday night

What time is the service, what do people wear, where do I park, what happens to my kids, how long does it last, will anyone make me stand up.

A plan-your-visit page that answers all of it without theology first. This is the page most church sites do not have, and it is the only one that turns a search into someone walking through the door.

The plan-your-visit page, in full

Six things. Most church sites have one or two of them, scattered. Put all six on one page and link to it from every screen.

  1. 01

    Service times, in text, on the homepage

    Not in an image, not in a PDF bulletin. If you have multiple services or a summer schedule, list both and say which one is running now.

  2. 02

    Where to park and which door to use

    Photos of the entrance from the parking lot. Old buildings are confusing and nobody wants to walk into the wrong door on their first Sunday.

  3. 03

    What people wear

    Say it plainly. Jeans are fine, or people dress up, or both happen. This is the single most searched question about visiting a church and almost nobody answers it.

  4. 04

    What happens with kids

    Where check-in is, what ages are separated, what your background check policy is for volunteers. Parents will not visit without knowing.

  5. 05

    How long the service runs

    Sixty minutes, ninety minutes. People planning around a nap schedule or a shift need the number.

  6. 06

    What will not happen to them

    Nobody will single you out, there is no expectation you give, you can leave. Saying it removes the actual fear.

Sermons, streaming, and where the files should live

Do not host video on the church website

Video is the fastest way to make a small site slow and expensive. Post it to a video platform or your streaming service and embed it. The sermon plays the same and the site stays fast.

Audio archives are worth keeping

A sermon page with the date, the passage, and the speaker is content people search for, and it is the part of the site that quietly earns visits all week.

Podcast feeds cost nothing to add

If you already record audio, publishing a feed puts your sermons where people already listen without giving anyone another app to open.

Write a real title and a short summary

Sermon 04-13 is not a title. The passage and the subject make the archive useful and findable.

Giving belongs to the church, not to the web guy

We do not touch offerings. The giving platform is the church's decision and the money goes directly to it. Our job is to make the button obvious to the people looking for it and invisible to the visitor who is not ready.

  • We link to the giving platform your church already uses rather than handling money on the website.
  • The giving page says what the options are: online, text, in person, by mail, and what a recurring gift means.
  • Designated funds are named, so someone giving to a building fund knows it went where they intended.
  • Nothing about giving appears before the visitor information. Ask after you have been useful.

Questions from church staff and boards

Our website is run by a volunteer who is leaving. What happens?

This is the most common reason a church calls us. We take over the hosting and the domain, document where everything lives, and set the site up so a staff member can make ordinary updates without touching code. If the volunteer built something custom that only they understood, we will tell you honestly whether it is worth keeping or rebuilding.

Do we need a members-only area?

Usually not. Almost everything churches want to gate is either public anyway or belongs in your church management system, which already handles directories, giving records, and small group rosters better than a website login will. A login on a church site is one more thing to maintain and one more thing to lock people out of.

Can we take online giving through the site?

We connect the giving platform you have chosen so the button lives on your page and the transaction happens with your provider. We do not process donations ourselves and we do not take a cut of anything. If you have not picked a provider yet, we will explain the trade-offs and let the church decide.

Who updates the service times when they change?

Whoever you want. We build the site so times, events, and announcements are edited in one place by a staff member or volunteer with no technical background. If you would rather send us the change, we can handle updates as part of an ongoing plan.

What does a church website cost?

Builds start at $500 and are quoted per project. Hosting starts at $15 a month, which covers the SSL certificate, backups, and WordPress updates. Tell us the budget you have and we will tell you what fits inside it rather than quoting a package you cannot carry.

Send us the site and the budget

We would rather fix the three things that matter than sell a church a package it cannot maintain. Tell us what you have and what you can spend.