The Challenge
This client operates a driver recruitment business in a niche that barely existed in Polish search: Russian-speaking taxi drivers looking for work in Warsaw, Kraków, and Wrocław. Their previous site had zero local SEO and no multilingual pages. Recruitment ran through Russian-language Telegram groups and word of mouth, but the website — the one place a driver would go to verify the company was real before handing over their documents — was invisible to the exact audience it needed to reach.
The problem wasn't a lack of demand. Drivers were searching constantly, in Russian, using phrases no generic Polish SEO campaign would ever target — city-specific, language-specific, and often phrased around eligibility ("driver job Warsaw without Polish") rather than the generic terms a translation tool would produce. None of that volume was being served.
Why Translation Wasn't Going to Work
The client had tried a version of this before, running their existing Polish site through a translation plugin. It technically produced Russian text, but it read like translated text — stiff, occasionally imprecise, and missing the specific phrasing drivers actually type into Google. Translated SEO content ranks poorly for the same reason translated ad copy converts poorly: it optimizes for what a page says, not for what a real person searching for that page actually says. We didn't patch the existing translation. We rebuilt the targeting from the query up — starting from what a Russian-speaking driver in Praga actually types at 11pm, looking for work tomorrow.
Research Before a Single Page Was Built
Before writing anything, we ran a full local-intent keyword audit across all three target cities, in Russian, Polish, and Ukrainian, cross-referencing search volume against the actual job-posting language used in Russian-speaking driver communities online — not just what a standard keyword tool suggested, but what the audience itself was already saying. That produced a working list of roughly 40 core phrases per city, split by intent: direct job search, company verification ("is this legit"), and requirements lookup — documents, licensing, vehicle type.
Three Cities, Three Landing Pages — Not One Page Translated Three Times
Instead of a single generic careers page, we built three separate city-specific landing pages — Warsaw, Kraków, Wrocław — each with its own URL, its own localized content, an embedded map, and a city-specific FAQ block addressing the exact concerns that surfaced during research: working hours, payout schedule, whether Polish language fluency was required. Each page targeted its own city's search cluster instead of all three competing against each other for one blended set of keywords.
Google Business Profile as the Anchor
For a recruitment business with no storefront customers physically visit, Google Business Profile isn't a nice-to-have — it's often the first thing a skeptical driver checks before trusting the company enough to apply. We built out a complete profile for each city: verified address, accurate categories, Russian and Polish business descriptions, weekly posts, and a structured review-generation process so drivers who'd already been placed could leave a quick review in their own language. All three profiles were fully verified and indexed within the first month.
The Citation Layer
We ran a structured citation campaign across Warsaw-specific business directories, prioritizing platforms with real local search authority over generic global directories that add volume but little ranking signal. Consistency mattered more than quantity — name, address, and phone number had to match exactly across every listing, since inconsistency is one of the most common reasons local rankings stall even when the content itself is strong.
Timeline
Month 1 was foundation: keyword research complete, all three landing pages live, Google Business Profiles verified and optimized, citation submissions underway. By month 2, we saw the first ranking movement — branded terms and long-tail city-specific phrases started appearing on page one. Month 3 was where it compounded: the primary Russian-language driver recruitment keyword for Warsaw hit position #1, and Google Business Profile impressions were already climbing sharply as profile authority built up. By month 4, that #1 position held, organic traffic across the three city pages was up 340% against the pre-campaign baseline, and profile impressions had grown 8×.
Adding Ukrainian Without Diluting the Core Campaign
Midway through the engagement, the client asked whether it was worth adding Ukrainian-language pages alongside Russian and Polish, given the growing Ukrainian-speaking population in all three cities. Rather than duplicating the existing city pages with a straight translation — the exact mistake we'd already fixed once — we ran a smaller version of the same research process: a focused keyword audit for Ukrainian-language driver search terms, checking how much they actually overlapped with the Russian-language terms already ranking. The overlap was partial, not total, which meant a translated Russian page would have missed a meaningful slice of Ukrainian search intent entirely. We built dedicated Ukrainian sections into each city page rather than a fourth full site, keeping the campaign focused instead of spreading it thin across near-duplicate content.
Common Mistakes We Deliberately Avoided
A few decisions here mattered as much as what we built. We avoided stacking all three cities onto one page with a language switcher, which would have diluted local relevance for each one individually. We avoided over-optimizing anchor text across the citation campaign, which search engines increasingly treat as a manipulation signal rather than a ranking boost. And we avoided declaring victory at the first ranking jump in month 2 — local rankings for competitive recruitment terms can be volatile in the first eight weeks, and reporting a premature win would have set the wrong expectation for what "stable #1" actually looks like by month 4.
The Result
+340% organic traffic in four months. Position #1 in Warsaw for the primary Russian-language driver recruitment keyword. Google Business Profile impressions up 8× over the same period. But the number that mattered most to the client wasn't traffic — it was applications. More qualified drivers found the site through a search they'd typed themselves, in their own language, and converted into applicants without the company running a single additional paid ad in that market.
What This Case Confirms
The lesson here isn't really about taxis. Multilingual SEO done properly isn't translation with extra steps — it's separate research, separate content, and separate pages built around how each language community actually searches, rather than retrofitting an existing English or Polish structure. That's the same approach we bring to every multilingual client, regardless of industry.