How to Submit a Sitemap to Google Search Console

Google discovers URLs by following links across the web, but discovery alone does not guarantee timely indexing. An XML sitemap lists the URLs you care about in one place and signals how they fit together. Submitting that sitemap in Google Search Console does not replace crawling, but it gives Google a direct inventory to compare against what it already knows—which is especially valuable after launches, migrations, or large content updates. Crawl budget and ranking are separate concerns; the sitemap’s job is to reduce guesswork about which URLs exist. The workflow below is short: confirm the file is valid, submit it, then interpret the status Google returns.

Before you submit — make sure your sitemap is valid

A sitemap is plain XML that follows the sitemaps.org rules: a root element that lists URLs (or, for index files, child sitemap locations). Each entry needs an absolute canonical URL in the location field; relative URLs, typos, or malformed tags break the file as far as parsers are concerned. When the XML is invalid or contains URLs that should not be indexed, Google may accept the submission and still not process every URL the way you expect—or it may surface a generic error until the underlying issue is fixed.

List only URLs that should be indexed: pages with a noindex directive, duplicate thin URLs, or staging hosts do not belong in the file you submit. Optional fields such as last modification time can help Google prioritize recrawls when they are honest; inflated or static dates across every row train nothing useful. Keep the file reachable at a stable URL over HTTPS and served with an appropriate XML content type so intermediate proxies do not transform it into HTML.

Broken markup is the most common self-inflicted problem. If your CMS or generator emits duplicate protocols, wrong encodings, or missing required elements, search engines may stop reading partway through the document. Before you paste the URL into Search Console, run the same file through a dedicated checker so you are not debugging Google’s UI when the real issue is the source file. Our Sitemap Validator validates structure against the standard and helps you catch XML and URL issues early, while you still have a short feedback loop with your deployment or CMS.

Step-by-step — submitting your sitemap

1.Open Google Search Console and sign in with the Google account that should manage the property.

2.Select the correct property, or use “Add property” to add your site first. Domain properties cover all protocols and subdomains once DNS verification completes; URL-prefix properties match a specific protocol and host, which matters when your sitemap URL must line up with how you verified ownership.

3.In the left sidebar, open Sitemaps under the Indexing section.

4.In **Add a new sitemap**, enter the path to your sitemap file only—for example sitemap.xml if the file lives at the root—so the full address becomes https://yourdomain.com/sitemap.xml. Use HTTPS and the same host you verified.

5.Click Submit.

6.After processing, check the Status column for the new row: a Success status means Google fetched the file and could read it at submission time. Discovery is not instant indexing; give the system time, then use URL-level reports if specific pages stall. Recheck after deploys because status can change if the URL 404s or the file breaks later.

What to do if your sitemap shows errors

Search Console summarizes problems in plain language, and a handful of messages cover most cases. If you see Couldn't fetch, the URL is wrong, the file is not actually reachable at that path, or the server returned an error when Google requested it. Open the sitemap URL in an incognito window or with curl and confirm you get HTTP 200 and XML content, not a login page or HTML error template.

Has errors or messages about malformed XML point back to the file itself: missing tags, invalid characters, or URLs that violate the protocol. Export the live file, fix the markup or the URLs it lists, redeploy, and validate again with Sitemap Validator before resubmitting or waiting for the next crawl.

**Submitted URL blocked by robots.txt** means Google can reach your sitemap document but one or more URLs inside it are disallowed for Googlebot in robots.txt. That is a policy signal, not an XML bug. Either remove the conflicting Disallow for those paths—if they are meant to be indexed—or accept that those URLs will not be crawled until the robots rules change. Fix robots and sitemap together so they tell the same story about what should be public.

If the row lingered in a “Pending” state for a long time before failing, treat that as another signal to verify fetchability, response time, and firewall rules—especially on hosts that throttle or challenge unidentified crawlers.

For large sites — sitemap index files

The sitemaps.org protocol limits a single sitemap file to fifty thousand URLs and fifty megabytes uncompressed. Large sites split work across multiple sitemap files and point to them from a sitemap index—a small XML document that lists child sitemap locations. You submit the index URL once in Search Console; Google follows the references. gzip compression is allowed when your server exposes a .gz URL that returns the correct encoding; the index file itself stays small because it only lists child locations, not every page. If you are close to the limit or reorganizing sections by product line or locale, use our Sitemap Index Generator to build a compliant index and Sitemap Split & Merger when you need to divide or combine existing files without hand-editing thousands of lines.

Don’t have a sitemap file yet? Build one in minutes with the free XML Sitemap Generator, host it on your site, then return to Search Console and submit the URL using the steps above.

How to Submit a Sitemap to Google Search Console (Step-by-Step)

Before you submit — make sure your sitemap is valid

Step-by-step — submitting your sitemap

What to do if your sitemap shows errors

For large sites — sitemap index files

SiteSupport Team

Related Articles

XML Sitemaps: The Complete SEO Guide for 2025

Robots.txt: What It Is, Why It Matters, and How to Write One

Continue Exploring This Topic

Sitemap Validator

XML Sitemap Generator

Sitemap Index Generator

Want AI-powered customer support?