A Cyrillic post title becomes a URL. Left alone it is percent-encoded into a line of gibberish that nobody can read, share or recognise in a search result.
Cyrillic content is fine everywhere except in the one place that has to be ASCII-safe.
A Cyrillic title percent-encodes into dozens of unreadable characters. Slugs are transliterated to Latin once, by one scheme, so the URL is legible and shareable.
Two transliteration schemes produce two different slugs for the same title, which means a URL changing when a plugin does. The scheme is fixed and the history kept.
Bulgarians frequently type Latin characters for Cyrillic words. Matching bridges the two so those queries still find content.
Storage stays in the EU with the location named, and delivery is local enough that latency is not a factor.
Alphabetical listings follow the Cyrillic alphabet rather than byte order, which places letters where readers expect them.
A percent-encoded Cyrillic URL is technically valid and practically useless. It cannot be read aloud, pasted into a document or recognised in a result listing.
This is not a speed problem. It is whether a URL survives being copied into a message, and an encoded Cyrillic slug does not.
Cyrillic content meeting an ASCII-safe URL is the whole problem, and consistency matters more than which scheme is picked.
| Setting | What we do | Why |
|---|---|---|
| Slug generation | Transliterated to Latin by one fixed scheme | A Cyrillic title percent-encodes into an unreadable string that cannot be shared, read aloud or recognised in a search result. |
| Scheme stability | Kept fixed with redirect history retained | Different transliteration schemes produce different slugs for the same title, so changing plugin silently changes every URL on the site. |
| Cross-script search | Latin-character queries bridged to Cyrillic | Bulgarians commonly type Latin letters for Cyrillic words, and ignoring that discards a real share of searches. |
| Sort order | Cyrillic alphabetical rather than byte order | Character-code ordering places Cyrillic letters in a sequence that does not match the alphabet readers learned. |
| Origin placement | EU, close to the domestic market | Bulgaria sits at the union's eastern edge and is well served from within it, so one nearby origin answers both latency and residency. |
Every plan includes free migration, daily backups, SSL and 24/7 support.
Move the site to an EU origin — migration is free, slug history preserved.