How to Submit an XML Sitemap to Google Search Console

Quick answer

To submit an XML sitemap to Google Search Console, first confirm that the sitemap is live and publicly accessible. Then open the correct Search Console property, choose Sitemaps, enter the sitemap path, and select Submit. A successful submission tells Google where the file is located, but it does not guarantee that every listed URL will be crawled or indexed.

For many small business websites, the sitemap address is /sitemap.xml or /sitemap_index.xml. Your content management system may use a different path, so verify the exact URL before submitting it.

What an XML sitemap does

An XML sitemap is a machine-readable list of the pages, posts, products, images, or videos you want search engines to discover. It helps Google understand the preferred URLs on your site and can be especially useful for a new website, a large website, a site with isolated pages, or a site that publishes frequently.

A sitemap is a discovery aid, not a ranking shortcut. Google treats sitemap submission as a hint. The pages still need to be accessible, useful, internally linked, indexable, and technically sound.

If you do not have a sitemap yet, create one with the Website Builder Central XML Sitemap Generator.

Before you submit: check these five items

Complete these checks before opening Search Console. They prevent many of the errors that make a sitemap appear submitted but unusable.

1. Confirm the sitemap URL

Open the sitemap in a private browser window. You should see XML content or a sitemap index, not a login page, a 404 page, or a redirect loop. Common locations include:

• The root sitemap path /sitemap.xml
• A sitemap index path such as /sitemap_index.xml
• A WordPress sitemap path such as /wp-sitemap.xml

Use the address your website actually provides. Do not assume that every platform uses the same filename.

2. Check that Google can access it

The sitemap must be available without a password and return a successful response. It should not be blocked by a firewall, maintenance mode, or an incorrect robots.txt rule. If the sitemap loads for you but Search Console reports that it cannot fetch the file, test the sitemap URL with URL Inspection and run a live test.

3. Include only canonical, indexable URLs

Your sitemap should contain the final HTTPS version of each URL you want indexed. Remove obsolete URLs, redirected URLs, duplicate parameter pages, staging URLs, and pages marked noindex. Listing a URL in a sitemap does not override a noindex directive or make a duplicate page canonical.

Use complete absolute URLs, including the protocol and domain. Keep the hostname consistent. Mixing www and non-www versions, or HTTP and HTTPS versions, can create avoidable errors.

4. Keep the sitemap within Google’s limits

A single sitemap can contain up to 50,000 URLs and be up to 50 MB when uncompressed. Larger sites should split URLs into separate sitemap files and place them in a sitemap index. Dividing sitemaps by content type can also make monitoring easier, for example pages, blog posts, products, and images.

5. Verify the correct Search Console property

Make sure the property matches the version of the site used in the sitemap. A Domain property covers protocols and subdomains. A URL-prefix property covers only the exact prefix that was verified. If the property is wrong, the sitemap may be rejected or associated with the wrong site.

How to submit your XML sitemap in Google Search Console

Follow these steps after the sitemap passes the checks above.

1. Sign in to Google Search Console

Open Google Search Console with the Google account that has access to the website property. You need owner permission to submit through the Sitemaps report. If you do not have access, ask the verified owner to add you or submit the sitemap for you.

2. Select the correct property

Use the property selector in the upper-left area and choose the domain or URL-prefix property that matches your live website. Double-check HTTPS, www, and any subdomain.

3. Open the Sitemaps report

In the left navigation, find Indexing and select Sitemaps. The report shows previously submitted files, the date Google last read each file, the number of discovered pages, and any processing errors.

4. Enter the sitemap path

In Add a new sitemap, enter the remaining path after the property URL, such as sitemap.xml or sitemap_index.xml. Search Console may display the property prefix for you. If the field accepts the full URL, paste the exact tested sitemap URL.

5. Select Submit

After submission, Search Console will attempt to retrieve and process the sitemap. A success message confirms that Google accepted the submission request. It does not mean every URL is indexed.

6. Review the status

Return to the Sitemaps report and review the submitted file. A Success status means Google could fetch and process it. Compare the discovered-page count with the number you expected. A much lower number may indicate missing URLs, nested sitemap problems, or an outdated file.

What the sitemap status means

Search Console may show one of several outcomes:

• Success: Google fetched and processed the sitemap.
• Has errors: Google processed part of the file but found problems that need attention.
• Couldn’t fetch: Google could not retrieve the sitemap at the submitted address.

Open the sitemap row to see the latest read date and specific error details. Fix the underlying problem on the website, confirm the live file, and submit again when necessary.

Common sitemap errors and how to fix them

Couldn’t fetch

Visit the sitemap URL directly. Confirm that it returns a successful response, is not protected by a login, and is not blocked by robots.txt or a security tool. Check for server outages, DNS issues, redirect chains, and an incorrect filename.

404 or sitemap not found

The submitted path does not exist. Find the correct URL in your CMS, regenerate the sitemap if needed, and submit the live address. If you recently moved the file, update any robots.txt reference too.

Invalid XML or parsing errors

Validate the XML structure. Look for malformed tags, unsupported characters, a missing namespace, invalid dates, or accidental HTML output. Rebuild the file using a dependable generator or your CMS, then test it before resubmitting.

URLs not allowed

The sitemap contains URLs from a different hostname, protocol, or directory scope. Standardize the URL format and make sure the sitemap is associated with a Search Console property that covers those URLs.

Redirected or noncanonical URLs

Replace redirected URLs with their final destinations. Keep only preferred canonical URLs that return a successful response and are eligible for indexing.

Submitted URL marked noindex

Decide whether the page should appear in search. If yes, remove the noindex instruction and verify that the canonical points to the same preferred URL. If no, remove the URL from the sitemap.

Should you resubmit after every website update?

Usually, no. Google periodically revisits a sitemap that it has successfully processed. You may want to resubmit after a major migration, a large batch of new pages, a significant sitemap restructuring, or a fix to a failed sitemap. Routine content changes normally do not require manual submission each time.

For one important new or substantially updated page, URL Inspection can be useful. For many pages, a clean sitemap and strong internal linking provide a more scalable discovery path.

Add the sitemap to robots.txt too

You can also reference the sitemap in robots.txt with a Sitemap line containing the full sitemap URL. This gives search engines another way to discover it. The line does not replace good sitemap maintenance, and robots.txt should not block the sitemap itself.

How to monitor results after submission

Check the Sitemaps report periodically for the latest read date, status, and discovered-page count. Then use the Page indexing report to understand which sitemap URLs are indexed and why others are excluded.

Pay attention to patterns, not only individual pages. If many URLs are excluded as duplicates, crawled but not indexed, or blocked, review templates, canonical tags, internal links, content quality, and server behavior.

Use our SEO checklist for a new business website to review the surrounding technical and on-page foundations.

XML sitemap submission checklist

• The sitemap opens publicly at a stable HTTPS URL.
• The file contains preferred canonical URLs only.
• Every listed URL uses the correct hostname and protocol.
• Redirected, broken, duplicate, staging, and noindex URLs are removed.
• The file is within size and URL limits.
• The matching Search Console property is verified.
• The sitemap is submitted in the Sitemaps report.
• Errors and discovered-page counts are reviewed after processing.
• The sitemap is referenced in robots.txt when appropriate.
• Indexing trends are monitored over time.

Final takeaway

Submitting an XML sitemap is a simple but important technical SEO task. The submission itself takes only a minute. The real value comes from maintaining a clean file, using the correct canonical URLs, fixing access and parsing errors, and monitoring how Google processes the pages.

If you want help reviewing your sitemap, Search Console setup, or wider website SEO, Contact Website Builder Central for practical support.

You can also review Google’s official Build and submit a sitemap guide and the

official Search Console Sitemaps report documentation.