What Is Google Search Console?
Google Search Console (GSC) is a free tool provided by Google that lets website owners monitor how Google crawls and indexes their site. It shows you which pages are indexed, flags crawl errors, reports Core Web Vitals data, and — most relevant to this guide — lets you submit and monitor sitemaps.
Submitting your sitemap directly in GSC is the single most reliable way to tell Google exactly which URLs exist on your site and ask it to crawl them. Google discovers pages through many paths (links from other pages, backlinks, crawl history), but a sitemap submission is a direct, authoritative signal. It is especially important for new sites, pages with few internal links, or large sites where crawlers might miss content buried in deep navigation.
If you don’t have a sitemap yet, use the sitemap.xml Generator to create one from a URL list in seconds before following the steps below.
Step-by-Step: Submitting Your Sitemap in Google Search Console
Step 1 — Verify Ownership of Your Property
Before you can submit anything, you need to verify that you own the site in GSC. Navigate to Google Search Console and add your property. GSC offers several verification methods:
- HTML file — upload a file Google provides to your server root
- HTML meta tag — add a
<meta>tag to your homepage<head> - Google Analytics / Tag Manager — if you already have GA or GTM installed, GSC can verify automatically
- DNS record — add a TXT record via your domain registrar
Choose the method that fits your setup. Verification is a one-time step.
Step 2 — Navigate to the Sitemaps Report
Once your property is verified and you’re inside GSC, look at the left sidebar and click Indexing → Sitemaps. This opens the Sitemaps report, which shows all sitemaps you’ve previously submitted and their status.
Step 3 — Enter Your Sitemap URL
At the top of the Sitemaps report, you’ll see an input field labeled “Add a new sitemap” with your domain pre-filled. Type the path to your sitemap file into the field.
For most sites, this will be one of:
sitemap.xmlsitemap_index.xmlsitemaps/sitemap.xml
The most common convention is placing the file at the root of your domain so the full URL is https://example.com/sitemap.xml. Enter just the path portion (after your domain) into the field.
Step 4 — Click Submit
Click the Submit button. GSC will attempt to fetch and read the file immediately. If the file is reachable and valid XML, you’ll see a success message and the sitemap will appear in your list with a Success status.
If the submission fails, GSC will show an error code. The most common errors are covered in the troubleshooting section below.
Step 5 — Review the Sitemap Status
After submission, the Sitemaps report shows:
- Status — Success, Couldn’t fetch, Has errors, etc.
- Discovered URLs — how many URLs Google found in the sitemap
- Last read — when Google last fetched the file
Click on a submitted sitemap to drill into its details, including any warnings or errors at the URL level.
Reference Your Sitemap in robots.txt
In addition to submitting via GSC, you should also reference your sitemap in your robots.txt file using the Sitemap: directive. This is a widely supported standard that allows any compliant crawler — not just Googlebot — to discover your sitemap automatically.
The Sitemap: directive goes at the end of your robots.txt and uses the full absolute URL:
User-agent: *
Disallow:
Sitemap: https://example.com/sitemap.xmlYou can list multiple Sitemap: directives if you have more than one sitemap file or a sitemap index:
Sitemap: https://example.com/sitemap_pages.xml
Sitemap: https://example.com/sitemap_blog.xmlThis is not a substitute for submitting via GSC — it doesn’t grant you the monitoring, error reporting, or index coverage data that GSC provides. But it is a best practice that costs nothing and ensures other crawlers (Bing, DuckDuckGo, etc.) can also find your sitemap without manual submission.
Checking Indexing Status After Submission
Submitting a sitemap is the beginning, not the end. Here is how to monitor what happens next.
The Coverage Report
In GSC, go to Indexing → Pages. This report shows all the URLs Google has processed, broken down into four buckets:
- Error — pages Google tried to index but couldn’t (404, server error, blocked by robots.txt, etc.)
- Valid with warning — indexed but with a note (e.g., submitted in sitemap but canonicalized to a different URL)
- Valid — successfully indexed pages
- Excluded — pages deliberately not indexed (noindex, canonicalized away, crawled but not indexed)
Compare the “Discovered URLs” count in the Sitemaps report against the “Valid” count in the Pages report. A large gap between discovered and indexed pages is a signal worth investigating.
The URL Inspection Tool
For any individual URL you’re concerned about, use the URL Inspection tool (magnifying glass icon in the top bar of GSC, or paste a URL in the top search box). It shows:
- Whether Google has indexed the page
- The last crawl date
- The canonical URL Google selected
- Any coverage issues specific to that URL
Re-Submitting After Site Changes
Google re-crawls submitted sitemaps on its own schedule, so you don’t need to resubmit for every page update. However, resubmitting is worth doing in these situations:
- You’ve published a large batch of new pages (a new product range, a new blog category, a migrated archive)
- You’ve done a site migration and the sitemap now contains many new URLs
- You’ve significantly changed the URL structure of existing pages
- Your previous submission returned errors that you’ve now fixed
To resubmit, go back to Indexing → Sitemaps in GSC, find your existing sitemap in the list, delete it using the three-dot menu, then add and submit it again. This re-triggers an immediate fetch attempt and resets the “Last read” timestamp.
Common Sitemap Errors and How to Fix Them
Error: Couldn’t Fetch
What it means: Google tried to retrieve your sitemap URL and got no response, or the connection timed out.
Fixes:
- Confirm the URL you submitted is exactly correct (no typos, correct path)
- Check that the file exists on your server — visit the URL in your browser to verify
- If your site uses HTTPS, ensure the HTTPS version is accessible (not just HTTP)
- Check your server logs for 5xx errors or connection timeouts
- Temporarily disable any IP-based rate limiting or WAF rules that might block Googlebot
Error: 404 Not Found
What it means: The server responded, but the sitemap file wasn’t found at the path you provided.
Fixes:
- Double-check the file path and filename (case-sensitive on Linux servers)
- Make sure the sitemap was actually uploaded or generated at that location
- If you recently moved the file, update the submitted URL in GSC and the
Sitemap:directive inrobots.txt
Error: Malformed XML
What it means: Google fetched the file but couldn’t parse it because the XML structure is invalid.
Fixes:
- Open the sitemap URL in your browser — most browsers will display an XML parse error with a line number if the structure is broken
- Validate the XML with a sitemap validator tool
- If you generated the sitemap manually, check for missing closing tags, unescaped characters (
&must be&,<must be<), or incorrect namespace declarations - Use the sitemap.xml Generator to regenerate a clean, valid file from your URL list
Error: Blocked by robots.txt
What it means: Your robots.txt file is disallowing Googlebot from accessing the sitemap URL.
Fixes:
- Open
https://example.com/robots.txtand check whether anyDisallow:rule covers the sitemap path (for example,Disallow: /sitemap.xmlorDisallow: /which blocks everything) - Use the GSC robots.txt tester to check which rules apply to your sitemap URL
- Update
robots.txtto allow access to the sitemap file, then resubmit
Sitemap Index Files for Large Sites
A single sitemap file can contain a maximum of 50,000 URLs and must not exceed 50 MB uncompressed. For large sites, the solution is a sitemap index file — an XML file that lists multiple child sitemap files.
<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<sitemap>
<loc>https://example.com/sitemaps/sitemap-pages.xml</loc>
<lastmod>2026-06-25</lastmod>
</sitemap>
<sitemap>
<loc>https://example.com/sitemaps/sitemap-blog.xml</loc>
<lastmod>2026-06-25</lastmod>
</sitemap>
<sitemap>
<loc>https://example.com/sitemaps/sitemap-products.xml</loc>
<lastmod>2026-06-25</lastmod>
</sitemap>
</sitemapindex>Submit the sitemap index URL to GSC just like a regular sitemap. GSC will follow the references to each child sitemap and process them individually. Each child sitemap still obeys the 50,000-URL / 50 MB limit.
A sitemap index is also useful for organizational reasons even on smaller sites — for example, keeping a separate sitemap for blog posts, product pages, and category pages makes it easier to see exactly how many pages of each type Google has discovered.
Key Takeaways
- Submit your sitemap via Google Search Console → Indexing → Sitemaps for direct monitoring and error reporting
- Always reference your sitemap with the
Sitemap:directive inrobots.txtso all compliant crawlers can find it - Monitor the Pages coverage report to identify gaps between discovered and indexed URLs
- Resubmit after major content updates or site migrations to trigger an immediate re-fetch
- Fix malformed XML, 404 errors, and robots.txt blocks before expecting successful indexing
- Use sitemap index files for sites with more than 50,000 URLs