Why XML sitemaps still earn their keep
Crawlers discover URLs through links—but sitemaps give search engines an explicit map of pages you care about. New sites, large catalogs, and recently redesigned architectures benefit most.
Fah Swe Tools / OptimizeImage includes an XML sitemap generator to help you create a structured list of URLs for Google Search Console and other search engines.
What an XML sitemap is (and is not)
A sitemap is a machine-readable file (often sitemap.xml) listing canonical URLs you want discovered. It can include optional hints like lastmod.
A sitemap is not:
- A guarantee of indexing
- A replacement for internal linking
- A place to list noindexed or blocked URLs
- A ranking booster by itself
Think of it as a discovery aid and inventory.
When to generate or regenerate a sitemap
- Launching a new domain or subdomain
- Migrating from HTTP to HTTPS or changing hosts
- Publishing a large batch of new landing pages
- Cleaning out outdated product/URLs after a catalog purge
- Splitting a huge site into sitemap index files
After major IA changes, update the sitemap and internal links together.
How to create and submit a sitemap
1. Collect the canonical URLs that should be indexed (exclude thank-you pages, cart, account, faceted duplicates).
2. Generate XML with the sitemap generator.
3. Host the file at a public URL such as https://example.com/sitemap.xml.
4. Reference it in robots.txt with Sitemap: https://example.com/sitemap.xml.
5. Open Google Search Console → Sitemaps → submit the URL.
6. Monitor “Discovered” vs indexed counts over the following days/weeks.
7. Fix exclusion issues (robots, noindex, canonicals) when important URLs stall.
URL quality rules for sitemaps
Include:
- Canonical HTTPS URLs
- Primary language versions you want indexed
- Key category, product, and article templates
Exclude:
- Redirecting URLs (use final destinations)
- Parameterized duplicates
- Paginated thin filters that create infinite spaces
- Admin, checkout, and private areas
- Soft-404s and intentionally noindexed pages
A smaller accurate sitemap beats a bloated noisy one.
Sitemap index files for large sites
When you exceed practical size limits or logical groupings, use a sitemap index that points to multiple child sitemaps (products, blog, marketing pages). Keep each child focused so updates are easier.
E-commerce tip: separate rapidly changing product sitemaps from stable content sitemaps.
Search Console diagnostics to watch
After submission, investigate:
- URLs in sitemap but “Crawled – currently not indexed”
- Soft 404 patterns
- Redirected sitemap entries
- Server errors during fetch
Sitemaps surface inventory problems early—use that signal.
Pair sitemaps with on-page and performance hygiene
Discovery without quality still fails. For new URLs in the sitemap:
- Unique titles/descriptions (meta tags checker)
- Solid keyword targeting (keyword position)
- Fast LCP (page speed checker + image compression)
Especially for image-heavy launches, compress assets before announcing crawlability.
Common sitemap mistakes
- Shipping HTML site maps only (helpful for users, not a substitute for XML)
- Listing both
wwwand non-wwwduplicates - Forgetting to update after migrations
- Auto-including every tag/archive URL on a blog
- Blocking the sitemap in robots.txt accidentally
Maintenance cadence
- Small marketing sites: update when pages are added/removed; review quarterly
- Publishers: automate on publish
- Large catalogs: automate daily/hourly for product availability changes
Whenever automation exists in your CMS, still spot-check output quality—plugins can include junk URLs.
Bottom line
An XML sitemap helps search engines understand which URLs matter. Generate a clean file, host it, submit it in Search Console, and keep it aligned with canonical reality.
Create your sitemap with the free XML sitemap generator on OptimizeImage, then submit it in Google Search Console.