How the console works
One engine, four categories - the Neurise console working model.
How the console works
The console runs on a single-engine model: every category is run by the same agent (Claude Code), and a category is simply a pack of commands and specialized agents wired into a shared interface.
Categories = command packs
| Category | Base command | What it does |
|---|---|---|
| SEO | /seo … |
Audits and optimization for classic search |
| GEO | /seo geo … |
Optimization for AI search and citations |
| Ads | /ads … |
Audit and planning of paid campaigns |
| Blog | /blog … |
Content production and optimization |
Each command takes arguments (usually a URL or a topic) and returns a result in a fixed format: a score, a prioritized issue list and an action plan.
Which category when
- Ranking a page -> SEO. Local? SEO plus the local module.
- Want to be cited by AI -> GEO (and write content in Blog with dual optimization).
- Burning ad budget -> Ads, start with
/ads audit. - Need content that ranks -> Blog, start with
/blog strategy.
Client workflow
Plan
Define what "winning" means for the client - scope, goals, metrics.
Analysis
Audit and research: /seo audit, /ads audit, competitor analysis.
Production
Execution: /blog write, technical fixes, creatives.
Control
Pre-publish QA - quality gates must pass before anything ships.
Report
Results and the next cycle. A loop, not a project - that is what a retainer is.