Nuclear Link Indexer

Sitemap Indexing: How to Submit and Check an XML Sitemap

Sitemap indexing starts with a simple distinction: submitting a sitemap helps Google discover your preferred URLs, but it doesn't make Google index them. An XML sitemap tells search engines which pages you want them to consider. Google still decides whether to fetch, process, and include each page in Search.

Open the sitemap, verify its URLs, and submit it under Sitemaps in Google Search Console. Then check its processing status separately from page indexing.

How XML Sitemaps Help Google Discover Pages

An XML sitemap lists URLs for discovery, especially on large sites or where pages are hard to find via internal links. It doesn't replace those links. A small, well-linked site may not need a sitemap.

Think of the process as four checkpoints:

Checkpoint Evidence you can look for What remains uncertain
1. Sitemap available Its URL opens and serves a readable file Whether Google has fetched it
2. Sitemap processed Search Console reports Success and a last-read date Whether Google crawled each listed page
3. Page URLs discovered Search Console reports URLs parsed from the sitemap Whether those URLs were indexed
4. Page indexing evaluated The Page indexing report or URL Inspection displays Google's URL-particular information Whether an indexed page will appear for a particular search

Google may discover a URL via a sitemap without crawling or indexing that page. Search visibility is a standalone outcome.

Google's sitemap documentation explicitly treats submission as a hint, not an indexing instruction. Where you're working via a full site launch instead of just a sitemap, see our guide to getting a website indexed on Google.

Which URLs Belong in Your Sitemap?

List the canonical URLs you want Google to index. A sitemap isn't an inventory of everything your site can serve.

Prior to submitting it, check a representative sample against this short preflight:

  • Preferred address: Use the complete, absolute URL, such as the intended https:// host and path. Prefer the URL you find as canonical, not alternate parameter or duplicate versions.
  • Accessible content: The page should resolve to its intended content, instead of an error, login screen, or unexpected redirect.
  • Indexing directives: Don't list pages you deliberately exclude with noindex. Check that significant pages aren't accidentally blocked from Google's crawling.
  • Redirects and replacements: Remove obsolete URLs that redirect elsewhere. List the final preferred destination instead.
  • Content selection: Include helpful pages intended for search, not every filter, internal search result, or temporary utility URL.

For example, if https://example.com/guides/solar/ is the preferred page and https://example.com/guides/solar/?ref=email is an alternate version, normally list the first URL only. Listing both doesn't make both eligible for standalone indexing.

A sitemap's <lastmod> value should reflect a real, significant page update. Google may use accurate modification dates but ignores the XML <priority> and <changefreq> values. Changing dates to suggest freshness isn't a substitute for updating content.

Accurate URL selection matters more than sitemap size.

How to Find or Create Your XML Sitemap

First check whether your publishing system already generates one. Common locations to try are https://example.com/sitemap.xml and https://example.com/sitemap_index.xml, but neither path is universal. Your robots.txt file may also contain a Sitemap: line pointing to the correct address.

Website setup Practical first step
CMS such as WordPress Check the CMS's built-in sitemap or configured SEO plugin prior to creating a second one
Webflow Review the site's sitemap setting and the generated /sitemap.xml file after publishing
Custom or static website Generate the sitemap from your preferred live URLs and publish it at a stable, accessible address

Webflow Sitemap Indexing

For Webflow, the official instructions specify Site settings → SEO → Sitemap. Enable Auto-generate sitemap, save, and publish. Webflow generates /sitemap.xml and updates it on publication. Check page-level exclusions.

What a Simple XML Sitemap Looks Like

A minimal sitemap might contain one preferred page:

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

Use UTF-8 XML and escape reserved characters. Google limits each sitemap to 50,000 URLs or 50 MB uncompressed. Larger sites may split files and group them with a sitemap index, which lists sitemap files instead of pages.

How to Submit a Sitemap in Google Search Console

Submitting via the Search Console Sitemaps report is free, but requires owner permissions for the relevant property. Without owner access, ask a verified owner to submit the sitemap or make it discoverable via robots.txt.

  1. Open Google Search Console and select the property covering the site's intended host and protocol.
  2. Confirm that your sitemap opens at its final public URL and is accessible without authentication. Check that it's the right sitemap for that site.
  3. Open Sitemaps in Search Console.
  4. Under Add a new sitemap, enter the sitemap address or path as requested for your property, such as sitemap.xml. Review the resulting URL prior to submitting.
  5. Select Submit. Return to the report to see whether Google fetched and read the sitemap, and inspect any reported errors.

Google may also discover a sitemap via robots.txt:

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

However, the Search Console Sitemaps report lists sitemaps submitted via that report or its API. A sitemap found only via robots.txt may not appear in the submitted list. That alone doesn't demonstrate Google has ignored it.

Submitting a sitemap isn't the same as requesting indexing of one page. For a particular page that you own and need Google to revisit, follow the standalone Submit URL to Google guide. For a collection of new or updated pages, a maintained sitemap is the more natural discovery mechanism.

For exact interface descriptions and error meanings, Google maintains the Search Console Sitemaps report help.

How to Tell Whether Sitemap Indexing Is Working

Start with the result the Sitemaps report provides. Success means Google fetched and read the sitemap without errors. It does not mean every URL was crawled, indexed, or assigned the canonical you preferred.

Last read indicates a fetch; Discovered pages counts parsed URLs, such as those in child sitemaps, not indexed pages.

Use this evidence-to-action table instead of treating one green status as the final result:

What you observe What you can conclude Best next check
Sitemap shows Success Google read the file without errors Filter the Page indexing report by that sitemap to evaluate the pages
Discovered pages is populated Google parsed those URLs Check whether significant URLs were crawled and indexed, not just counted
Last read is available but significant URLs are missing Google has accessed the file, but that doesn't establish individual inclusion Inspect a particular URL and Google's selected canonical
Has errors Google read the sitemap but encountered processing errors Open its error details, repair affected entries, and verify the updated file
Page indexing report displays excluded URLs Google has a page-level indexing outcome to investigate Standalone intentional exclusions from pages that should be indexed

For groups, use our Page Indexing Report guide. For one URL, see Google URL Inspection Tool for indexed-state and canonical evidence.

Example: Your sitemap has 120 preferred URLs and a Success status, but the Page indexing report displays that 35 of those URLs aren't indexed. You don't have a sitemap submission failure merely since the numbers differ. First check which 35 URLs matter, whether Google has crawled them, and whether they are duplicates, excluded intentionally, or affected by a particular issue. The next action depends on that evidence.

Common Sitemap Problems and What to Check Next

Separate errors in the sitemap file from decisions about individual pages.

Observation Likely issue or interpretation What to do next
Couldn't fetch Google did not retrieve the sitemap, or the fetch failed Check the URL, HTTP response, authentication, robots access, and server; if those look correct, check the Manual actions report
Has errors Google fetched the file but encountered processing errors Open the error details, repair malformed XML or affected URLs, and verify the updated file
Wrong domain, host, or path The submitted file or its URLs don't match the intended site configuration Confirm the Search Console property, full URLs, and appropriate sitemap scope
Redirecting, deleted, or noindex URLs listed The sitemap advertises pages you don't want indexed in that form Update the generator to list preferred, indexable destinations
Sitemap processed but pages not indexed File processing worked, but Google's page-level decision is standalone Review the Page indexing report, then diagnose why a page isn't indexed
Sitemap not visible in the submitted report It might have been found only via robots.txt, or you're viewing another property Check the property and submission history prior to assuming a fetch failure

A sitemap hosted in a subdirectory normally covers URLs in that directory and below unless an appropriate Search Console submission or cross-site setup extends its scope.

Where Google repeatedly may't fetch or process a sitemap, it may stop retrying. Fix the problem, confirm Googlebot may access the file, then resubmit it. Don't resubmit a successful sitemap since individual pages remain unindexed.

Keep Your Sitemap Accurate After Site Changes

Keep the sitemap aligned with your current preferred URLs.

  • New page: Add its canonical URL when it's published and intended for search.
  • Updated page: Update <lastmod> only when there has been a meaningful change, if your system provides that field reliably.
  • Removed or redirected page: Remove its obsolete address and list its replacement if that replacement belongs in Search.
  • CMS migration or domain change: Verify the generated hostnames, sitemap URL, redirects, and Search Console property.
  • Larger site: Split sitemap files when you reach Google's limits, and use a sitemap index when that makes management easier.

Automatically generated sitemaps may update as you publish. Routine updates don't normally require resubmission, and no manual resubmission schedule guarantees faster indexing.

Select your next check by the missing evidence. Where Google may't read the sitemap, fix access or syntax. Where Google reads it but doesn't index an significant URL, inspect that URL's indexing record. Where you need an independent signal, Nuclear Link Indexer's Google Index Checker provides a separate paid, site:-based search-result check, not an official Search Console report. Because site: results are not exhaustive, a missing match may't prove exclusion from Google's index. No check compels Google to index a page.