Multilingual SEO for translated websites

A translated page can be well written and still invisible in search. Usually the reason is technical: the search title is still in English, or the page tells Google that it is a copy of the English version. This page separates what Allinaa delivers in Premium localization from what stays with your website, and points to Google's own documentation for the second part.

Why translated pages need their own titles and descriptions

In search results, people see a title link and a short snippet, usually taken from your page title and meta description. Google's guidance on title links and snippets asks for titles and descriptions that are descriptive, concise and unique to each page. For a localized page, that means they should be written in the target language, not left in English.

A literal translation is often not enough either. People search with the words they actually use, and those differ between countries that share a language. A moving company's "free moving quote" might be searched as "presupuesto de mudanza" in Spain but as "cotización de mudanza" in Mexico. A title that reads well to the people you want to reach is worth more than a word-for-word copy of the English one.

Included in Premium localization: SEO titles and descriptions

Premium localization (from $500 per project, up to three languages) includes SEO titles and descriptions for the pages we localize. In practice, for each page we:

• write a title and a meta description in the target language, using the wording local customers use for your service;
• keep your brand name in the same place on every page;
• keep them short enough to read well in search results, and unique across your pages;
• check that the title matches what the page actually says, so visitors are not surprised when they arrive.

Standard localization (from $300 per project, one language) covers the page text reviewed by a person and adapted for local customers, without the SEO titles and descriptions. Both tiers are described on the website localization page and in the pricing section.

Your side: hreflang, canonicals and sitemaps

These settings live in your site's code or platform settings, so your web developer or your website builder handles them. Here is what Google's documentation asks for.

One URL per language

Google's guide to multi-regional and multilingual sites recommends a separate URL for each language version rather than switching the language with cookies or browser settings. Common patterns are folders such as /es/, subdomains, or separate country domains.

Hreflang annotations

Hreflang tells Google which pages are language or regional versions of each other. According to Google's page on localized versions, each version should list itself and all the others, the links must point both ways, and an x-default value can name the page for visitors whose language you do not cover. You can add them as HTML link tags, HTTP headers or in your sitemap. In HTML, a page set might carry:

<link rel="alternate" hreflang="en-us" href="https://example.com/" />
<link rel="alternate" hreflang="es-mx" href="https://example.com/es-mx/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/" />

Canonical tags

Each language version should declare itself as canonical. Google's page on consolidating duplicate URLs says that when you use hreflang, the canonical page should be in the same language. If your platform already has a multilingual feature, check whether it adds these tags for you before adding a second set by hand.

Sitemaps

List the URL of each language version in your sitemap so search engines can find the localized pages, and submit the sitemap in Google Search Console.

Common mistakes

• One canonical shared by every translation. If the Spanish and German pages all point their canonical at the English page, you are telling Google they are duplicates, and the English page may be shown instead.
• Automatic redirects by location or browser language. Google advises against them in its multilingual guide: visitors cannot reach the version they want, and crawlers may never see the other versions. Its page on locale-adaptive pages notes that Googlebot generally crawls from US addresses. Offer a visible language switcher instead.
• Hreflang without return links. If page A names page B but B does not name A, the annotations can be ignored.
• A translated body with an English title and description. This is the gap Premium localization closes.
• Mixed languages on one page. Google identifies a page's language from its visible content, not from the lang attribute, so a Spanish article inside English navigation and English buttons sends a mixed signal. See the multilingual guide.

Visitors who arrive in their own language

When search brings people to your localized pages, they will ask questions in that language. The Allinaa website assistant answers in the languages you configure, from the business information you approve. Read how to choose chatbot languages, or try it with the 14-day free trial at bot.allinaa.com/start.

Getting a quote

Send us the list of pages to localize, the target languages and countries, and any search terms you already know your customers use. Tell us too whether your site already has language versions or hreflang, so we can write titles that fit your structure. Use the contact form or write to info@allinaa.com. You will know the final price before any work starts.

Frequently asked questions

Does Allinaa add hreflang tags to my website?

No. Premium localization includes SEO titles and descriptions for the localized pages. Hreflang, canonical tags and sitemaps are set up by your web developer or by your website platform. We can tell your developer which pages belong together.

Should the URLs be translated too?

It is optional. What matters most is that each language version has its own URL. Readable words in the visitor's language are fine, but a stable URL that never changes is more important than a translated one.

Will my translated pages rank on the first page?

Nobody can promise that, and we do not guarantee rankings or traffic. Good titles and descriptions, correct language signals and genuinely useful localized content give the pages a fair chance to be shown to the right people.