Andrew Yim
d1cd1298a8
Pipeline Orchestrator: - Add 07-pipeline-orchestrator skill with code/CLAUDE.md and desktop/SKILL.md - Add /reference-curator-pipeline slash command for full workflow automation - Add pipeline_runs and pipeline_iteration_tracker tables to schema.sql - Add v_pipeline_status and v_pipeline_iterations views - Add pipeline_config.yaml configuration template - Update AGENTS.md with Reference Curator Skills section - Update claude-project files with pipeline documentation Skill Format Refactoring: - Extract YAML frontmatter from SKILL.md files to separate skill.yaml - Add tools/ directories with MCP tool documentation - Update SKILL-FORMAT-REQUIREMENTS.md with new structure - Add migrate-skill-structure.py script for format conversion Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
120 lines
3.0 KiB
Markdown
120 lines
3.0 KiB
Markdown
# 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
|
|
|
|
```markdown
|
|
## 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
|
|
|