Skip to content
EN

XML Sitemaps: What to Include and How to Check Them

Jack Lee

Written by Jack Lee

Website pages organized into a publishing inventory

A kitchen-appliance website publishes a new cooker-hood installation page. The owner adds it to the XML sitemap and expects it to appear in Google immediately. What did that change actually do?

An XML sitemap is a list of URLs you want search engines to know about. Adding a page may help Google discover it; it does not force a crawl, indexing, or a ranking. The important question is whether the file lists the right URLs.

What Does an XML Sitemap Do?

An XML sitemap is a machine-readable file, often at a URL such as https://example.com/sitemap.xml. It can list page addresses and, when known accurately, their last significant update dates. Google reads it as one discovery signal. Your site navigation and page structure help both visitors and crawlers find pages; the XML file supplements those links. Neither replaces the other.

On the appliance site, the installation page still needs a useful link from the relevant service or product section. A sitemap can point Google to the page, but cannot repair weak navigation or make an unhelpful page worth indexing. The technical SEO guide shows where discovery sits in the larger process.

Does Every Website Need One?

No. Google says a small site—about 500 important pages or fewer—with all important pages reachable through links from its homepage may not need a sitemap. A clean one can be useful when a site is new, large, changes often, or has important media, news, or language versions that need clearer discovery.

First check whether your CMS already generates one. WordPress and many hosted platforms do. A second manually maintained file can become inconsistent with the first; decide which published URL list is authoritative.

Which URLs Belong in the Sitemap?

Start with pages you actually want people to find in search. For the appliance business, that could include the cooker-hood installation service and a useful product category. List the full, preferred URLs, including the correct protocol, host, and path. If the same content appears at several addresses, list the version you prefer as canonical; a sitemap is a hint, not a command that forces Google to choose it.

Leave out generic booking confirmations, login pages, redirects, error pages, noindex pages, and sorting or filter URLs that merely repeat a category. Those pages tell a different story from “please consider this address for search.” If a confirmation includes personal details, protect it with access control; leaving it out of a sitemap is not privacy protection. Our indexing and noindex guide helps make the index decision before you edit the file.

A sitemap can also include separate language versions when each has its own indexable URL. Do not list a language variant that redirects to another page or is intentionally excluded from search.

What Is Inside a Small XML Sitemap?

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/cooker-hood-installation/</loc>
  </url>
</urlset>

<loc> holds the complete URL. Optional <lastmod> should reflect a real, significant change to that page, not the time the file was regenerated. Google ignores <priority> and <changefreq>; they cannot make a page rank higher or force daily crawling.

One sitemap can contain up to 50,000 URLs or 50 MB uncompressed. Beyond either limit, split it into smaller files and use a sitemap index if useful. Most small businesses will never approach that limit.

How Do You Publish and Check It?

  1. Open the exact sitemap URL in a browser. It should be public, load successfully, and contain production URLs rather than staging or old addresses. If your CMS provides a sitemap index, open a child file too.
  2. Spot-check representative entries: the new service page, a category, and a language version if applicable. Each should open the intended page without a redirect or noindex rule and match the preferred URL used in internal links.
  3. Make the sitemap discoverable by submitting its URL in Search Console's Sitemaps report or declaring its location in robots.txt. You submit the file's URL, not its XML contents.
  4. Read the report after Google fetches it. “Success” means the sitemap was read; it does not mean every listed page was indexed. If the file cannot be fetched or parsed, fix that error. For one missing page, use URL Inspection and the Page indexing report rather than resubmitting the same unchanged file.

Frequently Asked Questions

What Is an XML Sitemap in SEO?

It is a machine-readable list of preferred site URLs that helps search engines discover pages and understand selected details such as meaningful update dates.

Is sitemap.xml Still Relevant?

Yes, especially for new, large, changing, or media-rich sites. A small site with clear internal links may not need one for Google to find its pages.

Does a Sitemap Help SEO?

It can help discovery and monitoring. It does not guarantee crawling, indexing, ranking, or traffic; the listed pages must still be accessible and useful.

What Are the Limitations of an XML Sitemap?

A single file is limited to 50,000 URLs or 50 MB uncompressed. More importantly, submission is only a hint: it cannot replace internal links or make Google index every URL.

Local design preview

This form is a design preview. Subscriptions and external tools are not connected.

Browse the article library