Everything it does, and what it looks like on your site

Finds the right page even with typos, vague wording or the wrong term. It matches meaning as well as keywords.

For example: A visitor types discipleship for new beleivers (with a typo) and still gets the right articles, including one titled “Following Jesus: The First Steps.”

Narrow by topic, author, type, date or any custom field, with live counts.

For example: Search prayer, then narrow to podcasts by one author from the last 12 months, with a count beside each option.

Add synonyms, pin the right result to the top, and bury outdated pages.

For example: Make missions also match “missionary work,” and pin your Missions Sunday resource page to the top for “missions sunday.”

Suggestions drawn from what your visitors actually search for.

For example: Typing bap suggests “baptism” and “believer’s baptism,” because those are what your visitors search for most.

Recognizes Bible references and surfaces your content on that passage.

For example: Searching Rom 8:28 or Romans 8 returns the sermons and articles that teach on that passage.

“Near me” and map-area search for events, churches or offices.

For example: Events near me lists upcoming events within 50 miles, closest first.

Search and summaries in your audience’s languages.

For example: A French-speaking reader searches in French and gets French articles and summaries.

A short answer above the results, written only from your content, with numbered citations.

For example: “What do you teach about baptism?” returns a short answer that cites the articles it came from: [1], [2], [3].

Visitors ask follow-up questions and the AI keeps the context.

For example: After the baptism answer, the visitor asks What about infant baptism? and gets an answer in context, without repeating the question.

A short summary at the top of every article, so readers get the main point in seconds and decide whether to read on. Written in your voice, and approved by your editors before it’s published.

For example: A 3,000-word article gets a two-sentence summary at the top, approved by an editor before it goes live.

“Read next” and related-content blocks that actually match the topic.

For example: Under an article on prayer, “Read next” shows three more articles on prayer, not the three newest posts.

Instead of answering, the AI recommends a curated, ordered reading list, with a note on why each piece fits. It can ask one clarifying question first. Readers stay on your site, reading your work.

For example: Help me understand suffering in Job returns five articles in reading order, from introduction to deeper study, each with a note on why it’s there.

Each article’s approved summary is also built into the page’s code, so Google and AI assistants can use your own words instead of writing their own.

For example: An AI assistant describes your article using your editor-approved summary instead of improvising one.

AI assistants and agents can search and read your content through a standard, read-only connection (MCP), with a key you control, instead of scraping your pages.

For example: An AI agent helping someone prepare for a mission trip pulls your preparation resources directly, with links back to your site.

Make it easy for AI assistants to understand who you are and what you offer, through a standard file (llms.txt) written for them.

For example: When someone asks an AI assistant how to support your missionaries, it can point straight to your giving pages instead of guessing.

Lets AI assistants built into a visitor’s browser use your site’s own tools, such as search, find an event or give, following an emerging web standard.

For example: A visitor asks their browser’s assistant to find a way to support missionaries in Southeast Asia, and it uses your site’s own search instead of guessing.

See which AI bots (such as GPTBot, ClaudeBot and PerplexityBot) read your site, how often, and which pages they read.

For example: You learn AI crawlers read your beliefs page every week but never your giving page, so you fix the links to it.

Answers come from your published content and cite it. The AI can’t pull in the open web.

For example: Asked “What does the Bible say about baptism?”, the answer draws only on your articles, never on other traditions from the open web.

Set the tone, audience and theological or editorial stance the AI writes in.

For example: Answers are written for a lay audience, in a warm pastoral tone, and stay within your statement of faith.

Use a leading commercial model, our open-weights model, or your own.

For example: An organization whose policy rules out frontier AI runs its answers on our open-weights model instead.

Run the AI features on your own AI account or private endpoint. Your usage, your contract, your data terms.

For example: An organization with its own enterprise AI agreement runs every AI feature on its own account, under its own data terms.

Only published, public content is indexed, and unpublished pages drop out automatically. Each organization’s data is walled off at the database level.

For example: A staff member unpublishes an outdated policy page, and it drops out of search automatically.

Keys limited to exactly what each app may do and which content it may see. WordPress roles carry over into the portal.

For example: Your mobile app’s key can search public articles only; it can’t add or change content.

Search that respects paywalls and member levels, with single sign-on.

For example: A paying member sees members-only articles in search results; an anonymous visitor doesn’t.

See what people search for and find nothing, so you know what to write next.

For example: The report shows grief after miscarriage was searched again and again last month with no results: a clear next article to write.

Top searches, what people click, and which results fall short.

For example: Marriage is a top-10 search, but few people click the first result, a sign that page needs work.

We measure search quality on your own queries and prove each improvement.

For example: We score search quality on your 50 most common queries before and after every change, so tuning is proven, not guessed.

Ask questions about your own content: “What do we write about most? Where are our gaps?”

For example: A marketing director asks Which topics do we write about most, and which get the fewest clicks?

An email with top searches, new content gaps, and your most-read or changed content.

For example: Every Monday: the top 10 searches, new content gaps, and the articles that changed last week.

Connect Google Analytics, Search Console, Ahrefs, event registrations and email data to your content, and ask questions across them.

For example: Combine Google Analytics with your content to ask Which topics lead readers to register for our conference?

Readers follow topics, save articles, and get recommendations that fit their interests.

For example: A reader who follows missions and prayer sees those topics first in their recommendations.

Readers pick up where they left off, on any device.

For example: A reader who stopped halfway through an article on their phone sees Continue reading on their laptop.

Readers can reset everything we know about them in one step.

For example: A reader clicks Reset my data, and their reading history, bookmarks and interests are erased.

FAQs, study guides, discussion guides and outlines drafted from your approved content, for staff review.

For example: Create a four-week small-group guide on discipleship from our content produces a draft, citing its sources, for staff to review.