A buyer who saved a supplier’s product page last month should still be able to understand it next month. That sounds like a small requirement. It becomes more complicated when the page’s language depends on a third-party widget rather than content the supplier maintains.

Google’s September 1 update says its Google Translate Website Translator Widget will no longer be supported from October 1, 2026. The notice concerns that specific embedded widget. It is not an announcement that Google Translate, browser translation or every translation service is ending. Establish whether your website uses the affected component before commissioning a replacement.

Ask what happens when someone changes language

A language menu can conceal quite different arrangements. It may open a separately maintained English page, or it may translate the current page on demand. Some websites combine both approaches. A polished menu does not tell you which arrangement you have.

Ask the person maintaining the site to demonstrate a language change and explain where the translated text lives. Does the address change? Can an editor correct an individual passage? What happens to that correction when the original product description changes? These answers matter more than the number of languages in the menu.

For an international buyer, the distinction becomes visible when information stops matching. A translated page might describe one specification while a downloaded catalogue contains another. A form might look understandable until an error message appears in an unfamiliar language. The buyer experiences all of these elements as one supplier interaction, even if different systems generate them.

Suppliers with maintained language pages may need only a limited repair. Check supplementary areas such as help text, pop-ups or older product sections for reliance on the retiring widget. A component-level problem is not, by itself, a reason to replace the entire website.

Preserve the pages people already use

Begin with pages connected to active campaigns, recent inquiries or links repeatedly sent by the sales team. A visitor arriving from an old email will not necessarily pass through your new homepage. A procurement colleague may receive a forwarded link with no explanation of the website change.

For each priority page, follow the route from specification to document download and inquiry submission. Check the product name, measurements, qualifying conditions and the message shown after submission. If a visitor switches language halfway through, see whether the same product remains in view. Returning them to a general homepage makes them repeat work they have already done.

This is also a useful moment to distinguish language coverage from content ownership. Offering a language creates a maintenance obligation wherever important product details appear. It does not follow that a small supplier needs a large multilingual editorial team. It does mean the company should choose a scope it can keep accurate.

Google’s notice points site owners needing continued automated translation toward the Google Cloud API. That is a technical option, not a promise of a drop-in replacement. The right choice depends on the existing site, maintenance resources and the amount of content requiring review. A service integration and a set of maintained language pages solve different problems and carry different ongoing costs.

Make the replacement smaller than the ambition

A practical starting point is the product and inquiry content used by the markets you already serve. Build or preserve that route first. Additional languages can follow when there is someone able to maintain the commercially important information in them.

This approach may reduce the apparent breadth of the language menu. It can still improve the experience if the remaining pages make product selection and contact clearer. The objective is not to display as many language options as possible. It is to avoid asking a buyer to guess which version of a specification is current.

Keep existing independent page addresses where practical. If an address must change, identify the old links that need to reach the replacement. Include links in sales emails and downloadable material, not only those in navigation. Changes to the translation system should not make an established product difficult to find.

Before release, have someone who did not configure the replacement complete an authorized test journey. Let them find a specification, obtain the relevant document and try the inquiry route without coaching. Do not submit real customer details or send unapproved messages. The useful feedback is where they hesitate, misunderstand a condition or lose the selected language.

A separate discussion of localized supplier information covers the wider content problem. For this retirement, the immediate priority is narrower: keep the paths buyers already rely on understandable and intact.

Sources