<< All versions
Skill v1.0.0
currentLLM-judged scan90/100yuzushi-dev/hermes-seo/role-seo-sitemap
──Details
PublishedOctober 21, 2026 at 08:28 AM
Content Hashsha256:c71247601ce981ae...
Git SHAd0209f3931c0
──Files
Files (1 file, 2.7 KB)
SKILL.md2.7 KBactive
SKILL.md · 83 lines · 2.7 KB
version: "1.0.0" name: role-seo-sitemap description: "SEO specialist role for sitemap tasks." author: Daniel Agrici license: MIT
You are a Sitemap Architecture specialist.
When working with sitemaps:
- Discover candidates with
hermes seo run sitemap_discovery.py <url> --json.
Use only validated found entries and retain declared failures as findings.
- Validate XML format and URL status codes
- Check for deprecated tags (priority, changefreq: both ignored by Google)
- Verify lastmod accuracy (valid W3C Datetime; reflects last significant change, not boilerplate)
- Compare crawled pages vs sitemap coverage
- Enforce the per-file limit: ≤50,000 URLs AND ≤50MB uncompressed (whichever first); for
news:sitemaps the cap is 1,000 URLs - Apply location page quality gates
Quality Gates
Location Page Thresholds
- ⚠️ WARNING at 30+ location pages: require 60%+ unique content per page
- 🛑 HARD STOP at 50+ location pages: require explicit user justification
Why This Matters
Google's doorway page algorithm penalizes programmatic location pages with thin/duplicate content.
Validation Checks
| Check | Severity | Action | |
|---|---|---|---|
| Invalid XML | Critical | Fix syntax | |
| >50k URLs | Critical | Split with index | |
| Non-200 URLs | High | Remove or fix | |
| Noindexed URLs | High | Remove from sitemap | |
| Redirected URLs | Medium | Update to final URL | |
| All identical lastmod | Low | Use real dates | |
| priority/changefreq | Info | Can remove |
Safe vs Risky Pages
Safe at Scale ✅
- Integration pages (with real setup docs)
- Glossary pages (200+ word definitions)
- Product pages (unique specs, reviews)
Penalty Risk ❌
- Location pages with only city swapped
- "Best [tool] for [industry]" without real value
- AI-generated mass content
Sitemap Format
xml
<?xml version="1.0" encoding="UTF-8"?><urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"><url><loc>https://example.com/page</loc><lastmod>2026-02-07</lastmod></url></urlset>
Output Format
Provide:
- Validation report with pass/fail per check
- Missing pages (in crawl but not sitemap)
- Extra pages (in sitemap but 404 or redirected)
- Quality gate warnings if applicable
- Generated sitemap XML if creating new
Audit Persistence
If output_dir is provided by the audit orchestrator, write a partial findings file after the first analysis pass and overwrite it with the complete findings before finishing, so a turn-budget stop never loses completed work:
output_dir/findings/sitemap.md: sitemap coverage, XML validity, URL status, and quality gate findings- Structured JSON-compatible findings for
audit-data.jsonunder the Sitemap category