Academy › Courses › Get found on Google
My website in two languages, done right for Google
Knows how to decide whether your business needs a second version in another language and how to set it up so Google shows each visitor the version in their language. Knows what to translate word for word and what to rewrite because it just doesn't sell the same way in another language.
A customer has written to you in English, or you're seeing visits coming from abroad, and you're wondering if you need an English version of your website. You're not sure if it's worth setting up, where it should live, whether it's enough to run your text through a translator and publish it without a second look, or how Google knows which version to show to whom.
This course walks you through that decision from start to finish. First, you look at your own visits and messages to find out if you really need it, not just because it seems like a good idea. Then you decide where that second version will live and check that it carries the signal that tells Google which version to show for each language. If a platform built your website, that language signal is something it either includes or doesn't, so ask them what your site has before you start. Next, you separate what you can translate word for word from what you need to rewrite because people don't search or buy the same way in English. And by the end, you'll know how to check whether that English site is actually bringing you anything real.
This is for anyone who already gets visits, messages, or customers from other countries and isn't sure if an English-language site is worth building; it's not for anyone who doesn't yet have their Spanish-language site up and running.
- Decide if your business needs an English version by looking at the visits and messages you already get, not a gut feeling
- Choose between a folder, a subdomain, or your own domain for that version, and be able to explain why
- Check that your website carries the signal that tells Google which version to show people searching in each language
- Separate which text to translate word for word and which to rewrite because things don't sell the same way in English (price, currency, trust)
You should already have your Spanish-language site published and live.
The 6 lessons
In the order it makes the most sense to read them.
- 1
The test to run before you translate a single word
You'll know how to read the visits, the messages, and what sells to decide whether you really need a website in English, instead of building one on impulse.
5 min - 2
Folder, subdomain, or your own domain: where your English version lives
You'll leave knowing whether your English-language site belongs in a folder, a subdomain, or a new domain, and why a folder is the default choice for almost everyone.
7 min - 3
The signal that tells Google which version of your website to show in each language
You'll end up with both versions of your website pointing to each other in the code, so Google shows each visitor the one in their language.
6 min - 4
What you translate word for word and what you rewrite because that's not how people search here
You'll know which text on your English website needs to be written straight from real search terms, and which parts you can simply translate well.
6 min - 5
The price in pounds, the review in English: what convinces someone who's not from around here
You'll know which currency, date format, trust signal, and contact method to adapt in the English version so visitors don't just understand the site, but actually trust it.
7 min - 6
How do you know if the English version is bringing you anything
Decide whether to keep, expand, or take down the English version based on where your visitors are coming from and the real contacts it brings in, not just the feeling of having a complete website.
7 min