agentleFS
ZachArticulateVZachArticulateV/designer-pro-and-seo/skills/seo-sitemap/SKILL.md

seo-sitemap

Skill10 starsChanged 28 days agoMITView on GitHub

Audits and generates sitemaps.org-compliant XML sitemaps and the internal-link architecture around them. Validates structure and honesty (protocol limits, hosts, duplicates, lastmod format/future/auto-bumped, image/video/news/hreflang extensions), runs quality gates (4xx, redirects, noindex, canonical-elsewhere, missing pages), maps the internal link graph (orphans, click depth, broken links, dead ends, generic anchors), and generates sitemaps with real per-URL lastmod. Trigger when the user says "sitemap", "XML sitemap", "generate sitemap", "validate sitemap", "sitemap issues", or "sitemap index".

  • Reads credentials

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-agentic, seo-maps and 2 more.

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

  • timruebenachSkill

    seo-maps

    Maps intelligence for local SEO — geo-grid rank tracking, GBP profile auditing via API, review intelligence across Google/Tripadvisor/Trustpilot, cross-platform NAP verification (Google/Bing/Apple/OSM), competitor radius mapping, and LocalBusiness schema generation from API data. Three-tier capability: free (Overpass + Geoapify), DataForSEO (full intelligence), DataForSEO + Google (maximum coverage). Use when user says "maps", "geo-grid", "rank tracking", "GBP audit", "review velocity", "competitor radius", "maps analysis", "local rank tracking", "Share of Local Voice", or "SoLV".

    Also in 17 projects that use this

  • timruebenachSkill

    seo-flow

    FLOW framework integration — evidence-led SEO using the Find → Leverage → Optimize → Win loop. Surfaces stage-specific AI prompts from the FLOW knowledge base (41 prompts, CC BY 4.0). Use when user says "FLOW", "FLOW framework", "seo flow", "evidence-led SEO", "find leverage optimize win", or wants stage-specific SEO prompts.

    Also in 9 projects that use this

  • mangollcSkill

    seo-local

    Local SEO optimization: Google Business Profile post generation, 30-day posting calendars, NAP consistency checks, local citation audits, review response templates, local keywords.

    Also in 20 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Tier 1 — Firecrawl MCP: When connected, crawl the live site to discover the true URL set (including JS-only pages) before validating or …

    line 74
  2. Distinctive:

    Tier 4 — guided: If the URL set must come from a JS-rendered crawl and Firecrawl isn't connected, deliver the structural validation + …

    line 80
  3. Distinctive:

    Always end by stating which tier ran and what a full crawl would add.

    line 96

“Common” is measured: kept by at least 6 in 10 of the 31 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

seo-sitemap

Family: seo Status: Stable

Purpose

Audit and generation for XML sitemaps. The script handles structure deterministically (well-formed XML, the 50,000-URL / 50 MB protocol limits, automatic sitemap-index splitting, absolute-URL checks); the skill layers the live quality gates that catch the most common silent issues: URLs that 404, are noindexed, or canonicalize elsewhere should never be in a sitemap.

Triggers

  • "sitemap" / "xml sitemap"
  • "generate sitemap" / "sitemap index"
  • "sitemap issues"

Inputs

  • A sitemap file/URL (audit), or a list of URLs (generate)
  • Optional: base URL (for index child links) and a lastmod date

Steps

  1. Validate structure + honesty (.xml or .xml.gz; --as-of enables date checks):
    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/sitemap_tools.py" --validate sitemap.xml --as-of <YYYY-MM-DD>
    Protocol limits (50,000 URLs / 50 MB, absolute locs, root, namespace), host and scheme consistency, duplicates, fragments, tracking parameters, lastmod honesty (format, future dates, one date stamped on everything), ignored changefreq/priority, and the image / video / news / hreflang extensions. Codes S01–S26 and severities: references/seo-sitemap/gates-and-architecture.md.
  2. Run the quality gates — a sitemap should list only 200, indexable, self-canonical URLs. With page states from a crawl or tech_audit.py runs:
    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/sitemap_tools.py" --crosscheck sitemap.xml --pages pages.json
    or let the script sample-fetch them through the shared SSRF guard (it states the sampling boundary):
    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/sitemap_tools.py" --check-live sitemap.xml --sample 25
    Gates G1–G5: 4xx/5xx, redirects, noindex, canonical-elsewhere, and indexable pages missing from the sitemap.
  3. Audit the internal-link architecture against the sitemap — orphans, islands, click depth > 3, broken internal links, dead ends, nav-only and generic-anchor pages, internal nofollow:
    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/link_graph.py" --dir dist/ --base-url https://site.com --sitemap sitemap.xml --human
    (For a live site, feed a crawler's {page: [links]} export via --edges.)
  4. Generate a fresh sitemap with real per-URL change dates:
    python3 "${CLAUDE_PLUGIN_ROOT}/scripts/seo/sitemap_tools.py" --generate --urls urls.txt --out sitemap.xml \
      --base-url https://site.com --lastmod-file lastmod.csv
    It dedupes, drops non-http(s) URLs, and splits into an index past 50,000 URLs.
  5. Robots: confirm robots.txt has a Sitemap: directive (the AI-crawler verdict from scripts/seo/ai_crawlers.py lists the sitemaps it finds).

Capability routing

This skill follows the plugin's capability-tier cascade (references/CAPABILITY-TIERS.md) and always produces a validated sitemap:

  1. Tier 1 — Firecrawl MCP. When connected, crawl the live site to discover the true URL set (including JS-only pages) before validating or generating.
  2. Tier 2 — built-in (the default). Otherwise sitemap_tools.py validates structure deterministically and generates a sitemaps.org-compliant file from a URL list, with site_map.py supplying the robots + sitemap-recursion inventory. Fully offline — this is the product.
  3. Tier 4 — guided. If the URL set must come from a JS-rendered crawl and Firecrawl isn't connected, deliver the structural validation + generation and name what a full crawl would add.
capability:   site-map
tier1:        Firecrawl MCP
tier1_signal: FIRECRAWL_API_KEY | FIRECRAWL_API_URL
tier2:        sitemap_tools.py (validate + crosscheck + generate) + link_graph.py (internal-link graph) + site_map.py (robots + sitemap recursion -> URL inventory)
tier2_yields: validated sitemaps.org-compliant sitemap + 404/noindex/canonical offender list, zero spend
tier3:        none
tier3_signal: none
tier4:        paste the sitemap or URL list; add a Firecrawl MCP to discover JS-only URLs for a full inventory
needs_tier1:  none

Always end by stating which tier ran and what a full crawl would add.

Outputs

  • Structure + honesty validation report with a score
  • Quality-gate results (4xx / redirect / noindex / canonical-elsewhere / missing pages)
  • Internal-link architecture report (orphans, depth, broken links, anchors) with a score
  • Generated sitemap(s) + index for large sites

Dependencies

  • scripts/seo/sitemap_tools.py (required) — validate / crosscheck / check-live / generate
  • scripts/seo/link_graph.py (required) — internal-link graph audit
  • scripts/seo/site_map.py (required) — robots + sitemap-recursion URL inventory
  • references/seo-sitemap/gates-and-architecture.md (required) — codes, gates, scoring

Notes

The "no noindex, no canonical-elsewhere" gates catch the most common silent sitemap issue. Structure is validated offline; the live gates need URL fetches.

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.