How to Submit a Sitemap to Google Search Console
Submitting a sitemap is one of the simplest ways to help Google find and index your pages faster. This guide walks through verifying your site, locating your sitemap, submitting it, and reading the results.
Table of Contents
Why Submit a Sitemap at All
Google discovers pages mostly by following links, but that process can be slow and it can miss pages that are not well linked. A sitemap hands Google a tidy list of the URLs you care about, along with hints about when each page was last updated.
Submitting it through Search Console does two useful things. It nudges Google to crawl your list, and it gives you a report showing how many of those URLs were read and whether any had problems. For new sites, large sites, or pages buried deep in the structure, that visibility is well worth the few minutes it takes.
Before You Start
You need two things ready: a Google account and a sitemap file that is live on your website. The sitemap usually sits at an address like https://yoursite.com/sitemap.xml. If you do not have one yet, a sitemap generator can build it from your URL in moments.
Open your sitemap address in a browser first. If the XML loads, it is ready to submit. If you get an error, fix that before continuing.
Verifying Your Site
Search Console only lets you manage sites you own, so the first step is proving ownership. After adding your site as a property, you choose a verification method:
- HTML file upload. Download a file from Google and place it in your site root.
- HTML meta tag. Add a small tag to your homepage head section.
- DNS record. Add a record at your domain provider, which verifies the whole domain at once.
Pick whichever you can access most easily. Once Google confirms the marker, your property is verified and you can move on.
Submitting the Sitemap
1. Open the Sitemaps report
In Search Console, find the Sitemaps section in the left menu under Indexing.
2. Enter the sitemap path
In the Add a new sitemap field, type the part after your domain, such as sitemap.xml, then click Submit.
3. Wait for processing
Google reads the file and reports a status. It may take time before every URL is crawled, so do not expect instant results.
Reading the Sitemap Status
After processing, the report shows a status and the number of discovered URLs. Here is what the common results mean:
| Status | Meaning |
|---|---|
| Success | Google read the sitemap with no errors |
| Has errors | Some URLs or formatting need fixing |
| Couldn't fetch | Google could not reach the file at all |
A Success status does not guarantee every page gets indexed, since Google still decides what to include. But it confirms your list was received and is being considered.
Check back over the following days. The Pages report will show how many of your submitted URLs Google has indexed over time.
Where to Find or Create Your Sitemap
Before you can submit a sitemap, you need to know where yours lives or how to make one. Many sites already have a sitemap without the owner realizing it, while others need one built from scratch.
First, check the usual locations. Try opening yoursite.com/sitemap.xml in a browser. A lot of platforms generate this automatically. You can also look in your robots.txt file, since sitemaps are often listed there with a line that begins with Sitemap followed by the full URL.
If you run WordPress or a similar system, an SEO plugin usually produces and updates a sitemap for you. The address might be sitemap.xml or sitemap_index.xml depending on the plugin. For a custom or static site with no sitemap, a sitemap generator can crawl your URL and produce a clean XML file in moments, which you then upload to your root folder.
Whichever route you take, confirm the sitemap loads in a browser and lists your real, current URLs before submitting it.
Fixing Common Sitemap Errors
When Search Console reports a problem, the message usually points straight to the cause. Here are the errors you are most likely to see and how to resolve them.
- Couldn't fetch. Google could not reach the file. Confirm the URL is exactly right, the file is public, and robots.txt is not blocking it.
- URLs not accessible. Some listed pages return errors or redirects. Remove broken URLs and make sure each entry is a final destination returning a 200 status.
- Invalid XML. A formatting problem, often a special character or a missing tag. Regenerating the sitemap with a tool usually fixes the structure.
- Wrong domain or protocol. Entries must match your canonical domain version, whether that is www or non-www, http or https. Mixing them causes errors and duplicate signals.
After fixing an issue, you do not always need to resubmit. Google re-reads sitemaps periodically, but pressing submit again can prompt a faster recheck once you are confident the problem is resolved.
Monitoring Indexing Over Time
Submitting a sitemap is the start, not the finish. The real value comes from watching how Google responds over the following days and weeks. The Pages report in Search Console is where this story unfolds.
That report splits your URLs into indexed and not indexed, and for the ones left out it gives a reason. Common explanations include pages marked noindex, duplicates without a clear canonical, or pages Google crawled but chose not to index. Reading these reasons tells you exactly where to focus.
Do not expect every URL to be indexed, and do not panic over small numbers in the not indexed column, since some of those are intentional. What you want to see is a steady trend of your important pages moving into the indexed group over time. If a key page is stuck, use the URL Inspection tool to check its status and request indexing directly.
Sitemaps and Robots.txt Together
Your sitemap and robots.txt file work as a pair, and a conflict between them is a frequent cause of indexing trouble. The sitemap says here are the pages I want found, while robots.txt says here is what crawlers may or may not access.
The problem arises when a URL appears in your sitemap but is also blocked in robots.txt. You are sending mixed signals: inviting Google to a page while simultaneously closing the door. Make sure every URL in your sitemap is actually crawlable and not disallowed.
A helpful habit is to reference your sitemap inside robots.txt with a single line, such as Sitemap: https://yoursite.com/sitemap.xml. This gives crawlers another way to discover the file, even before you submit it in Search Console.
Keep the two files aligned and your crawl signals stay clear, which helps Google index the pages you care about.
FAQs
How long does it take Google to index my sitemap?
There is no fixed time. Some pages appear within days, others take weeks. Indexing depends on your site's authority, content quality, and how often Google crawls you.
Do I need to resubmit when I add new pages?
Usually no. If your sitemap updates automatically, Google re-reads it on its own. You only resubmit if you change the sitemap location or want to prompt a fresh look.
Why does my sitemap say "Couldn't fetch"?
That means Google could not load the file. Confirm the URL is correct, the file is publicly accessible, and that robots.txt is not blocking it.