davepoon/buildwithclaude / plugins/all-skills/skills/gsc-seo-optimizer
gsc-seo-optimizer
VerifiedAnalyze 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.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.1 KB |
| SKILL.md | skill md | 7.4 KB |
| references/data-access.md | markdown | 5.2 KB |
| references/data-quality.md | markdown | 4.7 KB |
| references/report-template.md | markdown | 1.1 KB |
| references/roi-rubric.md | markdown | 1.6 KB |
| scripts/gsc_fetch.py | script | 9.6 KB |
| scripts/import_gsc.py | script | 11.0 KB |
| scripts/requirements-api.txt | markdown | 53 B |
| tests/fixtures/Filters.csv | other | 75 B |
| tests/fixtures/Pages.csv | other | 123 B |
| tests/fixtures/Queries.csv | other | 95 B |
| tests/test_gsc.py | script | 9.0 KB |
references/report-template.md
View on GitHub# Report and baseline
Keep the user-facing report concise; save detail when useful.
- Scope: property, source, search type, target market/device/page filters, current and comparison dates, as-of date, latest available finalized day, declared versus verified export scope.
- Trend: independently sourced clicks/impressions/CTR; explain brand contribution and query mix when supported. Otherwise say visible rows only.
- Opportunities: URL, metrics, actual supporting queries, business relevance, diagnosis, proposed action, confidence, review interval.
- Skips: recently changed, irrelevant, brand sitelinks, insufficient evidence, or no actionable issue.
- Limitations: row caps, missing query-page linkage, hidden queries, incomplete days, missing indexing evidence.
- Next batch: concrete pages and changes, or a justified no-action conclusion.
For an approved edit save a baseline JSON/Markdown artifact containing exact scope, metrics/source files, changed URLs, edit/deployment date, prior/new title or content summary, and planned review date. Reuse that same scope when reviewing. Do not commit private exports or upload them without authorization.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| 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 implementation | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 fallback | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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 always | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |