Church life

A website for a church that has none

Grantkeeper builds and looks after a small site for you: service times, how to visit, ministries and contact, in English and Spanish if you need both.

What you send: Service times, address, parking and entrance, children's care, accessibility, languages, contact details, and a domain name if you have one.
What you send
What you get: A small site with Home, Plan a visit, Ministries and Contact pages, checked on phone and computer screens, with screenshots for you before anything is public.
What you get

Fictional example.

Text it like this

Fictional example.

You: We don't have a website. Make a simple one: Sunday 9 and 11, Spanish service at 1, 210 Church St, parking behind the hall, nursery at 11.
Grantkeeper: Draft site ready: Home, Plan a visit, Ministries and Contact, in your maroon and cream. Checked on a phone and a computer; screenshots are on your private page. Blanks: the pastor's name and an email. Want it live once those are in?

What the site includes

Four pages most visitors look for: a home page with service times and the address up top, a plan-a-visit page with parking, the entrance, children's care and accessibility, a ministries or programs page, and a contact page with a phone, an email and a map link. Each page can have a Spanish version with the same times and details.

Everything comes from what you send and your Business Brief. Anything missing stays as a visible blank until you fill it. The design uses your colors, lettering and a clean layout; photos cannot be placed on the site yet, though a captioned video made from your photos can be.

Preview, check, then live

Grantkeeper builds the site in its own work area, then checks it the way a visitor would: phone and computer screenshots, menus that open, buttons that go somewhere, nothing that scrolls sideways. You see the screenshots or a private preview first. Putting a version online takes a one-time code you text back, tied to that exact version, and a change that turns out wrong can be rolled back to the previous version the same way.

The site is published to Netlify, a website host, and we set that up with you, including your domain name if you have one.

Ad Grants and your own domain

If you plan to use Google Ad Grants, the ads have to point to your own website on a domain you control, with real content about your mission. Grantkeeper will not point grant ads at a preview or at our hosting. Once the site is live on your domain, it can build paused campaigns that link to it.

Later changes work by text. "Christmas Eve is at 5 this year" becomes a new preview, then a new live version when you send the code.

Already on WordPress? Use the plan a visit page recipe instead, which saves a draft on your existing site.

Sources: Google Ad Grants website policy, Netlify documentation

What you send

Service times, address, parking and entrance, children's care, accessibility, languages, contact details, and a domain name if you have one.

What Grantkeeper prepares

A small site with Home, Plan a visit, Ministries and Contact pages, checked on phone and computer screens, with screenshots for you before anything is public.

What to keep in mind

We turn on Website and publishing with you. Photos cannot be placed on the site yet. Grant ads need the site on your own domain.

Talk to us about Grantkeeper