Multilingual Website SEO: English and Spanish Setup Without Duplicate-Content Penalties

Multilingual website SEO sounds like a technical specialty, and parts of it are. But most of what goes wrong comes from three early decisions made in a hurry: how the languages are arranged in the URLs, whether the pages tell Google about each other, and whether the translation was done by a person or a plugin. Get those right and the rest is routine.

In the US, the second language that matters most for most businesses is Spanish. The US Census Bureau reports that more than 40 million people in the country speak Spanish at home, and a large share of them search in Spanish. A site that serves only English quietly turns that audience away. Here is the setup I recommend, and the mistakes I see most often.

Multilingual website SEO: why English and Spanish is the US default

The question is not whether a second language is worth it. It is which one, and for whom. Spanish suits businesses serving local households: home services, health, legal, education, restaurants. If you export or run an IT company, your second language may be German, French, or Ukrainian. The structure below works for any pair.

The quote travels because it is true. Customers buy in the language they think in. A translated site is not a courtesy. It is a sales channel.

Multilingual website SEO: choose your URL structure first

This is the decision that is hardest to undo, so make it before you build. There are three common structures.

For nearly every small business, I recommend subdirectories. You keep one domain, one set of backlinks working for both languages, and one site to maintain. Pick the version with the language folder in the URL, such as /es/, and keep it consistent.

Multilingual website SEO: hreflang without the headache

Hreflang is a small annotation that tells Google "this page also exists in Spanish, here." Google documents it in its guide to localized versions of your pages. The rules are short, but they are strict:

• Every page lists all its versions, including itself. The English page names the Spanish one and itself.
• The links are reciprocal. If English points to Spanish, Spanish must point back.
• Use valid codes, like en-us and es-us, and add an x-default for visitors who match neither.
• Point to canonical URLs, never to redirected or noindex pages.
• Match page to page. A translated services page points to the services page, not the homepage.

Multilingual website SEO: translate, do not just convert

Machine translation is a draft, not a deliverable. It gets the words right and the selling wrong. A Spanish page for a roofing company in Texas should not read like a manual from Madrid. Use a native speaker who understands your trade, and translate the parts that rank: titles, meta descriptions, headings, alt text, and URLs.

The same rule applies to everything on the page: forms, buttons, error messages, and the checkout. One English "Submit" button in a Spanish form tells the visitor nobody finished the job.

Multilingual website SEO: the duplicate-content myth

People often ask about the "duplicate-content penalty" for translated pages. There is no such penalty for translations. A Spanish page and its English counterpart are different content in different languages, so Google treats them as separate pages that serve separate audiences. The real risks are narrower:

• Untranslated text left on a Spanish URL, which makes two near-identical English pages.
• Missing hreflang, so Google guesses which version to show.
• Automatic redirects by IP or browser language, which block crawlers and trap visitors in the wrong version.

Let people switch languages with a visible link instead of forcing them. It is better for users and better for crawlers.

Multilingual website SEO: the launch checklist

1. Subdirectory structure chosen and applied to every page.
2. Hreflang on every page, reciprocal, with an x-default.
3. Titles, descriptions, headings, URLs, and alt text translated by a person.
4. A language switcher on every page, linking to the matching page.
5. A separate sitemap entry or section for each language, submitted in Search Console.
6. No automatic language redirects.
7. The
   25-point SEO audit
   run on both versions.

Multilingual website SEO: what we built for City Profit

Our sister company City Profit runs a bilingual site with English as the default and Ukrainian under /uk/. It is a subdirectory structure with its own language sitemap, human-translated titles and descriptions, and a visible switcher. The principle is the same one I recommend for English and Spanish, and the portfolio shows what the underlying SEO method delivers, including a first-page Google ranking in 30 days on a rebuilt one-page site.

If you are planning a bilingual site, think about it at build time. Retrofitting a second language into a site that was not built for it is much harder, which is one reason redesigns go wrong, as I describe in my redesign guide. Monika SYSTEM is $2,000, built on your own infrastructure with the SEO foundation included, and a second language is a scoped addition we price openly. Monika WAAS is $99 a month for a managed single-language site. Compare costs in how much a business website costs, check the FAQ, or tell us about your market.