Generate from the content source
A sitemap is easier to trust when it uses the same published records that create the pages. Keep article slugs and tool slugs in a structured collection, then generate the sitemap from those records. A separately maintained URL list tends to retain deleted pages and miss new ones when a collection grows beyond a few entries.
Include intended indexable destinations
List public canonical pages you want discovered, using absolute URLs on the correct production hostname. Remove preview environments, broken links and redirects from the intended set. The file is a discovery aid rather than a command to index everything. A sitemap entry cannot make a thin page useful or override an incompatible access policy.
Check a small example
Imagine a journal with a homepage and three articles. The expected set contains the archive and the three article URLs, along with the other public site pages. Removing one article should update both its route and its sitemap membership. A comparison between the exported HTML routes and sitemap URLs exposes either a missing page or an obsolete entry.
Use meaningful modification dates
If you provide lastmod, derive it from substantive content updates rather than assigning the current deployment time to every URL. Rebuilding an unchanged site does not mean each article was revised. Keep publication and modification dates distinct in the content model so an editor can explain why a timestamp changed and what the reader gained.
Keep discovery connected
Reference the sitemap from robots.txt and submit it through the appropriate search management tools when the site is live. Still provide ordinary links between archives and detail pages. A site whose only path to its articles is an XML file misses an opportunity to help real visitors navigate related subjects and understand the collection.
Validate structure and coverage
Open the final XML, check escaping, and confirm every listed URL resolves as intended. Test that the sitemap itself returns a successful response instead of the site’s generic error page. For larger collections, respect the documented file limits and introduce sitemap indexes when needed. Review reported errors alongside your own route inventory rather than treating submission as the end of maintenance.
Further reading
Put the idea to work.
Explore free browser tools for images, text and developer workflows.