Your agent ships the fix. Serpkin knows which one.

Your agent can already edit code. Serpkin tells it what to change and why: the next best SEO mission for your site, based on real search data, with the files to touch, a recipe and checks. Then it shows whether the change landed and what happened.

No. Serpkin works from site scans and its own search data, and brand-new sites start with foundation missions. Connecting Search Console makes missions and results sharper, because they come from your real queries and clicks.

Yes, for Google AI Overviews. Each month Serpkin checks your important queries: whether an AI Overview appears, whether it cites your site and which other sites it cites. You can also run a check on demand for 1 credit per query. If competitors are cited and you aren’t, you get a mission for that page.

Credits cover research you start: keywords, SERPs, competitors, AI visibility checks, content briefs and backlink refreshes. Each plan includes a monthly amount, and a keyword research run uses 2. Scans, foundation missions, result checks, rank tracking and monthly snapshots use none.

Yes. In Account, choose Cancel plan, then Pause my plan: your paid plan runs until the end of the period you’ve paid for, then your workspace switches to Free. Your history, missions and weekly site watch stay. Sites beyond the Free limit become watch-only (still watched, no new scans or research), and nothing is deleted. Resume any time to restore your plan.

No. Your coding agent implements the mission with its own access to your repository. You review, merge and deploy.

A mission is verified when its checks pass in a named environment, preview or production. After production, Serpkin takes a baseline and measures at 14 and 28 days, from Search Console or rank checks. It compares your target pages with similar pages you didn’t change and shows the net effect with a confidence label. Search impact can lag and has other causes, so read it as correlation, not proof.

Claude Code, Codex and Cursor, over MCP; npx serpkin sets up whichever it finds. In Claude Code it can install the Serpkin plugin, so /serpkin:next starts the next mission. Next.js routes are mapped to source files first. Astro, Remix, SvelteKit and Nuxt are best-effort, and any site works by URL.

Search Console access is read-only, and Google tokens are stored encrypted. Your agent key stays out of git: the config written into your repo only references it. Serpkin receives a map of URL paths to file names, not your source code.

When paid plans open, payments are processed by Creem (creem.io), the merchant of record, which handles checkout, invoices and sales tax/VAT. You can switch between monthly and yearly, pause or cancel from Account.