A family that has recently moved to your city will decide whether to visit you long before Sunday. They will search, they will find a page, and they will read it on a phone, probably in the evening, probably while tired. If nothing on that page suggests they would be able to follow the service, they will close it and keep looking. You will never know they were there.
This is the least glamorous part of welcoming people and one of the most decisive. A church can have excellent translation, a warm congregation and a genuinely open door, and still be invisible to the person standing outside it with a phone.
What a visitor is actually asking
Not your doctrinal statement. Not your history. Three concrete questions:
- Where exactly are you? Not the district — the door.
- When do you meet? And how long does it last.
- Will I understand anything?
The third is the one multilingual churches most often leave unanswered, which is remarkable given how much effort goes into answering it on the day. A church that offers five languages on Sunday and mentions none of them online is doing the hard part and skipping the easy one.
What belongs on the page
- The address, with a map, and the start time. In that order, above everything else.
- The languages available — stated plainly, and written in those languages. A reader scanning a page recognises their own script instantly and reads nothing else until they have found it or concluded it is not there.
- One sentence on how it works. "Scan a code at the door and follow the service on your phone" answers the real fear, which is not language but having to ask a stranger for help in front of people.
- A photograph of the actual room, with actual people in it. Not a stock image. People want to know what they are walking into and roughly what everyone is wearing.
- A way to make contact that somebody answers. A form nobody reads is worse than no form.
- Whether there is anything for children, which for a family is frequently the deciding fact.
Write for someone who is nervous
Visiting a church in a country you moved to eight weeks ago is intimidating in a way that is easy to forget if you have belonged somewhere for twenty years. The page that works is not the one with the best design; it is the one that removes uncertainty.
Say what time to arrive. Say whether there is parking and whether it is free. Say what people wear. Say whether anyone will be asked to stand up and introduce themselves — and if the answer is no, say so, because that is the specific thing many people are afraid of.
Keep the sentences short. Your page will be read by people whose reading in your language is slower than their speaking, and by people using a browser's own translation, which handles plain sentences far better than elegant ones.
The languages on the page and the languages in the room
These should match, and often do not. A church adds a language on Sunday because a family arrived, and the website stays as it was for two years.
Worth doing once a term: look at which languages people actually selected during services, and check the website says those languages are available. It takes ten minutes and it is the difference between a page that describes the church you were and one that describes the church you are.
Let past services do the selling
If you keep an archive of past talks in the languages you serve, link to it prominently. This is the strongest single thing on the page, because it converts a promise into evidence. A visitor who can read last week's sermon in their own language has already had their question answered rather than merely addressed.
It also does something a description cannot: it lets someone find out what your church is actually like — the tone, the subject matter, the length — before committing a Sunday morning to finding out in person.
It helps you be found at all
There is a search consequence worth understanding. A single page in one language can only be found by people searching in that language. A church with an archive of talks in six languages has, over time, a great deal of text that people searching in those languages can actually find.
Nobody searches for "multilingual church". People search for a phrase from a sermon, a topic they are worried about, or a place name in their own language. Having real content in their language is what makes any of that possible.
Keep it current, or keep it small
The most common failure of a church website is not ugliness; it is a page advertising an event from two years ago. That does more damage than a plain page, because it tells a visitor the church may not still be there.
If nobody has time to maintain a large site, build a small one. Address, times, languages, a photograph, a contact, and the sermon archive that updates itself. Six things that are true beat twenty that were.
A page, a subdomain, or your own domain
InMyTongue gives each church a public page — your logo, your contact details, your events and your sermon archive in every language you have used — reachable at a short address, or at your own domain if you have one. It updates itself as you preach, which solves the maintenance problem by removing it. New accounts include free credit. See what your page would look like.