Free tool

Can AI even find your church?

Put your website in below. We knock on your door twice... once as an ordinary browser, once as GPTBot... and show you exactly what each one gets handed.

I built church websites for years and never once checked what a crawler got handed. Not once. I looked at it on my phone, decided it was pretty, and went to lunch.

Then we started running this check on real church sites, and the same thing kept surfacing. The homepage loads beautifully for a person. GPTBot knocks and gets a 403 before it ever reaches the server. Nobody on staff chose that. It came switched on.

Add the church name and we will also ask a language model what it already knows about you. That part is usually the one that stings.

What it checks

Four questions, asked out loud.

01

The door

We request your homepage as Chrome, then as GPTBot, and compare the two answers. Same page, two visitors. If the codes differ, something is deciding who gets in.

02

The sign

We read your robots.txt for lines that tell GPTBot, ClaudeBot, PerplexityBot and friends to stay off the property.

03

The page

Structured data, title, description, and how much readable text is actually there. A homepage built of video and images gives an answer engine nothing to quote.

04

The answer

We ask a language model what it knows about your church right now. Whatever it says back is roughly what a searching family hears tonight.

Pastor, here is the part I want you to sit with. Does your site load for people? Almost certainly, or somebody would have called you by now. Does it load for the machine a family in your city is actually asking? Different question. Nobody calls you about that one.

And when it is broken, the fix is usually not a project. It is one toggle.

The honest limits: this check reads your homepage live, twice, then asks a language model what it already knows. It is a snapshot from one afternoon, not an audit. It does not crawl your whole site, it does not test every crawler on the internet, and a model's memory shifts week to week. Treat it as a smoke alarm, not a fire marshal's report. If it goes off, though, go look.

Want the long version of why any of this matters? How people actually find churches in 2026 →

So what do I do

You can't fix the model's memory this year... so win the search it runs instead.

AI answers come from two different places, and they move at two different speeds.

The model's memory is what it absorbed in training. A local church almost never crosses that threshold... which is why the box above shrugs at nearly every congregation in America. You influence this half slowly, by existing loudly on the open web for years — press, directories, reviews, a steady stream of pages that all agree on who you are. The next model trained learns what the web kept saying. That is a compounding game, and the churches that win it started publishing early.

The search it runs live is different. When a family asks ChatGPT about churches near them tonight, it does not answer from memory... it goes and reads the web right then, and it cites what it can reach and quote. That half is winnable in weeks, and it comes down to five moves:

  1. Unblock the crawlers. The check above just told you whether GPTBot can even reach you. If it cannot, nothing else on this list matters yet... and the fix is usually one switch in Cloudflare.
  2. Say the facts in schema. Service times, address, what to expect — stated in structured data, not locked inside a graphic. Machines quote what they can parse.
  3. Build out your Google Business Profile and gather real reviews. For every "near me" question, Maps data is the first thing these engines lean on. A thin profile is a thin answer.
  4. Make every directory agree. Apple Maps, Yelp, your denomination's directory... same name, same address, same hours. Contradictions read as unreliability.
  5. Answer real questions on real pages. The questions people ask an AI at midnight are the ones they will never ask your greeter. Write the answers plainly, and the engines will lift them.

Pastor, none of this requires a bigger church. It requires a findable one... and most of it is a few honest weeks of work.

Want the fix, not just the diagnosis?

Thirty minutes with Jeff. We walk your result line by line and tell you what we would change first... even when the honest answer is that you do not need us for it.

Book a meeting with Jeff →

So, Pastor... if a family in your city asked an answer engine about your church tonight, what would it say? Run the check and find out.