4 minute read · Practical marketing guidance
On this page 5 sections
A customer reading a service detail may want it in Spanish. If that detail has no Spanish counterpart, a language link needs an honest destination. Sending the customer to a broader overview can be useful, but it does not supply the missing explanation.
Decide what content exists before asking the website editor to connect it. The task is to distinguish an equivalent page from an alternative, then explain the remaining limitation.
Define what counts as a counterpart
An equivalent page should answer the same service question, with the applicable scope, conditions and next step intact. Its sentences and pathname need not match the English version. A translated menu surrounding unrelated or incomplete detail does not settle equivalence.
Google’s multilingual-site guidance recommends separate URLs for language versions and links through which users can choose another version of a page. It advises against automatic redirects based on presumed language. Those recommendations do not create a translation that your team has not prepared.
If the service facts or translation readiness remain unresolved, start with the bilingual website-copy guide. Here, the narrower decision concerns a detail that is missing in the requested language.
Choose among three content states
Use this decision aid before proposing the language route:
- A reviewed counterpart exists: Identify that exact page and confirm that it answers the same service question.
- Only a broader overview exists: Disclose that the specific detail is unavailable, and describe the overview as a separate alternative.
- Neither is ready: Assign the missing content for review. Do not invent a destination or imply that a counterpart is available.
This is an editorial policy proposal, not a prescribed widget design. The owner decides what alternative the business can support; the editor implements the agreed choice.
Two fictional journeys
Every business, page, path, label, translation, approval state and outcome below is hypothetical. No real translation has been reviewed, link activated, navigation changed or result observed.
A specific counterpart is available
Imagine a Henderson gate-assessment business. A reader starts at /services/gate-assessment/. Suppose a reviewed Spanish version exists at /es/servicios/revision-portones/, explaining the same assessment and review-before-quote step.
The proposed language choice would lead to that detail. Its availability and review are assumptions for this example. The actual arrival, content and return route would still need observation; the path strings prove nothing about a working website.
The specific detail is missing
In a second imagined journey, a reader opens /services/historic-gate-hardware/. No Spanish counterpart is assumed to exist. The only alternative is a broader service overview at /es/servicios/.
The proposed notice would explain that this particular detail is unavailable in Spanish. An overview link would name that broader destination instead of promising the same hardware explanation. A fluent reviewer would prepare the actual notice; no Spanish customer-facing wording is supplied or approved here.
The remaining content gap stays visible to the team. The overview is an alternative to consider, not evidence that the hardware question has been answered.
Match the notice to the destination
W3C’s link-purpose guidance explains that a link’s purpose should be identifiable from its wording or associated context. For a broader alternative, make that distinction clear where the choice appears.
Our internal-link guide covers the broader task of connecting questions and answers. This missing-counterpart decision comes before treating two pages as a language pair.
Assign the missing content and the website change separately
If a counterpart needs preparation, name the owner of its service facts and language review. If the counterpart already exists but the choice points elsewhere, give the editor the approved page pair. After agreed implementation, record the actual destination and any unanswered question.
Discuss language links and page planning within an agreed website design scope. Email sales@rank.vegas with your website, the starting service page and whether a Spanish counterpart or only a broader overview is available.