Skip to content

davepoon/buildwithclaude / plugins/all-skills/skills/gsc-seo-optimizer

gsc-seo-optimizer

Verified

Analyze Google Search Console exports or authorized API data to prioritize page improvements. Use for traffic changes, page/query opportunities, indexing evidence, and deciding when to leave recently edited or weakly supported pages alone.

references/roi-rubric.md

View on GitHub
# Opportunity rubric

Use qualitative prioritization unless the user supplied conversion and cost data. Search impressions alone are not revenue potential.

| Candidate | Evidence needed | Typical action |
|---|---|---|
| Relevant query near positions 4–20 | Page-specific non-brand query, sufficient impressions for the site's scale, matching product intent | Inspect snippet, content gaps and contextual internal links |
| Low CTR at a useful rank | Relevant query/device context; brand sitelinks and tiny samples excluded | Inspect actual SERP and snippet before rewriting |
| Relevant query beyond position 20 | Clear business value and a credible competitive/content gap | Larger test with lower near-term confidence, not a quick title win |
| Possible cannibalization | Same intent, overlapping pages, unstable preferred URL and evidence of harm | Choose a primary page only after checking content and links |
| Confirmed technical barrier | Inspection or rendered evidence of noindex/canonical/fetch problem | Fix the technical cause within approved scope |
| Newly optimized or weak evidence | Too few complete days, sparse queries, unrelated intent | Observe; no action is a valid recommendation |

Tie each action to a specific observation. Do not use a universal CTR benchmark as proof, a KD score as proof of easy ranking, or a high impression count as proof of product fit.

Prioritize a coherent small batch by business relevance, evidence strength, likely effort, and current visibility. Explain uncertainty and skip reasons. Review CTR after an adequate comparable window; ranking changes may require several weeks or longer, especially at low volume.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall