agentleFS
martinbattaglia-commitsmartinbattaglia-commits/Claude-skills/skills/seo-sitemap/SKILL.md

seo-sitemap

Skill0 starsChanged 5 months agoMITView on GitHub

Analyze existing XML sitemaps or generate new ones with industry templates. Validates format, URLs, and structure. Use when user says "sitemap", "generate sitemap", "sitemap issues", or "XML sitemap".

32 other projects use a version of this, 22 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AgriciDanielSkill

    seo-agentic

    Audit and fix agent readiness: the Lighthouse Agentic Browsing fraction, accessibility tree for agents, robots.txt and Content-Signal for AI agents, WAF treatment of agent traffic, llms.txt, Markdown delivery, ai-catalog.json, /.well-known discovery files, and WebMCP tools. Use when the user asks whether AI agents can use or browse the site, or about llms.txt or WebMCP. Exclude AI citability and brand signals (seo-geo) and commerce protocol depth (seo-ecommerce).

    Also in 5 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 5 are common, 1 is distinctive, and 1 is very specific to this project.

  • 5

    Common

    Most of the 27 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Common:

    All URLs return HTTP 200

    line 23
  2. Very specific:

    No deprecated tags: <priority> and <changefreq> are ignored by Google

    line 25
  3. Common:

    No non-canonical URLs in sitemap

    line 32
  4. Common:

    No noindexed URLs in sitemap

    line 33
  5. Common:

    No redirected URLs in sitemap

    line 34
  6. Common:

    Ask for business type (or auto-detect from existing site)

    line 50
  7. Distinctive:

    No sitemap found: Check common locations (/sitemap.xml, /sitemap_index.xml, robots.txt reference) before reporting "not found"

    line 104

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Sitemap Analysis & Generation

Mode 1: Analyze Existing Sitemap

Validation Checks

  • Valid XML format
  • URL count <50,000 per file (protocol limit)
  • All URLs return HTTP 200
  • <lastmod> dates are accurate (not all identical)
  • No deprecated tags: <priority> and <changefreq> are ignored by Google
  • Sitemap referenced in robots.txt
  • Compare crawled pages vs sitemap; flag missing pages

Quality Signals

  • Sitemap index file if >50k URLs
  • Split by content type (pages, posts, images, videos)
  • No non-canonical URLs in sitemap
  • No noindexed URLs in sitemap
  • No redirected URLs in sitemap
  • HTTPS URLs only (no HTTP)

Common Issues

IssueSeverityFix
>50k URLs in single fileCriticalSplit with sitemap index
Non-200 URLsHighRemove or fix broken URLs
Noindexed URLs includedHighRemove from sitemap
Redirected URLs includedMediumUpdate to final URLs
All identical lastmodLowUse actual modification dates
Priority/changefreq usedInfoCan remove (ignored by Google)

Mode 2: Generate New Sitemap

Process

  1. Ask for business type (or auto-detect from existing site)
  2. Load industry template from ../seo-plan/assets/ directory
  3. Interactive structure planning with user
  4. Apply quality gates:
    • ⚠️ WARNING at 30+ location pages (require 60%+ unique content)
    • 🛑 HARD STOP at 50+ location pages (require justification)
  5. Generate valid XML output
  6. Split at 50k URLs with sitemap index
  7. Generate STRUCTURE.md documentation

Safe Programmatic Pages (OK at scale)

✅ Integration pages (with real setup docs) ✅ Template/tool pages (with downloadable content) ✅ Glossary pages (200+ word definitions) ✅ Product pages (unique specs, reviews) ✅ User profile pages (user-generated content)

Penalty Risk (avoid at scale)

❌ Location pages with only city name swapped ❌ "Best [tool] for [industry]" without industry-specific value ❌ "[Competitor] alternative" without real comparison data ❌ AI-generated pages without human review and unique value

Sitemap Format

Standard Sitemap

<?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>

Sitemap Index (for >50k URLs)

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/sitemap-pages.xml</loc>
    <lastmod>2026-02-07</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-posts.xml</loc>
    <lastmod>2026-02-07</lastmod>
  </sitemap>
</sitemapindex>

Error Handling

  • URL unreachable: Report the HTTP status code and suggest checking if the site is live
  • No sitemap found: Check common locations (/sitemap.xml, /sitemap_index.xml, robots.txt reference) before reporting "not found"
  • Invalid XML format: Report specific parsing errors with line numbers
  • Rate limiting detected: Back off and report partial results with a note about retry timing

Output

For Analysis

  • VALIDATION-REPORT.md: analysis results
  • Issues list with severity
  • Recommendations

For Generation

  • sitemap.xml (or split files with index)
  • STRUCTURE.md: site architecture documentation
  • URL count and organization summary

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.