What if Google misses an important page on our site, even though the page is live and useful? That happens more often than many site owners think. A good xml sitemap helps search engines find the pages we want them to see.
In simple terms, an xml sitemap, a foundational element of technical SEO, is a machine-readable list of important URLs on our site. It doesn’t replace good internal links, which help prevent orphan pages, but it does give search engines a cleaner path to our content. Below, we’ll break down what it does, what it doesn’t do, and how we can create one on WordPress and non-WordPress sites.
What an XML Sitemap Actually Does
Think of an xml sitemap as a table of contents for search engines. Following the sitemap protocol, it uses the urlset element as the standard technical container to list key pages and often includes details like when a page last changed. That helps search engine crawlers discover content faster, especially on new sites, large sites (improving crawl efficiency), or sites with pages buried deep in the structure.
Still, we need to separate three ideas that often get mixed together. For a fuller look at how search engines work, it helps to see each step clearly.
Here’s the quick difference:
| Process | What it means | Where a sitemap helps |
|---|---|---|
| Crawling | Search engines find pages | Strong help |
| Indexing | Search engines store pages in their database | Some help |
| Ranking | Search engines order results | No direct help |
A sitemap can help a page get discovered. It can also support indexing by making page signals clearer. But it does not push a page to the top of search results. Rankings still depend on content, links, relevance, and page quality.
An xml sitemap helps search engines find important URLs, but it doesn’t make weak pages rank.
So, if we publish a new service page and want it found quickly, a sitemap is useful. If that page is thin, duplicate, or blocked from indexing, the sitemap alone won’t fix it.
What to Include, and What to Leave Out
A clean sitemap beats a big one. We should include only canonical url, indexable URLs. In plain English, that means the preferred version of a page, one that search engines are allowed to index.
That rules out a lot of clutter. We should leave out noindex pages, redirects, 404 pages, duplicate URLs, filtered search pages, and staging URLs. If a page shouldn’t appear in search, it usually shouldn’t sit in the sitemap either.
We also want accurate dates. The lastmod tag value should reflect real content changes, not fake updates. Optional attributes like changefreq and priority can provide more context to crawlers. If every page claims it changed today, search engines may ignore the signal. As of March 2026, Google’s latest spam update didn’t change sitemap guidance, so clean and honest sitemap habits still hold.
Large sites should use a sitemap index. That’s a master file that points to smaller sitemap files. It keeps each file within Google’s limits, 50,000 urls or 50mb file size uncompressed. For more detail, this sitemap best practices guide is a solid reference.
If we rely heavily on media or timely publishing, special sitemap types can help too. Image sitemaps can support image discovery, while video sitemaps and news sitemaps make sense only when those content types are a real part of the site.
How to Create an XML Sitemap in WordPress
WordPress already gives us a basic xml sitemap on many installs. Plugins add more control as a sitemap generator, which is why many site owners use Yoast or Rank Math. If we want a simple walkthrough of the basics, Yoast’s XML sitemap explainer is helpful.
Here’s the easiest path:
- Pick the source: Use WordPress core, or install an SEO plugin like Yoast or Rank Math for more control.
- Turn the feature on: In the plugin settings, keep XML sitemaps enabled.
- Open the xml sitemap: Common URLs are
/wp-sitemap.xmlor/sitemap_index.xml. - Trim the noise: Remove content types or taxonomies we don’t want indexed, such as thin tag archives or private pages.
- Submit it: Add the sitemap in google search console, then check the status for errors or excluded URLs.
- Reference it in robots.txt file: This gives crawlers one more path to find it.
A practical tip also matters here. Dynamic xml sitemaps should load fast and stay available, so solid managed WordPress hosting can make upkeep easier.
How to Create One on a Non-WordPress Site
If we don’t use WordPress, the process is still simple, especially for non-CMS sites. We can build the sitemap with a site generator, a crawler tool, or by hand for small sites.
Follow these steps:
- Gather the right URLs: Start with absolute urls of pages we want indexed, such as core services, products, blog posts, and contact pages.
- Create the XML file: Build a utf-8 encoded xml file where each URL sits inside the proper sitemap structure, using the loc tag and, when useful, lastmod. Apply entity escaping for any special characters in URLs.
- Save it in the site root: Most sites use
/sitemap.xml. - Use a sitemap index for scale: If the site is large, split files by type, such as pages, posts, and images.
- Submit and monitor: Add the sitemap to google search console, and if we use Bing, add it in Bing Webmaster Tools too.
After submission, watch what happens. First check the http status code of the sitemap for issues. A sitemap marked “Success” is a good start, but it’s not the finish line. We still need to monitor indexing coverage and check whether important URLs are discovered and indexed in google search console. If many submitted pages stay excluded, the problem is usually page quality, duplication, canonical signals, or crawl blocking, not the sitemap file itself.
Quick XML Sitemap Checklist
Before we call it done, we can run this short check:
- Include only canonical url pages
- Remove redirects, errors, and noindex pages
- Keep the
lastmod taghonest - Use a sitemap index for large sites
- Add image sitemaps, video sitemaps, or news sitemaps only when they fit the site
- Reference the sitemap in robots.txt file
- Submit it in Google Search Console and review errors regularly
In short, an xml sitemap is a simple but useful SEO asset. It helps search engines find the right pages faster, keeps crawl signals cleaner, and gives us a better way to monitor site health. If we treat it like a tidy map instead of a junk drawer, it becomes much more useful.
