AgentStack
SKILL verified MIT Self-run

Seo Gsc Opportunities

skill-lionkiii-claude-seo-skills-seo-gsc-opportunities · by lionkiii

>

No reviews yet
0 installs
14 views
0.0% view→install

Install

$ agentstack add skill-lionkiii-claude-seo-skills-seo-gsc-opportunities

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Seo Gsc Opportunities? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

GSC Opportunities — High-Impression Low-CTR Finder

@skills/seo/references/mcp-degradation.md @skills/seo/references/gsc-api-reference.md

Finds keywords with significant impressions but low click-through rates — indicating ranking positions where optimization can quickly increase organic traffic without new content creation.

MCP Check

Before calling any GSC tool, verify the MCP is connected:

  1. Use ToolSearch with query +google-search-console
  2. If tools returned — note the actual tool name prefix, proceed to Inputs
  3. If no tools returned — display the GSC MCP error template from

references/mcp-degradation.md and stop:

## Google Search Console MCP Not Available

The `/seo gsc opportunities` command requires the GSC MCP, which is not currently connected.

**What you can do:**
- Use `/seo technical ` for crawlability and indexability analysis (no live data)
- Use `/seo audit ` for a full static SEO audit

**To connect GSC MCP:**
- Install and configure a Google Search Console MCP server (see README for setup)
- Add it to ~/.claude/mcp.json at user scope (NOT project scope)
- Verify GSC property access before running commands (domain vs URL prefix format)
- See references/gsc-api-reference.md for property format details

Inputs

  • site: The GSC property URL. Accept both formats:
  • Domain property: sc-domain:example.com
  • URL prefix: https://example.com or https://www.example.com
  • If user provides a bare domain (no prefix), call list_sites to identify

the correct property format registered in GSC.

Date Calculation

Use Bash to calculate dates (GSC has ~3 day delay):

endDate=$(date -v-3d +%Y-%m-%d)
startDate=$(date -v-31d +%Y-%m-%d)
echo "endDate: $endDate | startDate: $startDate"

Execution

Step 1 — Find keyword opportunities: Call find_keyword_opportunities with:

  • siteUrl: the site property
  • startDate: calculated startDate
  • endDate: calculated endDate
  • minImpressions: 100 (keywords need at least 100 impressions to matter)
  • maxCtr: 0.05 (5% CTR threshold — keywords below this are underperforming)
  • maxPosition: 20 (only keywords ranking in top 20 positions)

Post-processing: Sort results by impressions descending (highest opportunity volume first).

For each keyword, add a "Potential" action recommendation:

  • Position 1-3 and CTR = 100, CTR =100 impressions and <5% CTR in top 20 positions for this period."

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.