XML Sitemap Guide: Priority, Changefreq & Google Submission (2026)
📅 August 2026⏱ 8 min read✍️ ToolLoom Editorial
A sitemap.xml file won't boost your rankings — but it does something arguably more important: it helps Google actually find your pages in the first place. Here's what a sitemap really does, which fields still matter in 2026, and how to submit one correctly.
An XML sitemap is a structured file listing the important URLs on your website, formatted according to the standard defined at sitemaps.org. Its job isn't to influence ranking — it's a discovery and crawling aid, helping search engines find pages more efficiently, especially ones that aren't well linked from elsewhere on the site or were just published.
For a small site with a clean navigation structure, a sitemap matters less since crawlers can find everything through normal links anyway. For larger sites, e-commerce catalogs, or sites with orphaned pages, it becomes genuinely useful infrastructure.
🔍
Discovery Aid
Helps crawlers find pages that internal links might miss.
⚡
Faster Indexing
New or updated pages can be discovered sooner.
🚫
Not a Ranking Factor
A sitemap doesn't directly improve where you rank.
📐
Standardised Format
Follows the sitemaps.org XML protocol used across all major search engines.
Anatomy of a sitemap.xml File
Every URL entry in a sitemap sits inside a <url> block, with up to four possible fields:
Tag
Required?
Purpose
<loc>
Yes
The full, absolute URL of the page
<lastmod>
Optional
Date the page was last significantly modified
<changefreq>
Optional
Hint about how often the page's content changes
<priority>
Optional
Relative importance (0.0–1.0) compared to other pages on your own site
Priority and Changefreq — Do They Still Matter?
Here's the part that surprises a lot of people: Google has publicly stated it largely ignores both the priority and changefreq fields. The reason is practical — most site owners set every single page to priority 1.0 and changefreq "daily" regardless of actual importance or update frequency, making the values statistically unreliable as a genuine signal.
⚠️
These fields remain part of the official sitemap protocol and some other search engines or third-party tools may still reference them, so including sensible, honestly-varied values doesn't hurt — but don't expect them to meaningfully influence Google's crawling behaviour today.
Lastmod — The Field Google Actually Uses
Unlike priority and changefreq, lastmod genuinely helps. An accurate last-modified date gives Google a real signal about which pages have recently changed and might be worth re-crawling sooner — but this only works if the date is honest. Setting every page's lastmod to today's date regardless of whether it actually changed undermines the field's usefulness in exactly the same way overusing priority does.
💡
Keep lastmod accurate and update it only when a page's content meaningfully changes — this is one of the few sitemap fields worth actually maintaining carefully.
The 50,000 URL Limit and Sitemap Index Files
A single sitemap file is capped at 50,000 URLs and must not exceed 50MB uncompressed. Sites exceeding this — large e-commerce catalogs, news archives, forums — need to split URLs across multiple sitemap files and reference all of them from one sitemap index file.
Sitemap Limits
Max 50,000 URLs per file · Max 50MB uncompressed per file
The sitemap index itself is what gets submitted to Search Console — it points to each individual sitemap in turn, and Google crawls through all of them.
How to Submit Your Sitemap to Google
1
Upload sitemap.xml to your root directory
It should be accessible at yoursite.com/sitemap.xml — the conventional expected location.
2
Reference it in robots.txt
Add a line like Sitemap: https://yoursite.com/sitemap.xml so crawlers can find it even without manual submission.
3
Open Google Search Console
Select your verified property from the property dropdown.
4
Go to the Sitemaps section
Found in the left-hand navigation menu of Search Console.
5
Enter the path and submit
Type sitemap.xml and click Submit — Google will periodically re-crawl it automatically afterward.
Worked Example — A Minimal Valid Sitemap
A correctly formatted sitemap listing two pages looks like this:
Field
Page 1
Page 2
loc
https://example.in/
https://example.in/about
lastmod
2026-08-01
2026-06-15
changefreq
weekly
monthly
priority
1.0
0.6
✅
Notice the homepage gets a higher priority (1.0) and more frequent changefreq (weekly) than the About page (0.6, monthly) — genuinely differentiated values like this are more meaningful than marking every page identically, even accounting for Google's reduced weight on these fields. Paste your URL list into ToolLoom's Sitemap Generator to build a complete, valid sitemap.xml like this instantly.
Common Sitemap Mistakes
Setting every page to priority 1.0 — defeats the purpose of a relative importance signal entirely
Using a fake or unchanging lastmod date — undermines the one field Google genuinely uses
Including non-canonical, redirected, or noindexed URLs — a sitemap should only list URLs you actually want indexed
Forgetting to reference the sitemap in robots.txt — an easy, free way to help crawlers discover it automatically
Never resubmitting after a major site restructure — stale sitemaps can point to pages that no longer exist
Exceeding the 50,000 URL limit without a sitemap index — large sites need to split into multiple files properly
🗺️ Generate Your Sitemap Instantly — Free
Paste your URLs — get a valid, ready-to-upload sitemap.xml with priority, changefreq and lastmod. No signup.
No. A sitemap doesn't influence ranking directly — it's a discovery and crawling aid, not a ranking signal. What it does is help Google find and crawl your pages more efficiently, especially pages that aren't well linked internally or are newly published, which can indirectly speed up how quickly new or updated content shows up in search results.
Google has publicly stated that it largely disregards the priority and changefreq fields because website owners frequently set every page to priority 1.0 or changefreq "daily" regardless of actual importance or update frequency, making the values unreliable as a genuine crawling signal. Google instead relies on its own crawling algorithms, internal link structure, and observed update patterns to prioritise crawling. The fields remain part of the sitemap protocol and some other search engines and tools may still reference them.
A single sitemap file can contain a maximum of 50,000 URLs and must not exceed 50MB uncompressed, per the sitemap protocol at sitemaps.org. Sites with more URLs than this limit need to split their URLs across multiple sitemap files and reference all of them from a single sitemap index file.
Upload sitemap.xml to the root directory of your domain, so it's accessible at yoursite.com/sitemap.xml. This is the conventional location search engines check by default, and it's also the location typically referenced by a Sitemap: directive inside your robots.txt file.
After uploading sitemap.xml to your site's root directory, sign in to Google Search Console, select your verified property, open the Sitemaps section from the left menu, and enter the sitemap path (e.g., sitemap.xml) before clicking Submit. Google will then periodically re-crawl the sitemap for changes without needing manual resubmission each time.
A sitemap index file is a special XML file that lists the locations of multiple individual sitemap files, rather than listing URLs directly. It's needed once a site's URL count exceeds the 50,000-URL limit of a single sitemap file — common for large e-commerce catalogs, news archives, or forums. The sitemap index itself is what gets submitted to Search Console, and it points to each individual sitemap file in turn.
About ToolLoom: We build free tools for Indian students, professionals and creators. All sitemap generation happens instantly in your browser from the URLs you paste in — nothing is crawled or stored. Found an error? Email contact@toolloom.in