Skip to content
Church Website Ideas Church Website Ideas Est. 2018
SEO与数字营销·

Subdirectory or Separate Site for a Second Language: How a Small Team Should Choose

For a volunteer-run church site adding a second language: when a subdirectory fits, when a separate site fits, how to test language switching, and how to keep pages, files and inquiry routes in sync.

Brand promotion: this article introduces Guangsuan's website build and multilingual planning services for small teams. It is a vendor introduction, not an independent review.

If your team shipped a first-visitor page on Saturday with a template and now needs Spanish, Chinese, or another second language, start with one question: will the second language describe the same services with the same contact path, or will it run as a different operation? When one team maintains the same brand and product, a language subdirectory is worth evaluating first. When markets have separate catalogues, service rules, or operating responsibility, compare a subdomain or a separate domain.

Short answer for a small team

The decision basis is business differences and long-term maintenance capacity. URL form alone does not create rankings, inquiries, or trust. A subdirectory such as example.com/es/ keeps one domain and shared templates, which suits one team publishing the same visitor information in two languages. A subdomain such as es.example.com keeps the main domain but allows separate deployment. A separate domain suits a ministry or operation with its own owner, renewal responsibility, content assets, and publishing rhythm.

Two checks belong with that answer. First, check URL structure and actual deployment together, because a shared domain can still use different applications and separate domains can still share hosting, accounts, and plugins. Second, if no one can review terminology in the new language or receive inquiries in it, narrow the launch to verified core pages rather than copying every page.

What subdirectory, subdomain, and separate domain change

Different language versions should use different URLs. One address that swaps text by cookie or browser setting creates sharing and search-entry problems: a shared link may open in the wrong language, and there is no clear entry point to index and link to.

StructureWhen to evaluate it firstDaily work it createsWhat it does not solve by itself
Language subdirectory, for example example.com/es/Same services, same contact path, one volunteer team maintaining both languagesShared templates, language plugin, permissions, and update noticesMissing terminology review; one system change can affect both languages
Language subdomain, for example es.example.comSeparate application or deployment is needed but the main brand domain should remainDNS, certificates, deployment, monitoring, and cross-site mappingA prefix does not replace language and regional explanation
Separate domainSeparate operating responsibility with someone owning renewal, admin access, and publishing long termDomain ownership, renewal, admin access, content-asset and account handoverLocal rankings and local trust do not arrive with the domain

One shared backend does not automatically complete translations. When source material changes, someone still has to find the affected languages, arrange translation and review, then update pages, attachments, and forms. If regional prices or catalogues can only be kept by constant manual edits, starting with fewer sites may not lower long-term cost.

For planning, Guangsuan's guide on choosing between subdirectories and separate sites describes the same decision in more detail: start from target regions, reading language, product scope, delivery rules, and contacts, then decide whether pages can be translations of each other or need regional content.

How a volunteer team can choose and test

Write down these five items before choosing. They also become the maintenance list later.

  1. Target regions and reading language. Name who the second language serves and where those readers arrive from.
  2. Scope. List the pages that need translation now: homepage, visitor card, service times, directions, kids check-in, contact form. Leave sermons, archives, and old posts until the core path works.
  3. Reviewer and inquiry owner. Name who checks wording and who replies to messages in the second language. Machine output is not a finished page.
  4. URL and switch plan. Give each translation its own URL and link pairs one-to-one. Do not point every second-language page at the translated homepage.
  5. Deployment note. Ask who hosts the site, how publishing works, how backups work, and how a fault in one language affects the other.

For a church team with two volunteers and a few hours per month, the practical rule is: same visitor information plus one reviewer plus one backend means evaluate a subdirectory first. Separate programs, separate contact teams, or separate hosting and compliance needs mean evaluate a subdomain or separate domain, and confirm who will own renewals and updates.

Saturday acceptance check for language switching

hreflang tells search engines which pages are corresponding language versions. canonical expresses a preference for the canonical address. They address different problems. A complete translation usually keeps its own canonical address and connects to its counterpart with hreflang, rather than pointing every translation canonical at the English page.

Run this check from one visitor page, not from the homepage alone:

  1. Open an English visitor page, switch language, and confirm it is still the same visitor page, with times, address, kids information, and form intact.
  2. Open navigation, one file download if used, and the inquiry or contact route, then switch back to English.
  3. Compare internal links, sitemap entries, language markings, and the addresses actually served, and fix places still using the old path.
  4. Provide a clear language switch and do not redirect automatically from a guessed browser language. A visitor who opens a shared link should still see the version that was shared, or be able to choose the other version.

As a hypothetical teaching example only, not a measurement: a team publishes /visit/ in English and /es/visit/ in Spanish. Entering /visit/, switching to Spanish, submitting the test form, then switching back catches a mismatched pair, an untranslated attachment, and a form that routes to the wrong inbox in one pass.

Keeping pages, files, and inquiry routes consistent

After launch, treat each product or ministry-page change as three updates: text, files, and entry points.

  • Text: update the source page first, then the paired translation. Note what changed, who reviewed it, and when.
  • Files: check PDFs, images with words, maps, and downloads in both languages. Replace both versions or remove the outdated one; do not leave a new English file linked from an old translated page.
  • Inquiry route: confirm the second-language form reaches someone who reads that language, states response time, and asks for the same required facts: name, attendance needs, kids ages if relevant, and how to follow up.

Assign each change to a named owner, even if one person holds several roles. Keep the language map, glossary, account access, and file locations where the team can retain them, not only in one volunteer's messages.

The published Guangsuan B2B website build scope is useful as a build checklist even for a non-commercial site: plan product or content categories, hierarchy, customisable URLs and an XML sitemap before building; keep title and description management editable; use overseas hosting with global CDN and SSL where readers are overseas; and keep data export so accumulated content is not locked in. For a church team, translate that into: stable URLs for visitor pages, editable titles and descriptions, readable mobile layout, and a backup and handover record.

Two boundaries matter. Completing a build is not the same as a ranking or inquiry guarantee; actual indexing and ranking are decided by search engines. Ongoing updates, translation review, plugin renewals, backups, and monitoring are separate from a one-time build fee and need their own owner and schedule.

Frequently asked questions

Do we need a separate site for every new language? No. List target regions, reading language, scope, delivery or service rules, and contacts first. If the same visitor information only needs another language introduction, paired translated pages are enough. Plan regional content when stock, schedules, service commitments, contracting details, or follow-up handling genuinely differ.

Will a separate domain rank better or earn more trust locally? Not automatically. Structure follows business differences and maintenance capacity. Check domain registration conditions, availability, and whether your entity qualifies before assuming a country-code domain is available.

Can we use machine translation for the new pages? Not as the finished page. Terms, times, addresses, and form wording need review before publication. If no reviewer exists yet, publish fewer verified pages in the language you can support, then expand when review capacity exists.


About the author

Church Website Ideas

Writes for Church Website Ideas — a weekly publication for pastors and church comms teams shipping websites that serve the congregation.