XML Sitemaps Explained: What They Are, How to Create One, and How to Fix Common Errors

If you have been looking into SEO, you have probably seen the word “sitemap” come up more than once. Maybe someone told you your site needs one. Maybe you saw it mentioned in Google Search Console and were not sure what to do with it.

This guide covers the whole topic in one place: what a sitemap is, the different types, how to create one, how to find one on any website, which tools are worth using, and how to fix the errors that show up in Search Console. No jargon overload. Just a clear, practical explanation.

What Is a Sitemap in SEO?

A sitemap is a file that lists the important pages on your website and tells search engines where to find them. Think of it as a directory you hand directly to Google. Instead of waiting for Google’s bots to stumble across your pages by following links, a sitemap says: “Here’s everything important on this site. Go index it.”

In practice, sitemaps are most commonly XML files that live at a URL like yoursite.com/sitemap.xml. When you submit that URL to Google Search Console, you are pointing Google straight to your content inventory.

The sitemap itself does not make your pages rank. It plays a meaningful role in whether your pages get found, crawled, and indexed in the first place, and without indexing, ranking is impossible. One thing worth being clear about from the start: Google treats a sitemap as a hint, not a command. Submitting one does not force crawling or indexing.

A sitemap also matters beyond Google now. AI crawlers such as GPTBot, ClaudeBot, and PerplexityBot use sitemaps to discover content the same way Googlebot does. If you want your pages cited in AI search results, a clean sitemap is part of that foundation too.

Sitemap Meaning in SEO: What It Actually Does

The term “sitemap” can sound more complicated than it is. In SEO, a sitemap serves one primary function: it helps search engines discover your content faster and more completely.

Here is why that matters. Google finds pages in two ways: by following links from other pages, and by reading sitemaps. If a page on your site is not linked from anywhere else, Google’s crawler may never find it, unless your sitemap points to it directly.

This is especially relevant in a few common situations:

New websites. If your site launched recently and does not have many backlinks yet, Google’s crawler has few paths into your content. A sitemap gives it a direct route. Our guide on steps to rank a newly launched website covers this as one of the first priorities.

Large websites. A site with hundreds or thousands of pages cannot rely purely on internal links to ensure everything gets crawled. A sitemap makes sure nothing important gets missed.

Sites with rich media. If you have images or videos you want indexed in Google Images or Google Video, standard crawling alone may not surface all of them. Specialised sitemaps fill that gap.

Frequently updated content. If you publish new blog posts regularly, a sitemap tells Google when content was last modified, which helps it prioritise fresh content for crawling.

Types of Sitemaps

Not all sitemaps are the same. Here is what each type means and does.

XML Sitemaps

This is the one people mean when they talk about “sitemaps” in an SEO context. An XML sitemap is a structured, machine-readable file that lists your URLs along with metadata. Search engines read it. Humans generally do not look at it directly.

A typical entry looks like this:

<url>
  <loc>https://yoursite.com/services/</loc>
  <lastmod>2026-08-14</lastmod>
</url>

You may see older examples that also include changefreq and priority tags. Google has confirmed it ignores both. The only metadata Google actually uses is lastmod, and only when it is accurate. Setting a fake “updated today” date on every URL trains Google to distrust your sitemap, so let your plugin set it honestly.

Most WordPress sites generate the XML sitemap automatically through Rank Math or Yoast SEO. You can verify yours exists by visiting yoursite.com/sitemap.xml or yoursite.com/sitemap_index.xml in your browser.

HTML Sitemaps

An HTML sitemap is a page on your website that lists your important pages in a readable, clickable format. It is designed for human visitors, not bots. You have seen these before: they are often linked in a website’s footer and present the site structure as a simple list of links organised by section.

HTML sitemaps are genuinely useful for large websites where visitors might struggle to find specific pages through normal navigation. They support user experience, and indirectly help SEO by ensuring internal links reach pages that might otherwise be buried.

Image Sitemaps

An image sitemap tells Google about the images on your site: where each image lives and which page it belongs to. Google is good at finding text but routinely misses images, especially ones loaded through JavaScript, lazy-loaded below the fold, or hosted on a CDN.

Two technical details most guides still get wrong. First, Google deprecated the image:caption, image:title, image:geo_location, and image:license tags; the only tag Google now reads per image is image:loc, the image URL itself. Second, Google allows up to 1,000 image entries per URL element, so a product page with a large gallery can list every image inside one URL block.

If your images sit on a CDN with a different domain, verify that domain in Search Console separately. Otherwise crawl errors on those images go unreported. For e-commerce stores, photographers, food blogs, and local businesses with strong visual content, image search is an underused traffic source, and the sitemap is what puts you in the running for it.

Video Sitemaps

The same concept, for video content: title, description, duration, and thumbnail URL. Video schema markup has taken over much of this function, so video sitemaps matter most for publishers with large amounts of embedded video.

News Sitemaps

News sitemaps are for publishers who want articles in Google News. They carry news-specific metadata such as publication date and title. If you run a news publication or publish time-sensitive editorial content, implement one.

Sitemap Index Files

Google’s limit is 50,000 URLs per sitemap file and a maximum of 50MB uncompressed. Larger sites split their content into multiple sitemap files and use a sitemap index file to link them together. Our own index at seo24.ca/sitemap_index.xml does exactly this: it references separate sitemaps for posts, pages, and categories.

Why Sitemaps Matter for SEO

“Sitemaps help SEO” is vague, so let us get specific.

Faster Indexing for New and Updated Content

When you publish a new page or update existing content, Google has to wait for Googlebot to recrawl your site on its own schedule. A properly maintained sitemap with accurate lastmod timestamps signals that specific pages have changed, which can trigger a faster recrawl. This is particularly valuable if you publish blog content regularly and want new posts in search results quickly.

Finding Pages That Are Not Well-Linked

Internal linking is one of the main ways Google discovers pages on your site. If a page is buried several levels deep in your navigation or simply does not receive many internal links, it can be slow to get crawled or skipped altogether. A sitemap catches those orphaned pages and puts them on Google’s radar, even if your internal link structure has not caught up yet.

Crawl Budget Efficiency

Larger sites have a crawl budget: the number of pages Google will crawl in a given period. An accurate sitemap helps Google spend that budget on pages that actually matter rather than wasting it on low-value URLs or outdated pages.

Clarity Around Site Structure

A sitemap gives Google an organised view of which pages exist, how they relate, and which ones you consider important. That context supports Google’s understanding of your site’s topical coverage, which feeds into how well your content ranks.

When Does Your Site Actually Need a Sitemap?

Here is something most articles skip: not every website desperately needs one. Google itself says its crawler can discover most pages on a well-linked site without a sitemap.

That said, a sitemap is strongly recommended if your site is new with few backlinks, has more than a few hundred pages, contains pages that are not well-linked internally, publishes new content regularly, or carries rich media you want surfaced in specialised search results.

Even for small, well-linked sites there is no downside to having one. It is a small layer of insurance that important pages do not get missed.

How to Create a Sitemap

Creating a sitemap does not require technical expertise. Pick the route that matches your setup.

Using a WordPress Plugin or Your CMS

If your site runs on WordPress, this is by far the easiest path, and it is how we set up every site we build. Rank Math and Yoast SEO both generate and update the XML sitemap automatically:

1. In your WordPress dashboard, go to Plugins, then Add New.
2. Install and activate Rank Math or Yoast SEO.
3. Sitemap generation is on by default in both. In Rank Math the settings live under Rank Math, then Sitemap Settings; in Yoast under SEO, then Features.
4. Find your sitemap at yoursite.com/sitemap_index.xml.

From that point it stays current on its own. Publish a post, and it appears in the sitemap with an honest lastmod.

Shopify, Wix, and Squarespace generate sitemaps automatically at /sitemap.xml with no setup at all. On Shopify it cannot be customised; on the others, barely. That is usually fine.

Using an Online Generator

For smaller custom-built sites, tools like XML-Sitemaps.com or Screaming Frog crawl your site and produce a sitemap file you upload to your server’s root directory via FTP or your hosting panel. This works well up to a few hundred pages. The catch: nothing updates automatically. Every time your content changes, you regenerate and re-upload.

Writing It Manually

For full control on a small site, you can write the XML yourself in a text editor: XML header, a urlset tag with the sitemap namespace, one url block per page containing loc and optionally lastmod, then close the urlset. Save as sitemap.xml, validate it with an online XML validator, and upload it to your root directory. It works, but it is error-prone and every site change means a manual edit, so we only recommend it when no automated option exists.

Creating an HTML Sitemap

If you want a human-facing sitemap too, create a page called “Sitemap”, organise your main sections in a hierarchical list of links with descriptive anchor text, and link it from your footer. Keep it to the pages visitors actually look for rather than a dump of every URL.

How to Find Any Website’s Sitemap

Useful for checking your own site or researching a competitor. Work through these in order; the first two solve it most of the time.

Try the default locations. Add /sitemap.xml, /sitemap_index.xml, or /wp-sitemap.xml (WordPress core’s default) after the domain. Shopify, Wix, and Squarespace all use /sitemap.xml.

Check robots.txt. Visit yoursite.com/robots.txt and look for a line starting with Sitemap:. It states the full sitemap URL, and a site can list several. This is the most reliable method because the robots.txt file is meant to declare exactly this.

Check Google Search Console. For your own site, the Sitemaps report under Indexing shows every submitted sitemap, its status, and its last read date.

Use search operators. site:example.com filetype:xml or inurl:sitemap site:example.com can surface publicly indexed sitemap files when the standard locations come up empty.

Look in the footer. HTML sitemaps usually live behind a “Sitemap” link in the site footer.

If none of that works, the sitemap probably does not exist, which for very small or old sites is common. If it is your own site, that is your cue to create one using the methods above.

Submitting Your Sitemap to Search Engines

Generating the sitemap is step one. Submitting it is step two.

In Google Search Console, open Sitemaps under the Indexing section, enter your sitemap URL, and click Submit. Google will begin reading it, and the report will show how many URLs were discovered along with any errors. Cross-reference the discovered count against the Page Indexing report to spot gaps between submitted and indexed pages.

Do the same in Bing Webmaster Tools: verify your property, open the Sitemaps section, and submit the same URL. It takes two minutes and there is no reason to skip it, particularly for local businesses.

Also reference the sitemap in your robots.txt file with a Sitemap: line so any crawler can discover it without a submission.

Choosing a Sitemap Tool

Which tool you need depends on your platform and how much control you want.

For WordPress sites, Rank Math or Yoast SEO is the answer. Both automate generation and updates completely, cover image sitemaps, and give you granular control over which post types appear. Rank Math offers finer per-page control; Yoast is simpler. You do not need a separate sitemap tool on WordPress.

For quick one-off generation, XML-Sitemaps.com crawls up to 500 pages free in the browser, no installation. Good for small static sites; you re-upload manually after every content change.

For large or complex sites, Screaming Frog SEO Spider and Sitebulb are desktop crawlers built for technical SEO work. Both generate fully customisable sitemaps (canonical handling, noindex exclusion, image and hreflang entries) as part of a proper site audit. Screaming Frog’s free tier stops at 500 URLs; both need a licence for full use and some technical comfort.

For visual site planning, tools like Slickplan, DYNO Mapper, and Octopus.do build interactive sitemap diagrams for design teams planning a site structure. Useful in a redesign project, but they are planning tools, not SEO tools, and are not what you submit to Google.

Common Sitemap Errors and How to Fix Them

A badly maintained sitemap creates mixed signals and can work against you. These are the problems we see most often in Search Console, and how to resolve each one.

Sitemap Could Not Be Fetched

Search Console reports “Couldn’t fetch” when it cannot reach the file at all. Usual causes: a mistyped URL in the submission or robots.txt, the file was moved or deleted, server errors (404, 500), or file permissions blocking access. Load the sitemap URL in your browser first. If it loads for you but not for Google, check server logs for errors on Googlebot requests, confirm robots.txt is not blocking the sitemap path, then resubmit. Repeated fetch failures alongside slow pages point to server health problems, which show up in Search Console’s Crawl Stats report.

Sitemap Submitted, but Zero URLs Discovered

The file was found but Google extracted nothing usable. Open the sitemap in your browser and confirm it actually lists URLs. Run it through an XML validator to catch syntax errors such as missing tags or unescaped characters (an ampersand must be written as &). If the structure is fine, the problem is the URLs themselves: they may all be blocked by robots.txt, carry noindex tags, return 404, or declare a canonical pointing somewhere else.

Noindex Pages in the Sitemap

A noindex tag tells Google to keep a page out of search results. Listing that same page in your sitemap says the opposite. Pick one: remove the page from the sitemap, or remove the noindex tag if you do want it indexed. Rank Math and Yoast exclude noindexed pages automatically, so this error usually means a manual sitemap or a misconfigured plugin.

URLs Blocked by robots.txt

Same contradiction, different mechanism. If robots.txt disallows a URL that your sitemap submits, Google cannot crawl it no matter what the sitemap says. Audit both files together, then either remove the disallow rule or remove the URL from the sitemap depending on whether you want the page crawled.

Non-Canonical and Duplicate URLs

Only include the canonical version of each page. Listing both site.com/page/ and site.com/page, or mixing HTTP with HTTPS and www with non-www, wastes crawl budget and muddies Google’s understanding of which version to index. Our post on canonical URLs explains how canonicalisation works in detail.

Outdated URLs and 404s

A sitemap that points to deleted pages signals a poorly maintained site and wastes crawl budget. Crawl the URLs in your sitemap periodically to catch 404s, implement 301 redirects for moved content, and let your plugin drop removed pages automatically. If you maintain the sitemap by hand, this audit belongs in your regular maintenance routine.

Sitemap Exceeds Size Limits

More than 50,000 URLs or 50MB uncompressed in a single file and Google may ignore part of it. Split into multiple sitemaps under an index file, and take the opportunity to strip low-value URLs while you are at it. Session-generated URLs, filtered category pages like /category/?sort=price, thank-you pages, and admin pages have no place in a sitemap.

Sitemap Rarely Crawled

If Google reads your sitemap infrequently, check that lastmod reflects genuine modification dates, then look at overall site health. Slow server responses and frequent errors reduce crawl frequency across the board, and no sitemap fixes that.

Sitemaps and the Bigger SEO Picture

A sitemap is a foundational technical element, but it is one piece of a larger puzzle. Getting indexed is the prerequisite for ranking; sitemaps help with that. Getting indexed does not guarantee ranking, which requires good content, backlinks, and proper on-page optimisation.

If pages show up in your sitemap but still are not indexed, that is a separate issue. The crawled, currently not indexed problem is one of the most common technical SEO frustrations, and it usually points to content quality or relevance rather than the sitemap. Similarly, if pages are indexed but not ranking where you would expect, the sitemap is not the culprit; our post on reasons your optimised page won’t rank walks through the real causes.

If you are not sure whether your sitemap, robots.txt, and canonicals are pulling in the same direction, a no-cost check of your sitemap and indexing setup will tell you which URLs are listed, which are missing, and which should not be there at all. And where the sitemap keeps drifting out of sync with the site, the fix usually sits upstream in the theme or plugin configuration; our technical SEO service covers the full audit and implementation across sitemap, canonicals, robots.txt, and site structure.

FAQ: Sitemaps in SEO