Interpreting traffic from Bulgaria
Bulgaria writes Bulgarian in Cyrillic and is an EU member under GDPR — a combination that is uncommon, since most Cyrillic-script markets sit outside the EU. This page explains how to read a 'BG' country signal, why script and EU rules both matter, and how to separate machine traffic from human Bulgarian visitors.
Cyrillic script inside the EU
Bulgarian (bg-BG) is written in Cyrillic, which is unusual for an EU member — most Cyrillic-script markets are outside the EU. Content and encoding for the BG segment must handle Cyrillic correctly, and language signals should reflect bg rather than being confused with other Cyrillic languages such as Russian.
When the country reads BG, confirm script handling and that hreflang reflects Bulgarian specifically.
EU rules and machine traffic
As an EU member, Bulgaria falls under GDPR, so apply the same consent posture as other EU traffic — even though the Cyrillic script might tempt you to group it with non-EU Cyrillic markets. Hosting networks in the region can resolve to Bulgaria and inflate the apparent country.
Separate machine traffic before reading BG as audience so crawlers and hosted clients are not counted as Bulgarian users.
- Locale is bg-BG, written in Cyrillic
- EU member: GDPR consent applies
- Don't group with non-EU Cyrillic markets
How it appears in analytics and logs
A 'BG' country value means the connecting network resolved to Bulgaria at the edge. Bulgarian (bg) is written in Cyrillic, yet Bulgaria is an EU member under GDPR, so script handling and EU consent both apply.
Diagnostic use case
Read a Bulgaria country segment for coarse trends while accounting for the Cyrillic bg-BG locale, EU consent rules, and cloud traffic that can inflate the country signal.
What WebmasterID can help detect
WebmasterID classifies bot versus human server-side, so a BG segment can be read with crawlers separated, and locale signals can be checked against a Cyrillic bg-BG audience.
Common mistakes
- Confusing Bulgarian Cyrillic with Russian or another Cyrillic language.
- Applying non-EU consent posture to BG because of the Cyrillic script.
- Counting cloud-hosted or crawler requests as Bulgarian human visitors.
Privacy and accuracy notes
WebmasterID treats a Bulgaria country signal as a coarse, privacy-safe edge estimate — never an exact location and never derived from raw client IPs stored in your analytics.
Related pages
- EU vs non-EU traffic segmentation
Grouping traffic into a coarse EU vs non-EU bucket is a privacy-safe way to add compliance context without precise location. This page explains how to derive the bucket from country signals, why it is useful for data-protection considerations, and its limits.
- Language vs country targeting
Language and country are distinct signals: Accept-Language reflects a browser's language preference, while edge country reflects the connecting network's location. This page explains why conflating them produces poor targeting and where hreflang belongs.
- Interpreting traffic from Serbia
Serbia is unusual in that Serbian is written in both Cyrillic and Latin scripts, and the country is outside the EU, so EU consent rules do not automatically apply. This page explains how to read an 'RS' country signal, why dual scripts matter, and how to separate machine traffic from human Serbian visitors.
- Privacy-first analytics
Coarse, privacy-safe geo without raw IPs or fingerprinting.
Sources and verification notes
- W3C — language tags (BCP 47 / bg-BG)Bulgarian is written in Cyrillic.
- European Commission — GDPR
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.