Skip to content

Google translates your search result: check notranslate

Decide whether to allow translated Google results, find inherited notranslate rules, and test the page without confusing translation with hreflang.

By Crawlito · 5 min read

In short

  • Google documents notranslate as an opt-out from its translation features in Search.
  • A translated search result is different from a language version you publish.
  • Review the public response before changing language redirects or hreflang.
On this page

If Google translates your search result and you want to control that behavior, review the documented notranslate rule and your actual public response. If you want translated results but never see them, check for an inherited opt-out before changing your language pages. Neither outcome alone proves that your original page is indexed under the wrong language.

The first task is to identify which translation you observed. A browser translation, a Google-translated search result, and a translated page on your own domain are different experiences. Save the entry path and destination before editing metadata.

Identify who produced the translation

Start with the exact search result or visitor report. Record the query language, result title, snippet, destination, and the language of the page after opening it. Then open the original page directly in a fresh browser session.

Google's translated results documentation describes a Search feature that can translate results into the user's language and provides an opt-out. It is not the same as publishing a separate localized URL yourself.

If the direct page is translated only after the browser's own translation control is used, investigate that browser behavior separately. A screenshot of translated text does not identify which system changed it.

Compare the source page's visible language with its declared language and any alternate URLs. A misplaced redirect could send everyone to the wrong page, which requires a different fix. The language redirect guide covers that route-selection problem.

Keep one reproducible observation rather than assuming all visitors see the same translated result. Search presentation can vary, and absence in one test is not proof of an opt-out.

Find the rule in HTML and headers

Save the public page response:

bash
curl -sS -L -D language-headers.txt -o language-page.html \
  'https://www.example.com/guides/install'

Search both files for notranslate. Inspect the final document, and distinguish a directive applied to Googlebot from one applied generally to supporting search systems. Google's documented HTML form includes:

html
<meta name="googlebot" content="notranslate">

The rule may also be delivered in an HTTP response header. If a CMS panel says translation is allowed but the public header says otherwise, follow the response that readers and crawlers actually receive.

Check the page template, shared head component, and hosting rules. A developer may have copied a setting from a product where automatic translation caused confusion. That inherited setting can then reach an unrelated help center without an explicit decision.

Do not remove every robots directive while investigating. Preserve the rest of the intended indexing and preview rules. Record the exact line you changed so the team can distinguish the translation decision from unrelated search controls.

Decide whether the opt-out serves your readers

Review the actual content and audience. A setup guide with clear language may benefit from reaching readers who do not speak the source language. A page containing terminology that requires careful localization may need a reviewed translation experience.

This is a product decision, not a general SEO rule that every site should follow. Ask which errors would materially affect the task: a mistranslated button name, a changed unit, or an instruction that no longer matches the interface.

Use an example from your own page. Compare a short instruction with the real app action. If the translated text says to delete a record when the original says to archive it, document that specific issue. Avoid judging an entire language audience from one awkward phrase.

If you offer a reviewed localized page, make it easy for readers to find. That is a separate publishing task from the Search translation opt-out. The multilingual readiness guide helps organize checks across the language versions you actually maintain.

Do not add machine-generated language pages solely to replace the translation feature. Publish only versions you can keep accurate.

Apply a scoped change in the owning template

If you decide to permit Google's translation features, remove the unintended notranslate rule from the affected pages. If you decide to opt out, add the documented directive through the site's supported metadata mechanism.

Choose the narrowest scope consistent with the decision. A specialized reference section may need a different policy from marketing pages or general support articles. Avoid a site-wide setting when only one content type has the issue.

Check the generated output after saving. Some systems combine page-level and global settings, while delivery rules may add headers independently. A local template preview is not the final evidence.

Review an unaffected page as a control. The change should not silently alter the site's language routing, canonical URLs, or other robots instructions. If it does, separate those changes before release so the translation decision remains reviewable.

Keep a short note with the purpose and owner of the setting. Future editors should know why a section opts out, rather than treating an unexplained tag as stale code to remove.

Verify the source page before judging Search presentation

Fetch the public response again and confirm the intended directive is present or absent. Check the original text, language selection links, and main task on the page. A translation setting is not useful if the original page is broken.

Then observe Search over time with dated examples. The immediate acceptance test is the correct public instruction, not a demand that a particular translated result appear in your next search. Search presentation remains a separate outcome.

If you publish language alternatives, inspect them independently. The hreflang audit guide addresses relationships between your own localized URLs. Adding hreflang does not make a translation opt-out disappear, and removing notranslate does not create a localized page.

Use a small evidence table:

ItemWhat it establishes
Public responseThe instruction currently delivered
Original pageThe source content readers can access
Localized URLA version maintained by your site
Dated Search exampleOne observed presentation

This keeps implementation evidence from being overstated as a universal search result.

Check the reader's next step in each language experience

A translated explanation should still lead to a usable task. Test the link to your app, documentation step, or contact flow from the experience you observed. Record where the language changes and whether the interface still makes sense.

For example, a translated help article may link to an English-only configuration screen. The article can name the exact interface label so the reader can find it. That is an editorial improvement independent of metadata.

Avoid placing product tokens, command names, or version strings in prose that obscures their exact spelling. Use code formatting where it clarifies the literal value readers need. Verify copy-and-paste examples against the supported product version.

If the next step involves a form, check its validation and confirmation language as well. A readable article does not complete the journey if the reader cannot understand what happened after submission.

These checks help evaluate whether the translation decision improves a real task rather than treating translated impressions as an outcome by themselves.

Frequently asked questions

Is notranslate the same as noindex?

No. They address different behavior. Review the translation rule without assuming it also removes the page from search.

Does removing notranslate guarantee translated results?

No. It removes that opt-out. It does not require Google to display a translated result for a particular query.

Does this control every AI assistant's translation?

No. This guide describes Google's documented Search behavior. Do not assume unrelated services use the same control.

Run the original URL through the free Crawlito check to review its public technical state before comparing language experiences.

Filed under Structure and schema. Topics: meta-robots, multilingual, googlebot