International SEO
Multilingual SEO for Small Businesses: Choose Markets, Languages and URLs
Country versus language, URL structures, hreflang reciprocity and a rollout checklist for adding your second (or fifth) market.
By the Seozumi editorial team · · about 6 min read
Adding a second language or country to your website can open real demand, but it is also one of the easiest ways to create duplicate pages, confused search results and content nobody reads. This guide is for small teams that want to expand carefully: how to decide on markets, how to structure URLs, how to use hreflang, and how to localize rather than just translate.
Country and language are separate decisions
A market is a combination of a language and, optionally, a country. They are not the same thing:
- Spanish is spoken in Spain, Mexico, Colombia and the United States, with different vocabulary, prices, currencies and regulations.
- Switzerland has German, French and Italian speakers in one country.
- English for the US (
en-US) and English for the UK (en-GB) share a language but differ in spelling (“color” vs “colour”), terms (“zip code” vs “postcode”), currency and often legal requirements.
Ask two questions separately: Which language does this customer search in? and Does the offer change by country? If you sell downloadable software at one global price, one page per language may be enough. If you ship physical goods, quote local prices or follow local rules, you probably need country-specific pages.
Choosing which markets to add first
Start where you already have evidence instead of where translation is cheapest.
- Open the Performance report in Google Search Console and filter by Country. Impressions from a country you do not target yet are a strong hint.
- Check where existing customers, inquiries and support requests come from.
- Confirm you can actually serve the market: shipping, payment methods, support hours, language skills for replies.
- Look at what local competitors publish. If they answer questions your translated page would not, plan for that work.
One well-maintained new market is better than five neglected ones.
URL structures: pick one and stay consistent
| Structure | Example | Good for |
|---|---|---|
| Subdirectories | example.com/es-mx/ | Most small businesses: one domain, shared authority, simple setup. |
| Subdomains | mx.example.com | Separate teams or platforms per market. |
| Country domains | example.com.mx | Strong local presence, but each domain must be bought, verified and built up separately. |
Avoid relying on cookies, browser language or IP detection to show different content on the same URL. Google usually crawls from US addresses without a language preference, so it may only ever see one version. Give every version its own URL and let visitors switch with a visible language selector.
Translated slug examples
Localize the URL slug as well as the content, using the words customers actually type. Examples:
/en-us/services/water-heater-repair//en-gb/services/boiler-repair/(UK customers usually search for boilers, not water heaters)/es-mx/servicios/reparacion-de-calentadores//es-es/servicios/reparacion-de-calentadores-de-agua/
Keep slugs lowercase, use hyphens, and drop accents if your platform handles them inconsistently.
hreflang: tell Google which version is for whom
hreflang annotations tell Google that several URLs are versions of the same page for different languages or regions, so it can show the right one. Google’s documentation on localized versions of your page is the authoritative reference. The key rules:
- Reciprocity. If page A lists page B as an alternate, page B must list page A. One-way annotations are ignored.
- Self-reference. Each page lists itself as well as its alternates.
- Valid codes. Use an ISO 639-1 language code, optionally followed by an ISO 3166-1 alpha-2 region:
en,en-GB,es-MX.en-UKis not valid; the UK code isGB. - x-default. Add
hreflang="x-default"for the page that should be shown when no version matches, such as a language chooser or your main English page.
Example for the water-heater page, placed in the <head> of every version:
<link rel="alternate" hreflang="en-US" href="https://example.com/en-us/services/water-heater-repair/" />
<link rel="alternate" hreflang="en-GB" href="https://example.com/en-gb/services/boiler-repair/" />
<link rel="alternate" hreflang="es-MX" href="https://example.com/es-mx/servicios/reparacion-de-calentadores/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/en-us/services/water-heater-repair/" />hreflang and canonical tags work together
Each language version should have a self-referencing canonical. A common mistake is pointing the canonical of the Spanish page at the English page; that tells Google the Spanish page is a duplicate and it may drop it, cancelling the hreflang.
Localize, don’t just translate
A literal translation answers the original market’s questions in another language. Localization answers the new market’s questions. For each page, check:
- Search terms. Research keywords in the target language; do not translate your English keyword list word by word.
- Units, currency and formats. Prices in local currency, metric vs imperial, date formats, phone numbers with country codes.
- Local proof. Local addresses, service areas, certifications and examples that make sense to that audience.
- Regulation and claims. Warranty, consumer and health rules differ; have someone qualified review sensitive claims.
- Tone. Formal vs informal address (for example “usted” vs “tú” in Spanish) depends on market and brand.
Machine translation can be a starting draft, but a fluent human should review every page before it goes live.
Rollout checklist
- Choose one new market based on evidence and capacity.
- Decide on the URL structure and the language code for that market.
- Localize the highest-value pages first: homepage, main services or products, contact, pricing.
- Add reciprocal hreflang plus x-default, and self-referencing canonicals.
- Add the new URLs to your XML sitemap and link them from a visible language switcher.
- Inspect a few new URLs in Search Console and check the Pages report after a few weeks. Our indexing checklist covers those checks in detail.
- Plan local content for that market, not just translated pages (see how to find SEO blog topics).
Errors to avoid
- Automatic redirects based on IP that stop visitors (and Googlebot) from reaching other versions.
- hreflang pointing to URLs that redirect, return 404 or are noindexed.
- Mixing languages on one page, such as translated body text with an untranslated menu and footer.
- Launching many half-translated pages at once instead of a few complete ones.
- Treating a country as a language (there is no “Swiss” language code) or using invalid region codes.
Multilingual SEO rewards consistency more than size. Start small, get the technical signals right, and earn each market with content written for the people who live there.
