Google translated results: checks, reporting, and notranslate

This guide is for a site owner deciding whether automatic translation of their material in search is acceptable. Prepare the page address, original language, query language, and access to the relevant Search Console property. Changing the rule requires access to the page’s HTML or HTTP-response configuration.

Google documents a possibility of translation, rather than a requirement to translate every eligible result. The feature is available on mobile and desktop. Listed destination languages include English, French, and Hindi; Russian is absent from the checked list. That boundary concerns the published destination-language list and does not establish a prohibition on using Russian-language content as the original.

We recommend recording the original page language separately from the displayed result language. When a result appears translated, preserve the query, date, device, title, and snippet. A language match alone is insufficient to establish that the result is Google’s automatic translation.

Section sources:[1] Google Search Central

According to the documentation, clicking a translated title opens a machine-translated page. Users can also view the original search result and access the whole page in its original language. Google explicitly says it does not host translated pages; it compares this experience with Google Translate or translation in Chrome.

A practical check should cover the complete journey: the result, the page that opens, and access to the original. Record whether important statements retain their meaning and whether the page’s main action remains usable. This is a proposed user-experience check, not a test we performed.

Google says JavaScript, images, and other page features are usually supported. The qualifier does not guarantee every element. If something fails, preserve the specific element and the difference between original and translated views. The document separately says ad-network operators may need additional action, but detailed advertising configuration is outside this guide.

Section sources:[1] Google Search Central

The documented monitoring route is the Performance report and its Search Appearance filter for translated results. Google explicitly connects this route with impressions and clicks. Inspecting the page after following a result answers a different question: whether the translation is useful to the reader.

Open the report, select the relevant segment, and record the period alongside the applied filter. Preserve the available metrics with their names. For subsequent observations, use a comparable period and the same segment; this is an editorial recording procedure, not an additional Google requirement.

If you cannot obtain the segment, record the observed situation: the option cannot be found, data is absent, or report access is restricted. The examined documentation does not provide a complete troubleshooting procedure for these cases. An unavailable observation therefore should not automatically be recorded as an absence of translated results.

Section sources:[1] Google Search Central

Participation requires no separate opt-in. If automatic translation is acceptable, first check whether an existing notranslate rule contradicts that decision. Absence of an opt-out does not itself promise that a translated result will appear.

Google documents opting out through a meta tag or HTTP header. The important decision boundary is that notranslate opts out of all translation features in Google Search. The source does not offer a narrow setting that disables only translated titles while preserving the other search translation features.

The documented options appear below. Choose the option matching the intended scope and inspect the actual HTML or server response. Do not extend the stated Google Search scope to every possible translation mechanism outside search.

• For Google: <meta name="googlebot" content="notranslate">.
• For search engines supporting the rule: <meta name="robots" content="notranslate">.
• HTTP-header option: X-Robots-Tag: notranslate.

Section sources:[1] Google Search Central

This checklist is an editorial tool assembled from the documented capabilities and limitations. A completed card should connect the chosen policy with a page address, observable behavior, and a next action. An empty field means an incomplete check, rather than a positive result.

• Context: page address, original language, intended translation language, device, and observation date.
• User journey: preserved result, opened translation, access to the original, and any semantic or functional problems.
• Reporting: period, Search Appearance filter, available impressions and clicks, or a precise description of the unavailable observation.
• Decision: permit translation, opt out of Google Search translation features, or defer the change until a specific problem is checked.
• Configuration check: selected meta tag or HTTP header, its actual presence or absence, and the address where it was inspected.
• Completion: the reason for the decision, unresolved questions, and a trigger for another check, such as changed documentation or a discovered translation error.

Section sources:[1] Google Search Central

Do not treat a machine-translated view as evidence that a publisher-produced language edition exists. The document describes translation of the user’s viewing experience. If a particular passage matters, compare its meaning with the original rather than judging from a translated title alone.

Do not declare an opt-out successful solely because one result stops appearing after a change. First inspect the served rule and preserve the observation separately from its proposed explanation. The document supplies no application deadline and does not offer that single observation as a completion test.

For the different task of comparing AI-system answers across languages, use the guide to [cross-language AI-search measurement](/en/knowledge/cross-language-ai-search-measurement/). The output here is narrower: a justified page-translation decision and a reproducible record of its verification.

Section sources:[1] Google Search Central

We computed the supplied public snapshot’s SHA-256 and matched it against the specified value. We then read the document body and separately matched its language, destination, reporting, and notranslate provisions to the guide’s claims. The check took place on 2026-10-27 using [Google Search Central’s documentation](https://developers.google.com/search/docs/appearance/translated-results).

To repeat the method, extract those groups of provisions and separate Google’s direct statements from proposed verification actions. The checklist connects them into a decision sequence; it does not report experimental results. We did not test live search results, actual translations, or Search Console accounts. Original editorial copy is licensed CC BY 4.0; the source remains subject to its own terms.

Section sources:[1] Google Search Central