Files
our-claude-skills/custom-skills/16-seo-search-console/desktop/SKILL.md
Andrew Yim b6a478e1df feat: Add installation tool, Claude.ai export, and skill standardization (#1)
## Summary

- Add portable installation tool (`install.sh`) for cross-machine setup
- Add Claude.ai export files with proper YAML frontmatter
- Add multi-agent-guide v2.0 with consolidated framework template
- Rename `00-claude-code-setting` → `00-our-settings-audit` (avoid reserved word)
- Add YAML frontmatter to 25+ SKILL.md files for Claude Desktop compatibility

## Commits Included

- `93f604a` feat: Add portable installation tool for cross-machine setup
- `9b84104` feat: Add Claude.ai export for portable skill installation
- `f7ab973` fix: Add YAML frontmatter to Claude.ai export files
- `3fed49a` feat(multi-agent-guide): Add v2.0 with consolidated framework
- `3be26ef` refactor: Rename settings-audit skill and add YAML frontmatter

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
2026-02-03 16:48:06 +07:00

3.2 KiB

name, description
name description
seo-search-console Google Search Console data analyzer for performance, queries, and index coverage. Triggers: Search Console, GSC analysis, search performance, rankings, CTR optimization.

SEO Search Console

Purpose

Analyze Google Search Console data: search performance (queries, pages, CTR, position), sitemap status, and index coverage.

Core Capabilities

  1. Performance Analysis - Clicks, impressions, CTR, position
  2. Query Analysis - Top search queries
  3. Page Performance - Best/worst performing pages
  4. Index Coverage - Crawl and index issues
  5. Sitemap Status - Submission and processing

Data Collection

Option 1: User Provides Data

Request GSC export from user:

  1. Go to Search Console > Performance
  2. Export data (CSV or Google Sheets)
  3. Share with assistant

Option 2: User Describes Data

User verbally provides:

  • Top queries and positions
  • CTR trends
  • Coverage issues

Analysis Framework

Performance Metrics

Metric What It Measures Good Benchmark
Clicks User visits from search Trending up
Impressions Search appearances High for target keywords
CTR Click-through rate 2-5% average
Position Average ranking <10 for key terms

Query Analysis

Identify:

  • Winners - High position, high CTR
  • Opportunities - High impressions, low CTR
  • Quick wins - Position 8-20, low effort to improve

Page Analysis

Categorize:

  • Top performers - High clicks, good CTR
  • Underperformers - High impressions, low CTR
  • Declining - Down vs previous period

Workflow

  1. Collect GSC data from user
  2. Analyze performance trends
  3. Identify top queries and pages
  4. Find optimization opportunities
  5. Check for coverage issues
  6. Provide actionable recommendations

Output Format

## Search Console Analysis: [Site]

### Overview (Last 28 Days)
| Metric | Value | vs Previous |
|--------|-------|-------------|
| Clicks | X | +X% |
| Impressions | X | +X% |
| CTR | X% | +X% |
| Position | X | +X |

### Top Queries
| Query | Clicks | Position | Opportunity |
|-------|--------|----------|-------------|

### Top Pages
| Page | Clicks | CTR | Status |
|------|--------|-----|--------|

### Opportunities
1. [Query with high impressions, low CTR]
2. [Page ranking 8-20 that can improve]

### Issues
- [Coverage problems]
- [Sitemap issues]

### Recommendations
1. [Priority action]

Common Issues

Issue Impact Fix
Low CTR on high-impression query Lost traffic Improve title/description
Declining positions Traffic loss Update content, build links
Not indexed pages No visibility Fix crawl issues
Sitemap errors Discovery problems Fix sitemap XML

Limitations

  • Requires user to provide GSC data
  • API access needs service account setup
  • Data has 2-3 day delay
  • Limited to verified properties

Notion Output (Required)

All audit reports MUST be saved to OurDigital SEO Audit Log:

  • Database ID: 2c8581e5-8a1e-8035-880b-e38cefc2f3ef
  • Properties: Issue (title), Site (url), Category, Priority, Found Date, Audit ID
  • Language: Korean with English technical terms
  • Audit ID Format: [TYPE]-YYYYMMDD-NNN