Save as sitemap.xml at your site root, then submit it in Google Search Console. WordPress users: Rank Math or Yoast already generate this automatically at /sitemap_index.xml.
Free XML sitemap generator
An XML sitemap is a list of your important pages that helps search engines discover and crawl them efficiently. This free tool — built by a Singapore SEO agency — turns a plain list of URLs into a valid sitemap.xml file, with optional lastmod, changefreq and priority tags. It removes duplicates, skips invalid URLs, and gives you clean XML to copy. Everything runs in your browser — your URLs are never uploaded.
What an XML sitemap does (and doesn’t do)
A sitemap helps search engines find your pages — especially useful for large sites, new sites with few backlinks, or pages buried deep in your structure. It does not guarantee indexing or improve rankings by itself; it’s a discovery aid, not a ranking factor. Think of it as handing Google a table of contents. The pages still have to earn their place through quality and relevance, but a clean sitemap makes sure nothing important gets overlooked.
lastmod, changefreq and priority explained
lastmod tells crawlers when a page last changed — genuinely useful, and Google does pay attention to an accurate one. changefreq (daily, weekly, monthly…) hints at how often a page updates, and priority (0.0–1.0) suggests relative importance within your site. Google treats the last two as weak hints at best, so don’t obsess over them — keep lastmod honest and set a sensibly higher priority for your key pages, and you’ve done everything that matters.
Submitting your sitemap
Save the output as sitemap.xml, upload it to your site’s root (so it lives at yourdomain.sg/sitemap.xml), then submit that URL in Google Search Console under Sitemaps. Add a line to your robots.txt pointing to it too. If you run WordPress with Rank Math or Yoast, a sitemap is generated and kept up to date automatically at /sitemap_index.xml — use this tool for static sites, custom builds, or to hand a developer a starter file.
How a sitemap fits a healthy crawl strategy
An XML sitemap is a discovery aid, not a ranking lever — its job is to hand search engines a clean, authoritative list of the URLs you want crawled and indexed. It becomes genuinely valuable on larger sites, on sites with pages that aren’t well linked internally, and on newer domains that haven’t yet earned deep crawling. On a small, tightly interlinked site, Google will likely find everything anyway, but a sitemap still speeds up discovery of fresh content and gives you a diagnostic surface in Search Console.
The most useful discipline is to keep the sitemap to your canonical, indexable URLs only. Every entry should return a 200 status, be self-canonical, and not carry a noindex tag. A sitemap full of redirects, 404s, parameter variants or noindexed pages sends mixed signals and dilutes the trust Google places in the file. If crawl budget and indexing are ongoing headaches, our technical SEO team can restructure how your URLs are discovered.
Sitemap index files and large sites
A single sitemap is capped at 50,000 URLs and 50MB uncompressed. Once you approach either limit — or simply want cleaner reporting — split your URLs into multiple sitemaps grouped by content type (say, one for pages, one for blog posts, one for case studies) and tie them together with a sitemap index file. This structure makes Search Console’s coverage reports far more useful, because you can see indexing rates per content type and spot which section has a problem instead of staring at one undifferentiated number.
Automate the file wherever possible. A sitemap that’s regenerated whenever you publish or unpublish stays trustworthy; a hand-maintained one drifts out of date within weeks and quietly starts listing dead URLs. Most WordPress SEO plugins produce a live, auto-updating sitemap index — this manual generator is best for static sites, quick audits, or submitting a specific curated list of priority URLs for faster indexing.
Frequently asked questions
Do I need an XML sitemap?
It’s strongly recommended, especially for larger or newer sites. Small sites with good internal linking may be crawled fine without one, but a sitemap rarely hurts and often helps discovery — so there’s little reason not to have one.
How many URLs can a sitemap contain?
A single sitemap file can hold up to 50,000 URLs and must be under 50 MB uncompressed. Larger sites split URLs across multiple sitemaps referenced by a sitemap index file.
Does a sitemap improve my rankings?
Not directly. It helps search engines discover and crawl your pages, which is a prerequisite for ranking, but the ranking itself depends on content quality, relevance and authority — not the sitemap.
Should I include every page?
Include the canonical, indexable pages you want in search. Leave out noindex pages, redirects, duplicates and thin utility pages — a focused sitemap of your best URLs sends a cleaner signal than a bloated one.
Should redirected or noindexed URLs go in my sitemap?
No. Include only canonical URLs that return a 200 status and are meant to be indexed. Listing redirects, error pages or noindexed URLs contradicts the file’s purpose and can slow Google’s trust in it. Keep the sitemap as a clean statement of the pages you actually want in the index.
How do I know if Google is using my sitemap?
Submit it in Google Search Console under the Sitemaps report, which then shows how many URLs Google discovered versus indexed, plus the last read date and any parsing errors. Comparing submitted-to-indexed counts per sitemap is one of the quickest ways to diagnose an indexing problem on a specific section of the site.
