Add SEO skills 33-34 and fix bugs in skills 19-34

New skills:
- Skill 33: Site migration planner with redirect mapping and monitoring
- Skill 34: Reporting dashboard with HTML charts and Korean executive reports

Bug fixes (Skill 34 - report_aggregator.py):
- Add audit_type fallback for skill identification (was only using audit_id prefix)
- Extract health scores from nested data dict (technical_score, onpage_score, etc.)
- Support subdomain matching in domain filter (blog.ourdigital.org matches ourdigital.org)
- Skip self-referencing DASH- aggregated reports

Bug fixes (Skill 20 - naver_serp_analyzer.py):
- Remove VIEW tab selectors (removed by Naver in 2026)
- Add new section detectors: books (도서), shortform (숏폼), influencer (인플루언서)

Improvements (Skill 34 - dashboard/executive report):
- Add Korean category labels for Chart.js charts (기술 SEO, 온페이지, etc.)
- Add Korean trend labels (개선 중 ↑, 안정 →, 하락 중 ↓)
- Add English→Korean issue description translation layer (20 common patterns)

Documentation improvements:
- Add Korean triggers to 4 skill descriptions (19, 25, 28, 31)
- Expand Skill 32 SKILL.md from 40→143 lines (was 6/10, added workflow, output format, limitations)
- Add output format examples to Skills 27 and 28 SKILL.md
- Add limitations sections to Skills 27 and 28
- Update README.md, CLAUDE.md, AGENTS.md for skills 33-34

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
2026-02-14 00:01:00 +09:00
parent dbfaa883cd
commit d2d0a2d460
37 changed files with 5462 additions and 56 deletions

View File

@@ -1,7 +1,10 @@
---
name: seo-knowledge-graph
description: |
Knowledge Graph and entity SEO analysis. Triggers: knowledge panel, entity SEO, knowledge graph, PAA, FAQ schema, Wikipedia, Wikidata, brand entity.
Knowledge Graph and entity SEO analysis.
Triggers: knowledge panel, entity SEO, knowledge graph, PAA, FAQ schema,
Wikipedia, Wikidata, brand entity, 지식 그래프, 엔티티 SEO,
지식 패널, 브랜드 엔티티, 위키데이터.
---
# Knowledge Graph & Entity SEO
@@ -69,9 +72,60 @@ All reports must be saved to the OurDigital SEO Audit Log database.
Report content should be written in Korean (한국어), keeping technical English terms as-is.
## Output Format
```json
{
"entity_name": "OurDigital",
"knowledge_panel": {
"present": false,
"attributes": {}
},
"entity_presence": {
"wikipedia": false,
"wikidata": false,
"wikidata_qid": null,
"naver_encyclopedia": false,
"naver_knowledge_in": false,
"google_knowledge_panel": false
},
"entity_schema": {
"organization_count": 2,
"person_count": 1,
"same_as_links": ["https://linkedin.com/...", "https://facebook.com/..."],
"same_as_count": 2,
"issues": [
"Duplicate Organization schemas with inconsistent names",
"Placeholder image in Organization schema",
"Only 2 sameAs links (recommend 6+)"
]
},
"paa_questions": [],
"faq_schema_present": false,
"entity_completeness_score": 12,
"recommendations": [
"Create Wikidata entity for brand recognition",
"Add 4-6 more sameAs social profile links",
"Replace placeholder image with actual brand logo",
"Consolidate duplicate Organization schemas",
"Add FAQPage schema to relevant pages"
],
"audit_id": "KG-20250115-001",
"timestamp": "2025-01-15T14:30:00"
}
```
## Limitations
- Google Knowledge Panel detection via search results is not guaranteed (personalization, location-based)
- Direct Google scraping may be blocked (403/429); prefer WebSearch tool
- Wikipedia/Wikidata creation requires meeting notability guidelines
- PAA questions vary by location and device
- Entity completeness scoring is heuristic-based
## Reference Scripts
Located in `code/scripts/`:
- `knowledge_graph_analyzer.py` -- Knowledge Panel and entity presence analysis
- `entity_auditor.py` -- Entity SEO signals and PAA/FAQ audit
- `base_client.py` -- Shared async client utilities
- `knowledge_graph_analyzer.py` Knowledge Panel and entity presence analysis
- `entity_auditor.py` Entity SEO signals and PAA/FAQ audit
- `base_client.py` Shared async client utilities