Back to Blog

How to Submit a Sitemap to Google Search Console (2026)

Step-by-step walkthrough: verify your site, submit the sitemap URL, fix the common errors, and know what to expect afterwards.

I
Indexly Team
· · 11 min read

How to Submit a Sitemap to Google Search Console (2026)

Submitting your sitemap to Google Search Console takes about three minutes: sign in, select your property, open the Sitemaps report, paste your sitemap URL, click Submit. That's the whole job — but it's easy to trip on verification, pick the wrong property type, or enter the URL in a format Google won't accept.

This guide walks through the exact steps, shows what the "Success" state looks like, covers the common errors and how to fix them, and explains what you should (and shouldn't) do after submission.

Table of contents

  1. Before you start: what you need
  2. Step-by-step: submitting your sitemap
  3. What happens after you submit
  4. Common errors and how to fix them
  5. Do you need to resubmit when content changes?
  6. Bonus: listing your sitemap in robots.txt
  7. FAQ

Before you start: what you need

Three things before you can submit:

1. A sitemap. A publicly-reachable XML file listing your URLs. If you don't have one yet, see our complete XML sitemap guide or use a hosted tool like Indexly's free tier to generate one from your site URL.

2. The sitemap's full URL. Something like https://example.com/sitemap.xml or https://cdn.indexly.dev/sitemaps/1234/56/789/sitemap.xml. Open it in a browser first to confirm it loads and shows XML — if the browser shows a 404 or a rendered error page, the rest of this guide won't help.

3. A verified Google Search Console property for your site. This is where most beginners get stuck. You need to have already added your site to Search Console and proved you own it. If you haven't, do that first — instructions below.

If you haven't verified your site yet

Go to search.google.com/search-console and click "Add property." You'll see two options:

  • Domain — verifies the whole domain including all subdomains (example.com, www.example.com, blog.example.com). Requires DNS verification, which means adding a TXT record at your domain registrar.
  • URL prefix — verifies only the exact URL you enter (https://example.com/ is different from https://www.example.com/). Can be verified through several methods: HTML file upload, HTML meta tag, Google Analytics, Google Tag Manager, or DNS.

Pick Domain if you can. It covers everything under your domain and survives subdomain or protocol changes. Pick URL prefix only if you don't have DNS access.

Once verified, you'll see the property in the dropdown at the top-left of Search Console. Now you're ready to submit.

Step-by-step: submitting your sitemap

Step 1: Open Search Console and select your property

Go to search.google.com/search-console and sign in with the Google account that has access to the property.

At the top-left, there's a dropdown showing the current property. If you manage multiple sites, select the one you want to submit a sitemap for.

Watch out for: if you verified both https:// and https://www. as separate URL-prefix properties, the sitemap goes in whichever one your site actually serves from. Submitting to the wrong property means Google won't associate the sitemap with your real site.

Step 2: Open the Sitemaps report

In the left sidebar, under Indexing, click Sitemaps.

You'll see two sections: "Add a new sitemap" at the top, and "Submitted sitemaps" below (empty if this is your first time).

Step 3: Enter your sitemap URL

In the "Add a new sitemap" field, paste your sitemap URL.

For Domain properties: enter the full URL, including the domain. Example: https://example.com/sitemap.xml.

For URL-prefix properties: the domain is already filled in. You only enter the path. Example: type sitemap.xml and the field will show https://example.com/sitemap.xml.

If your sitemap is hosted on a different domain (for example, Indexly's hosted URL at https://cdn.indexly.dev/sitemaps/1234/56/789/sitemap.xml) — submit the full external URL. Google accepts cross-domain sitemaps when submitted directly through Search Console, even though it rejects them from robots.txt.

Step 4: Click Submit

Google will attempt to fetch the sitemap immediately. Within seconds you'll see a success or error message.

If successful, you'll see a "Sitemap submitted successfully" confirmation, and the sitemap will now appear in the "Submitted sitemaps" list with its status.

Step 5: Verify the status

In the "Submitted sitemaps" list, your sitemap will show one of these statuses:

Status What it means
Success Sitemap was fetched and parsed without errors
Has errors Sitemap was fetched but contains invalid URLs or formatting issues
Couldn't fetch Google couldn't download the file (wrong URL, 404, server error)
Pending Sitemap was submitted but Google hasn't processed it yet (usually clears within a few hours)

Click the sitemap's row to see detail — how many URLs were discovered, when it was last read, and any errors. A healthy sitemap will show a URL count matching your site and a recent "last read" date.

What happens after you submit

A few things to expect, and a few things not to expect.

Google fetches your sitemap. Usually within seconds of submission, then periodically thereafter — on a schedule Google determines based on how often the sitemap actually changes.

Google starts crawling the URLs it contains. This doesn't happen all at once. For a new or small site, Google may crawl a few URLs per day. For an established site, crawling is much faster.

Not every URL will be indexed. A sitemap is a discovery tool, not a command. Google still evaluates each URL individually and decides whether it's worth keeping in the index. If specific pages aren't getting indexed, see why Google isn't indexing your pages.

You'll start seeing data in the Pages report. Within a few days, Search Console → Pages will begin showing which URLs from your sitemap got indexed and which didn't, and why. This is the single most useful report in Search Console for diagnosing indexing problems.

Don't request indexing on every URL in your sitemap. The URL Inspection tool's "Request Indexing" button is rate-limited to around 10–12 submissions per day. Use it for the handful of URLs you care most about, not as a bulk tool.

Common errors and how to fix them

"Couldn't fetch"

Google tried to download your sitemap and got an error. Possible causes:

  • Wrong URL. Open the sitemap URL in a private/incognito browser window. If it doesn't load, the URL is wrong or the file isn't where you think it is.
  • 404 on the sitemap path. Your sitemap is at /sitemaps/main.xml but you submitted /sitemap.xml.
  • Blocked by robots.txt. Rare, but check. Your sitemap itself should not be blocked.
  • Server returned 500. Happens with dynamic sitemaps on large sites — the controller times out. Try the URL in a browser; if it hangs for more than 30 seconds, your sitemap generator is too slow.
  • Authentication required. If your sitemap is behind basic auth or a login page, Googlebot can't reach it.

"Has errors"

Sitemap was fetched but contains problems. Click the row to see specifics. Common ones:

  • Invalid URL: a URL in the sitemap isn't a valid absolute URL (starts with / instead of https://, contains un-escaped special characters, etc.).
  • URL not allowed: a URL points outside the sitemap's scope — typically a different domain — without cross-site submission being set up.
  • Empty sitemap: the file parsed but contained zero URLs.
  • Unsupported format: Google expected XML and got something else (HTML error page, plain text without the XML schema).

"Submitted URL blocked by robots.txt"

Not a sitemap-submission error per se, but shows up in the Pages report afterward. Means a URL in your sitemap is disallowed in your robots.txt. Fix by either removing the URL from the sitemap or removing the Disallow: rule — whichever reflects your actual intent. See sitemap vs robots.txt for the full treatment.

"Couldn't fetch" but the URL loads fine in your browser

Three likely causes:

  1. Your firewall is blocking Googlebot. Some hosting providers (or Cloudflare's Bot Fight Mode set too aggressively) rate-limit Googlebot. Check your WAF logs.
  2. You submitted http:// instead of https:// or vice versa.
  3. The server is slow and Googlebot's fetch timed out. Try retriggering the submission after you've confirmed the sitemap loads quickly.

Do you need to resubmit when content changes?

No. Once you submit a sitemap, Google re-fetches it on its own schedule. You don't need to resubmit every time your content changes.

The one exception: if you actually change the sitemap's URL (moved from /sitemap.xml to /sitemaps/main.xml, or switched to a hosted sitemap on a different domain), you submit the new URL and optionally remove the old one.

What does matter is that the sitemap at your submitted URL stays accurate and reachable. A sitemap that was submitted six months ago and is now 40% stale is a sitemap Google will start trusting less — regardless of how many times you click "Submit." The ongoing job isn't submission, it's maintenance.

This is one of the main reasons hosted sitemap tools exist. Indexly keeps your sitemap continuously fresh from external infrastructure, so after you submit the Indexly URL to Search Console once, it stays accurate for years without you touching it.

For a deeper look at how often your sitemap should actually update, see how often should your sitemap update.

Bonus: listing your sitemap in robots.txt

Independent of Search Console submission, you should also list your sitemap in your robots.txt file. This is a free signal and takes one line:

User-agent: *
Allow: /
Sitemap: https://example.com/sitemap.xml

Robots.txt lives at https://yoursite.com/robots.txt. Adding a Sitemap: line tells every crawler that reads the file — Google, Bing, and others — where to find your sitemap. This doesn't replace Search Console submission (the coverage data in GSC is worth the separate submission), but it's a belt-and-braces backup.

You can list multiple sitemaps or a sitemap index:

Sitemap: https://example.com/sitemap-products.xml
Sitemap: https://example.com/sitemap-blog.xml
Sitemap: https://example.com/sitemap-index.xml

Both approaches should point at the same URLs — they're not substitutes.

FAQ

How do I submit a sitemap to Google Search Console?

Sign in to Search Console, select your verified property, click Sitemaps under Indexing in the left sidebar, paste your sitemap URL into the "Add a new sitemap" field, and click Submit. Google fetches the sitemap within seconds and begins crawling the URLs it contains over the following days.

Do I need to submit my sitemap to Google every time I update my site?

No. Once submitted, Google re-fetches your sitemap automatically on its own schedule — usually daily for active sites, less often for static ones. You only need to resubmit if the sitemap's URL changes. The ongoing job is keeping the sitemap accurate, not re-clicking Submit.

How long does it take Google to process a submitted sitemap?

Google typically fetches the sitemap within seconds of submission. Processing it (validating URLs, checking for errors) takes a few minutes to a few hours. Actually crawling and indexing the URLs inside the sitemap can take anywhere from a day to several weeks, depending on your site's authority and crawl rate.

Can I submit more than one sitemap?

Yes. You can submit multiple sitemaps per property, and it's often useful — for example, a separate sitemap per content type (products, blog, categories) helps you diagnose indexing issues by section in Search Console. For sites over 50,000 URLs, you'll need multiple sitemaps managed by a sitemap index file.

What if I don't have a sitemap yet?

Generate one first. Most CMSes (WordPress with Yoast, Shopify, Webflow, Ghost) produce a sitemap automatically — usually at yoursite.com/sitemap.xml or yoursite.com/sitemap_index.xml. Sites on custom stacks can use a hosted tool like Indexly's free tier to generate and host one without touching code.

My sitemap says "Couldn't fetch" — what now?

Open the sitemap URL in a private browser window. If it doesn't load, the URL is wrong or the file isn't accessible. If it loads fine, check whether your firewall or WAF is blocking Googlebot, confirm you submitted the exact HTTP/HTTPS and www/non-www variant that matches your site, and verify the sitemap isn't blocked in robots.txt.


The bottom line

Submitting a sitemap to Search Console is easy. Keeping the sitemap accurate for the next few years is the actually-hard part — and the one most sites quietly give up on after month three.

If you'd rather not think about it, try Indexly free. Paste your site URL, get a hosted sitemap URL in sixty seconds, submit that URL to Search Console once, and it stays current forever. No plugin, no cron job, no credit card. Every page found. Every page indexed.

I

Indexly Team

Writing about SEO, sitemaps, and how to get every page indexed by Google.

Enjoyed this post?

Get our next one delivered to your inbox — no spam, ever.

Back to Blog

Ready to get your site fully indexed?

Get started free