agentleFS
Sign inStart free
6t9xstar6t9xstar/one-step-seo/skills/sitemap-robots/SKILL.md

sitemap-robots

Skill5 starsChanged 37 days agoMITView on GitHub

Audit robots.txt directives, AI crawler access rules, XML sitemap discovery, sitemap index structures, and crawl coverage using one-step-seo sitemap and audit commands.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 7

    Very specific

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

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

    Verify whether Sitemap: directives in robots.txt resolve properly or whether a <sitemapindex> is properly structured.

    line 13
  2. Very specific:

    Verify /robots.txt returns 200 OK with valid User-agent: / Allow: / Disallow: groups.

    line 30
  3. Very specific:

    Check whether G02-ai-blocked fires, and inspect the exact list of blocked AI bot tokens (out of the 25 recognized AI crawlers such as …

    line 31
  4. Very specific:

    When T06-sitemap fails, specify whether the file was missing (HTTP 404) or returned 200 with zero valid <loc> entries.

    line 55
  5. Very specific:

    When reporting orphan pages, cite the exact URLs listed under Possibly orphaned pages in index.md.

    line 56
  6. Very specific:

    Crawler Access Policy: Search engine vs AI crawler permissions (Allow vs Disallow by user-agent).

    line 61
  7. Very specific:

    Never recommend exposing private admin, API, or user-account paths in robots.txt or sitemap.xml.

    line 72

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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-robots — Sitemap & Robots Discovery Policy

1. Description & Activation Criteria

Activate sitemap-robots when the user wants to:

  • Inspect or troubleshoot /robots.txt and /sitemap.xml discovery (T05-robots, T05-robots-disallow, T06-sitemap, G02-ai-blocked).
  • Verify whether Sitemap: directives in robots.txt resolve properly or whether a <sitemapindex> is properly structured.
  • Seed a multi-page audit from the XML sitemap (--crawl sitemap) to uncover unlinked or orphaned pages.

2. Inputs & Prerequisites

  • Target: Public http(s) URL or local build directory containing robots.txt and sitemap.xml.
  • Optional flags:
    • sitemap <url> --json: Fast discovery inspection without running a full page crawl.
    • audit <url> --crawl sitemap --pages <N>: Crawl pages seeded directly from /sitemap.xml (or the first Sitemap: URL in robots.txt).
    • --skills sitemap-robots: Filter audit findings to robots, sitemap, and crawl-policy rules.

3. Step-by-Step Workflow

  1. Run discovery diagnostics:
    • Execute npx one-step-seo sitemap <url> --json.
    • Inspect robotsFound, robotsSitemaps, sitemapFound, sitemapUrl, sitemapUrls, sitemapTruncated, and llmsFound.
  2. Audit robots.txt syntax and crawler permissions (T05-robots, G02-ai-blocked):
    • Verify /robots.txt returns 200 OK with valid User-agent: / Allow: / Disallow: groups.
    • Check whether G02-ai-blocked fires, and inspect the exact list of blocked AI bot tokens (out of the 25 recognized AI crawlers such as gptbot, claudebot, perplexitybot, google-extended).
  3. Evaluate XML Sitemap health (T06-sitemap):
    • Confirm the sitemap contains valid <loc> entries (or plaintext URLs) and is not an HTML 404 page served with a 200 status.
    • Distinguish a standard <urlset> (~N URLs) from a <sitemapindex> (~N child sitemaps).
  4. Compare sitemap inventory against internal link discovery:
    • Run npx one-step-seo audit <url> --crawl sitemap --pages 20 --out ./seo-report.
    • Inspect the terminal output and index.md / index.html for Possibly orphaned pages (URLs present in sitemap.xml that received zero inbound internal links from crawled pages).

4. Tools & CLI Commands

# Quick JSON check of robots.txt, sitemap.xml, and llms.txt
npx one-step-seo sitemap https://example.com --json

# Audit 20 pages seeded from the XML sitemap
npx one-step-seo audit https://example.com --crawl sitemap --pages 20 --out ./seo-report

# Focused sitemap & robots rule check on a single URL
npx one-step-seo page https://example.com --skills sitemap-robots --out ./seo-report

5. Evidence Requirements

  • Quote report.site.robots, report.site.sitemap, report.site.sitemapUrls, and report.site.llms from report.json (or robotsFound, robotsSitemaps, sitemapFound, sitemapUrl, sitemapUrls, sitemapTruncated, llmsFound from sitemap --json). For blocked AI crawlers, quote the G02-ai-blocked finding evidence from report.findings (or signals.robotsAiBlocked / signals.blockedBots from ai --json).
  • When T06-sitemap fails, specify whether the file was missing (HTTP 404) or returned 200 with zero valid <loc> entries.
  • When reporting orphan pages, cite the exact URLs listed under Possibly orphaned pages in index.md.

6. Expected Outputs

  1. Discovery Status Summary: Status of /robots.txt, Sitemap: declarations, resolved /sitemap.xml URL, entry count, and /llms.txt.
  2. Crawler Access Policy: Search engine vs AI crawler permissions (Allow vs Disallow by user-agent).
  3. Remediation Snippets: Ready-to-use robots.txt or sitemap.xml structure fixes.

7. Limitations & External Data

  • Same-origin enforcement: Sitemap URLs and child <sitemapindex> files are filtered to the audited origin for security; cross-host sitemap seeds are ignored.
  • Crawl cap: getSitemapUrls follows up to 5 child sitemaps in a <sitemapindex> and caps crawled pages at --pages (max 200).
  • External data (advisory): Live Google Search Console sitemap submission errors and index coverage ratios require GSC access.

8. Safety & Approval Rules

  • Never recommend exposing private admin, API, or user-account paths in robots.txt or sitemap.xml.
  • Remind users that robots.txt Disallow prevents crawling, not indexing of linked URLs — sensitive pages must use noindex or authentication.

9. Examples

# Inspect sitemap and robots configuration in JSON mode
npx one-step-seo sitemap https://example.com --json

# Audit sitemap-seeded pages and check for orphans
npx one-step-seo audit https://example.com --crawl sitemap --pages 15 --out ./seo-report

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.

Check your setup, free