whats_next
Not sure what to do next? whats_next looks at where your project stands — crawl, audits, Search Console, reports — and tells you the single best next…
Cost: Free (0 credits).
whats_next is the guide for non-experts. It looks at where a project stands — whether it has been crawled, whether Google Search Console is connected, whether you have pulled performance data — and tells you the single best next step, a short reason, and the two or three steps that come after.
What it does
It reads the project's current state through the same tenant-scoped data the tools use (your latest crawl_site and pull_gsc_data runs, plus your Search Console connection) and walks a simple ladder:
- No project yet → run
setup_project. - No crawl yet → run
crawl_site(works without Search Console). - Crawl ready → run the audits:
audit_onpage,audit_tech,audit_schema. Connecting Search Console withconnect_gscis optional and never a barrier. - Search Console connected, no data pulled → run
pull_gsc_data. - Data pulled → run the discovery tools:
find_quick_wins,detect_cannibalization,analyze_content_decay. - Everything fresh → you're all set:
generate_reportfor a shareable summary, and themonthly-routineprompt to keep it up to date.
Example
Ask your MCP client in plain language:
What should I do next with my example.com project?
Input
| Field | Type | Required | Description |
|---|---|---|---|
project_id | string (uuid) | No | Optional project to route from (from setup_project / list_projects). Omit it to route from your project list. |
Returns
One clear next step for the project, a short reason, and the next two or three steps — all in plain language, naming the exact tools to run.