Which XML Sitemap Fields Crawlers Actually Use
In an XML sitemap only a few fields carry weight — loc is essential, lastmod is trusted as a freshness signal if you keep it honest, while changefreq and priority are largely ignored. Include only canonical, indexable 200 URLs and split large files with a sitemap index under 50,000 URLs.
Most sitemap tags do almost nothing — the two that matter are <loc> and an honest <lastmod>. Crawlers largely ignore <changefreq> and <priority>, so a lean sitemap of canonical 200 URLs beats a cluttered one every time.
Quick answer
<loc> is essential — it is the URL. <lastmod> is trusted as a freshness signal only if you keep it honest. <changefreq> and <priority> are largely ignored. List only canonical, indexable 200 URLs, and split anything over 50,000 URLs with a sitemap index.
Which fields do crawlers actually read?
Two carry real weight. <loc> is non-negotiable — it names the URL. <lastmod> helps crawlers decide what to re-fetch, but only if it reflects genuine edits; auto-bumping it site-wide trains crawlers to ignore it. The rest is mostly decorative.
Why are changefreq and priority ignored?
Because sites gamed them. Nearly everyone set priority to 1.0 and changefreq to "daily," so the signals became meaningless. Google now infers crawl frequency from links, real freshness, and structure instead — so tuning these tags is wasted effort.
What belongs in a clean sitemap?
Only URLs you want indexed and cited: canonical, indexable pages returning 200. Exclude redirects, noindex pages, 404s, and non-canonical duplicates. Media discovery is the one place extensions earn their keep — image and video sitemap tags help engines find media they would otherwise miss.
| Field | Used by crawlers? | Notes |
|---|---|---|
| <loc> | Yes — essential | The URL itself; use the canonical, indexable version |
| <lastmod> | Yes, if honest | Freshness signal for re-crawl — don't fake or auto-bump it |
| <changefreq> | Largely ignored | Sites set it arbitrarily; crawlers infer frequency instead |
| <priority> | Largely ignored | Nearly everyone sets 1.0 — signal is worthless |
| Image / video extensions | Yes — useful | Helps engines discover media they'd otherwise miss |
| File size limits | Enforced | Max 50,000 URLs / 50MB — split with a sitemap index |
A short, honest sitemap of canonical URLs does more than a padded one. More in does a sitemap help AI crawlers and canonical URLs and AI citation.
Related questions
Does a sitemap help AI crawlers?
Yes — it helps them discover and prioritize your canonical URLs efficiently.
Read the full answer →Do canonical URLs affect AI citation?
Yes — crawlers consolidate signals onto the canonical URL and cite that one.
Read the full answer →What is crawl budget for AI?
The finite attention crawlers spend on your site — a clean sitemap spends it well.
Read the full answer →Frequently asked questions
- Do changefreq and priority tags do anything?
- Very little. Google and most crawlers largely ignore changefreq and priority because sites set them arbitrarily and they proved unreliable. Your crawl priority is inferred from links, freshness, and site structure instead, so spending time tuning these two tags rarely changes how often pages are crawled.
- Does lastmod actually help?
- Yes, when it is honest. Crawlers use lastmod as a freshness signal to decide what to re-crawl, but only if it reflects real content changes. Faking or auto-bumping lastmod on every page teaches crawlers to distrust it, which can hurt how quickly your genuinely updated pages get re-fetched.
- How big can an XML sitemap be?
- A single sitemap file is limited to 50,000 URLs and 50MB uncompressed. Larger sites split their URLs across multiple sitemap files and list them in a sitemap index file, which itself can reference up to 50,000 sitemaps. Only include canonical, indexable URLs that return a 200 status.