A Russian–English wedding site that keeps Cyrillic names intact
Transliterating Russian names into Latin script produces spellings nobody recognises, including the people they belong to. Serving Russian and English from one site keeps each guest list in its own script while the RSVP data stays unified.
Transliteration loses people
The same Cyrillic surname can be rendered several defensible ways in Latin script, and guests will not recognise the version you picked. Storing names as entered, in Cyrillic, means place cards and confirmations match what people actually answer to.
Patronymics are not middle names
A patronymic is a required part of a formal Russian name and carries respect that a middle name does not. Guest fields keep the full form rather than compressing it into a first-and-last structure that reads as informal.
ZAGS and the celebration are different days
The registry ceremony and the celebration are frequently separate, with different guest lists. English-speaking guests assume one continuous event. Separate schedule entries with their own descriptions make the structure explicit.
A tamada-led evening runs on a different clock
A toastmaster-led reception has a structure — sequenced toasts, games, courses — that guests from other traditions will not anticipate. Listing the evening's segments with times sets expectations for everyone.
FAQ
Can guests reply in Cyrillic?
Yes, including free-text fields. Responses from both languages arrive in one list.
Will the Russian version rank in Yandex?
Each language has its own indexable URL with correct hreflang, which is what Yandex needs. Ranking depends on your content and domain, not on the builder alone.
Can we use a custom domain?
Yes, on paid plans.
Can the site be hidden from search engines?
Yes. Search visibility is a per-site setting you control.