Quick site health check
Get a snapshot of your site’s SEO health in one short conversation. Start here for a regular pulse check or when you want a fast read on what’s happening.
Replace yourdomain.com with your GSC property URL.
Step 1: Read 28 days of search performance
Section titled “Step 1: Read 28 days of search performance”What’s the overall SEO performance of yourdomain.com over the last 28 days? Flag anything that looks unusual.
The assistant pulls get_performance_overview and check_alerts, summarizes clicks, impressions, CTR and average position, and highlights measured risks.
Step 2: Check traffic concentration and anomalies
Section titled “Step 2: Check traffic concentration and anomalies”Are there any traffic concentration risks or sudden drops I should know about?
The assistant calls traffic_health_check and analytics_anomalies to surface z-score spikes, dips and traffic concentration.
Step 3: List pages between positions 4 and 15
Section titled “Step 3: List pages between positions 4 and 15”What are the easiest improvements I can make right now on yourdomain.com?
The assistant calls quick_wins to surface page-level opportunities ranked 4 to 15 with high impressions and CTR below the built-in benchmark. It does not return query-level opportunities.
Step 4: Compare 2 adjacent 28-day periods
Section titled “Step 4: Compare 2 adjacent 28-day periods”Compare the last 28 days with the immediately preceding 28 days. What changed, and which queries or pages account for the measured difference?
The assistant calls compare_search_periods for two adjacent equal-length windows. The result can localize a change, but it does not prove why the change happened.
Optional: compare Google and Bing
Section titled “Optional: compare Google and Bing”Bing is configured for https://yourdomain.com/. Compare the top queries and pages with Google over the requested 28-day window. Keep positions separate and omit deltas unless
compare_search_enginesconfirms equal exact observed windows.
Use google-bing-comparison.md when the cross-engine difference needs a deeper investigation.
What to do with the output: the quick audit surfaces signals. If something looks off, go deeper with traffic-drop.md or page-deep-dive.md. Keep this workflow read-only unless a later prompt explicitly confirms one named write.
See the 2026-10-07 Claude Code Ultimate Guide run for real measurements, page checks, proposed actions and a recorded MCP trace.