Free · no call required
None of these ask for a card, and none of them put you on a list. Two of them take under a minute. I would rather you find out what is true about your church on your own, and then decide whether I am any use to you.
We ask for your homepage as an ordinary browser, then as GPTBot, ClaudeBot, OAI-SearchBot and PerplexityBot, and show you what each one was handed. Then we ask a language model what it already knows about your church, and what it can say once it reads your page. The gap between those two answers is usually the whole story.
You get a result you can forward to whoever manages your website, naming exactly what is turning crawlers away.
Paste last Sunday's message. Back comes the Monday devotional, the mid-week group questions, the dinner-table question for your kids' families, a blog title your city could actually search for, and the one sentence worth quoting. Your words, not ours.
You get a full week of content out of a sermon you have already preached, to keep.
Paste a link to a sermon from your own church's YouTube. You get a devotional, two blog posts and the transcript. Everything is a draft for you to review and make your own.
You get a devotional, two blog posts and the transcript from a sermon you have already preached, emailed to you when it is ready.
Find, Gather, Grow, Go. One honest question per step. Nothing is submitted, emailed or stored... the maths runs on your own phone and disappears when you close the tab, which means the only person you can fool on that page is you.
You get a twelve-point scorecard naming the one step quietly costing you the other three. Put it on the screen in Monday's staff meeting.
The method, given away, hours included. What we actually do each week for adults, kids and youth, written so your team could run it without us.
You get the whole process, including how long each piece takes. If your team runs it themselves, good.
Run the check first. If it comes back clean I am not going to invent a problem so this page has something to sell you... that promise is written into the tool itself. If it comes back ugly, the fix is very often one setting rather than a project, and I will tell you that too.