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

## Why Submit a Sitemap to Google Search Console?

A sitemap is an XML file that tells search engines about the pages on your website. While Google can discover pages by following links, submitting a sitemap directly to Google Search Console provides several advantages.

First, it speeds up discovery of new content. When you publish a new page, Google may not find it immediately through crawling. A sitemap ensures Google knows about it right away.

Second, it helps with large or complex sites. If your website has thousands of pages, orphan pages (pages with few internal links), or dynamically generated content, a sitemap ensures nothing gets missed.

Third, it gives you visibility into indexing issues. After submission, Google Search Console shows you exactly how many URLs were discovered versus indexed, helping you identify problems.

## Step 1: Find or Create Your Sitemap

Most modern CMS platforms generate sitemaps automatically. Here's where to find yours:

### WordPress

If you use Yoast SEO, your sitemap is at: yoursite.com/sitemap_index.xml. For Rank Math, it's the same location. WordPress core (5.5+) also generates a basic sitemap at yoursite.com/wp-sitemap.xml.

### Shopify

Shopify automatically generates a sitemap at yoursite.com/sitemap.xml. You don't need any plugins.

### Custom Sites

For static sites or custom builds, you'll need to generate a sitemap using a tool or script. The sitemap must be valid XML following the sitemap protocol at sitemaps.org.

### How to Verify Your Sitemap Exists

Open your browser and visit yoursite.com/sitemap.xml. You should see an XML file listing your URLs. If you get a 404 error, your sitemap either doesn't exist or is at a different location.

## Step 2: Log Into Google Search Console

Go to search.google.com/search-console and sign in with your Google account. You must have verified ownership of the property (website) before you can submit a sitemap.

If you haven't verified your site yet, Google offers several verification methods: HTML file upload, HTML meta tag, Google Analytics, Google Tag Manager, or domain-level DNS verification.

## Step 3: Navigate to the Sitemaps Report

Once logged in, select your property from the dropdown if you manage multiple sites. In the left sidebar, find the 'Indexing' section and click 'Sitemaps'.

This page shows all previously submitted sitemaps, their status, and when Google last read them.

## Step 4: Submit Your Sitemap URL

At the top of the Sitemaps page, you'll see an input field labeled 'Add a new sitemap'. Enter your sitemap URL here.

You only need to enter the path portion. For example, if your full sitemap URL is https://yoursite.com/sitemap.xml, just type 'sitemap.xml' in the field.

Click the Submit button. Google will immediately attempt to fetch your sitemap.

## Step 5: Check the Submission Status

After submitting, you'll see your sitemap listed with one of these statuses:

**Success**: Google fetched your sitemap successfully and is processing the URLs.

**Couldn't fetch**: Google couldn't access your sitemap. Check for robots.txt blocks or server errors.

**Has errors**: The sitemap was fetched but contains invalid XML or URLs with issues.

## Step 6: Monitor Indexing Progress

Click on your submitted sitemap to see detailed metrics:

**Discovered URLs**: The total number of URLs found in your sitemap. This number should match what you expect based on your site's page count.

**Indexed URLs**: The URLs that Google has successfully added to its search index. This number is often lower than discovered URLs��that's normal.

If there's a large gap between discovered and indexed URLs, check the Pages report (also under Indexing) to understand why specific pages aren't being indexed.

## Common Sitemap Errors and How to Fix Them

### Error: Couldn't Fetch

This means Google couldn't access your sitemap at all. Common causes include: your robots.txt is blocking the sitemap, the server returned a 4xx or 5xx error, or the URL is incorrect.

To fix: Check your robots.txt file at yoursite.com/robots.txt. Make sure there's no Disallow rule blocking your sitemap. Try accessing the sitemap URL directly in an incognito browser window.

### Error: Sitemap Contains Errors

This indicates the sitemap XML format is invalid. Common issues include: unclosed XML tags, invalid characters, or URLs that aren't properly encoded.

To fix: Use a sitemap validator tool to check your XML. Most online validators will pinpoint exactly where the error is.

### Error: URLs Blocked by robots.txt

Your sitemap is valid, but some URLs inside it are blocked from crawling by robots.txt rules.

To fix: Either remove those URLs from your sitemap, or update your robots.txt to allow crawling if those pages should be indexed.

## Best Practices for Sitemaps

**Keep sitemaps under 50MB uncompressed or 50,000 URLs.** If your site is larger, use a sitemap index file that references multiple child sitemaps.

**Only include canonical URLs.** Don't include URLs that redirect, return 404, have noindex tags, or are duplicates of other pages.

**Update your sitemap when content changes.** Most CMS platforms do this automatically. For static sitemaps, set up a process to regenerate them.

**Include the lastmod date.** This tells Google when each page was last updated, helping prioritize crawling of fresh content.

If you encounter indexing issues after submitting your sitemap, see our guide on [how to fix crawl errors in Google Search Console](/blog/fix-crawl-errors-google-search-console) for troubleshooting steps.

## What Happens After Submission?

Google doesn't index all URLs immediately after you submit a sitemap. Here's the typical timeline:

Within minutes: Google fetches and parses your sitemap, and the status updates in Search Console.

Within hours to days: Googlebot begins crawling the URLs in your sitemap based on your site's crawl budget.

Within days to weeks: Crawled pages are evaluated for quality and either indexed or marked with issues in the Pages report.

Sites with established authority and fresh content typically see faster indexing. Brand new sites or pages with quality issues may take longer or not be indexed at all.