Keep sitemap URLs on the correct domain

SkillDev tools

sitemap-domain is an agent skill for SEO checks on sitemaps. It finds <loc> URLs whose protocol or hostname differs from the sitemap's own domain, a common issue after HTTP-to-HTTPS migrations, domain changes, or www/non-www redirect setups. Google silently drops cross-domain sitemap entries, so fixing these mismat

Available today. Use it from your connected AI after setup.

Have an agent environment that can load skills and access the site's sitemap file.

Then ask your AI: use the Keep sitemap URLs on the correct domain skill

What your AI can do with it

  • Parse all <loc> values in a sitemap and extract each URL's protocol and hostname
  • Flag URLs whose protocol or hostname differs from the sitemap file's own URL
  • Detect http vs https, www vs non-www, and old-domain vs new-domain mismatches
  • Explain why Google ignores cross-domain sitemap URLs and how they are silently dropped
  • Review metadata generation, rendered HTML, structured data, and response headers for viola
  • Guide updating all <loc> URLs to the canonical protocol and hostname, then regenerating an

Getting started

  1. Have an agent environment that can load skills and access the site's sitemap file.
  2. Add the sitemap-domain skill to the agent's available skills.
  3. Ask the agent to check the sitemap when the site has migrated protocols or domains, or when sitemap submission reports low coverage.
  4. Apply the agent's fix by updating all <loc> URLs to the canonical protocol and hostname, then regenerate and resubmit the sitemap.
  5. Consult references/rule.md for full implementation details, code examples, and framework-specific guidance.

What this skill tells your AI

The instructions your AI receives, as published by thedaviddias/front-end-checklist in skills/sitemap-domain/SKILL.md and read by ahel’s review.

Google ignores sitemap entries from domains it cannot verify as yours — cross-domain URLs are simply skipped, meaning those pages lose the crawl-discovery benefit of the sitemap.

Quick Reference

  • Every <loc> URL must use the same domain and protocol (https://www.example.com) as the sitemap file itself
  • Cross-domain URLs in a sitemap are ignored by Google
  • Mixing http:// and https:// URLs in one sitemap creates conflicting signals
  • Mixing www and non-www variants indicates a canonicalization issue to fix first

Check

Parse all <loc> values in the sitemap and extract the protocol and hostname. Flag any URL whose protocol or hostname differs from the sitemap's own URL. Common mismatches: http vs https, www vs non-www, old domain vs new domain.

Fix

Update all <loc> URLs to use the canonical-url protocol and hostname. If the site is on https://www.example.com, every sitemap URL must start with https://www.example.com/. Regenerate and resubmit the sitemap.

Explain

Explain why Google restricts sitemap URLs to the same domain, how cross-domain URLs are silently dropped, and how domain mismatches in a sitemap reveal underlying canonicalization problems.

Code Review

Review metadata generation, rendered HTML, structured data, and response headers related to Keep sitemap URLs on the correct domain. 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-domain

Signals

GitHub stars
74k
Forks
7k
Last commit
Aug 2026

Questions

When should this skill be used?
Use it for sites that recently migrated from HTTP to HTTPS, changed domain name, or have www/non-www redirect configurations, and whenever sitemap submission reports low coverage.
Why are some sitemap URLs ignored by Google?
Google ignores sitemap entries from domains it cannot verify as yours. Cross-domain URLs are simply skipped, so those pages lose the crawl-discovery benefit of the sitemap.
Advanced
Item type
skill
Key
sitemap-domain
Source
github.com/thedaviddias/front-end-checklist