Sitemap priority myths (and what actually helps discovery)

XML sitemaps are a discovery aid, not a vote ballot. Google has been clear that `priority` and `changefreq` are hints it may ignore entirely.

What sitemaps do well

They list canonical URLs you want crawled, optionally with `lastmod` when you truthfully know content changed. Search Console uses them to monitor coverage and spot exclude patterns — especially on large or fresh sites.

They help when internal linking is weak: new domains, isolated landing pages, or massive faceted archives where crawlers might miss deep URLs.

They do not replace internal links, good information architecture, or fast pages. Think of sitemap as “here is the inventory,” not “here is why we rank.”

Priority and changefreq folklore

Assigning `0.8` vs `0.5` does not move rankings. Teams that set everything to `1.0` waste everyone’s time. If you set `changefreq` to `daily` on a yearly privacy policy, crawlers learn to distrust your signals.

Honest `lastmod` helps more than invented priority. Update it when content materially changes, not on every deploy that only touched CSS.

Split very large sites into sitemap index files per section (docs, blog, products). Stay within size limits and include only indexable 200 URLs — not redirects, not 404s, not parameterized duplicates.

Building sitemaps without typos

Paste your URL list, set defaults once, and export escaped XML. The Sitemap Generator on DroidXP builds a valid `urlset` client-side — optional `lastmod`, `changefreq`, and `priority` fields if you still want them for legacy tools.

After generation, spot-check a few URLs in the browser, then submit in Search Console. Automate regeneration in your static site build or CMS webhook so launch day is not manual XML editing.

Reference the sitemap from `robots.txt` with a full absolute `Sitemap:` URL. Pair with the Robots.txt Generator so crawlers find both files quickly.

Measuring whether it worked

Watch indexed vs submitted counts, not vanity priority tags. Fix canonical tags and duplicate content before adding more sitemap URLs.

For JavaScript apps, ensure critical routes return meaningful HTML or documented rendering — sitemap cannot fix uncrawlable shells.

Refresh sitemaps after migrations and hreflang changes; stale maps send bots to old hosts while your 301s do the heavy lifting.