Skip to main content

Accounts & Groups

Search engine tasks can log into an account before searching (Google, Bing, Naver — see Use Account). Searches from logged-in accounts with real history carry substantially more weight. The Manage Account button inside a search engine task opens the account manager.

Importing accounts​

You can add accounts one by one in the account manager, or import many at once. To import in bulk, click Manage Account in a search-engine task, open the import option, and paste (or load a text file with) one account per line.

Format​

Each line has up to four fields — email and password are required, recovery email and 2FA secret key are optional:

email:password|recovery_email|2fa_secret_key
  • email and password — required, separated by a colon :.
  • recovery_email — optional; append it after a pipe |.
  • 2fa_secret_key — optional; the account's authenticator secret, for logging into 2FA-protected accounts.

Because the recovery email is recognized by its @, you can skip it and still add a 2FA key — put the secret straight after the password. Both | and : work as separators.

Concrete examples (one account per line):

# email + password only
[email protected]:An0therPass

# + recovery email
[email protected]:MyP4ssw0rd|[email protected]

# + recovery email + 2FA secret key
[email protected]:S3cretPass|[email protected]|JBSWY3DPEHPK3PXP

# + 2FA secret key, no recovery email
[email protected]:B0bPassword|JBSWY3DPEHPK3PXP

The recovery email is only used for Gmail accounts, and only when Google asks for it during verification — providing it makes logins more reliable. Outlook and Naver accounts ignore it.

After importing, save the set into a named profile to reuse it later.

note

Passwords cannot contain quotation marks (").

Two-factor authentication (2FA / OTP)​

Google accounts protected with authenticator-app (TOTP) two-factor authentication are supported — the bot generates the rotating 6-digit codes itself, so logins don't get stuck on the 2FA prompt.

Provide the account's 2FA secret key (the base32 string Google shows under "Can't scan it?" / "Set up manually" when you add an authenticator app — e.g. JBSWY3DPEHPK3PXP), not a one-time code. The bot derives a fresh code from that secret at each login, exactly like Google Authenticator would. Add it as the last field when importing, or type it into the account's 2FA secret key field in the account manager.

tip

When enabling 2FA on the Google account, choose Authenticator app and copy the setup/secret key. SMS-based 2FA is not supported.

Account groups​

Organize accounts into groups (e.g. per niche or per campaign set). Campaigns pick accounts from the group you assign; you can clear all accounts of a group in one action. Import/export includes accounts with their groups, so account sets move between machines cleanly.

Login behavior​

Configure how the bot treats logins per account — for example logging in fresh vs. reusing an existing logged-in profile. Combined with browser profiles, an account can stay permanently logged into its own warmed-up profile: the bot links the account to a profile rather than juggling cookies.

Selection​

When a task runs, the bot picks a random account from the assigned pool/group, avoiding reuse patterns.