The client wants a blog in Russian and English. You have already connected multilingual support on other pages — and then it turns out that the blog is a separate story.
Why a Tilda Blog Is a Separate Task
Regular Tilda pages are blocks of text. The proxy intercepts the HTTP request and substitutes the content — Tilda knows nothing about it.
This won't work with a blog. A blog in Tilda works through collections: each article is an entry in a collection, and the collection is linked to a project. When a user opens /blog, Tilda dynamically serves entries from the current project's collection.
The English version of the blog is not a translation of pages. It is a separate set of articles in a separate collection.
Three options that don't work
Simply translate the pages. The proxy will translate the interface: the "Blog" title, buttons, meta tags. But the articles — titles, announcements, content — will be taken from the same Russian collection. The reader lands on a page with an English interface and Russian articles.
Create a folder /en/blog/. Tilda allows you to create folders, but all pages of one project use the same language setting. It is not possible to have a separate language blog within one project.
Duplicate the project. Technically, this works. But any template changes will have to be made twice. Add a third language — three times. With five languages, this becomes unmanageable.
How it works through a proxy
Multify solves the problem at the routing level. The user opens mysite.com/en/blog — the proxy recognizes the request and takes entries from the English collection. Tilda works as usual, just with its own stream connected for each language.
The language switcher on the article page leads to the translation of the same article, not to the blog's main page. This works through slug mapping: if the slugs match or explicit mapping is specified, the transition is correct. Search engines also see explicit interlinking via hreflang at the level of each individual article.