List the pages you genuinely want indexed
A Sitemap is most useful when it behaves like a clean inventory. Every URL should return a successful response, declare itself canonical, and contain content you are comfortable showing in search.
Redirects, error pages, internal search results, drafts, and noindex pages make the file noisy. They also make Sitemap reports harder to interpret because submitted and indexable stop meaning the same thing.
Use lastmod only when it tells the truth
Changing every lastmod value on every deployment does not tell Google which content changed. A useful date reflects a meaningful edit to the page body, structured data, primary media, or important links.
Store update dates with the content rather than generating one global date. If you cannot maintain reliable dates, omitting lastmod is cleaner than publishing a timestamp that changes without reason.
Split Sitemaps for reporting, not for rank
Small sites can use one file. Larger tool sites may separate articles, tools, converters, and localized pages so Search Console reports are easier to compare. The split does not make one section rank higher.
After publishing, submit the Sitemap index once and watch discovered, crawled, and indexed counts. A gap is a prompt to inspect page quality and canonical signals, not a reason to submit the same file every day.
Practical checklist
- Include only canonical URLs that return 200.
- Exclude redirects, drafts, errors, and noindex pages.
- Use accurate page-level lastmod dates.
- Keep each language alternate complete and reciprocal.
- Monitor each Sitemap group in Search Console.