- Start with Google Business Profile, not the website. For “church near me” searches the local pack appears on about 93% of local-intent queries. The website is the second stop, not the first.
- Service times inside an image are invisible to Google. So is a PDF bulletin. This is the most common single cause.
- Check you’re actually indexed before assuming it’s a ranking problem. Search
site:yourchurch.org— if pages are missing, nothing else matters yet. - AI search barely touches local intent. AI Overviews appear on roughly 7–15% of genuinely local queries. Local search is the least disrupted part of the web.
A church website that nobody visits usually has one of six specific problems, and they are diagnosable in about twenty minutes. Work down this list in order — it is sequenced so the cheapest and most common fixes come first.
1. You’re not in the local pack
When someone searches “church near me” or “baptist church [your town],” Google shows a map with three listings above the organic results. Whitespark‘s study of 540 local queries found the local pack appears on 93% of local-intent searches. If you’re not in it, the website is competing for the leftovers.
| 1 | Claim your Google Business Profile if you haven’t. It’s free. |
| 2 | Set the primary category correctly — this is consistently ranked the single strongest local pack factor. |
| 3 | Make sure service times in the profile match the website exactly. |
| 4 | Add real photos. Profiles with photos get engaged with more. |
| 5 | Ask a handful of regular attenders to leave an honest review, and reply to every one. |
2. Your service times are inside an image
This is the most common technical failure on church websites and the easiest to fix. A graphic that says “Sundays 9am & 11am” is, to a search engine, a picture of nothing. The same applies to a PDF bulletin, a Canva flyer, or text baked into a hero slider image.
Put service times in the page as real text. Then put them in your Google Business Profile. Then make sure the two match.
3. You’re not indexed
Before assuming a ranking problem, confirm Google has your pages at all. Search site:yourchurch.org. Count the results against the number of pages you have.
| What you see | What it means | Fix |
|---|---|---|
| No results at all | Not indexed. Possibly blocked entirely. | Check Settings → Reading for “Discourage search engines”. Verify in Search Console. |
| Far fewer pages than you have | Partial indexing | Submit your sitemap in Google Search Console |
| The right pages, wrong descriptions | Indexed, but titles and meta are weak | Rewrite page titles to include the town name |
| Old pages that no longer exist | Stale index | Set up redirects, resubmit the sitemap |
4. Your pages don’t mention where you are
A surprising number of church sites never state the town. “Grace Community Church” as a page title tells Google nothing about geography. “Grace Community Church | Louisville, KY” does.
Put the town in the homepage title tag, the H1 or the opening paragraph, the footer, and the Plan Your Visit page. Not stuffed everywhere — just present, naturally, where a human would expect it.
5. The site is slow on a phone
Most church websites are visited on a phone, often on cellular data, often by someone deciding on a Saturday night. Google’s threshold for Largest Contentful Paint is 2.5 seconds; above 4 seconds is classified as poor.
| ✓ | Run your homepage through PageSpeed Insights and look at the mobile score, not desktop. |
| ✓ | The usual culprits: an uncompressed hero image, a rotating slider, and embedded video that loads whether or not anyone plays it. |
| ✓ | Compress images before upload. A 4MB photo straight off a phone is the single most common cause. |
6. Nothing has changed in two years
An events calendar whose most recent entry is from 2024 actively signals that the church may not be active. If you cannot commit to maintaining a calendar, remove it and put service times and a contact number in its place. An accurate small site beats a stale large one.
What about AI search?
Less than you have probably been told. Whitespark measured AI Overviews on 15% of genuinely local-intent queries against local packs on 93%, and Sterling Sky tracked AI Overviews on about 7% of local keywords in 2026. Local search is the least disrupted corner of the web.
What has changed is that people increasingly ask an AI assistant for a recommendation and then verify it themselves — Yext found 93%+ take at least one verification step, and 58% go directly to the organisation’s own website. Which makes an accurate, fast website more important, not less.