Multilingual rollout for regional dealership: 3 of the top 10 organic-traffic pages now in non-English.

A regional commercial automotive dealership with multiple locations across Western New York came to us about adding multilingual to their site. The business case they had in mind was straightforward: there are growing non-English-speaking communities in their markets, and they wanted to be able to serve customers in their preferred language. The SEO angle wasn’t on their radar. Multilingual was, in their thinking, an audience-reach play, not a search-traffic play.

What actually happened surprised everyone, including us.

The setup.

The client serves Buffalo, Rochester, Syracuse, and surrounding markets with commercial vehicles for fleet operators, owner-operators, and municipal customers. They’re a major regional player in a competitive industry where local SEO matters a lot. Most of their organic search traffic was coming from terms tied to their service area: commercial vehicles models, parts and service, dealership locations.

Western New York’s market dynamics shape what multilingual means here in ways that matter to the SEO outcome. The region’s metro areas (Rochester, Buffalo, and Syracuse) all have substantial non-English-speaking populations. Rochester is a major refugee resettlement city with significant Spanish, Burmese, Karen, Somali, Nepali, and Arabic-speaking communities. Buffalo has densely-populated immigrant neighborhoods with growing Spanish-speaking and various Asian and African language communities alongside a legacy Polish population. Syracuse has Bosnian, Vietnamese, and Caribbean diaspora communities. The total non-English-speaking population across the region is in the hundreds of thousands. For a commercial vehicle dealership, that customer base includes business owners, fleet operators, owner-operators, and municipal contacts whose preferred language for substantial business decisions isn’t English.

Their existing site was English-only. There wasn’t a specific known problem with non-English-speaking customers, no flood of inquiries getting missed, no documented business case for translation. The multilingual conversation started from a simple understanding that the regional non-English-speaking population was large, the cost of adding multilingual was modest, and the potential upside on SEO and audience reach was worth exploring even without a known unmet demand.

The architectural approach.

A multilingual rollout that works for SEO is fundamentally different from a multilingual rollout that just bolts translation onto an existing site. The architectural decisions made at launch determine whether each language version becomes its own indexable search-engine surface or just a translation overlay that Google can’t really see.

The decisions that mattered for this client:

URL structure. Each language version got its own subdirectory path rather than living as a fragment of the English URL or behind a query string. Subdirectory URLs let each language version accumulate independent SEO authority while still benefiting from the domain’s overall authority.

hreflang declarations. Every page in every language got proper hreflang meta tags telling Google which page corresponds to which language version. Without these, Google guesses, often wrong, about which language version to show to which user. With them, each language version stands alone in its language’s search results without competing against the English version for the same query.

Translated metadata. Page titles, meta descriptions, and image alt text all got translated alongside body content. The metadata is what Google uses to decide whether a page is relevant to a search query, so untranslated metadata leaves each language version effectively invisible to non-English search even if the body content is translated.

Per-language sitemaps. Each language version got its own XML sitemap referenced from robots.txt. The sitemaps tell Google explicitly: here are the canonical URLs for each language, here’s their structure, here’s how often they change.

What we built.

We integrated multilingual on their existing site using a tooling stack that fit the client’s editorial workflow. Cloud-based translation handled the bulk of the content (titles, descriptions, body copy across many pages of vehicle inventory and service information), with the option for human review on the highest-value pages where machine translation might miss industry-specific terminology. The translation tooling integrates with the WordPress admin so editors don’t need to learn a separate translation system; they publish in English and the translations flow through the same workflow.

The hreflang and URL structure work was all set up at launch so the foundation didn’t have to be migrated later as the site grew. Adding additional languages in the future is incremental rather than architectural, because the structure already supports them.

Why the SEO mechanism works the way it does.

The mechanism behind the surprising outcome is something most US-based businesses don’t intuit. Google detects when a search user’s browser or account is set to a non-English language and dramatically prefers results in that language. The preference isn’t subtle. It’s a major ranking signal that can elevate a less-authoritative page in the matching language over a more-authoritative page in English.

In a market where almost every competitor is English-only, being the one result available in the user’s preferred language is a meaningful ranking advantage. The competition in non-English SERPs is dramatically thinner than the equivalent English SERPs. A US service business that ranks middling-to-good in English SERPs (against dozens or hundreds of competitors) frequently ranks at or near the top in Spanish SERPs (against a handful of competitors) for the equivalent queries.

There’s also a multiplication effect from long-tail queries. Every long-tail query the English version captures has translated equivalents in every language version. A site that ranks for 500 English keywords often ranks for thousands of combined keywords across English and one or two non-English languages, because the long tail is bigger when it spans languages.

The surprising outcome.

Within months of launch, 3-4 of their top 10 organic-search traffic pages were in languages other than English. Not just bringing in modest incremental non-English traffic alongside the existing English traffic, but rising into the top tier of overall site traffic.

This is exactly the kind of outcome that’s hard to predict ahead of time, because the SEO mechanism doesn’t depend on there being a known unmet demand. The non-English search results appear, get clicks from users whose Google language preference matches, and the engagement signals reinforce the rankings over time. The audience reach happens whether or not the business was aware of it as a gap before launch.

And critically, the English-language pages didn’t lose ground. The non-English versions added incremental traffic on top of the existing English-language performance rather than displacing it.

What this case study illustrates.

Multilingual is one of the most underrated SEO moves available to a US-based business. The conventional thinking treats it as audience-reach work that’s only worth doing if there’s a substantial known non-English-speaking customer base to serve. The reality is that the non-English-speaking audience is almost always larger than the business assumes, the SEO competitive landscape is dramatically thinner in non-English SERPs, and the same site infrastructure that serves the English audience can serve all the language versions with the right architectural decisions made at launch.

Read more about going multilingual for SEO and the architectural decisions that determine whether the multilingual investment compounds.