A Telegram bot that drives real organic visits to your site
Graphref operates a pool of real devices. When you submit a job, those devices perform an actual Google search for your keyword, locate your domain in the results, and click through. Google registers it as genuine organic traffic — which you can verify in Search Console.
Job pipeline
From your command to a click in Google — every step in the process.
You send
/run keyword domain
via Telegram bot
Job enqueued
Redis queue
10 credits deducted
Worker picks up
Real device executes
run.py subprocess
Google search
Searches keyword
clicks your domain
You're notified
Bot sends result
visible in GSC
You send /run keyword domain
via Telegram bot
Job enqueued in Redis queue
10 credits deducted
Worker picks up and executes
run.py subprocess on real device
Google search performed
Finds your domain, clicks it
Bot notifies you with result
Appears in Google Search Console
Queue & workers
Jobs are stored in a Redis-backed queue (RQ). Workers continuously pull jobs in order and execute them. Multiple workers can run in parallel, which is why server load affects queue time.
Auto-refund policy
Credits are refunded automatically for any job that doesn't complete successfully — network errors, invalid domain, worker interruption, or timeout. No manual request needed.
Job lifecycle
Every job moves through these states. The bot notifies you when a job leaves the active states.
State transitions
All commands
Every command the bot supports, with real examples of what you send and what you get back.
/run <keyword> <domain>10 creditsEnqueues a new search job. Graphref searches for your keyword on Google and clicks your domain in the results.
/status [job_id]FreeReturns the current state of a job. Omit job_id to check your most recent active job.
/jobs [n]FreeLists your last N jobs (1–10) with their status, keyword, domain, and timestamps.
/cancel [job_id]Refunds 10 creditsCancels a queued job before it starts. Credits are refunded immediately. Cannot cancel a job that has already started.
/queueFreeShows current server load: how many jobs are queued globally and how many of yours are active.
/creditsFreeShows your current credit balance and how many /run calls you can make with remaining credits.
/buyFreeDisplays available credit packages with PayPal checkout links. Credits are added instantly after payment.
/referralFreeGenerates your unique referral link. When someone signs up through your link and completes their first run, you earn 30 bonus credits.
Inside the worker
What actually happens between “worker picks up” and “job finished” — every step the real device takes.
Worker dequeues the job
An idle worker process polls the Redis queue and atomically pops the next job. The job transitions from queued → started and is locked so no other worker can claim it.
Real browser launches
The worker spawns run.py as a subprocess on a real device. A headless Chromium instance starts with a unique user-agent and viewport — indistinguishable from a normal desktop session.
Google search is performed
The browser navigates to google.com and types the keyword into the search box. The search is submitted and the SERP (Search Engine Results Page) loads fully before any action is taken.
Results scanned for your domain
The script iterates through organic result links, checking each href for a match to your domain. If the domain appears in the top results it proceeds; otherwise the job exits with a non-zero code and credits are refunded.
Domain link is clicked
The target link receives a real mouse-click event (not a direct navigation). The browser follows the redirect chain exactly as a human visitor would — including Google's click-tracking URL — then waits for the page to fully load before the job is marked finished.
How Graphref avoids low-quality traffic flags
Google's systems look for patterns that separate automated activity from genuine users. Graphref is built around passing every one of them.
Real browser fingerprint
A physical device runs a standard Chromium build with no automation flags. Canvas, WebGL, audio, and font fingerprints match a normal desktop browser — nothing headless-specific is exposed.
Click routed through Google
The click follows Google's /url?q= redirect chain before landing on your site. This is what Google's click-through measurement infrastructure expects to see — a direct navigation would register as referral traffic, not organic.
Unique IP per session
Each job runs from a distinct residential IP address. No repeated subnet patterns, no datacenter ranges. IP reputation is clean and geographically varied.
Human-paced timing
Keystrokes, mouse movements, and page interactions are paced with randomised delays. No sub-millisecond precision that would stand out in event timing analysis.
Dwell time, not bounce
The browser waits for the full page load and remains on the destination for a natural duration. Immediate exits are a strong signal of bot activity — Graphref never bounces.
No repetitive patterns
Jobs from different users are interleaved in the queue. No single keyword or domain is hit at a metronomic interval. Traffic variance mirrors organic user behaviour.
Ready to try it?
New accounts start with 50 free credits — no card required.