School website translation: widgets vs. translated pages

Picture a parent opening your enrollment page in Spanish. The introduction is clear. Then the application button leads to an English-only form, and the document checklist is a scanned PDF.

The parent still has to find someone to explain the next step.

A useful school website translation helps a family finish a task: register a child, check a bus schedule, understand a deadline, or contact the right person. Choosing a translation approach starts with those tasks.

Look at what happens after someone chooses a language

A translation widget is a control on your website, often a dropdown or button. Some tools translate the page on demand in the visitor's browser. Other services publish separate language versions and support editing. The button's appearance tells you very little about what happens behind it.

Published translated pages have their own addresses. A school might have an English enrollment page at /enrollment and a Spanish version at /es/enrollment. Staff can review the content and send families directly to the version they need.

These capabilities are worth checking in a demonstration:

For a school choosing a long-term approach, our recommendation is separate language pages with an explicit review process. Evaluate any service against those capabilities, including services marketed as widgets.

Start with the pages families depend on

You do not need to begin with every archived announcement. Build the first translation list with the people who answer family questions: the front office, enrollment team, communications staff, and language-support staff.

Ask which pages a family needs before they can take action. A useful starting set is:

• Enrollment requirements, deadlines, and the application or registration process.
• School calendars, closures, early dismissal, and pickup information.
• Transportation, meals, and attendance procedures.
• Contact details and instructions for getting help.
• Current forms and documents linked from those pages.

Choose languages using information your school already holds appropriately and conversations with families. Website traffic alone will not tell you who struggled to use the existing site.

For each priority page, name an owner. Someone should know when its English content changes, who reviews the translation, and how to correct a problem reported by a family.

Give reviewers a clear job

Machine translation can provide a starting draft. The review process should focus on meaning and action.

Consider the difference between “submit an application,” “complete registration,” and “accept an offered place.” A family needs to understand which step applies, what it requires, and when it must happen. A fluent-sounding sentence can still describe the wrong step.

Create a short school glossary covering program names, campus names, grade levels, common abbreviations, and terms that should remain unchanged. Then give a reviewer familiar with the language and school context the source text alongside the draft.

Ask them to check:

1. Dates, times, locations, fees, and required documents.
2. Instructions about what the family must do next.
3. School-specific terms and names.
4. Links, button labels, and contact information.
5. Wording that sounds natural and is easy to act on.

Build review time into routine publishing. For urgent updates, agree in advance who can approve the critical details and which other communication channels will support the website.

Publish language versions people can find and share

Google recommends distinct URLs for different language versions. It also warns that versions shown only through language settings or dynamic changes may not all be discovered and crawled. Google's multilingual-site guidance.

Ask your website team to connect equivalent pages with hreflang: information that tells search engines which language versions belong together. Google documents how to implement those links, including the links back between versions. Google's localized-page guidance.

These steps support discovery; they do not guarantee indexing, rankings, or inquiries.

For families, a stable address has a simpler benefit: a staff member can send the Spanish enrollment page directly, and the family can return to that same page later. Keep a visible way to switch languages and test that sharing the link works without the sender's browser preferences.

Follow the task beyond the page

A translated page can lead into a calendar service, payment screen, PDF, or form managed somewhere else. Each handoff needs checking.

Walk through one complete task in every priority language. For example, start at an open-house announcement, find the event date, open the registration form in a test environment, and review its confirmation message.

Check whether a family can understand required fields and correct an error. If a document has separate language editions, label the links clearly and keep each edition's date visible. If a third-party service does not support a needed language, explain that limitation and provide a clear route to assistance.

Assign ownership for these handoffs. Otherwise the main website may improve while the final step remains difficult.

Check accessibility in each language

Translation and accessibility need attention together. Longer text can crowd a button or overlap a menu. A language control must work with a keyboard, and a page should identify its language in the underlying markup so assistive technology can interpret it appropriately. W3C guidance on page language.

Include the translated versions in your accessibility checks. For right-to-left languages, review the layout as well as the words. Ask a fluent reviewer to test the mobile experience and important tasks, not just read a translation in an editing panel.

Keep translations in the publishing routine

Use a simple content record: page owner, source update date, language reviewer, review status, and live link. When the original changes, identify the affected translations and assign the update.

Begin with one enrollment task and one day-to-day family task. Invite a few people who use the selected languages to try them, record where they hesitate, and fix those points before extending the approach.

That gives your team a repeatable way to maintain information families can use throughout the school year.

Use the accessible PDF checklist for school staff when the journey includes documents, and the school website migration checklist when moving existing language pages to a new platform.

Want to explore this approach for your website? See EdPilotHub's translation offering, or talk with our team about your priority pages and languages.