Skip to content
Back to skills

Sitemap Domain

ASecurity

Use when applies to sites that have recently migrated from HTTP to HTTPS, changed domain name, or have www/non-www redirect configurations. Use when sitemap submission reports low coverage.

  • 74,358 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 5, 2026
developmentgofrontend

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned October 5, 2026

npx -y skills add thedaviddias/Front-End-Checklist --skill sitemap-domain --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Sitemap Domain?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Sitemap Domain
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thedaviddias-sitemap-domain/badge)](https://www.skillsdirectory.com/skills/thedaviddias-sitemap-domain)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: sitemap-domain
description: "Use when applies to sites that have recently migrated from HTTP to HTTPS, changed domain name, or have www/non-www redirect configurations. Use when sitemap submission reports low coverage."
metadata:
  category: seo
  priority: medium
  difficulty: beginner
  estimatedTime: "10"
  source: frontendchecklist.io
  url: https://frontendchecklist.io/rules/seo/sitemap-domain
---

# Keep sitemap URLs on the correct domain

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/rules/seo/sitemap-domain

Files in this skill

  • SKILL.md2.1 KB
  • references/rule.md3.8 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…