sitemap-audit

Validate AEM Edge Delivery Services sitemaps against query index content and URL reachability.

1|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/aemgdc/aemdev --skill sitemap-audit-aemgdc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sitemap-audit
Source: https://github.com/aemgdc/aemdev/tree/main/.agents/skills/sitemap-audit
Command: npx skills add https://github.com/aemgdc/aemdev --skill sitemap-audit-aemgdc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Sitemaps on AEM Edge Delivery Services sites often drift out of sync with published content, leaking draft or fragment URLs, listing deleted pages, or missing live pages, which harms SEO and indexing. This Skill audits the sitemap against the query index and live URLs to surface every discrepancy with concrete fixes. ## Core Features & Use Cases - Cross-Reference Validation: Compares sitemap.xml entries against the paginated query-index.json to find missing pages, stale entries, and lastmod mismatches. - Health & Structure Checks: Verifies URL reachability (404s, redirects, 5xx), robots.txt Sitemap directives, fragment/draft leaks, lastmod date formats, and sitemap size limits. - Actionable Reporting: Produces a summary table plus specific addition, removal, and helix-sitemap.yaml configuration fix recommendations. - Use Case: Before launching an EDS site, run the audit to confirm all published pages appear in the sitemap, no /drafts/ or /fragments/ paths leak, and robots.txt points to the production sitemap. ## Quick Start Audit the sitemap at https://www.example.com/sitemap.xml against its query index and report any missing, broken, or leaked URLs.

Frequently Asked Questions about sitemap-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a sitemap on an AEM Edge Delivery Services site?▼

Fetch the sitemap.xml and robots.txt, then cross-reference every URL against the paginated query-index.json, which is the canonical list of published EDS content. Check URL reachability with HEAD requests and validate lastmod dates against the query index lastModified field.

How do I find pages missing from my EDS sitemap?▼

Compare the query index entries against sitemap URLs; pages in the query index but absent from the sitemap are gaps, excluding intentional omissions like /drafts/, /fragments/, /nav, /footer, and noindex pages. Fix them by adjusting include patterns in helix-sitemap.yaml.

Why do draft or fragment URLs appear in my sitemap?▼

Fragment and draft leaks happen when helix-sitemap.yaml is missing exclude patterns or uses /fragments/* instead of /fragments/**, which misses nested paths. Add /drafts/** and /fragments/** to the exclude list and republish the configuration.

Why do all lastmod dates in my sitemap look identical?▼

Uniform lastmod dates indicate the properties.lastmod mapping in helix-sitemap.yaml is missing or points to a build-time field instead of actual content modification. Set properties.lastmod to lastModified so dates come from the query index.

What are the limitations of auditing very large sitemaps?▼

Sites with 10,000 or more URLs are not suited for full audits; spot-check a sample of around 50 URLs plus all flagged entries instead. Sitemaps exceeding 50,000 URLs or 50MB violate the sitemap protocol and must be split.