Daily Web Digest

Guides

What Is a Sitemap, and Does Your Website Need One?

XML vs HTML sitemaps, when Google says a small site can skip one, where WordPress, Shopify and Wix keep yours, and five sitemap mistakes to avoid.

By Daily Web Digest Editors
7 October 2026 · 7 min read
In this guide
  1. What a sitemap is
  2. Do you require one on your site? Google's own answer
  3. Your sitemap is stored in WordPress, Shopify and Wix.
  4. What is the purpose of lastmod, and what Google disregards?
  5. Submission of your sitemap.
  6. There are five typical sitemap errors.
  7. The short answer
  8. Sources

In case you have created a Google Search Console, you must have wondered in the search engine that you was supposed to do something in the Sitemaps report. Perhaps a tutorial mandatory required you to turn in a sitemap on day one.

This is what a sitemap is and what Google recommends its existence is, where your platform already holds one, and how to avoid mistakes.

What a sitemap is

According to Google, this type of file is referred to as a sitemap in which you give data about the pages, videos and other files on your site and how they relate to each other. It is read out by search engines to crawl your site more quickly.

Consider it a list you submit to search engines: the following are the URLs that I am interested in, and at this point one of them last changed meaningfully. The bare minimal XML sitemap is as follows:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/kerala-banana-chips/</loc>
    <lastmod>2026-09-28</lastmod>
  </url>
</urlset>

One sitemap file can hold up to 50,000 URLs or 50 MB uncompressed. Bigger websites break out URLs to multiple files in a sitemap index, and the platforms described below all generate one automatically.

XML sitemaps vs. HTML sitemaps.

XML sitemap HTML sitemap
Written for Search engines Visitors
What it is A record of URLs, possibly with dates, readable by a machine. A typical web page that contains links, usually in the footer.
Submitted in Search Console? Yes, you would like to. No, it's crawled like any other page

Google also has documentation on sitemaps of files in XML, RSS/Atom, or plain text. An HTML sitemap is a mere page of links: helpful to human visitors in a large site and an alternate route to crawlers, but no replacement of the crystal clear menus and internal links. It is typically optional on a small blog, on good category pages.

Do you require one on your site? Google's own answer

The sitemap overview of Google is straightforward. You might need a sitemap if:

  • Your site is big therefore more difficult to ensure that all pages are linked somewhere.
  • Your website is new and has minimal outbound links.
  • You have many video or image contents or are featured in Google News.

You might not need one if:

  • Your site is small, as would be considered by Google as 500 or less, only the pages you want to see in the search results you want.
  • Your site is thoroughly connected within, meaning Googlebot can access all significant pages on the home page.
  • You don't have many media files or news pages you want shown in search.

Google includes the added value of a sitemap having no guaranty with crawling or indexing but most sites do have a sitemap.

A Pune freelancer who has a 12 pages portfolio, all accessible through the menu fits the might not need one description. A handicraft shop in Jaipur which is stocking new additions each week fits the other list.

Most readers will have the answer to this question: Google indicates that a sitemap is probably already provided by a CMS like WordPress, Wix or Blogger. Your mission is to ensure its presence, contains the correct URLs and can be searched by Google.

Your sitemap is stored in WordPress, Shopify and Wix.

Platform Where to look Good to know
WordPress (5.5 and later, no SEO plugin) yoursite.com/wp-sitemap.xml Built in. Off when search engines are discouraged to periodically search this site.
WordPress with Yoast SEO or Rank Math yoursite.com/sitemap_index.xml The sitemap of the plug-in itself. Yoast also redirects /sitemap.xml to it.
Shopify yourstore.com/sitemap.xml Automatically generated, updated. Inaccessible when the store is in private mode.
Wix yoursite.com/sitemap.xml Created and revised automatically, as a sitemap index.

WordPress. The list of sitemap core posts, pages, categories, tags, author archives and the homepage, and WordPress uses it as a reference in the robots.txt file it creates. WordPress 6.5 and onwards has lastmod dates on posts. An SEO plugin is installed and one checks the settings of the plugin to determine which sitemap is active.

Shopify. Separate sitemaps of the products, collections, blogs and pages are connected to the sitemap and updated when you add them. Each foreign domain is further broken down into a sitemap on the Basic plan or beyond; Shopify recommends adding other additional domains to your original domain.

Wix. Wix maintains the sitemap and its lastmod dates up to date. Fill in the SEO Setup Checklist, and Wix automatically sends the sitemap to Google; this feature needs a Premium plan and a reference domain.

What is the purpose of lastmod, and what Google disregards?

A sitemap can have optional tags on each URL. In the case of Google, all that counts is one thing only.

lastmod The date of the last change in the importance of the page. Google says it uses this value if it's "consistently and verifiably" accurate. Changes to the main content, structured data or links are seen as important, as well as by Google, but not an updated copyright date. Google stated in a 2023 blog post that the lastmod is one of its signals used to schedule recrawls of previously-known URLs.

According to Google documentation changefreq as well as priority is not taken into account. In a 2023 post, it was clarified that changefreq intersects with lastmod, and priority does not tend to represent the actual significance of a page.

There would be no point in prioritising 1.0 to your favourite pages as Google is concerned. False lastmod is self-defeating: eventually we will no longer trust you, as Google indicates.

Submission of your sitemap.

Within Google Search Console.

  1. Check your sitemap URL (see the table above) in a browser to verify that it loads.
  2. Test it with the URL Inspection live test (optionally) to make sure that Googlebot is able to access it.
  3. Click the Sitemaps report, paste the URL in Add a new sitemap and hit Submit.
  4. Check the status. Success: means that Google read it without mistakes. Couldn't fetch is an expression that is used to indicate that Google was not able to retrieve the file. Error status The error status indicates that it was read, only with issues on some of the entries.

Google crawls the sitemap quickly, however crawling its URL takes time and is not guaranteed. Never resubmit without considerable modification. The report only lists sitemaps provided there or by the Search Console API thus one discovered in robots.txt can be missed even when in use by Google. The Sitemaps section of Bing Webmaster Tools is similar.

In robots.txt

With a single line of robots.txt, you can also indicate crawlers to your sitemap:

Sitemap: https://www.example.com/sitemap.xml

Make use of the complete address; you are allowed to have a couple of sitemaps. It is automatically included in the robots.txt that WordPress creates and other sites might do so as well, so verify first.

A former trick has been replaced: Google discontinued its sitemap "ping" URL, due to the announcement of the move in June 2023, therefore any instructions to ping Google have become obsolete.

There are five typical sitemap errors.

1. Unsubscribing to pages that you are not interested in search. Google states to paste the URL that you would like to be displayed in search results, which are usually the canonical ones. Redirects, 404s, noindexed pages, tracking-parameter duplicates and thank-you pages are out of place.

2. concealing sitemap with Google. Google honours robots.txt when retrieving sitemaps and thus a sitemap that has been blocked cannot be read. One cannot do so in the background with a login or on a Shopify store in private mode. And the task of searching in WordPress can be turned off by clicking Discourage search engines.

3. Faking lastmod dates. A date stamping tool to add the day date on all pages can be used to teach Google to disregard your dates. Maintain the lastmod to change with content.

4. Confusion of versions of your site. Google prefers full, un-qualified URLs and crawls just as they are provided. When your site has the version of https://www/, in this case, a sitemap of URLs starting with http or non-www URLs, or staging URLs used during a migrate, directs Google in the redirects or the incorrect location. Search Console further breaks down sitemaps by property: one you submit under http://example.com won't be displayed under https://example.com.

5. "Use sitemap as index me button. Google calls submitting a sitemap "merely a hint". The fact that the daily resubmission will not accelerate anything, and that the addition of a sitemap to the report will not make Google lose memory on the report or its links. When not indexed, check out internal links and content quality instead of indexed pages.

The short answer

Does your web site require a sitemap? Google exclaims that it is likely not and you have a small and well connected one. However, on WordPress, a store you already have one, the helpful thing is to test it: open it, verify that it contains solely pages that you like to appear in search, and verify that Search Console reads it and that there are no errors. A clean sitemap can assist in getting your pages noticed by search engines. It doesn't make them index or rank those pages.


Sources