The question behind one login per client
You build or maintain sites for several clients and want a separate Yandex login for each project, so search data, notifications and access never mix. Buying a ready Yandex account per client is one way to get those logins without registering each one yourself. The harder question comes right after: should that bought login be the Owner of the client's site in Yandex Webmaster, or should it hold a narrower role that the client grants?
The answer decides what happens when a contract ends, when a client moves to another agency, or when you lose access to one of the accounts. Settle it first, because it also decides how many accounts you need and which listings fit the job.
What each Webmaster role can do
Yandex Webmaster Help describes four roles. An Owner has verified the site and has full control, including managing other users' permissions. Edit can view and change all site information but cannot assign or revoke roles. View is read only. Partial access is limited to specific tools, such as indexing, search appearance and feeds, where the user can view and edit. Each user holds one role, and only an Owner with verified ownership can hand roles out or take them back.
Two details matter for agency work. First, one site can have multiple owners, so ownership does not have to be either yours or the client's. Second, a granted role does not make the site appear in the recipient's account by itself. The person signs in with their Yandex ID and adds the site, using exactly the address the owner added, because Webmaster treats https and http, or www and no www, as different sites.
A worked example with three clients
Hypothetical setup: a freelance developer looks after three sites. Client A, a bakery, already has a Yandex ID and wants to stay in charge. Client B, a small furniture workshop, has no Yandex account and no interest in creating one. Client C, a language school, has said it may move to another agency next year.
For client A, the bakery's own login verifies the site as Owner and adds the developer's bought login with Edit. Work goes on normally, and the bakery can revoke the role later without touching anything else. For client B, the bought login verifies the site because nobody else will; the developer writes this into the agreement and promises to add the workshop, or whoever it names, as a second owner on request. For client C, the school verifies as Owner and the developer takes Edit or Partial access, so an agency change becomes a role revocation instead of a hunt for passwords.
The outcome is three bought accounts, one per client, and only one of them holds ownership. That is a typical pattern: the number of accounts follows the number of clients, while ownership follows whoever has the longest-term interest in the site.
When a bought login should be the Owner
Ownership on your login fits when the client has no Yandex ID, has asked you in writing to run the site's search presence, and accepts that you will add the client or a successor as another owner whenever asked. It also fits your own sites, demo projects and staging domains you control.
It does not fit when the client expects to keep control, when the site matters far more to the client than to you, or when you have not yet replaced the account's password, phone number and recovery details with your own. Ownership rests on a verification code that stays on the site. Yandex notes that verified rights may be revoked if its robot cannot find the code at the next check, so whoever owns the site in Webmaster must also be able to keep that code in place on the server.
What to look for in a Yandex listing for this use
For Webmaster work you want an account you can make entirely yours. Prefer listings that say whether a phone number is linked and whether it can be replaced, whether a backup email or security question is set and handed over, and whether the account was used before. An account with unknown earlier use could already hold roles on other people's sites, which you would then have to find and remove before a client ever sees the login.
Yandex's user agreement places responsibility for everything done under a login on the person who holds it, including after access details have been passed on, and it does not allow selling or reselling access to Yandex services unless Yandex authorizes it. Buying an account on rStock does not change those terms or give you any permission from Yandex. Plan to use each account under Yandex's rules and to keep its registration details accurate and current, as the agreement asks.
Buying the client logins on rStock
rStock is an independent marketplace and is not affiliated with Yandex. Stores are approved before they can sell, which does not certify that a particular account suits Webmaster work, so compare what each listing actually states alongside the store's rating, reviews, sales count and insurance balance. If a detail you need is missing, pick a better-documented listing rather than guessing.
You pay from your rStock balance, and the account arrives as a delivery record on your order page. The payment is held for the limited window shown on that page, so sign in and secure each account soon after delivery. When you are ready, open the Yandex category, shortlist accounts whose listings answer the phone and recovery questions clearly, and buy one for each client project you actually run.