Home · Product · Integrations

Integrations

Cricket works out of the box from a single URL — the integrations make it sharper. Each one is optional, connected per project, scoped as narrowly as the provider allows, and disconnectable in one click from Settings. Here's exactly what each connection reads, what it unlocks, and what we'll never do with it.

Google Search Console + Analytics free

One "Connect Google" sign-in covers both. We request exactly two read-only scopes — webmasters.readonly (Search Console) and analytics.readonly (GA4) — nothing else, and never write access.

GitHub — the coding agent pro

Connect a repository and the SEO/GEO agents graduate from advice to action: Cricket opens a real pull request that adds a generated llms.txt for your site plus a paste-ready checklist of the on-page fixes, so shipping the technical work is a code review, not an afternoon. Connections are per project, you choose the repository, and nothing is ever committed without a PR you approve and merge yourself.

X (Twitter) publishing pro

Connect your own X account and every drafted post or reply gains a "⚡ post now" button. Publishing is strictly one-click-one-post: each press publishes exactly the draft you pressed it on, from your account, and nothing is ever scheduled or auto-posted in the background. Without the connection you still get every draft with a prefilled compose link — one tap to open it in X, ready to send.

WordPress publishing pro

Point Cricket at your WordPress site and the daily article can be published to it directly — formatted HTML, on your domain, under your byline. Each publish is a button you press on a specific article; drafts never leave the dashboard on their own.

Reddit — live thread discovery pro

Different from the others: this one needs nothing from you. Cricket discovers public threads via Reddit's public data — it never asks for your Reddit account, and it never posts. It finds the conversations, ranks them for genuine relevance, and writes disclosed reply drafts; posting is always you, in your own browser, under your own name. That boundary is deliberate — it keeps your account safe and the participation honest.

The AI engines we monitor

For the AI-search citation monitor, Cricket queries multiple answer engines — including ChatGPT and Perplexity — with neutral buyer questions about your category, and measures who gets recommended. No connection needed on your side; results appear as your visibility score, share of voice, and citation gaps. A failed engine call is excluded from the math, never counted against you.

IntegrationAccessUnlocksPlan
Google (GSC + GA4)Read-only, 2 scopesLive Search & Traffic tabs, keyword opportunities, daily deltasFree
GitHubRepo you chooseReal PRs: llms.txt + fix checklistPro
X publishingYour account, per-clickOne-press posting of approved draftsPro
WordPressYour site, per-clickOne-press article publishingPro
Reddit discoveryNone (public data)Live threads + disclosed reply draftsPro
AI enginesNoneCitation checks, share of voice, gapsPro
The common thread: integrations only ever widen what Cricket can read or let you ship faster — they never hand it permission to act on your behalf without a click from you. Every token is stored per project, deleted on disconnect, and wiped completely if you delete your account.

Start with just a URL — connect Google in the dashboard afterwards for the live-data tabs. It's free.

Open the app →