Google Translate is not a localization tool, and the method you proposed will not give you a good translation.
An automated translation cannot understand differences in context. Let's take the single word "back" displayed on a button in your UI. Does this mean...
"Return to the previous screen/state" (like navigating a multi-screen UI, or unpausing and returning to gameplay), which we might translate into French as "retour"
"Switch to the rear side of this object" (like switching between front and back designs for a shirt you're customizing), which we might translate as "côté arrière"
"Invest and become a backer of this project/cause" (like supporting a Kickstarter or charitable project), which we might translate as "soutenir" or "financer"
...etc. And this is for just one common word translated into one language. Multiply this uncertainty by all the words in your game, by all the languages you want to support. If you automatically substitute word by word, you're playing Russian Roulette, and eventually you will get the wrong interpretation of a word somewhere, or they'll chain together into gibberish.
(Real-world example of this from my own recent experience: I have a student who sometimes leans on automatic translation for in-class discussions. Unfortunately the translator seems to translate "life amount", as in HP/Health Points, into "blood volume", which has a significantly more gruesome sound to an English-speaker!)
And that's not even talking about subject-verb agreement, gendered languages, or the variety of plural rules that can also change which specific form we'd translate to based on nearby words/values.
And it's saying nothing about voice and tone, matching the style of communication in your game to the right level of formality or casualness for its brand or the character who's speaking.
Your translation should be done at the granularity of a complete passage of text, not word by word. Say an entire heading or paragraph, or an entire message spoken by a character.
Each place the same text occurs in a different context, it should be given a different underlying localization ID (key), so that it can be translated differently in the two contexts. (eg. if it occurs sometimes as a label on a stat profile and sometimes as a power-up toast in the HUD and sometimes as a column heading in a leaderboard, each of these may take different forms or need to be abbreviated differently to fit — something I ran into myself with gadget names in Splinter Cell Blacklist for example)
This includes if sometimes you want to display the word in a different case, or add a colon at the end like "Strength" vs "STRENGTH: 42" — different languages actually have different rules for how this is done, so it's better to let a translator pick the right way to do it for their language.
Each localization ID should be associated with not just the display text in the source language, but also with a description explaining what it means in the context where it appears. Then a translator can see both these pieces of information and take them into account when crafting an appropriate translation.
And lastly: you should hire a proper translator, a human with the judgement to navigate this context and the expertise to tell good translations from bad, something an automated online tool cannot do for you.
(Also, do not use my translations either — it's been a long time since I studied in French immersion, and so these examples themselves may be inaccurate, or technically valid but inappropriate for regional dialects)
I'd also add: localization is NOT the most boring part of game development. It's laborious, to be sure. But the challenge of identifying all the texts that need translation, organizing them in a way that's intuitive to work with, describing them in a way that's clear to translators, finding ways to assemble dynamic texts with proper gender and numeric agreement, and staying within display length budgets — it's fascinating.
If it's just a stepping stone on your way to your goal, then as Ze Frank says, try to fall in love with the shape of the stone. 😉
(Or hire someone who will — you'll get better localization from someone who's passionate about it than someone who just wants to get it over with!)
=GOOGLETRANSLATE(cell with text, “source language”, “target language”)formula ;-) \$\endgroup\$