Tr
FREE SEO Audit (224) 600-4353Call
Home/Blog/How to Submit a Sitemap to Google: Step-by-Step…
Modern SEO · August 7, 2026 · 15 min read

How to Submit a Sitemap to Google: Step-by-Step Guide

Learn how to submit a sitemap to Google effectively. Our step-by-step guide ensures your site gets indexed quickly and without errors.

How to Submit a Sitemap to Google: Step-by-Step Guide

To submit a sitemap to Google, verify ownership of your site in Google Search Console, open Indexing > Sitemaps, paste your sitemap URL into the “Add a new sitemap” field, and click Submit. Google will attempt to fetch the file immediately, and the full submission process completes promptly. That’s the short version. The sections below walk through every prerequisite, common error, and alternative method so you get it right on the first try.

Here’s the quick-start checklist:

  • Verify ownership of your property in Google Search Console (required before you can submit anything)
  • Confirm your sitemap file is publicly accessible at a known URL, such as https://yourdomain.com/sitemap.xml
  • Open Search Console, select your property, go to Indexing > Sitemaps, and paste the URL
  • Click Submit and watch for a status of “Success” in the Sitemaps report
  • If you see “Couldn’t fetch” or “Has errors,” use the debugging steps in the troubleshooting section below

The sitemaps.org XML protocol defines the accepted format rules your file must follow before Google will process it. SEOLEVELUP, LLC Website Design SEO Company handles this entire process for clients who prefer a hands-off setup.


Table of Contents

What do you need before submitting a sitemap?

Three things will block you before you even reach the submission screen: no verified property, an inaccessible sitemap file, and a mismatched domain/protocol. Fix these first and the rest of the process moves quickly.

Ownership verification. You must be a verified owner of the Search Console property, not just a delegated user with restricted access. If you haven’t verified yet, the Sitemaps report won’t accept your submission.

Publicly reachable sitemap. The file must load without a login prompt, a redirect loop, or a 404. Googlebot needs to fetch it the same way any anonymous visitor would. Authentication walls, staging-environment restrictions, and firewall rules that block crawlers all cause immediate fetch failures.

Correct canonical domain and protocol. Know exactly which version of your domain you’re submitting under: https:// vs. http://, www vs. non-www. A sitemap submitted to the wrong property variant will fail or show no data.

Accepted format. Google supports XML sitemaps, sitemap index files, RSS/Atom feeds, and plain text URL lists. The file must follow the sitemaps.org specification to pass processing.

Pro Tip: Open your sitemap URL in a private browser window before you submit. If it loads cleanly with no redirect or login wall, run a Live URL Inspection in Search Console on that same URL and confirm the Page fetch status reads “Successful.” A failed fetch there predicts a failed submission.


How do you verify site ownership in Google Search Console?

Verification is the gate. You cannot submit a sitemap to Google without it, and choosing the wrong property type is one of the most common reasons submissions fail silently.

Domain property vs. URL-prefix property

A Domain property covers your entire domain, including all subdomains (www, m, blog) and both http and https protocols. It requires a DNS TXT record added at your domain registrar. A URL-prefix property covers only a single URL prefix, such as https://www.yourdomain.com/. It supports multiple verification methods: uploading an HTML file, adding a meta tag to your homepage, or connecting through Google Analytics or Google Tag Manager.

The practical difference matters for sitemap submission. Common mistakes include submitting to the wrong property variant, such as submitting to the http:// property when your site runs on https://, which produces “Couldn’t fetch” errors even when the sitemap file itself is fine.

Steps to verify a Domain property

  1. Open Google Search Console and click Add property.
  2. Select Domain and enter your root domain (e.g., yourdomain.com, no protocol prefix).
  3. Copy the TXT record value Google provides.
  4. Log in to your domain registrar (GoDaddy, Namecheap, Cloudflare, etc.) and add the TXT record to your DNS settings.
  5. Return to Search Console and click Verify. DNS propagation can take a few minutes to a few hours.

Steps to verify a URL-prefix property

  1. Click Add property, select URL-prefix, and enter the full URL including protocol (e.g., https://www.yourdomain.com/).
  2. Choose a verification method. The HTML file upload is the most reliable: download the file Google provides and upload it to your site’s root directory so it’s accessible at https://www.yourdomain.com/googleXXXXXXXX.html.
  3. Alternatively, paste the meta tag Google gives you into the <head> section of your homepage before the <body> tag.
  4. Click Verify.

Pro Tip: Choose the Domain property whenever you control DNS. It covers every protocol and subdomain variant under one property, so you never have to wonder which version of your site a sitemap submission belongs to.


How do you create or find your sitemap?

Before you can submit, you need the exact URL of a valid sitemap file. Where that file comes from depends on how your site is built.

CMS-generated sitemaps

Most modern CMS platforms generate sitemaps automatically.

  • Wix — and Squarespace both auto-generate and manage sitemaps for you. On these platforms, Google may already be discovering your sitemap without any manual action on your part. Check yourdomain.com/sitemap.xml first.

Manual XML creation

If you’re running a custom-built site, you can create a sitemap manually. A minimal valid XML entry looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.yourdomain.com/page/</loc>
    <lastmod>2026-01-15</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Place the file at your site’s root directory so it’s accessible at https://yourdomain.com/sitemap.xml. The sitemaps.org XML protocol defines every allowed tag and attribute.

Sitemap creation methods compared

Method How to create Where to host Submission method Trade-offs
CMS plugin (WordPress/Yoast) Auto-generated on plugin activation Site root, managed by plugin Search Console UI or robots.txt Easiest; updates automatically with new content
Platform-managed (Wix, Squarespace) Auto-generated by platform Platform servers Search Console UI No control over file structure; may already be submitted
Manual XML Write or export by hand Site root (recommended) Search Console UI or robots.txt Full control; requires manual updates
Third-party generator Online tool exports the file Your server or CDN Full URL in Search Console UI Useful for static sites; cross-domain hosting requires full URL submission

If your sitemap is hosted on a CDN or external domain, submit the full URL in Search Console. The robots.txt Sitemap directive won’t work for cross-domain discovery.

Pro Tip: After creating or locating your sitemap, paste its URL into a validator that checks against the sitemaps.org specification before submitting. An invalid XML structure will cause a processing error in Search Console even if the file loads correctly in a browser.


How to submit a sitemap in Google Search Console

This is the core of the process. The Sitemaps report in Search Console is where you submit, monitor, and troubleshoot your sitemap.

Step-by-step submission

  1. Go to search.google.com/search-console and sign in with the Google account that has verified owner access.
  2. Select the correct property from the property selector in the top-left corner. Double-check that the protocol and subdomain match your sitemap’s URL.
  3. In the left navigation, click Indexing, then click Sitemaps.
  4. In the “Add a new sitemap” field at the top of the report, enter your sitemap URL. For a URL-prefix property, you can enter just the path (e.g., sitemap.xml). For a Domain property, enter the full URL (e.g., https://www.yourdomain.com/sitemap.xml).
  5. Click Submit.

Google will attempt to fetch the file immediately. The submission process typically completes in about three minutes, though full processing of the URLs inside the sitemap takes longer.

What you’ll see in the Sitemaps report

After submission, your sitemap appears in the “Submitted sitemaps” list with the following columns:

  • Type: — Sitemap, Sitemap index, or RSS/Atom

A “Success” status means Google fetched and processed the file, not that every URL inside it has been indexed. Submitting a sitemap is a hint to Google, not a guarantee of crawling or indexing. Search Console’s real value here is visibility: you can see when Googlebot last accessed the file and whether any processing errors occurred.


Other ways to notify Google about your sitemap

If you don’t have verified owner access to Search Console, or you want Google’s crawler to discover your sitemap automatically, two alternatives exist.

The robots.txt Sitemap directive

Add this line anywhere in your root robots.txt file:

Sitemap: https://www.yourdomain.com/sitemap.xml

You can list multiple sitemaps with multiple Sitemap: lines. Google discovers this directive when it next crawls your robots.txt file, so discovery is not immediate the way a Search Console submission is. This method is appropriate when:

  • You lack owner-level access to Search Console
  • You want crawlers other than Google (Bing, DuckDuckGo) to find the sitemap automatically
  • You’re managing a large number of sites and want a passive discovery mechanism

Note that the robots.txt method won’t work for sitemaps hosted on a different domain. Cross-domain sitemaps require direct submission through the Search Console UI.

The Search Console API

For developers or agencies managing multiple sites, the Search Console API accepts programmatic sitemap submissions via an authorized PUT request to the /sitemaps/feedpath endpoint. The required OAuth scope is https://www.googleapis.com/auth/webmasters. This approach suits automated workflows where sitemap URLs change with deployments, or where you need to submit sitemaps across dozens of properties without manual UI work.


How do you read the Sitemaps report and fix errors?

The Sitemaps report gives you four possible statuses, and each one points to a different fix.

Status meanings

Status What it means First action
Success File fetched and processed without errors Monitor URL counts; no action needed
Has errors File fetched but some URLs inside it have issues Click the sitemap to see error details
Couldn’t fetch Googlebot couldn’t retrieve the file Check accessibility, robots.txt, and server response
Pending Fetch queued but not yet attempted Wait; resubmit if status doesn’t change after a day

Common errors and how to fix them

  • Unsupported format: — The XML structure doesn’t match the sitemaps.org specification. Validate the file and correct any malformed tags.

Debugging checklist

  1. Paste the sitemap URL into a private browser window. If it doesn’t load cleanly, the problem is server-side.
  2. Run a Live URL Inspection in Search Console on the sitemap URL. Confirm “Page fetch: Successful.”
  3. Check your robots.txt at yourdomain.com/robots.txt for any rules that block the sitemap path or Googlebot broadly.
  4. If you’re using Cloudflare or another WAF, verify that bot-protection rules aren’t blocking Googlebot’s user agent.
  5. Fix any invalid URL entries inside the sitemap file itself.
  6. Delete the sitemap in the Sitemaps report and resubmit the corrected version.

Sitemap best practices and technical limits

Submitting a sitemap is only as useful as the file itself. A poorly structured sitemap can waste crawl budget and send Google mixed signals about your site’s priorities.

What to include:

  • Canonical URLs only. If a page has a canonical tag pointing elsewhere, don’t list the non-canonical version.
  • Absolute URLs with the correct protocol and subdomain (e.g., https://www.yourdomain.com/page/, not /page/).
  • Pages you actually want indexed: published, publicly accessible content.

What to exclude:

  • Pages behind authentication or paywalls
  • Duplicate or thin content pages
  • URLs with noindex directives
  • Redirect chains or 404 pages

Technical limits and format rules:

  • Follow the sitemaps.org XML protocol for all format requirements.
  • For large sites, use a sitemap index file that references multiple individual sitemaps. Both sitemap index files and multiple Sitemap: lines in robots.txt let Google find all your sitemap files.
  • Gzip compression is supported and reduces file size for large sitemaps.
  • Monitor the “Last read” date in the Sitemaps report. If Google hasn’t re-fetched your sitemap in weeks, check for server or accessibility issues.

Pro Tip: Use lastmod only when the page content genuinely changed. Setting every URL to today’s date signals nothing useful to Google and can reduce the credibility of your lastmod data over time.


When should you submit a sitemap, and how long does indexing take?

Not every site needs to submit a sitemap manually, but certain situations make it worth doing right away.

Submit when:

  • You’re launching a new site that has no inbound links yet
  • You’ve completed a major redesign or domain migration
  • You’ve changed your canonical URL patterns (e.g., adding or removing www)
  • You’ve published a large batch of new pages that you want discovered quickly
  • You’re troubleshooting indexing gaps and want visibility into crawl behavior

Timeline expectations:

  • Fetch attempt: seconds to a few minutes after submission
  • Processing (URL count update in the report): minutes to a few hours
  • Crawling of listed URLs: days to a few weeks, depending on your site’s authority and crawl budget
  • Indexing of crawled pages: additional days to weeks; submitting a sitemap is a hint, not a guarantee that every URL will be crawled or indexed

You don’t need to resubmit your sitemap every time you publish new content. Google refetches sitemaps on its own schedule. Resubmit only when the sitemap URL itself changes, when you’ve fixed errors that caused a failed fetch, or when you want to prompt a fresh fetch after a major content update. For a deeper look at how search engine indexing works beyond sitemaps, the relationship between crawl budget and site authority matters more than submission frequency.


When should you submit a sitemap, and how long does indexing take? — overview diagram

Programmatic sitemap management with the Search Console API

For developers managing multiple properties or building automated deployment workflows, the Search Console API handles sitemap submissions without manual UI work.

Key technical details:

  • Endpoint: PUT https://www.googleapis.com/webmasters/v3/sites/{siteUrl}/sitemaps/{feedpath}
  • Required OAuth scope: https://www.googleapis.com/auth/webmasters
  • Authentication: OAuth 2.0 with credentials tied to a verified owner of the property

When the API makes sense:

  • CI/CD pipelines where the sitemap URL changes with each deployment
  • Agencies managing sitemap submissions across dozens of client properties
  • CMS-driven workflows that generate new sitemaps on a schedule and need automatic resubmission

Caveats to build around:

  • The API enforces the same ownership verification requirement as the UI. If the authenticating account isn’t a verified owner, the request returns a permission error.
  • Fetch failures, blocked URLs, and format errors behave identically to UI submissions. Build error handling that checks the response and logs failures.
  • Test the sitemap URL’s accessibility before triggering the API call, just as you would before a manual submission.

Pro Tip: Store your OAuth credentials in environment variables, not in your codebase. Search Console API access grants broad property management permissions, and exposed credentials can allow unauthorized changes to your Search Console data.


Key Takeaways

Submitting a sitemap to Google requires a verified Search Console property, a publicly accessible sitemap file in an accepted format, and a correctly matched domain and protocol before the submission will succeed.

Point Details
Verify ownership first You must be a verified owner in Search Console before the Sitemaps report accepts any submission.
Match domain and protocol Submit to the property that matches your sitemap’s exact URL (https vs. http, www vs. non-www) to avoid fetch errors.
Submission is a hint Google fetches the file immediately but does not guarantee crawling or indexing of every listed URL.
Fix errors before resubmitting Delete the failed sitemap, correct the underlying issue (accessibility, format, robots.txt), then resubmit.
SEOLEVELUP handles it for you SEOLEVELUP, LLC Website Design SEO Company manages verification, sitemap generation, and Search Console troubleshooting for clients who prefer hands-off implementation.

Why sitemap submission is more about visibility than speed

Most site owners treat sitemap submission as a one-time task that makes Google index their pages faster. That framing misses the real value. The submission itself takes three minutes. What you get in return is a persistent window into Googlebot’s behavior: when it last fetched your file, how many URLs it found, and which ones it couldn’t process. That data is worth more than the submission event itself.

The verification step trips up more people than the submission does. Choosing a URL-prefix property when you should have chosen a Domain property, or submitting to the http:// variant when your site runs on https://, produces errors that look like server problems but are actually configuration mismatches. The fix is always the same: match the property to the canonical version of your domain, and use a Domain property when you have DNS access.

One field observation worth noting: sites that monitor their Sitemaps report regularly, specifically the “Last read” date and the URL count over time, catch crawl issues weeks before they show up as ranking drops. A sitemap that hasn’t been re-fetched in 30 days, or one where the discovered URL count suddenly drops, usually signals a server configuration change, a robots.txt edit, or a WAF rule that went unnoticed. The sitemap report doesn’t fix those problems, but it surfaces them early enough to act.


Why sitemap submission is more about visibility than speed — overview diagram

SEOLEVELUP handles sitemap setup, verification, and Search Console management

Getting the sitemap submitted is one step. Keeping Search Console clean, the sitemap current, and the indexing healthy over time is where most site owners fall behind.

SEOLEVELUP, LLC Website Design SEO Company

SEOLEVELUP, LLC Website Design SEO Company builds sites with sitemap-ready architecture from day one, handles Google Search Console verification, and manages ongoing crawl health so you’re not checking “Last read” dates manually every month. For businesses that have already built a site and just need the technical layer sorted, the team handles sitemap generation, robots.txt configuration, property verification, and error resolution as part of a broader SEO engagement. If your site has indexing gaps, fetch errors, or a Search Console property that’s never been properly configured, a custom website and technical SEO audit is the fastest way to identify what’s blocking Google from seeing your full site. For ongoing Search Console monitoring and local search visibility, managed local SEO services keep your sitemap, indexing, and rankings under active oversight. Call (224) 600-4353 or request a free SEO audit at seolevelup.com.


Useful sources and official references

NewerHow to Track Website ROI After Launch: A Practical GuideOlderWebsite Launch Checklist Guide: Pre-Launch to Post-Launch

Want this applied to your site?

Reading is FREE. So is the audit. We will show you where you rank on Google, Maps and AI search, and what to fix first.

Or call (224) 600-4353

SEOLEVELUP, LLC. Website Design SEO Company
★★★★★

5.0 on Google. 1S183 Summit Ave, Suite D, Oakbrook Terrace, IL 60181. Open 7 days, 7am to 11pm.

☎ Call NowFREE Audit
FREE SEO + AI Visibility Audit
0
Would love your thoughts, please comment.x
()
x