In short
- A mission is one task: what to change and why now, the target pages and files, steps for your framework, and the checks Serpkin runs.
- Missions fall into three groups: fix what's broken, win more searches, and get found elsewhere.
- The queue puts work in progress first, then fixes that block indexing, then the highest rule-based priority score.
- Dismiss a mission with a reason; two "not relevant" or "disagree" dismissals of one growth kind rank that kind lower.
- New missions per month: 3 on Free, 30 on Builder and 150 on Pro.
A mission is one SEO task for one site: the change worth making next, why it matters now, the files to edit and the checks that prove it worked. Serpkin builds missions from your site scan, Search Console when it's connected, rankings, backlinks, AI answers and your competitors' new pages. Your coding agent picks them up over MCP, one at a time. This page explains the mission types, how they're ranked, what each status means and how to dismiss one.
What a mission contains
- What and why: a plain title, the evidence it's based on (a scan, Search Console, rankings or search data) and a one-line reason it comes now.
- Where: the target pages and, from your route map, the source files that render them.
- How: steps for your framework, with snippets for metadata, sitemaps, redirects or structured data where they apply.
- Done when: acceptance checks that Serpkin runs itself when you verify the mission.
Page text and search queries inside a mission come from the web, so they're marked as untrusted data. Agents connected to Serpkin are told to treat them as information, never as instructions.
Mission types
The app groups missions the same way, by what they get you:
| Group | Examples | What it gets you |
|---|---|---|
| Fix what's broken | Pages that don't return 200, unintended noindex, missing sitemap or robots.txt, broken links, canonicals, Core Web Vitals, structured data, and "Fix the basics" | Google can crawl, index and understand every page |
| Win more searches | Near page one, shown often but rarely clicked, pages competing for one query, declining pages, new pages, free tools and comparison pages | More of the searches people already make |
| Get found elsewhere | Directory listings, backlinks to win back, sites that link to competitors, getting cited in Google's AI answers | Visitors, links and citations from other sites |
Small page fixes, such as titles, meta descriptions, canonical URLs, H1 headings, link previews and structured data, ship together as one Fix the basics mission: several quick fixes in one change and one check.
Where growth missions come from
Which growth missions you get depends on the data your site has. A new site starts with foundation fixes from the scan. With rankings, Serpkin adds missions from its own search data and estimated rankings. With Search Console connected, missions come from your real queries and clicks. Competitor watch, AI answer checks and backlink snapshots add their own missions on top. See Competitor watch.
How missions are ranked
Your agent asks for the next mission, so the order matters. The queue is sorted by four rules, in this order:
- 1In progressA mission you already started comes first, so work gets finished.
- 2BlockingFixes that stop Google from crawling or indexing the site.
- 3Priority scoreA rule-based score from the data level, signal size, effort and confidence.
- 4Oldest firstTies go to the mission that has waited longest.
The priority score is a ranking aid, not a traffic forecast. Each mission also carries a short "why now", for example "These queries already rank close to page one, and the page has specific gaps to fix." Your agent sees it with the mission.
Statuses and lifecycle
- 1ReadyFound and waiting. Data refreshes update it in place.
- 2In progressYour agent started it. Refreshes only flag that the data changed.
- 3ImplementedThe change is submitted and waiting to be verified.
- 4VerifiedSerpkin's checks passed on the environment you named.
- 5MeasuringA baseline is taken and results follow at 14 and 28 days.
| Status | Meaning |
|---|---|
| Ready | Open and waiting for your agent. If the rule fires again with new data, the mission is refreshed in place. |
| In progress | Started. Serpkin won't move the goalposts: new data only marks it as changed. |
| Implemented, awaiting verification | The agent submitted the change; verification is pending or running. |
| Failed | The last verification failed. Fix what the checks reported and verify again. |
| Verified, then completed | Checks passed. After the 28-day measurement the mission is completed. |
| Resolved | The issue went away on its own after a fresh scan or data refresh. You can bring it back. |
| Dismissed | You chose not to do it. It stays hidden for 180 days unless you restore it. |
A mission that was completed can come back as a new mission after 90 days if its rule fires again, so a problem that returns is caught.
Dismissing a mission
You or your agent can dismiss a mission, optionally with a reason: not relevant, already done, too much work, disagree or other, plus a short note. Restore it from the app at any time.
Monthly mission limits
Each plan includes a number of new missions per month: 3 on Free, 30 on Builder ($29 a month) and 150 on Pro ($79 a month). The count resets on the 1st (UTC). Missions that already exist keep refreshing when you reach the limit; only new ones wait. When you get close, the app and your agent say what the next plan includes. See Plans and limits.
Questions
Why did a mission disappear?
If the issue went away after a fresh scan or data refresh, Serpkin marks the mission resolved. You can bring it back from the app if you still want to do it.
Can I do a mission that isn't first in the queue?
Yes. Ask your agent for a specific mission, or start it from the app. The queue order is a recommendation, not a rule.