What Yandex is, and how it compares with Google as a search engine

Most marketing teams in Thailand know the Google rulebook well and have never opened a Yandex results page. This article is a primer on the platform itself: what the company is, how its search engine differs from Google in ways that change how you would actually work, what its other services do, where the advantages and the limits honestly sit, and the narrow set of Thai businesses for which it deserves any attention at all.

You will not find market share percentages, user counts or cost comparisons here. Those figures move, and a number written into an evergreen page is usually wrong within a year. What follows is the mechanics, plus a list of things to go and verify yourself in a current source before you act on any of it.

What Yandex is

Yandex is a Russian technology company that began as a search engine in the early years of the commercial web and grew into a group of consumer and business services. The name is generally explained as a contraction of yet another indexer, with a play on the Russian pronoun that begins the word. Search is the product it is known for, and in its home market it is the search engine most people reach for, but describing Yandex as a search engine understates what it is now.

A closer description is a portfolio company organised around daily-use software. Search sits alongside mapping and turn-by-turn navigation, ride-hailing and delivery, an online marketplace, a web browser, machine translation, cloud infrastructure, a voice assistant, mail, storage and music. In shape, that is closer to Naver in Korea or Kakao than to a pure search business. The services share accounts, share data where users allow it, and appear inside each other, which matters a great deal for how a results page looks.

One structural point worth knowing before anyone signs a contract: the corporate arrangement behind Yandex has changed in recent years, and the entity operating the Russian business is no longer the same company as the one that was listed on a foreign exchange under that name. Anyone entering a commercial agreement should confirm current ownership, the contracting entity and the governing jurisdiction directly, rather than relying on an article.

The other thing Yandex is not: a translated copy of Google. The interface will look familiar, and the general job is the same, but the engineering priorities, the vertical surfaces on the results page and the tooling given to site owners are different enough that treating one as a clone of the other produces bad decisions.

Yandex versus Google as search engines

The comparison that matters to a marketer is not which engine is better in the abstract. It is which one your audience uses, and what changes about your work when you optimise for one rather than the other. The table below sets the two side by side on the dimensions that change day-to-day practice, and the sections after it explain the two that carry the most weight.

Two caveats on that table. First, both engines change, so treat it as a description of emphasis rather than a fixed specification. Second, ranking philosophy is where most comparisons go wrong. Both engines use machine-learned ranking over a large set of signals, both weigh relevance, quality and user behaviour, and neither publishes a formula. The differences are of emphasis and of training data, not of category, and anyone who tells you they know the weightings for either engine is guessing.

Why Russian morphology is a real engineering difference

This is the part that gets skipped, and it is the part that changes how you write and how you build a keyword list.

Russian is a heavily inflected language. Nouns change their ending according to grammatical case and number, adjectives agree with the noun in gender, number and case, and verbs carry aspect as well as person and tense. A single dictionary word can appear in a dozen or more written forms, and the ending is not decoration. It carries the grammatical role, which is part of the meaning. English does very little of this: a plural s, a past tense ed, a participle ing, and not much else.

That difference shows up in how a search engine handles a query. The cheap approach, and the one that works acceptably for English, is stemming: strip suffixes with a set of rules until you reach a stem, then match documents whose words reduce to the same stem. Applied to a language with rich inflection, rule-based suffix stripping fails in both directions. It conflates words that share a stem fragment but mean different things, and it misses irregular forms where the root itself changes, because no suffix rule can connect them.

The alternative is morphology-aware search: run a morphological analyser backed by a lexicon, map each surface form to its lemma plus a set of grammatical features, handle irregular forms by dictionary rather than by rule, and then decide, per query, whether two forms should be treated as the same term or kept apart. Yandex invested in this early because its home language demanded it. Google does inflection work for Russian too. The point is not that one engine ignores morphology and the other does not; it is that one was designed around it from the first version, and the results reflect that heritage.

Three consequences for anyone doing the work:

• Repeating an exact keyword form on a page buys you less than it might in English, because the engine already knows the forms are related. Writing natural Russian is the better strategy, and it is also the harder one to fake.
• A keyword list translated word by word from English will contain the wrong grammatical forms. Volume data pulled against those forms will misrepresent demand. The list has to be built in Russian by someone who reads Russian.
• Case and word order can shift what a query is asking for. Two phrasings that look like the same keyword to a non-speaker can carry different intent, which affects how you group them and what page you point them at.

What vertical integration does to a results page

Both engines fill their results pages with their own services. The practical question for a site owner is which query types still hand a click to an independent website, and the answer differs by engine because the surfaces differ.

When a group owns the maps product, the business listing directory, the marketplace, the navigation app and the media player, a results page can answer many queries without sending anyone anywhere. A local query can resolve inside a map module fed by the group's own business listings. A product query can resolve inside a marketplace module showing offers and prices. A route query goes to navigation. A media query goes to the player. Paid blocks take space at the top and often the bottom.

For an SEO the implication is concrete. The mental model of ten organic positions is a poor guide to what is actually available, and for whole classes of query the winning move is not to rank a page at all. It is to be present inside the vertical: a complete and verified business listing, a marketplace offer with clean data, a product feed the engine can read. That is a different workstream from content and links, with different owners inside a company, and it needs to be scoped separately.

Because results composition varies by country, device, query language and the individual query, none of this can be settled from a description. Run the queries you care about, on the device your customers use, from the market you are targeting, and record what you see. That single exercise is worth more than any general article on the subject, including this one.

The tools a site owner gets, and why you cannot skip them

Every engine keeps its own crawl and index state, and only that engine can tell you what it did with your pages. This is the reason a site targeting two engines needs both toolsets rather than a favourite one.

Yandex Webmaster is the counterpart to Google Search Console. You verify ownership of the domain, submit sitemaps, watch indexing status, see which pages were excluded and the reason given, check how the engine renders your pages, and read the notices it raises about quality problems. It also reports the queries your site appears for on that engine, and an engine-side quality indicator for the site. No third-party rank tracker can substitute for this, because a rank tracker observes the results page from outside and cannot tell you why a URL was dropped from the index.

Yandex.Metrica is the free analytics tag. The part that surprises people arriving from Google Analytics is the behavioural tooling in the free tier: session recording, click and scroll heatmaps, and form analytics. Google Analytics 4 does not include session replay, so teams usually pay a separate vendor for it. Metrica goals also feed the advertising platform, which is why an advertiser on that platform ends up running the tag regardless of what else is on the site.

Two technical details worth knowing before an implementation:

• The crawler identifies itself as YandexBot and obeys robots.txt. On top of the standard directives, the engine supports Clean-param, which tells the crawler that named URL query parameters do not change page content, so variants collapse to one URL. It does the job you would otherwise handle with canonical tags and parameter rules. Canonical tags are also understood, and the sensible approach is to set both rather than choose.
• Structured data based on schema.org is understood, but the product feed format used by the group's marketplace is its own, not the feed format used by Google Merchant Center. A retailer planning both needs two feed builds, and should budget for that rather than discovering it late.

The rule that follows from all of this: never let Search Console data stand in for how another engine sees your site. They disagree, and the disagreement is usually informative.

The main Yandex services and what each one is for

Availability of any individual service varies by market and changes over time, so treat this as a description of what exists rather than a promise about what you can sign up for from Bangkok. Check the ones you care about directly.

• Search and its verticals: web, images including reverse image lookup, video, and a news aggregation surface.
• Maps and Navigator: mapping, business listings and turn-by-turn navigation. The business listing is the local presence surface, the same role a business profile plays elsewhere.
• Yandex Go: the mobility and delivery umbrella, covering ride-hailing and courier services, with food and grocery delivery products alongside it.
• Market: the group's online marketplace, where sellers list products and buyers compare offers.
• Browser: a Chromium-based web browser with its own interface and features, which also distributes the search engine by default.
• Translate: machine translation for text and pages.
• Cloud: infrastructure and platform services for developers, in the same category as other public clouds.
• Alice: a voice assistant, also shipped in the group's smart speakers.
• Mail, Disk, Music, Weather and Calendar: the everyday consumer utilities that keep an account active.
• Yandex Direct and the advertising network: the paid layer, covering search advertising and a partner network for display placements. Relevant Audience covers the execution side of that on its Yandex advertising service page, which is the right place to look for campaign mechanics rather than this primer.
• Webmaster and Metrica: the free tools described above, and the reason a site owner has an account at all.

The advantages, stated plainly

• If your audience searches in Russian in its home market, this is where that demand is expressed. No other channel substitutes for demand capture on the engine people actually use.
• The free tooling is genuinely capable. Session recording and heatmaps at no cost is a real budget line that other stacks charge for.
• One account family covers search advertising, a display network and analytics, which reduces the number of integrations to maintain compared with assembling the same functions from separate vendors.
• Because the engine handles word forms well, well-written natural copy tends to work better than mechanical keyword repetition. That rewards teams who can write properly in the language.
• Many international brands never build for this engine at all, so the competitive set on a given results page is often domestic rather than global. That is a qualitative observation about who bothers, not a claim about cost.

The limitations, stated just as plainly

An evergreen primer that only lists advantages is marketing copy, not information. These are the constraints that decide most cases.

• Language runs through everything. Interface, documentation and support lean Russian. English material exists and is thinner. This is a staffing question before it is a marketing question, and it is the constraint that stops most projects.
• Content has to be written, not translated. Machine output in an inflected language reads as machine output to a native speaker, and it will not carry the register a booking or a purchase decision needs.
• The work does not transfer. Outside Russian-speaking markets this is a minor engine, so effort spent here does not improve your position anywhere else. Compare that with work on Google, where the same page can serve many markets.
• Fewer integrations. Connectors to Western CRM, tag management, BI and bid management tools are sparser. Expect manual reporting or custom development, and price that in.
• Two measurement systems. Running Metrica alongside Google Analytics 4 means two tags, two data models and two definitions of a session and a conversion. Decide in advance which system is the source of truth for each metric, and write the reconciliation method down before launch rather than during the first monthly report.
• Legal, payment and compliance questions are real and are not answerable here. Cross-border advertising into that market raises questions about contracting entities, payment routes, tax treatment and sector rules that depend on your own jurisdiction and industry. Take professional advice for your own situation. Do not take a marketing article, this one included, as clearance to transact.
• Thin local expertise. There are few practitioners in Thailand, so the options are training someone, hiring remotely, or working with a partner who already has the capability.

Why a Thai business might care, and why most should not

The realistic audience in Thailand is narrow: tourism operators, hotels and resorts, clinics and wellness businesses, and retail or property businesses that already serve Russian-speaking visitors. If Russian-speaking demand already reaches you and you can serve it in Russian, there is a case for being findable on the engine those visitors use at home, and the destination and property angles are covered in more depth on the tourism marketing and hotel marketing pages.

For every other Thai business, whose customers search in Thai or English, this is not a priority and should not take budget or attention away from Google Ads, organic work on Google, or display advertising. Saying so is not modesty about a channel. It is the correct answer for most readers of this page.

Before treating it as a live option, check that all of the following are true:

1. A measurable share of your customers or enquiries already comes from Russian speakers, visible in your own analytics rather than assumed from a news story.
2. Someone on the team, or a partner, can write Russian and answer enquiries in Russian at the speed a customer expects.
3. You can offer a Russian-language landing experience with real copy, not an English page with a translate widget bolted on.
4. Pricing, booking and payment can be completed by a Russian-speaking customer without a phone call in English.
5. The legal and payment questions have been answered by a professional for your own jurisdiction and sector.
6. You can measure the channel separately from Google, and you have agreed what a result is worth before you spend.

If two or more of those are missing, the honest answer is not yet. Fixing the missing ones is the project, and the advertising comes after.

What to verify yourself before deciding anything

This page deliberately contains no figures, because the figures are exactly what changes. Here is what to look up, and where.

• Current search engine share in the specific country you are targeting, from a current source with a stated methodology, not from an article that cites another article.
• Whether the specific products you need are available to a business registered in your country, confirmed on the platform itself.
• Current account, billing and eligibility rules for the advertising platform, which change more often than editorial content does.
• Current documentation for Webmaster, Metrica, robots directives and feed formats before an implementation, because implementation details drift.
• Your own data first: language and country reports in your analytics, and the query languages already showing in Search Console. If there is no Russian-language demand there, that is the answer.

On cost, be careful. There is no reliable public benchmark for what a click or a lead should cost a Thai advertiser on this platform, and any figure quoted as one is either from a different market, a different category or a different year. Derive your own ceiling instead: take what a booking or an order is genuinely worth to you, take your conversion rate on comparable traffic, and work backwards to the most you can pay for a click. Then run a small test and compare what actually happens against that ceiling. That number is yours and it is true, which is more than can be said for a benchmark copied from a slide.

Frequently asked questions

Is Yandex just the Russian version of Google?

No, and treating it that way leads to poor decisions. The two do the same job and look broadly similar, but the language engineering, the mix of the company's own services inside the results page, the webmaster and analytics tools and the feed formats all differ. A site that ranks well on one engine is not automatically visible on the other, and the diagnostic tools you would use are different products.

Do I need a completely separate website in Russian?

Usually no, a properly built Russian-language section of your existing site is enough. What matters is that the Russian pages have their own indexable URLs, correct language annotation so each version is served to the right audience, and copy actually written in Russian rather than machine translated. A separate domain adds cost and splits authority, and it is rarely the first thing a business in this position needs.

Can I use Google Analytics instead of Yandex.Metrica?

You can measure the traffic in Google Analytics, but you will still want Metrica for two reasons. The advertising platform reads Metrica goals for conversion optimisation, so campaigns run worse without it, and the free behavioural tooling, session recording and heatmaps, has no equivalent in the free Google product. Running both is normal, provided you decide in advance which one is the reference for each number.

Is Yandex available in Thailand?

Availability differs by product and changes, so check each service directly rather than assuming. The search engine is reachable from most places as a website, but consumer products such as mobility and delivery operate only in the markets where the group runs them, and business products can have their own country and entity requirements. Confirm on the platform for the specific service and the specific country before planning around it.

Should a Thai business with no Russian-speaking customers use Yandex at all?

No. If your customers search in Thai or English, your search work belongs on the engine they use, and the effort is better spent on Google search and paid, on your website experience, and on the channels that already produce enquiries. Adding a second engine with a language barrier attached, for an audience you do not have, is a way to spend money and learn nothing.