Getting started
How it works
What SERPclimber does, the observe-audit-prioritize-work-verify-report loop, and how much the engine owns.
SERPclimber is an SEO workspace organized around projects. Each project is one website: its goal, business context, connected data, allowed scope, and autonomy policy.
For every project the engine runs one continuous loop:
- Observe — crawl the site, sync Google Search Console and GA4 daily, snapshot backlinks and listings, and check how AI engines answer questions in your space.
- Audit — turn those observations into evidence-backed issues and opportunities, grouped by department.
- Prioritize — re-rank the backlog against the project goal every hour and promote only the most useful findings into Tasks.
- Work — execute approved tasks through the engine, you, or an external agent connected over MCP.
- Verify — check the live result and measure the outcome when a measurement window is useful.
- Report — write weekly or monthly digests of what changed, what improved, and what comes next.
The workspace
Each project opens on Performance → SEO and has five sections: Performance (with SEO, GA4, AI answers, Crawlers, and Authority tabs), Tasks, Audit, Reports, and Settings. Every task has a project-wide number such as #42 and its own thread, where evidence, plans, approvals, receipts, and your comments live together.
The assistant is available everywhere: on its own page, in a pane pinned beside any page, and behind the Explain with AI button on every Performance card. Ask it what needs you, why a task exists, or what a chart means. See Chat.
How much the engine owns
- Audit only / MCP — the engine observes, files findings, and plans. You or your external agent perform every change.
- Copilot — the engine performs low-risk, reversible work and asks before risky, external, or paid actions. New projects start here.
- Full — the engine performs everything its policy allows, including paid evidence within budget.
- Custom — set a default rule and override it per department or action class.
Start by connecting your data, then read the first Audit and open the first task the engine puts in Needs you.
