Skip to content
Envize

← Back to blog

SEO5 min readBy Envize Team

Hungarian SEO is broken in most keyword tools — here's what to do

Agglutinative morphology, ő/ű characters, and stemming blind spots mean Ahrefs and Semrush systematically under-report Hungarian search volume. A field guide.

If you run keyword research for Hungarian queries the same way you do for English ones, you'll be wrong by a factor of two to ten. The problem isn't the tools — it's that Hungarian is a fundamentally different kind of language, and the major SEO platforms haven't caught up.

Here's the field guide we use on every Hungarian SEO engagement.

Why Hungarian breaks everyone's assumptions

Hungarian is agglutinative — a single "root" word can appear in hundreds of inflected forms depending on case, tense, possession, number, definiteness, and a handful of other axes. The English noun book has at most two forms (book, books). The Hungarian könyv can be könyv, könyvet, könyvben, könyvek, könyvekben, könyvemnek, könyveidről, and so on — dozens of real-world forms, all with meaningfully different search intent.

Worse for tooling: these forms don't always stem back cleanly. Könyv and könyvek share a prefix; lóként ("like a horse") and ("horse") share barely anything visible to a naive stemmer.

Google handles this reasonably well. Keyword tools that rely on post-hoc clickstream normalization don't.

The three mistakes we see most

1. Picking the nominative singular and stopping there

A team asks Ahrefs for volume on weboldal készítés ("website creation"). It reports 1,300 monthly searches. Fine. But the query is just as commonly written as weboldal készítése (with the definite possessive suffix), weboldalkészítés (compound), weboldal készíttetés (causative), or weboldal fejlesztés — each of which shows different volume in each tool, but which Google clusters as near-identical intent.

Fix: For every target keyword, gather the top 5–10 inflected variants and the most common compound. Sum the volumes. The real addressable volume is often 3–8× what the nominative singular shows.

2. Mishandling ő and ű

The Hungarian long vowels ő and ű are routinely typed as o and u by users who don't have a Hungarian keyboard set, who are on mobile, or who are just in a hurry. Google maps these to the correct forms. Some keyword tools don't.

Check any high-volume HU term in both forms. Költözés vs. koltozes, fűtésszerelő vs. futesszerelo — the diacritic-free variant sometimes shows higher volume in tools because of how clickstream data is collected from browsers that didn't encode the diacritics properly.

Fix: Include both the diacritic-perfect and the stripped forms in your keyword map. Especially for mobile-heavy queries (local services, e-commerce).

3. Treating compound words as separate words

Hungarian compounds freely. Weboldalkészítés is one word. So is keresőoptimalizálás (SEO), digitálismarketing-ügynökség, tartalommarketing-stratégia. In some tools these tokenize cleanly, in others they don't, and in user search they vary — the same person will type it both ways on different days.

Fix: Always run the one-word and space-separated variants. Look at the SERPs — if Google serves the same top ten, it's one intent.

A practical keyword-research workflow for Hungarian

  1. Start with buyer language, not tool output. Ask sales what phrases prospects actually use in calls. These are your seeds.
  2. Inflect the seed. For each seed noun, generate 8–12 forms using a morphological list (we keep one internally; you can start with a grammar reference). For verbs, do tenses + personal endings.
  3. Diacritic-sweep. For each variant, also include the ASCII-stripped version.
  4. Compound-sweep. Try the compound, the hyphenated, and the spaced versions.
  5. Pull volumes. Run every variant through your tool. Expect to find 3–8× the nominative-only volume.
  6. Cluster by SERP. Two variants whose top-5 SERP overlap ≥ 60% are the same intent — merge them into one target.
  7. Pick the canonical form. Usually: the nominative singular with correct diacritics, unless a compound variant has meaningfully higher volume. Use the canonical in <title>, <h1>, URL slug; use the full cluster in body text.

Structured data is underused in HU

One cheap ranking advantage on the Hungarian web right now: most competitors don't emit rich schema. An Organization, Article, BreadcrumbList, and FAQPage on every relevant page is table-stakes we rarely see on HU SMB sites. For local businesses, LocalBusiness schema still produces map-pack wins that Western European sites got years ago.

Google.hu is Google, mostly

There are no meaningful HU-specific search engines. Bing is a rounding error. Yandex is irrelevant. The Hungarian local-directory ecosystem (cylex.hu, aranyoldalak.hu) still sends a bit of referral traffic for brick-and-mortar categories, but the SEO game is the Google game.

One footnote: Hungarian users are mobile-heavier than the EU average, and rural broadband is slower than Western Europe. Core Web Vitals that pass a London benchmark can fail in Miskolc. Test with throttled connections.

Takeaway

Hungarian SEO isn't harder than English SEO. It's different in ways that default workflows don't capture. If your keyword research starts with a singular nominative and stops there, you're missing most of the opportunity. If it accounts for agglutination, diacritics, and compounding, you find volume that competitors who run off tool defaults never see.

Which is, of course, the definition of an advantage.

Related posts