Robots — Software Robots That Reply, Post & Fix SEO Automatically
ReplyBot answers reviews, PostBot publishes content, RankBot fixes SEO — all as scheduled robots with logs, retries, and per-user isolation. Start software, add hardware later.
Three scheduled robots
that work while you sleep.
Automation for local businesses and agencies usually means one giant dashboard with a hundred toggles. Robots takes the opposite route: three focused bots, each owning one task end to end, each logging every run.
Reviews
ReplyBot
Paste a Google or Yelp review, get three on-brand reply variants instantly. Enable auto-run and it polls on a 15-minute schedule. Every reply is logged to robot_logs for a transparent audit trail.
- • Google + Yelp review replies
- • 3 on-brand variants per review
- • 15-min auto-run schedule
- • Full robot_logs history
Content
PostBot
Feed it a blog post or URL and it generates full channel packs, then publishes to your connected accounts with cooldown windows and a 7-day duplicate guard so you never blast the same post twice.
- • LinkedIn, X, Bluesky, email
- • Cooldown + duplicate protection
- • 12-hour repost lockout
- • Recency map per channel
SEO
RankBot
Reuses the scan and Fix Kit pipeline to detect weak queries, draft the fix (llms.txt, FAQPage schema, comparison content), and open the PR — a robot that closes its own tickets.
- • Built on scanInfra Fix Kits
- • Waits for AI-visibility scans
- • Drafts fixes as pull requests
- • Earns back citations automatically
Automation you can audit,
not just hope about.
Most marketing automation tools are a black box: it ran, trust us. Robots logs every scheduled run to a dedicated robot_logs table — channel, status, retries, model used, elapsed — so you can reconcile exactly what happened and fix it when it doesn't.
Isolation at the account level
Per-user RLS means an agency running ReplyBot for clients sees one audit trail per client, never a blended mess. That matters when you're proving work to a client or defending behavior to a platform like Google Business Profile.
Promises become shipped facts
"We reply to all reviews within an hour" becomes a shipped fact instead of a staff goal — the same reason the crawlers and bots you let run on your site deserve an explicit policy: treating automation as infrastructure you control and observe.
Recency as a rank signal
PostBot's 12-hour cooldown and 7-day duplicate window stop both spam and embarrassment. Consistent publishing is one of the strongest signals in ranking in AI search, and batching it through a robot makes the consistency automatic.
The suite, wired together
The robots pair with the rest of the Launch at Dawn suite: ReplyBot shares its engine with the Reviews tool, PostBot reuses the Repurpose packs, and RankBot consumes output from the AI Search tracker. One API surface, three purpose-built robots on top. For the mindset behind all of it, read the crawlers and bots policy guide and how to rank in AI search.
Automation bots,
answered.
How is a "robot" different from a normal automation tool?
Each robot owns one job end to end — draft, publish, fix — runs on its own schedule, and writes a row to robot_logs per run. You get an audit trail you can reconcile, not a black box.
Do the robots run on Vercel cron?
Yes. Schedules are declared in vercel.json (e.g. the 15-minute reviews crawl) and each run is authorized with a server-side cron secret, then executed with the service-role key so no user session is required.
Can ReplyBot post to Google Business Profile directly?
Drafting and scheduling are live today; direct GBP publishing is staged and falls back to draft mode until Google Business Profile credentials are configured. Replies are stored in your review log regardless.
Will PostBot ever double-post my content?
No. Each channel enforces a 12-hour cooldown and a 7-day duplicate window; attempting a duplicate publish is rejected by the API before anything goes out.
What is RankBot actually fixing?
It watches AI-visibility scan output for weak queries and drafts targeted fixes — llms.txt entries, FAQPage schema, comparison content — then opens a pull request so the fix lands in code, not a ticket.
Do I need to keep the browser open?
No. The robots run server-side on a schedule; your dashboard is how you observe them, not what powers them.
Hire the staff
that never sleeps.
Three scheduled robots that reply, publish, and fix — each logged, each isolated, each ready tonight.