An AI sitemap optimization agent checks that the XML file Google fetches lists canonical URLs, stays inside protocol limits, and carries a lastmod date only when that date matches a real content change.
TLDR
A sitemap helps discovery. It does not guarantee crawl or index (sitemap overview).
One file: 50,000 URLs or 50 MB uncompressed. Larger sets use a sitemap index (build a sitemap).
Google uses lastmod only when it is consistently accurate. Google ignores changefreq and priority.
Sites of about 500 pages or fewer, with solid internal links, often do not need a sitemap. Large, new, or media-heavy sites do.
First-party GSC (24 Augβ21 Sep 2026): /skills/seo-sitemap had 70 impressions and 0 clicks at position ~50. The query ai sitemap optimization agent had 55 impressions at position ~59.
Search Central defines a sitemap as a file that lists pages, videos, and other files you consider important, plus optional dates and language alternates. CMS platforms such as WordPress often emit one already.
This pillar is the method. Agent recipes (/cline/seo-sitemap) install the same checks. The parent catalog is the skills directory.
Check
Pass
URL
Canonical, 200, same host policy you submit
Format
XML urlset, RSS, or text. Extension matches the bytes
Discovery
Listed in robots.txt and submitted in Search Console
HTML twin
People can open /sitemap and follow real links
Limits and the index file
From the build guide: split any sitemap over 50,000 URLs or 50 MB uncompressed. A sitemap index lists those files. Each index may hold up to 50,000 sitemap loc values. You can submit up to 500 index files per Search Console property (large sitemaps).
Child sitemaps should live in the same directory as the index, or deeper, unless you use cross-site submission. Referenced files must be on the same site.
This property publishes sitemap-index.xml plus the Astro sitemap. The agent should compare that index to live 200 HTML, not to draft URLs.
Google uses lastmod when it is consistently and verifiably accurate, for example by matching the pageβs last significant change (build a sitemap). The sitemaps.org protocol says the date is the page change, not the moment the file was generated. Use W3C Datetime. A date-only value YYYY-MM-DD is valid.
Significant updates include main content, structured data, or links. A copyright-year bump is not. If dates are wrong, omit lastmod. Google ignores changefreq and priority.
HTML map versus XML
XML is for crawlers. The HTML map at /sitemap is for people and for link discovery. Google says a well-linked site of about 500 indexable pages may not need XML at all. This site is larger than that, so both layers stay.
Do not put noindex URLs, parameter duplicates, or soft-404s in either file. Pair the audit with robots.txt for AI bots so a Disallow does not hide the sitemap URL itself.
Run the sitemap skill
npx @seoskillsai/cli add seo-sitemap
npx @seoskillsai/cli run seo-sitemap --target "https://example.com"
The CLI skill writes the XML index and the categorized HTML map. Keep this URL as the method page. Do not copy this H1 onto /cline/seo-sitemap or other agent recipes. Those URLs already collect a few impressions at much stronger positions. They stay install pages.
No. Google says a sitemap helps discovery and does not guarantee that every URL is crawled or indexed.
What is the file size limit?
50,000 URLs or 50 MB uncompressed per sitemap. Use an index file above that.
Should every URL have lastmod?
Only when the timestamp matches a significant page change. Wrong dates are worse than none. Google ignores changefreq and priority.
Do small sites need XML?
Googleβs own threshold is about 500 pages, when internal links already reach every important URL and you are not pushing video, image, or news files.
Where do agent install steps live?
On /{agent}/seo-sitemap. This page owns the method and the query already assigned here.