How to Submit a Sitemap to Google Search Console

To submit a sitemap to Google Search Console, open the Sitemaps report under Indexing, enter your sitemap address, such as sitemap.xml, and click Submit, after first uploading a valid sitemap file to your site root. Build that file in seconds with our free sitemap generator.

Try it now: Sitemap Generator →

What a Sitemap Is, and What Submission Does Not Promise

A sitemap is a machine-readable file, usually named sitemap.xml, that lists the pages on a website that its owner wants search engines to discover, with optional details for each page such as the last modified date, how often it changes, and its relative priority. Submitting it to Google Search Console hands that list to Google directly, instead of waiting for Googlebot to find every page by following links, which speeds up discovery, especially for new pages, pages with few inbound links, and large sites where crawling every link takes time. What submission does not do is equally important: Google states plainly that a sitemap is a hint, not a directive, so submitting a page does not guarantee it will be crawled, and crawling does not guarantee it will be indexed, and indexing does not guarantee it will rank. A sitemap cannot rescue thin, duplicate, or low-value pages, and a site with fewer than about 500 pages whose pages are all reachable from the homepage may not need one at all, though submitting one still costs nothing. The honest way to think about it is as a map handed to a visitor: it helps them find the rooms, but it does not make them like what is inside. That framing keeps expectations realistic, and it explains why the status report below matters more than the submit button itself.

Try it now: Sitemap Generator →

Build a Valid Sitemap File First

Submission fails most often on the file, not on the form, so the file must be valid before it is ever submitted. A valid XML sitemap starts with an XML declaration and a urlset element, and each page is a url entry containing a loc element with the full absolute address, including https and the domain, because relative addresses are not processed correctly. Two optional elements per page are worth using: lastmod, the date the page last changed, which helps Google prioritize recrawling, and changefreq plus priority, which state how often a page changes and how important it is relative to other pages on the same site. The hard limits are 50,000 URLs and 50 megabytes uncompressed per file, and sites above either limit must split into multiple sitemaps listed in a sitemap index file, which is itself submitted instead of the individual files. The fastest way to build a correct file is to paste the page addresses into our free sitemap generator, which validates each address as it builds, sets lastmod, changefreq, and priority, and gives a copy-or-download result that can be uploaded unchanged. Before submitting, open the finished file in a browser and confirm it loads as XML, not as an error page, because a file that returns a 404 or an HTML error page at its own address cannot be submitted successfully, whatever the form says.

Submit It: The Search Console Steps, Plus Robots.txt and Bing

With a valid file uploaded to the site root, so that it lives at an address like example.com/sitemap.xml, submission itself takes under a minute. Sign in to Search Console with an account that owns the property, select the correct property, because a sitemap submitted to the wrong property helps nobody, then open Indexing in the left navigation and click Sitemaps. In the Add a new sitemap box, enter the path after the domain, usually just sitemap.xml, or sitemap_index.xml for an index file, and click Submit, then refresh after a few minutes to see the status. Two companion steps cover the crawlers that do not use Search Console: add a line to robots.txt reading Sitemap followed by the full sitemap address, which is how Bing, DuckDuckGo, and other crawlers find the file without an account, and submit the same file separately in Bing Webmaster Tools, which feeds Yahoo and other search partners. The robots.txt step deserves care, because the sitemap line belongs in robots.txt alongside the crawl rules, and our guide to creating a robots.txt file for WordPress shows where it goes, while our free robots.txt generator builds the file with the sitemap line included. A sitemap referenced in robots.txt but never submitted to Search Console still gets found eventually, but submission gives the status feedback that robots.txt alone cannot provide.

Reading the Status Report and Fixing Common Errors

After submission, the Sitemaps report shows a status for the file, and the status is the real deliverable of the whole exercise. Success with a discovered URL count means Google fetched the file and read that many addresses, and those pages now enter the crawl queue on Google's schedule, which is usually days, not minutes, for a small site. Could not fetch usually means a typo in the submitted path, a file that returns a 404, a server error, or a robots.txt rule that blocks the sitemap path itself, and the fix is to open the sitemap address in a browser, confirm it loads, and check that robots.txt does not disallow it. Errors on individual URLs, shown in the report detail, usually mean a listed address redirects, returns a 404, is blocked by robots.txt, or is a duplicate of a canonical address, and the fix is to remove or correct those entries and let the next crawl pick up the cleaned file. Two myths should be retired: resubmitting after every publish is unnecessary, because Google recrawls a submitted sitemap on its own schedule, and resubmission does not speed up indexing of a page Google has already seen and chosen not to index. The correct rhythm is to submit once, fix fetch errors promptly, regenerate the file when a meaningful number of pages are added or removed, and check the report monthly. For the rest of a launch checklist, our guides to generating Open Graph tags and writing meta descriptions that get clicks cover the social and search snippets, while our free keyword density checker and our free UTM builder cover the on-page and campaign checks that follow indexing.