To submit a sitemap to Google in 2026, confirm the file loads at a public URL, open the Sitemaps report in Google Search Console, paste the sitemap URL into “Add a new sitemap,” click Submit, and add a Sitemap: line to your robots.txt as a second route. Google Search Central documents each of those steps, and the same documentation sets the hard limits: 50,000 URLs and 50MB uncompressed per file. The submission takes about a minute. Getting the file right takes longer, and Google states plainly that a sitemap “doesn’t guarantee that all the items in your sitemap will be crawled and indexed.”
Here is the method in full, with the limits, the platform shortcuts for WordPress, Yoast, Shopify, and Wix, and the errors that block most first submissions.
What is the exact process to submit a sitemap in Google Search Console?
Four steps, in this order: publish the file, test that Googlebot can reach it, paste the URL into the Sitemaps report, and read the status. Google Search Console Help lists them in that sequence, and you need owner permissions on the property to submit through the report.
1. Publish the sitemap at a public URL
Put the file on your own domain, ideally at the root, such as https://example.com/sitemap.xml. Google’s documentation says a sitemap only affects URLs in its own directory and below, so a file at /blog/sitemap.xml cannot cover /services/. Root placement covers the whole site. The name does not matter to Google. The file must be UTF-8 encoded, and every URL inside must be absolute, including protocol and host.
Want to know whether Google can see your best pages at all? Request a free AI visibility audit and we will check what is crawlable and what is missing.
2. Test that Googlebot can fetch it
Search Console Help tells you to confirm access with the URL Inspection tool before submitting. Paste the sitemap URL into the inspection bar at the top of Search Console and run a live test. A sitemap blocked by robots.txt, a login wall, or a server error will fail here, and it is far quicker to find that out before you submit than after.
3. Paste the URL into the Sitemaps report
In Search Console, open Indexing, then Sitemaps. Type the sitemap path into the “Add a new sitemap” box. If you verified a domain property, enter the full URL. Click Submit. Google Search Console Help says the sitemap should be fetched immediately. The report keeps a table of every sitemap you submitted, up to 1,000 entries.
4. Read the status
The report shows one of three statuses. Success means the sitemap was fetched and read without errors. Has errors means Google fetched it but hit parsing problems, and the URLs it could parse are still queued for crawling. Couldn’t fetch means Google could not retrieve the file, and Search Console Help says Google retries for several days before it stops trying. Crawling the listed URLs takes longer than reading the file, and the time depends on the size and activity of your site.
Should you also list the sitemap in robots.txt?
Yes, as a second route that costs one line. Google’s robots.txt documentation calls the Sitemap directive optional and allows zero or more per file, and the sitemaps.org protocol uses the same syntax. Google will find the line the next time it crawls your robots.txt file. Search Console remains the better route because it shows you fetch dates and processing errors, but robots.txt also reaches Bing and every other crawler that reads the file.
Add this anywhere in the file:
Sitemap: https://example.com/sitemap.xml
The URL must be fully qualified. Google’s documentation says it does not assume or check http, https, www, or non-www alternates, so a line that points to the wrong variant points to a file that may not exist. Google adds that you can list as many sitemap lines as you like. The robots.txt route matters for Bing Webmaster Tools too, and our guide to getting indexed on Bing covers the Microsoft side.
One route you should skip: the ping URL. On June 26, 2023, Google Search Central announced the sitemaps ping endpoint was deprecated and said requests to it would return a 404 error after six months. The post says the deprecation is complete, that the vast majority of unauthenticated submissions led to spam, and that you can still submit through robots.txt and Search Console. Old plugins that call the ping URL do no harm, but they do nothing useful either.
What limits and format rules must your sitemap meet?
Each sitemap file holds a maximum of 50,000 URLs and 50MB uncompressed, according to both Google Search Central and the sitemaps.org protocol. Exceed either and you must split the file. Google supports three formats: XML, RSS, mRSS and Atom 1.0, and plain text files with one URL per line. XML is the most versatile because it carries the extra metadata.
The limits and rules in one place:
| Rule | Requirement | Source |
|---|---|---|
| URLs per sitemap | 50,000 maximum | Google Search Central, sitemaps.org |
| File size | 50MB uncompressed maximum | Google Search Central, sitemaps.org |
| Sitemaps per index file | 50,000 maximum | Search Console Help, sitemaps.org |
| Encoding | UTF-8 | Google Search Central |
| URL form | Absolute, fully qualified | Google Search Central |
| Reserved characters | Escape &, ’, ”, >, < as entities | sitemaps.org |
| Compression | gzip allowed, size limit applies to uncompressed file | sitemaps.org |
| Required XML tag | <loc> inside each <url> | sitemaps.org |
For a large site, build a sitemap index: a file that lists other sitemaps. Submit the index once and Google discovers the children. A sitemap index accepts up to 50,000 sitemaps, and Google’s documentation says you can submit several sitemaps and index files.
Two details trip people up. First, the URLs in the file should be the canonical versions you want in results, not parameter variants or duplicates. If you are unsure which version that is, read our explainer on what a canonical tag is. Second, Google ignores the priority and changefreq values entirely, so you can stop tuning them.
Does lastmod matter, and what should you put in it?
Yes, if it is accurate. Google’s 2023 announcement says lastmod is now “useful in many cases” and that Google uses it as a signal for scheduling recrawls of URLs it already discovered. The conditions are strict. The date must be in a supported format, and it must consistently match reality. The post gives its own example: if a page changed seven years ago but the sitemap says it changed yesterday, Google will eventually stop believing you.
Google defines the target as the last significant modification: a change to the main text, structured data, or links. A footer copyright update or a sidebar tweak does not count. If your platform cannot tell you the real date for a page, such as an aggregated category page, Google says it is fine to omit lastmod for those URLs. Use it on all pages or only the ones you are confident about.
The practical rule is to let the CMS write lastmod from the real edit timestamp and never hand-edit it or set it to the current date on every build. Search Console reports lastmod format problems after you submit.
How do WordPress, Yoast, Shopify, and Wix handle sitemaps?
All four generate a sitemap without any plugin work, so on these platforms your job is to find the URL and submit it, not to build the file. Confirm each URL in a browser before you paste it into Search Console.
WordPress core. Since WordPress 5.5, core generates an index at /wp-sitemap.xml. The WordPress core team documents that each sitemap holds 2,000 entries by default, that the index can hold up to 50,000 sitemaps, and that WordPress adds a reference to robots.txt automatically. Setting Site Visibility to discourage search engines turns the feature off.
Yoast SEO. Yoast’s help documentation tells you to submit sitemap_index.xml, and to use the full URL if your Search Console property is a domain property. Yoast says it also pings search engines each time a post is updated, after you have submitted the sitemap manually to Google and Bing. Given Google’s deprecation of ping, treat that as a Bing-side convenience, not a Google shortcut. If you run both Yoast and core sitemaps, submit only one so you do not send duplicate files.
Shopify. Shopify’s help center says sitemap files are generated automatically at yourdomain.com/sitemap.xml and update when you add a product, collection, page, or blog post. The file links to separate sitemaps for products, collections, blogs, and pages. To submit, verify the domain, open Indexing then Sitemaps in Search Console, enter sitemap.xml, and click Submit. Stores with multiple domains need a separate submission for each.
Wix. Wix documents that every site has a sitemap at /sitemap.xml that updates automatically. If you connect Google Search Console through the Wix SEO Setup Checklist, Wix submits the sitemap for you, and no repeat submission is needed. That path requires a Premium plan and a connected domain. Manual submission still works.
How do you fix a sitemap Google will not accept?
Match the status to the cause. “Couldn’t fetch” points to access. Check that robots.txt does not block the sitemap path, that the URL returns a 200 status, and that the file is not behind a redirect chain or a login. Then resubmit. “Has errors” points to content. Open the report detail, read the error, and fix the flagged line: invalid dates, unescaped ampersands, relative URLs, or a size over the limit.
Then check what the sitemap contains, because a successful fetch does not mean a healthy file. Remove URLs that redirect, return errors, or carry a noindex tag. A sitemap is a list of pages you want indexed, and contradicting it with noindex sends Google mixed signals.
Do not remove a bad sitemap and assume the problem is gone. Search Console Help warns that removing a sitemap does not make Google forget the sitemap or the URLs in it. To stop Google visiting those URLs, use robots.txt rules or noindex directives instead.
Finally, set expectations. Google’s overview says you may not need a sitemap at all if your site has roughly 500 pages or fewer and Googlebot can reach every important page by following links from the home page. Sitemaps help most on large sites and new sites with few external links. If pages stay unindexed after a clean submission, the cause is usually crawl access or page quality, which we walk through in how to get Google to index your site.
For Bing and other engines that support IndexNow, there is a push option. The IndexNow documentation says you can submit up to 10,000 URLs per POST request and prove ownership with a key file of 8 to 128 characters. Google does not list itself as a participant there, so IndexNow does not replace Search Console.
FAQ
How do I submit a sitemap to Google Search Console?
Open Search Console, choose your property, go to Indexing then Sitemaps, paste the sitemap URL in the “Add a new sitemap” box, and click Submit. You need owner permissions. Google attempts to fetch the file immediately, and the report then shows Success, Has errors, or Couldn’t fetch. Crawling the listed URLs takes longer than reading the file.
How long does Google take to process a submitted sitemap?
Google tries to fetch the sitemap right away, but its documentation says crawling the URLs inside can take some time depending on the size and activity of your site. It gives no fixed number of days. If a fetch fails, Google retries for several days before stopping, so a Couldn’t fetch status deserves a fix and a resubmission.
Can I submit a sitemap to Google without Search Console?
Yes. Add a Sitemap: https://example.com/sitemap.xml line to your robots.txt file and Google finds it on the next robots.txt crawl. You can also use the Search Console API to submit programmatically. The old ping URL no longer works, since Google deprecated it in 2023 and requests to it now return a 404 error.
How big can a sitemap be?
Google and the sitemaps.org protocol both cap a single sitemap at 50,000 URLs and 50MB uncompressed. If you pass either limit, split the file and list the pieces in a sitemap index, which can point to up to 50,000 sitemaps. gzip compression is allowed, but the 50MB limit applies to the uncompressed size.
Do I need a sitemap if my site is small?
Often not. Google’s documentation says a site with about 500 pages or fewer, where Googlebot can find every important page through links from the home page, may not need one. A sitemap helps more on large sites, new sites with few external links, and sites heavy in video, images, or news. Submitting one still costs almost nothing.
Does submitting a sitemap guarantee my pages get indexed?
No. Google says submitting a sitemap is a hint and that it does not guarantee every listed URL will be crawled or indexed. The sitemap helps discovery. Whether a page is indexed depends on crawl access, duplication, and quality. Use the Page indexing report in Search Console to see why specific URLs were left out.
The short version
Publish one clean file, test it with URL Inspection, submit it in the Sitemaps report, and point to it from robots.txt. Keep every listed URL canonical and indexable, keep lastmod honest, and split anything over 50,000 URLs or 50MB. Then stop resubmitting: Google reads the file on its own schedule once it knows where it lives. If you want a second set of eyes on whether Google and the AI engines can find your priority pages, book your free audit and we will show you what we see.
Tagged