Guides · Search
SEO localization: a practical guide to getting found in other languages
SEO localization means adapting your website to how people search and buy in another language or market. Start with a page that already helps customers, find the questions your new audience asks, and adapt the page around them. Then make sure visitors and search engines can reach the translated version. This guide walks through nine steps, with short examples you can apply to your own site.
Step 1: Choose one market and a few pages worth translating
Start small. Pick one market you can serve, and a handful of pages with a clear customer need, a product that fits it and an obvious next action. Your sales enquiries, the languages your customers already write in and the countries that appear in Search Console are good places to look.
Example: a business selling label-design software could begin with its product page, its pricing page and a guide to preparing print-ready labels. Translating an unrelated blog post that happens to get a lot of traffic may bring visitors who will never need the product.
What you have at the end: a short list of pages, the audience each one serves, and the action each page should lead to. You do not need to translate the whole site before you know whether a market responds.
Step 2: Find the searches behind the translation
A keyword translated word for word is often not what people in the other market type. Research the wording first:
- Write down the problem the page solves, in one sentence.
- Ask someone who knows the target language for several ways a customer would describe that problem.
- Search those phrases in the intended country and language.
- Note what the results are: tools, tutorials, agencies or product comparisons. That is what searchers expect to find.
- If you have a keyword tool, check the demand for each phrase, and write down the tool, the country, the date and the estimate.
- Keep the phrases that describe the same customer task. They belong on one page.
Example, in English to show the method (it says nothing about demand in another language):
- translate a website: the searcher wants a method or a tool, so the page explains the approaches.
- translate a website without coding: they want a setup they can do themselves, so the page shows the steps and where the limits are.
- keep website translations updated: they have a workflow problem, so the page explains how changes are found and checked.
If one search wants a tutorial and another wants a product comparison, they may deserve different pages. And translating this list would not be local research: the other market's phrases have to come from that market.
Step 3: Make the page answer the search
Search intent is what someone expects to find after they click. Start with the headings: a reader skimming the page and a search engine both use them to decide what the page is about.
- Vague: Our international solution
- Specific: Keep your website translations updated as your content changes
Then the opening paragraph. It should answer the question in the reader's own terms before it says anything about you. Under the specific heading above, for example:
When you change a product description, its translations can fall behind. A repeatable review process helps you find the changed text, update the affected languages and check the result before it goes live.
In the target language, write the headings, the example and the call to action from the research in step 2, not only the sentences.
A translation can be fluent and still answer a question that market never asks.
Step 4: Adapt the search title, description and next action
The title names the page's purpose, the description says why to visit, and the heading on the page confirms the promise. The next action tells the reader what to do once they agree.
Example for an English page:
- Title: Website Translation Without Coding: A Practical Guide
- Description: Compare ways to translate your website, review the wording and keep each language up to date. Start with a few important pages.
- Heading (H1): How to translate your website without coding
- Next action: Choose the setup that fits your website
Each language needs wording that makes sense to its own audience, from its own research, not a literal translation of the English title. Google may show a different title or snippet from the one you wrote, and the description is not a ranking factor in itself: its job is to earn the click once the page is shown.
Step 5: Give each language a page people can reach
A simple test: copy the address of a translated page and send it to someone. They should see the same language straight away, without changing a setting first. That takes one address per language, for example:
- English: example.com/en/website-translation/
- German: example.com/de/website-translation/
A translated slug (a German word in the German address) can help, but a translated address is not the same as translated content. The example keeps the path the same to show the separate addresses.
What about translation done in the browser with JavaScript? Google can read content that JavaScript produces. The problem comes when another language appears only after a visitor clicks a button or changes a preference: Google may never reach that version. A separate address that reliably opens in its language is a much stronger foundation, and delivering the translated text in the page's first HTML removes the dependence on rendering. WordPress has no single translation mechanism either, so look at how your plugin and its settings publish each language. Google explains the details in its guides to JavaScript SEO and multilingual sites.
Step 6: Connect the language versions with hreflang and a canonical
These two labels are the core of multilingual SEO:
- hreflang connects the equivalent pages in different languages, so a search engine can show the German reader the German version.
- A canonical names the preferred address of a page. Each language version names itself. A canonical that sends every translation back to English tells search engines to ignore the translations.
An optional x-default names a fallback page for readers whose language you do not cover; not every multilingual page needs one. Hreflang helps a search engine choose the right language version, but it does not get a page indexed or ranked on its own. Use real, published addresses. Google's guide to localized versions has the full rules.
On the German page. The English page carries the same two alternate links and its own English canonical.
<link rel="canonical"
href="https://example.com/de/website-translation/">
<link rel="alternate" hreflang="en"
href="https://example.com/en/website-translation/">
<link rel="alternate" hreflang="de"
href="https://example.com/de/website-translation/">Step 7: Check the page before you promote it
- Open the translated address in a fresh browser session: it should open in its language.
- Read the title, the heading, the navigation, the body and the next action in that language.
- Ask a reader of the target language whether the page answers the question it was written for.
- Follow the important internal links: they should lead to pages in the same language.
- Confirm the page may be indexed, is linked from your site and is listed in the sitemap.
- Run URL Inspection in Search Console on the address to see whether Google can fetch it and what it renders.
The page source shows the first HTML only, not everything Google can render with JavaScript. A successful live test proves Google can reach the page, not that it is indexed yet.
Having a person read the page before it goes live is a quality decision, not a Google requirement: machine translation is not barred from search. What counts is whether the page is useful and accurate, and whether you control what gets published.
Step 8: Keep the page useful when the source changes
A page that ranks will be edited. If a delivery promise changes from five days to ten, it has to change in every published language: a translation can be fluent and still be wrong because the source moved on.
- Find the pages and languages the change affects.
- Update the affected text in each language.
- Have a person read the changes that carry weight: prices, promises, terms.
- Check the published result.
The continuous localization guide follows one page through a change.
Step 9: Measure the visits that matter
In Search Console, filter by page and by country. With a separate address per language, each translated page is its own row: you see which searches show it, where those searchers are and where it ranks. More impressions can mean wider visibility, but they do not prove on their own that you reach more buyers. Watch whether visitors take the next step.
Use the same analytics events everywhere, such as a trial start or a contact form, with the page and the language recorded alongside. A separate event name for every translated page is unnecessary. Check access and indexing right away; judge rankings over several comparable weeks, not day to day.
Steps 5 and 6
The WordPress plugin and the proxy publish each language as its own page
Two Lionrapid routes render every language before it reaches the browser, so each language has its own address and its text is in the first HTML. The WordPress translation plugin serves each language under its own path for every post type, sets the html lang attribute, a canonical per language and hreflang with an x-default, translates the title, the description and the Open Graph tags, and hands its canonical to Yoast, Rank Math or AIOSEO where one is installed. The edge proxy does the same for any website it sits in front of: language paths, hreflang, canonical and og:url rewritten to the public address, translated title and meta, and the names, headlines and descriptions in product and article structured data. Setup for each is in how to translate your website.
- Language paths per post type
- hreflang + x-default
- Canonical per language
- Translated title, meta, OG
Who does what
What Lionrapid automates, what you choose, what needs judgement
Automated: language addresses, hreflang and canonical, translated title and meta, the language switcher, a cache purge when new translations arrive, and serving only the rows marked ready. Chosen by you: the language list, which languages stay out of search until you have read them, the paths left untranslated, the switcher style. Editorial: the research per market (steps 1 and 2), the rewritten headings and calls to action (steps 3 and 4), and which pages get a translator and which ship after your own read.
- Automated: addresses, tags, serving
- Chosen: languages, hold-backs, exclusions
- Editorial: research, headings, review
Step 7
Keep a language out of search until you have read it
A translation reaches visitors only once it is marked ready: by a person, per row or per language, unless you set the project to publish straight after machine translation. A language still in review can also be kept out of search engines: the proxy serves it with a noindex header and leaves it out of hreflang and the sitemaps, and the plugin applies the same setting from the server. Release it when the pages read right, and the signals appear on the next crawl.
- Ready rows only
- noindex while in review
- Out of hreflang and sitemaps meanwhile
Step 8
Changed sentences are found for you
When a page changes, only the changed sentences need translating again. On a website an edited sentence is new text: it shows in the source language until its translation is marked ready, so an old promise never lingers in another language, and the approved sentences around it stay as they were. The cache is purged when the new translation arrives. The continuous localization guide shows the whole cycle.
- Changed sentences only
- Approved text kept
- Cache purged when it arrives
FAQ
SEO localization, answered
SEO localization, also called localization SEO, is adapting a page so that people in another language or market find it and act on it: the wording they search for, a page written around that wording, and a published language version that search engines can reach and connect to the original. Translation is the middle of it, not all of it.
Translation carries the meaning across; SEO translation usually means translating the text with keywords in mind. SEO localization starts earlier and ends later: it researches what people in the market search for, adapts the headings, examples and call to action around it, and publishes each language so it can be found. Multilingual SEO is the technical part of that last step: an address per language, hreflang and a canonical per language.
Start from the problem the page solves, not from your English keyword. Ask someone who knows the language how customers describe that problem, search those phrases in the target country, note what kind of pages come up, and check the demand in a keyword tool if you have one. Keep the phrases that share one customer task on one page. Step 2 above has the method and an example.
Google can read content that JavaScript produces. The risk is a language that appears only after a click or a stored preference: Google may never reach it. A separate address per language that opens in that language, with the translated text in the first HTML, is the stronger foundation. The Lionrapid WordPress plugin and edge proxy publish every language that way.
Hreflang is a label in the page head that connects the equivalent pages in different languages. Every language version needs it, pointing at each of the others and at itself. Whether you write it by hand depends on your tool: the Lionrapid WordPress plugin and edge proxy add hreflang, an x-default and a canonical per language on their own.
No. A translated page is eligible to rank; whether it does depends on the wording, the competition in that market, the rest of the site and time. What a good setup gives you is the technical half: each language at its own address, in a form search engines can index, with the signals that tell them which language is which.
In Search Console's performance report, filter by page for the language address and by country for the market. If the English page shows for searches in the other country, check the hreflang on both versions, check with URL Inspection that the translated page is indexed, and check that your internal links lead readers to the right language.
The WordPress translation plugin renders each language on your server under its own path, sets lang, canonical and hreflang, translates title, meta and Open Graph, adds alternates to Yoast sitemaps, and purges the common cache plugins when a new translation arrives. Its page lists the settings and a checklist for before you publish.
Publish your first language the way search engines can read it
Website routes are on every paid plan, from EUR 9.90 a month; every signup starts free with 3,000 words of documents.