Botlord Platform
One Windows desktop app hosts every engine. Install once, activate your license, then open the modules your plan includes.
Botlord Platform replaced separate per-bot installers. Google Ads Clicker, CTR Surge, Yahoo, Amazon, and SoundCloud run as modules inside the same app — shared configuration, one updater, one logs view. This guide covers installation, licensing, the campaign system, and platform-level settings that apply to all modules.
Download the latest installer from your dashboard under Software, or use the public download page at /download. One installer covers all modules — there is no separate download per engine.
Stable releases use latest.exe on the CDN. Beta is a separate channel (beta.yml + beta.exe) published independently — only use beta when you are explicitly testing pre-release builds.
Exclude the install folder from antivirus before running updates. Antivirus quarantine of bot.js or Electron files is the most common cause of update failures.
Your Botlord Platform subscription unlocks the host app and a set of modules based on plan tier. Starter includes Search Traffic (Google SERP). Scale adds Bing, Yahoo, DuckDuckGo, and Yandex SERP engines. Enterprise adds all ad engines, Amazon PPC, SoundCloud, and upcoming modules.
Paste your license key on first launch. Modules your plan includes appear unlocked in the module list. Add-ons (individual engine upgrades) are purchasable from your dashboard without upgrading your base plan.
Device seats apply to the platform license — each machine that activates the same license uses one seat. Manage seats and revoke devices from the Licenses section of your dashboard.
Each module is a traffic engine with its own campaign settings, logs, and configuration. Modules share the same runtime infrastructure — proxies, profile pools, and captcha solvers are configured once and apply to all modules.
Current modules: Search Traffic (CTR Surge — SERP organic clicks), Ad Traffic (Google Ads, Yahoo Ads, Amazon PPC), SoundCloud (streaming plays). Social Traffic and Marketplace Traffic are on the Enterprise roadmap.
Module docs assume the platform is installed and licensed. Work through the essential services stack (AdsPower, CapMonster, proxies) before scaling any module.
Every module uses the same campaign model: Targeting (what to search or visit), Traffic (which engine), Strategy (what to click, bounce rate), Behaviour (dwell, scroll, navigation depth), and AI (optional AI steering).
Campaign builder: create and edit campaigns in the app UI or in the web campaign builder at thebotlord.com. Web-built campaigns sync to the desktop when the bot starts — cloud campaigns take priority over local config on conflict.
Keyword groups let you organise one campaign into multiple topic segments with independent settings. Each group can have its own task list, dwell range, and domain filter.
Search tasks navigate to a SERP, find the target result, and click it — the standard task for all search and ad engines.
Direct tasks navigate straight to a URL without a search step. Useful for direct product page visits, referral traffic, or warmup to specific landing pages.
Warmup tasks run normal browsing sessions to age a profile before CTR work. The bot visits content sites, reads articles, and navigates naturally — no ad clicks.
AI Agent tasks run a fully autonomous session guided by a natural-language prompt. The AI plans and executes every step using an LLM provider you configure (OpenAI, Anthropic, OpenRouter, DeepSeek, Gemini, or a local model).
SoundCloud tasks play a track URL to a target play count with configurable delay between plays.
Disposable mode creates a fresh browser profile for every session — fast, clean, and best for burst campaigns. This is the default for all modules.
Trusted Identities mode reuses persistent profiles with a warmup phase. New profiles browse normally for several days before doing CTR or ad-click work. Better stealth, slower ramp-up.
Adaptive mode lets the platform decide per-session based on the profile's trust score. Recommended when you want the platform to manage profile lifecycle automatically.
Profile warmup templates control what kind of browsing a new profile does during warmup: Casual (general browsing), Researcher (reading articles), Shopping (product pages), Mobile (mobile-style session), Brand Boost (brand research).
Proxies are configured at the global level and apply to all modules. Paste proxy lines in Configuration: ip:port, ip:port:user:pass, or socks5://ip:port:user:pass format.
Residential and mobile proxies perform significantly better than datacenter across all engines. Datacenter proxies carry a stealth score deduction and trigger sorry-redirects more often on Google.
Rotate per session for best results. Per-request rotation mid-session looks unusual for organic browsing or ad clicking.
Match proxy geo to the target market — a UK proxy clicking US Google Ads is a geographic mismatch that signals bot behaviour.
The stealth score (0–100, grade A–F) measures how detectable your campaign config looks. Biggest deductions: datacenter proxy (−20), high captcha rate (−20), dwell under 2 seconds (−15), concurrency above 10 (−10).
The adaptive rate controller automatically adjusts delay and concurrency based on detection signals — sorry redirects, captcha blocks, proxy timeouts. Choose Safe (conservative), Balanced (default), or Aggressive risk profiles.
SERP Intelligence analyses page composition before each click — detecting AI Overviews, ad density, Maps packs, and Shopping carousels. Enable it in the AI tab for automatic risk-level adjustment per SERP.
Set a start and end hour to restrict when workers run. The bot pauses outside the window and resumes automatically when it opens. Overnight windows are supported — start 22, end 6 runs from 10pm to 6am.
Enable specific weekdays only to mirror real business hours. A common setup is Monday–Friday, 7am to midnight.
Set campaign start and end dates for time-bounded runs. Workers stop automatically on the end date.
Older Google Ads Clicker, CTR Surge, Yahoo, and Amazon standalone installers are in maintenance mode. No new features are added to standalone builds.
Dashboard download links for legacy products redirect to the Botlord Platform installer. Existing licenses migrate to the unified app on platform plans.
Legacy build archives may still appear under Software for rollback — new work should use the platform runtime.
Production customers should stay on the stable channel (latest.exe / latest.yml). Stable releases go through QA before publishing.
Beta is a separate build on the CDN — only use it when explicitly testing pre-release features. SaaS version sync tracks stable; beta is published independently by desktop CI.
After any update (stable or beta), run a short manual session before leaving anything unattended on a VPS.