agentleFS
oegeyilmaz9oegeyilmaz9/seo-aeo-geo-ultimate/skills/seo-sitemap/SKILL.md

seo-sitemap

Skill6 starsChanged 3 months agoApache-2.0View on GitHub

Use when auditing, generating, or planning XML and Markdown sitemap changes from a verified canonical URL inventory, discovery evidence, and current protocol guidance; do not promise crawling or indexing from sitemap inclusion.

32 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-sxo, seo-maps and 8 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.
  • timruebenachSkill

    seo-sxo

    Search Experience Optimization: reads Google SERPs backwards to detect page-type mismatches, derives user stories from search intent signals, and scores pages from multiple persona perspectives. Identifies why well-optimized pages fail to rank by analyzing what Google rewards for each keyword. Use when user says "SXO", "search experience", "page type mismatch", "SERP analysis", "user story", "persona scoring", "why isn't my page ranking", "intent mismatch", or "wireframe".

    Also in 20 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

  • indranilbanerjeeSkill

    seo-drift

    Compare two SEO exports (Search Console, two dates): gainers, losers, drift classes. \"what moved after the core update\"

    Also in 20 projects that use this

  • mangollcSkill

    seo-backlinks

    Backlink analysis and link building strategy: competitor backlink profiling, outreach plan generation, monthly SEO reporting framework, toxic link identification, link opportunity scoring, and unlinked mention discovery.

    Also in 17 projects that use this

  • +6 more from timruebenach

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 31 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read references/sitemap-inventory-protocol.md before creating or changing a sitemap.

    line 19
  2. Distinctive:

    Compare with intent: Check whether each listed URL is expected to be canonical, accessible, indexable, stable, and within the declared …

    line 28
  3. Very specific:

    Generate only from verified inventory: Use current official protocol/engine documentation for limits and fields.

    line 30
  4. Distinctive:

    Do not list redirecting, error, duplicate, blocked, noindex, session, staging, faceted, or unapproved URLs merely to increase coverage.

    line 35
  5. Distinctive:

    Do not submit every URL variant, use sitemap timestamps as a freshness hack, or assume sitemap acceptance proves indexing.

    line 36
  6. Distinctive:

    Keep user-facing availability, crawlability, canonicalization, and actual indexed state as separate measurements.

    line 37

“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

XML and Markdown Sitemaps

Markdown delivery contract

Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats. Include concise robots/XML-sitemap discovery comments and llms.txt navigation sentences pointing to actual Markdown answers; preserve the native protocols and verify delivery as described in the local contract.

Lane outputs: sitemap-inventory.md; sitemap-dispositions.md; markdown-coverage.md (combine small related steps with stable section links). Own reconciliation of CMS/routes, XML, internal discovery and every inventory URL disposition. Produce sitemap.md, topic maps and exact canonical-to-.md mappings for the entire eligible scope. Preserve XML protocol and truthful lastmod; keep excluded sensitive URLs in private records.

Purpose

Compare sitemap files with the URLs a site actually intends to expose, then produce safe inventory, generation, or cleanup recommendations. A sitemap is a discovery hint; it neither forces crawling nor guarantees indexation.

Read references/sitemap-inventory-protocol.md before creating or changing a sitemap.

Input gate

Require the current sitemap/index files, expected canonical/indexable URL inventory, preferred host/protocol, robots/sitemap discovery context, relevant locale rules, and source of truth for update time. Do not generate a sitemap from an unfiltered crawler export or an unverified CMS list.

Workflow

  1. Parse and retain evidence. Record sitemap URL, fetch time/status, declared locations, syntax errors, and any nested sitemap references.
  2. Compare with intent. Check whether each listed URL is expected to be canonical, accessible, indexable, stable, and within the declared locale/host policy. Separately identify important intended URLs that are absent.
  3. Classify mismatches. Distinguish sitemap hygiene, canonical/indexability conflict, stale inventory, locale mapping, server delivery, and unresolved access issues.
  4. Generate only from verified inventory. Use current official protocol/engine documentation for limits and fields. Include lastmod only when it is a truthful, reliable content-change timestamp. Do not fill optional fields with invented values.
  5. Release safely. State source system, affected sitemap/index, rollout, test URL, validation, monitoring, and rollback. Coordinate locale URLs with seo-hreflang and technical delivery with seo-technical.

Guardrails

  • Do not list redirecting, error, duplicate, blocked, noindex, session, staging, faceted, or unapproved URLs merely to increase coverage.
  • Do not submit every URL variant, use sitemap timestamps as a freshness hack, or assume sitemap acceptance proves indexing.
  • Keep user-facing availability, crawlability, canonicalization, and actual indexed state as separate measurements.
  • For large/sensitive changes, create an approved seo-action-plan; this skill only prepares the change and validation path.

Formal evidence handoff

When this work needs a cross-team, approval-ready plan, package evidence-bound findings as an immutable seo-findings.json bundle using the checked-out suite contract. Let <suite-root> mean ${CLAUDE_PLUGIN_ROOT} in Claude Code. In Codex, read .seo-suite-runtime.json beside this SKILL.md when present and use its suite_root value; otherwise use the absolute repository checkout. Keep every referenced capture/source below raw/, retain declined claims and limitations, and run python "<suite-root>/scripts/validate_seo_findings.py" validate-findings <bundle>/seo-findings.json --bundle <bundle>. Send only a passing bundle to seo-action-plan; otherwise label the handoff provisional.

Output

Return the verified inventory comparison, sitemap defects/opportunities, source-of-truth assumptions, a generated XML proposal when authorized, and test/rollback instructions. Never output a sitemap “score” or an indexing guarantee.

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.