Seo Sitemap logo

Seo Sitemap

CommunityPopular
AgriciDaniel
seo-sitemap

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".

Overview

PublisherAgriciDaniel
Repositoryclaude-seo
Skill nameseo-sitemap
Stars
17.1K
Forks
2.5K
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by AgriciDaniel on GitHub. Read the source before you install it.

Installation

Install the Seo Sitemap AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/AgriciDaniel/claude-seo.git /tmp/claude-seo
mkdir -p .claude/skills
cp -r /tmp/claude-seo/skills/seo-sitemap .claude/skills/seo-sitemap
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Seo Sitemap in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Seo Sitemap on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Seo Sitemap is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Sitemap Analysis & Generation

Mode 1: Analyze Existing Sitemap

Discover candidates before reporting a sitemap missing:

bash
"${CLAUDE_PLUGIN_ROOT}/scripts/claude-seo" run sitemap_discovery.py <url> --json

The helper reads every bounded Sitemap: declaration in robots.txt, validates cross-host targets through the shared SSRF-safe fetch layer, and still probes common paths when a declared sitemap is stale or invalid. Use only entries in found; preserve declared failures as findings instead of treating a robots.txt line alone as proof that a sitemap works.

Validation Checks

  • Valid XML format
  • Per-file limit: ≤50,000 URLs AND ≤50MB uncompressed (whichever is hit first)
  • All URLs return HTTP 200
  • <lastmod> accurate: must be a valid W3C Datetime and reflect the last significant content change (main content, structured data, links, not copyright/boilerplate edits). Google only honours <lastmod> when consistently and verifiably accurate, so warn when values are suspiciously uniform or newer than the page's real content.
  • 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
>50MB uncompressed 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)

Extension sitemaps (image / video / news)

Google documents three subtypes with their own rules, validate per-subtype:

  • Image (http://www.google.com/schemas/sitemap-image/1.1): only two valid tags remain, <image:image> and <image:loc> (max 1,000 <image:image> per <url>). <image:caption>/<image:geo_location>/<image:title>/ <image:license> were deprecated (2022), flag as info-level removable.
  • Video: required <video:video> with <video:thumbnail_loc>, <video:title>, <video:description>, plus <video:content_loc> or <video:player_loc>; mRSS also supported. Flag deprecated/removed tags (<video:category>, <video:gallery_loc>, <video:price>, <video:tvshow>, player autoplay/allow_embed) as info-level removable; recheck Google docs before citing a removal date.
  • News: max 1,000 <news:news> per file (not 50,000); include only articles from the last 2 days; required <news:publication>/<news:name>/ <news:language>/<news:publication_date>/<news:title>; submit/discover through Search Console or robots.txt/sitemap index; use Publisher Center only for publication management where relevant. When the news: namespace is detected, override the generic 50k check with the 1,000 cap.

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 whichever comes first: 50,000 URLs or 50MB uncompressed, 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
<?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
<?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: Run sitemap_discovery.py and report "not found" only when its found list is empty after declared and common candidates are checked
  • 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

Frequently asked questions

What does the Seo Sitemap AI skill do?

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".

Why use Seo Sitemap on TypingMind?

Because you install it once and use it with any model. Seo Sitemap is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Seo Sitemap in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AgriciDaniel/claude-seo/tree/main/skills/seo-sitemap. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Seo Sitemap?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Seo Sitemap?

As many as you like. As long as a model supports skills, you can use Seo Sitemap with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Seo Sitemap AI skill free?

Yes. It is published on GitHub by AgriciDaniel under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇