Inventory what has actually been translated
Review the main text, tables, captions, downloads and the next action for each resource. A translated menu does not mean the article itself is translated. Give each edition an explicit internal state such as missing, partial, under review or published. Record the specific unfinished elements instead of a single ambiguous translation complete checkbox.
Google determines a page’s language from its content and recommends keeping the content and navigation in a single language where possible. Its localized-version guidance distinguishes translated main content from copies where only peripheral text changes. These points do not make every mixed-language quotation a defect; the practical question is whether the promised edition delivers understandable content.
Choose an honest publishing treatment
If a complete edition is not ready, keep the unfinished translation in the editorial workflow rather than advertise it as a finished guide. Link to the available original with an explicit language label when it is useful. A short translated summary can be a deliberate resource, but describe it as a summary and identify what remains available only in the original.
Do not imply that a translation will arrive on a particular date unless someone has accepted that commitment. Record an owner and an internal review date without turning them into a public promise. If a partial page is already public, review whether its current content independently helps the reader before deciding whether to complete, revise or withdraw it.
Make the limits visible where they matter
Place the availability notice near the relevant choice or content, not only in a footer. Name the missing component precisely: the article, the downloadable checklist or the setup video. A translated article with an English-only attachment needs a different explanation from an article whose entire body is still English.
Provide a useful next step consistent with real service availability. That might be reading the original, using another relevant guide or contacting a support channel that actually handles the requested language. Do not invent bilingual support to soften the notice. Keep the notice understandable to the person who selected the unavailable language.
Illustrative example: a translated guide with an untranslated file
Imagine an Arabic maintenance guide is complete but its linked worksheet remains English-only. The editor records the attachment as untranslated, labels the download ورقة العمل متاحة بالإنجليزية and checks whether the guide can still be followed without that file. This fictional example distinguishes the article’s availability from that of its supporting resource.
If the worksheet is essential and the guide cannot explain the required fields, the editor keeps the Arabic release pending or supplies a reviewed explanation before publishing. If it is optional, the guide can explain its purpose and language without claiming the file is Arabic. The decision record contains the dependency, treatment and owner; it contains no invented completion date.
Review availability again after publication
For each displayed language claim, open the destination and read the actual body and attached material. Confirm that navigation does not identify an unfinished edition as complete and that alternate-language metadata describes real counterparts. A status code alone does not establish translation completeness. Coordinate URL removal or redirection with a separate technical review when a published page must be withdrawn.
When the translation is completed, remove obsolete notices, update its editorial state and recheck references to the original. Retain the review record so a later content change can reopen only the affected items. An SEO audit can find destination inconsistencies; a language reviewer must establish what is translated and whether the disclosure accurately sets expectations.