Include indexable pages in your sitemap
SkillSearchSitemap-coverage is a skill for AI agents that checks whether every indexable page on a site appears in its XML sitemap. Pages missing from the sitemap depend on link-based crawl discovery, which can delay indexing of new content. It suits content sites, e-commerce stores, and any site where timely indexing of new pages matters, and helps when investigating why new pages take a long time to appear in search results.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an agent that can load skills, and access to the site's XML sitemap and its list of canonical, indexable URLs.
Then ask your AI: use the Include indexable pages in your sitemap skill
What your AI can do with it
- Compare canonical, indexable URLs on a site against the URLs in the XML sitemap
- Flag pages that return HTTP 200, have no noindex directive, and a self-referencing canonic
- Identify pages with noindex, redirects, or non-self canonical tags that should be removed
- Use the Google Search Console Coverage report to find indexable pages not in the sitemap
- Explain how missing sitemap coverage slows crawl discovery and which page types to include
- Review metadata generation, rendered HTML, structured data, and response headers for this
Getting started
- Have an agent that can load skills, and access to the site's XML sitemap and its list of canonical, indexable URLs.
- Add the sitemap-coverage skill to the agent's available skills.
- Ask the agent to check the site, providing the sitemap location and, if available, Google Search Console access for the Coverage report.
- Review the flagged pages, then add missing indexable pages to the sitemap and remove noindex, redirecting, or non-self-canonical pages from it.
- Automate sitemap generation so newly published content is included immediately.
What this skill tells your AI
The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/sitemap-coverage/SKILL.md and read by ahel’s review.
Pages absent from the sitemap rely entirely on crawl discovery via links, which can delay indexing of new content, especially on large sites or pages with few inbound links.
Quick Reference
- Every canonical-url, indexable page should appear in the sitemap
- Pages with
noindexor non-self canonical tags must NOT be included in the sitemap - Paginated pages, filtered variants, and faceted URLs are usually excluded unless they have unique content
- Use Google Search Console Coverage report to find indexable pages not in the sitemap
Check
Compare the list of all canonical-url, indexable URLs on the site against the URLs in the XML sitemap. Flag any page that returns HTTP 200, has no noindex directive, has a self-referencing canonical, but is absent from the sitemap.
Fix
Add missing indexable pages to the sitemap. Remove pages that carry noindex, redirect, or non-self canonical tags from the sitemap. Automate sitemap generation so newly published content is included immediately.
Explain
Explain how missing sitemap coverage slows crawl discovery, which types of pages should and should not be included, and how to use Google Search Console to identify gaps.
Code Review
Review metadata generation, rendered HTML, structured data, and response headers related to Include indexable pages in your sitemap. Flag exact routes or templates where search-facing output violates the rule, and describe how to verify the final page output.
For full implementation details, code examples, and framework-specific guidance,
see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/seo/sitemap-coverage
Signals
- GitHub stars
- 74k
- Forks
- 7k
- Last commit
- Aug 2026
Questions
- What kinds of sites is this for?
- Content sites, e-commerce stores, and any site where timely indexing of new pages matters.
- When should it be used?
- When investigating why new pages take a long time to appear in search results, or when auditing sitemap coverage generally.
Advanced
- Item type
- skill
- Key
sitemap-coverage- Source
- github.com/thedaviddias/front-end-checklist