Multilingual SEO for church websites: separate URLs, hreflang and reviewed translation

How to publish your church website in more than one language so each community finds the right page: separate URLs, hreflang, a visible language switcher and human review.

By SermonLingo TeamUpdated 8 min read

How should a church website handle more than one language?

A church website should give each language its own web address, such as /es/ for Spanish, with the whole page written in that language. Connect the versions with hreflang annotations, add a visible language switcher, and have a fluent reader review every translated page. Google recommends separate URLs over cookies or browser settings, and it works out a page's language from its visible text.

This guide is about your website. Translating a service as it happens is a different job, covered near the end, and the two work best when your site explains how guests follow the service in their language.

We read the Google documents linked here in October 2026, including its pages on managing multilingual sites and localized versions of a page.

Which pages should you translate first?

Translate the pages that help someone take a first step, and leave the archive alone. A short, fully translated set beats a long, half-translated one.

Translation priority for a church website
PageWhy it comes firstWhat the reviewer checks
Plan your visit and service timesEvery newcomer asks where and whenTimes, address, which services use this language
Contact and directionsA visitor who cannot reach anyone leavesPhone, form labels, who answers in this language
Children and family check-inParents need safety and process details before they comeCheck-in steps, age groups, pickup rules
What to expect and what we believeBuilds trust before the first visitTradition-specific vocabulary and tone
Events and classes for that communityGives a clear next stepDates, cost, registration, childcare
Blog archive and old newsLittle value to a newcomerSkip, or summarize in one reviewed page

Translate each page and its navigation together. Google notes that translating only the template, such as menus and footers, while the main text stays in one language creates a poor experience, because the same content then appears in results under different boilerplate. A short page that is fully in Spanish serves a Spanish reader better than a long English page with Spanish buttons.

On the English site, link only to translated pages that exist. A link to a missing page frustrates the reader and teaches search engines nothing.

What URL structure should a church use?

Google recommends separate URLs for each language version rather than cookies or browser settings that swap the text on one address. Its guide compares a country domain, a subdomain such as es.example.org, a subfolder such as example.org/es/, and URL parameters, which it does not recommend. For most churches a subfolder is easiest: one site, one host, low maintenance.

Avoid changing content by cookie, visitor location or browser language on the same URL. Google explains that its crawler usually comes from the United States and sends requests without an Accept-Language header, so it may never see your Spanish version.

Avoid automatic redirects based on a guess about the visitor's language, too. Google says they can stop people and search engines from reaching every version. Offer a visible language switcher instead:

  • Label each language in itself: Español, Português, 한국어, not Spanish, Portuguese, Korean.
  • Put it in the header or footer of every page.
  • Link to the same page in the other language when it exists, and to that language's home page when it does not.
  • Keep one language per page. Google advises against side-by-side translations because it decides a page's language from the visible content.

Words from the target language are welcome in the address itself, for example /es/visita/. Your CMS normally handles character encoding.

How does hreflang work, and how do you add it?

Hreflang annotations tell Google that two pages are the same content in different languages, so it can show searchers the right one. Google says it can sometimes find alternate versions without them but recommends stating them explicitly. You can place them in the page head, in HTTP headers or in your sitemap. The three methods are equivalent, so use whichever your site makes easiest.

For an English page at /visit/ and a Spanish page at /es/visita/, the head of each page would contain the same three lines, shown here as text:

  • <link rel="alternate" hreflang="en" href="https://example.org/visit/" />
  • <link rel="alternate" hreflang="es" href="https://example.org/es/visita/" />
  • <link rel="alternate" hreflang="x-default" href="https://example.org/visit/" />

These rules from Google's localized versions page trip people up most often:

  • Each version lists itself and every other version, using full web addresses.
  • Links must run both ways. If page A names page B but B does not name A, the annotations may be ignored.
  • Start with a language code, optionally followed by a region, such as es, pt-BR or fr-CA. A region alone is not valid. Only codes from the ISO lists work, so es-419 for Latin American Spanish is not supported. Use plain es.
  • For Chinese scripts, Google supports zh-Hans for Simplified and zh-Hant for Traditional.
  • The x-default line names a fallback page for people whose language you do not cover.
  • You may leave a language out on some pages. Google still processes pages that point to each other, but link new translations back to the original.

Google also says it does not use the HTML lang attribute to detect language. Keep the attribute correct anyway for browsers and assistive technology. Many multilingual plugins write the annotations for you. Confirm by viewing a page's source, or by inspecting it with the URL Inspection tool in Search Console.

Is machine translation good enough for church pages?

Machine translation is a useful first draft and a risky final draft. It handles plain sentences well and stumbles in the places churches care about most:

  • Times and dates. Clock formats, date order and written-out numbers differ by language and region.
  • Tradition-specific words. Communion, Eucharist and Lord's Supper are not interchangeable to every congregation.
  • Ministry names, forms and children's safety policies, where one wrong word changes what a parent understands.
  • Register and tone, such as whether Spanish-speaking members expect tú or usted from the church.

Use a simple review process: a machine or volunteer draft, a fluent reviewer, a short glossary of your church's terms, then publish and record who reviewed the page and when. Google's guidance on generative AI content asks site owners to fact-check and review AI-generated content before publishing, including titles, descriptions and structured data. Apply the same standard to AI translation.

Resist bulk translation. Converting hundreds of old posts into several languages to look larger adds little, and Google's scaled content abuse policy targets many pages made mainly to manipulate rankings without helping people. The safer test is whether a reader in that language would be glad each page exists.

Browser translation is a fallback. A visitor can use it on any page, which helps them read, but it does not give Spanish-language searchers a page of their own to find.

How do sermons and live translation fit in?

A translated sermon summary can serve people who could not attend in their language. Treat transcripts as raw material. SermonLingo's Advanced and Premium plans include transcripts in every language, exportable as TXT, CSV, SRT or WebVTT, and they remain drafts until a fluent person has read them. Our guide to sermon transcript SEO walks through the editing workflow.

Live translation at services is a separate job from website translation, but your website should explain it. SermonLingo gives guests captions in 54 languages and an AI voice in 13, and guests join by scanning a QR code or opening a link, with no app. A page titled "Services in your language" should say which services are translated, which languages are available and how to join. Plans are on the pricing page, and the demo service shows the guest view.

The two meet in one sentence on every translated page, for example: "Scan the QR code at the door to follow the service in Spanish on your phone." Searchers need words on the page at midnight. Guests need captions or voice on Sunday.

How do you check that Google sees each language?

  1. Inspect a translated page with the URL Inspection tool and confirm the rendered text is in the right language.
  2. Search site:example.org/es/, using your own address, to see which translated pages are indexed.
  3. In the Search Console Performance report, add a Pages filter for URLs containing /es/. Compare impressions, clicks and queries with the English pages, and check that the queries are in Spanish.
  4. Read each translated page's title as it appears in results. Google advises unique, descriptive titles, so write them in that language: "Servicios en español | Example Church, Springfield".
  5. Wait. Google says changes can take anywhere from hours to months, and suggests waiting a few weeks before judging.

Results vary by device, place and settings, so treat spot checks as hints and rely on Search Console for patterns. For a content plan across several language communities, see our guide to an SEO content plan for multilingual ministries, and for the local side, local SEO for churches.

Questions

Do we need hreflang if we only translate a few pages?

Not strictly. Google can sometimes find alternate versions on its own, but it recommends stating them. On a partial site, annotate only the pages that have a translation, make the links run in both directions, and link new translations back to the original. Never point hreflang at a page that does not exist.

Is a translation plugin enough for our church site?

That depends on what it does. Some plugins create separate translated URLs, while others only change the text in the visitor's browser. Google recommends separate URLs, so check which your plugin produces, then have a fluent reader review the pages. A plugin saves typing but cannot judge tone, theology or accuracy.

Do we need separate Spanish pages for Mexico and Spain?

Usually not. One Spanish version with the plain code es serves most churches, and Google does not support es-419 for Latin America. Use region codes only if you truly publish different pages for different countries. Choose vocabulary and register with the members you serve, and ask which words feel natural to them.

Does the HTML lang attribute help Google rank our Spanish pages?

Google says it detects a page's language from the visible content and does not use the lang attribute or the URL for that. Keep lang correct for browsers and assistive technology anyway, and focus on writing the whole page, including navigation and buttons, in one language.

All articles