XML Sitemaps and Discovery Signals

Sitemaps Are Discovery Hints

A sitemap inventories preferred URLs. It does not replace internal links, guarantee crawling, or guarantee indexing. It helps search systems find URLs, especially on new or recently changed sites.

Include absolute, canonical URLs that the site genuinely wants indexed. Exclude redirects, errors, blocked or noindex URLs, duplicate variants, and internal search results. lastmod should describe a meaningful page change, not the build time stamped onto every URL.

changefreq and priority are optional protocol hints. They are not ranking controls.

Decide Which URLs Belong in the Sitemap

A reliable sitemap is the result of earlier decisions:

1. Which URLs are canonical?
2. Which canonical URLs return successful responses?
3. Which pages are intended to be indexed?
4. Which pages are meaningful enough to discover through search?
5. Which pages changed in a way that justifies updating lastmod?

If those decisions are unclear, the sitemap becomes a wish list. A redirected URL in the sitemap tells crawlers to request an address the site no longer prefers. A noindex URL in the sitemap asks for discovery while also saying not to index the page. Those conflicts may not break a site, but they reduce trust in the site's signals.

Small sites can often maintain a sitemap through the route or content registry. Larger sites need generation rules that exclude drafts, private pages, internal search results, parameter variants, and error routes by default.

Minimal Valid Sitemap

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/</loc>
    <lastmod>2026-08-20</lastmod>
  </url>
  <url>
    <loc>https://example.com/menu</loc>
    <lastmod>2026-08-18</lastmod>
  </url>
</urlset>

A single sitemap is limited to 50,000 URLs or 50 MB uncompressed by the protocol. Small learner projects usually do not need sitemap indexes.

Inclusion Decision Table

Search Console successfully read this sitemap and discovered 229 pages. This confirms sitemap processing, not that every listed URL was indexed.

View full-size image

Testing a Sitemap Like a Developer

Do not stop at "the XML opens in a browser." Test the file in layers:

• Syntax: the XML is well-formed and uses the correct namespace.
• URL format: every <loc> is absolute and uses the preferred protocol and host.
• Response: every listed URL returns a successful final response.
• Canonical: every listed URL is the preferred canonical version.
• Index directive: every listed URL is allowed to be indexed.
• Freshness: lastmod changes only when the page meaningfully changes.

When a generated sitemap fails, fix the source rule rather than hand-editing the output. Otherwise the next build will recreate the mistake.

Submit and Verify the Sitemap

Publishing the file and submitting it are separate steps. Submit only after the sitemap and its listed URLs pass the checks above.

Google Search Console

1. Open the correct verified property and confirm you have permission to submit a sitemap.
2. Request the public sitemap URL in a browser or command-line client. It must be accessible to Google without signing in.
3. Open Sitemaps, enter the sitemap path for that property, and submit it.
4. Record the submitted URL, submission date, status, last read date, and discovered-page count when they are available.
5. If Google reports a fetch or parsing problem, reproduce it against the public file before changing the site.
6. Use the Page indexing report's sitemap filter to investigate the index state of that submitted set.

Search Console records a sitemap address; it does not upload the XML file. A successful result means Google fetched and processed the file. It does not mean every URL was crawled or indexed.

Bing Webmaster Tools

1. Open the correct verified Bing property.
2. Open Sitemaps, choose Submit sitemap, and provide the public sitemap URL.
3. Record whether the sitemap was submitted directly, discovered, or imported, together with its processing state and discovered-URL count.
4. Use Bing URL Inspection or Site Explorer for important URLs that need individual diagnosis.

Importing a property from Search Console can make verification easier, but do not assume that a Google submission proves Bing processed the sitemap. Check Bing's own result.

Screenshot pending - Bing Sitemaps: Add a real, redacted Bing Webmaster Tools Sitemaps capture when authorised access is available. Do not invent a success state, discovered-URL count, warning, or error.

Read Each State Precisely

Processing and indexing can take time. If the file is fetchable, valid, and submitted, record the pending state and review date. Investigate a reported fetch, syntax, response, directive, or canonical conflict; do not manufacture a technical fault simply because indexing is not immediate.