gsc-opportunity-report
Analyze Google Search Console performance for SEO growth, local-demand capture, ranking opportunities, CTR gaps, query/page trends, cannibalization, and emerging demand. Use when the user asks for a G
SKILL.md.claude/skills/gsc-opportunity-report/SKILL.md
GitHubGSC Opportunity Report
Produce an evidence-first Search Console report that converts search data into prioritized actions.
Workflow
- Establish the dataset before interpreting it.
- Identify property, exact date range, timezone if known, search type, filters, dimensions, and whether the data is complete or sampled/limited.
- Accept connected data, CSV/XLSX/Sheets, JSON, screenshots, PDFs, or pasted tables.
- If multiple exports exist, reconcile them before drawing conclusions.
- Normalize metrics without assuming a fixed current GSC schema.
- Use clicks, impressions, CTR, average position, query, page, country, device, date, and search appearance when present.
- Preserve exact source values; calculate derived metrics separately.
- Compare the current period with the immediately preceding equal-length period by default. Add year-over-year only when comparable data exists.
- Segment before concluding.
- Brand vs non-brand when identifiable.
- Service intent vs informational intent.
- Local/commercial intent vs broad traffic.
- Page, query, device, geography, and search appearance where useful.
- Find opportunities, not just winners and losers.
- High impressions + weak CTR at competitive positions.
- Queries/pages sitting near page-one or top-three thresholds.
- Rising demand with insufficient landing-page coverage.
- Pages losing clicks despite stable demand.
- Cannibalization or multiple URLs competing for the same intent.
- Query-to-page mismatches and thin local/service coverage.
- New queries with business intent.
- Separate signal from noise.
- Do not overreact to tiny volumes, average-position movement caused by query-mix changes, or one-day spikes.
- State materiality thresholds used when possible.
- Tie findings to business outcomes. For Nick's, prioritize likely impact on calls, directions, tire inquiries/orders, appointments, vehicle arrivals, repeat customers, reviews, and revenue rather than traffic for its own sake.
- Read
references/report-contract.mdand follow its output structure.
Analysis rules
- Never infer conversions or revenue from clicks alone.
- Never call an SEO change successful because impressions rose if qualified clicks, local intent, or downstream outcomes did not improve.
- Distinguish observed facts, derived calculations, and hypotheses.
- Flag data gaps that could materially change the conclusion.
- Prefer exact dates and raw deltas plus percentage changes.
- When current Google behavior or documentation materially affects the interpretation, verify it with an authoritative current source before relying on it.
Useful triggers
Examples: "run my GSC report", "analyze this Search Console export", "what SEO opportunities are hiding here?", "compare the last 28 days", "which queries should Nick's attack next?"