A translated button must promise the same action as the original. If the original asks for information, the translation must not quietly promise a booking.
Prepare the meaning before asking someone to translate the words. Give the reviewer the whole journey, the facts that must stay true and the questions the business still needs to answer.
This guide produces a translation brief for one page and its connected material. It does not supply an approved translation, publish a language version or establish a ClickFunnels AI translation feature. The business, source text and decisions below are fictional.
Name the language and intended audience
Record the source language, intended target language and relevant regional context. “Translate for international customers” is too broad for a reviewer to assess terminology, dates or the service actually available.
The example is an English page for a remote room-layout advice session. The proposed audience reads Spanish in Mexico. That audience choice is an invented planning assumption, not evidence of demand or eligibility for the service.
Keep language and business coverage separate. A Spanish page does not establish that the business serves every Spanish-speaking country. Confirm the service area, operating language and follow-up arrangements before describing them.
Assign two roles. The offer owner confirms what the business provides. A reviewer competent in the target language checks meaning and suitability. One person may fill both roles, but the two decisions still need evidence.
Fix ambiguous source text before translation
In the fictional offer, a person can request information about one remote advice session. It includes discussion of a room sketch and written suggestions. It does not include a measured floor plan, furniture purchasing or a reserved appointment from submitting the request.
Those assumptions belong in the brief. So do missing facts. The source page contains “Available from 03/04” and “Session fee: $75,” but the supplied material does not establish the date, year or currency.
A translator cannot determine those facts from fluency. Mark both strings HOLD FOR OWNER. Do not choose a date order or convert a currency to make the page look finished.
W3C's internationalization guidance highlights local name, address and date conventions, along with clear source text. Use those checks to uncover assumptions rather than simply replacing English words. W3C: Internationalization Quick Tips.
Give each important segment a meaning record
Use stable IDs so the translator, offer owner and implementer can discuss the same text. Include where it appears and what it does.
Scroll horizontally to compare all columns.
| ID | Fictional source segment | Meaning to preserve | Decision before translation |
|---|---|---|---|
| L01 | Ask about a room-layout session | Request information; no reservation | Ready for translation draft |
| L02 | Bring a room sketch to discuss | Participant supplies a sketch; advice does not include measuring the room | Ready with a definition of “sketch” |
| L03 | Available from 03/04 | Start date, year and date order unresolved | Hold for owner |
| L04 | Session fee: $75 | Currency and the complete fee basis unresolved | Hold for owner |
| L05 | Request received | Proposed message only for a confirmed received request; not a booking | Ready for wording draft; actual display condition still requires implementation verification |
“Ready” means the intended meaning is sufficiently specified to draft wording. It does not mean the translation, page or receiving behavior has been checked.
Attach surrounding copy to each segment. A heading without its paragraph or a button without its destination can invite an incorrect interpretation. Include labels, help text and errors when they are part of the same task.
Build a small terminology register
Define terms that could change the offer. For this example:
- Session: one remote conversation about the participant's supplied room sketch.
- Sketch: a participant-prepared drawing for discussion; it is not a verified measurement record.
- Request: an information enquiry awaiting a reply; it does not reserve a session.
- Suggestions: written advice within the agreed scope; not a finished architectural plan.
Leave the target-language terms blank for the translator. Ask them to record the chosen wording and any ambiguity they cannot resolve. Do not call a machine-generated glossary approved merely because its entries are consistent.
Record exact names or identifiers that must remain unchanged, with a reason. Distinguish a brand name from ordinary descriptive text. A blanket “do not translate headings” rule could leave important instructions inaccessible to the intended reader.
Include the material beyond the main page
Follow each link and promised next step in the plan. Does the reader reach an English-only resource, a separate form or a person who cannot reply in the expected language?
List those boundaries explicitly. In this example, the preparation worksheet has not been translated, and the reply language is unconfirmed. The brief must resolve those issues or accurately explain the limitations before inviting a reader into that journey.
Include text embedded in images, download contents, document titles and relevant status messages in the inventory. W3C recommends checking images and examples for translatability and cultural suitability. That is a reason to inspect the actual material, not to invent a cultural preference for an entire country. W3C: Internationalization Quick Tips.
If an equivalent page exists, plan a clear way to reach it. Verify the actual destination before offering a language switch; an untranslated home page is not automatically an equivalent version of this task.
Review meaning and layout separately
Ask the language reviewer to explain the translated action and conditions back in terms the offer owner can assess. Compare that explanation with the segment register. Resolve disagreement before marking the wording approved.
Then inspect the implemented page. Translated text can occupy different space. W3C advises allowing text to reflow and avoiding tight fixed containers. A source-language screenshot cannot establish that the translated button or error fits. W3C: Text size in translation.
The page's language declaration also needs implementation attention. W3C describes declaring the default language on the HTML element and identifying language changes in content. A language label in the brief does not set that markup. W3C: Declaring language in HTML.
Keep four results separate: meaning review, resolved business facts, rendered journey checks and actual receiving behavior. All remain NOT RUN in this example. A correct translation does not prove a form saves, a reply arrives or a service is available.
Finish a brief another person can use
Use the translation-brief worksheet for L01–L05, the terminology register, connected-material inventory and blank review records.
Give each unresolved item an owner and next action. Preserve the source version and approved translation version together so a later offer change triggers a review of the affected language versions.
For a ClickFunnels AI project, include that brief with the workflow and access guidance at /agents. This preparation grants no builder access and establishes no automatic translation, localization, routing or publication capability. Resolve the ambiguous date and currency before asking the translator to finish the page.