Question 1

How do I stop certain parts of my page from being translated with @google-translate-select?

Accepted Answer

Add `class="notranslate"` to HTML elements you want to exclude, such as prices or code snippets. The README highlights this for e-commerce use cases.

Question 2

@google-translate-select vs i18n libraries like react-i18n or vue-i18n?

Accepted Answer

@google-translate-select is for quick, client-side Google Translate integration, while i18n libraries offer full control with local translation files but require manual setup and maintenance.

Question 3

Can @google-translate-select translate content loaded dynamically via API?

Accepted Answer

No, it only works with static content on initial page load. For dynamic content, you'd need to trigger a page refresh or use alternative methods.

Question 4

How to set up @google-translate-select if my site's default language isn't English?

Accepted Answer

Use the `defaultPageLanguageCode` prop to specify your source language code, e.g., "es" for Spanish, as noted in the README tips.

Question 5

Is @google-translate-select good for SEO in multilingual sites?

Accepted Answer

No, because translations happen client-side, search engines may not crawl the translated versions, which can hinder international SEO efforts.

Question 6

How to install @google-translate-select in a Vue 3 project?

Accepted Answer

Install the Vue 3 package via npm or yarn, then import and use the component as shown in the documentation. The monorepo includes separate packages for each framework.

Question 7

Does @google-translate-select work with server-side rendering (SSR)?

Accepted Answer

The README doesn't mention SSR support; since it relies on Google's client-side SDK, SSR compatibility is likely limited and would require additional configuration.

v-google-translate

What is v-google-translate?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions