Prompts

Alongside its tools, SeoGrep ships MCP prompts — ready-made, guided workflows that string the tools together into the routines you run most often. Your MCP client lists them as slash-style prompts you can pick by name; each one walks you through the steps, one tool at a time, in plain English. They spend no credits on their own — the tools they call do.

Available prompts

new-site-audit

A first-time audit of a website, end to end. Give it a domain and it walks through setup_project → crawl_site → audit_onpage / audit_tech / audit_schema → generate_report. It works without Google Search Console; connecting it is offered as an optional step for deeper, query-level analysis.

monthly-routine

Your monthly maintenance pass for a project. Give it a project_id and it refreshes Search Console data with pull_gsc_data, runs the discovery tools (find_quick_wins, detect_cannibalization, analyze_content_decay), and rolls the findings up with generate_report.

If the project isn't connected to a Search Console property yet, the prompt points you at list_gsc_properties to see what your connected Google accounts can already reach, then track_gsc_property to link the right one — both free, and neither needs a new Google sign-in. Only if you have no Google account connected at all does it send you to connect_gsc first.

quick-wins-sprint

A focused sprint on the pages ranking just below page one. Give it a project_id and it refreshes Search Console data, runs find_quick_wins, and prioritizes the highest-impact, lowest-effort fixes.

gsc-health-check

A checkup on your Google Search Console connections. A connection can stop working quietly — an access grant gets revoked in the Google account, a property is removed, or a permission level is downgraded — and nothing announces it. The first symptom is usually a pull that comes back with nothing, which reads like a site with no traffic.

The prompt runs list_gsc_properties to see what each connected account can reach, names the accounts that did not answer (as unknown, never as empty — an account SeoGrep couldn't reach hasn't told you it has no properties), points you at a reconnect for those, and flags properties whose permission level can't answer performance queries. If you give it a project_id, it finishes by confirming the fix with a 7-day pull_gsc_data — the cheapest call that proves a credential can actually fetch data rather than merely list it.

Not sure which to run?

Ask the whats_next tool — it looks at where your project stands and points you at the right next step (and, when you're all set, at the monthly-routine prompt).