How to submit a sitemap to Google: the two methods that work, and how to read the result
Build a valid XML sitemap, submit it in Search Console, declare it in robots.txt, and read the report properly.
Published by AI Knows Us · Updated 13 October 2026
Google supports two methods for submitting a sitemap, and both take minutes. Submit the sitemap URL in the Sitemaps report of Google Search Console, and add a Sitemap: line to your robots.txt file so every crawler finds it without being told. Those are the methods set out in Google's own sitemap documentation. The ping endpoint that older guides tell you to call is gone: Google announced on the Search Central blog in June 2023 that the sitemaps ping endpoint was being retired because it was being used almost entirely for spam.
Submission is the easy part. What decides whether the sitemap does anything is what is inside it.
Step by step, in Search Console
- Confirm the sitemap loads. Open the URL in a browser, usually
https://example.com/sitemap.xml, and check it returns the file rather than an error page. - Open Search Console and select the property that matches the site, including the protocol and the www choice. A sitemap submitted to the wrong property reports nothing.
- Go to Sitemaps in the left navigation, under Indexing.
- Enter the path, for example
sitemap.xml, and submit. - Come back the next day. The report moves from Pending to Success and shows the number of discovered URLs.
Google's reference for that report is its Sitemaps report help page, and the Search Console guide covers what the surrounding numbers mean.
The robots.txt line, which is worth adding either way
One line, at the top or the bottom of the file, with the full absolute URL:
Sitemap: https://example.com/sitemap.xmlIt is read by every crawler that fetches robots.txt, not only Google, which makes it the highest value line in the file. For the rest of that file, see how to write a robots.txt.
What a valid sitemap looks like
<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
<url>
<loc>https://example.com/</loc>
<lastmod>2026-10-01</lastmod>
</url>
<url>
<loc>https://example.com/pricing</loc>
<lastmod>2026-09-18</lastmod>
</url>
</urlset>The rules that matter, from the sitemaps protocol published at sitemaps.org and Google's build a sitemap documentation:
- One file holds up to 50,000 URLs and 50MB uncompressed. Past that, split the file and list the parts in a sitemap index.
- Every URL is absolute, and on the same host as the sitemap.
lastmoduses a valid date format and reflects the date the page last changed in a way a reader would notice. Google uses the value where a site reports it accurately, so a file that stamps today's date on every page teaches it to ignore the field.- Google also accepts RSS and Atom feeds and a plain text file of one URL per line. XML is the format worth standardising on, because it carries
lastmod.
Only put pages in it that you want indexed
A sitemap is a statement that these URLs are your canonical, indexable pages. Mixed signals are the most common reason a sitemap gets submitted and nothing changes.
| Include | Leave out |
|---|---|
| URLs that return HTTP 200 | Redirects, 404s and soft 404s |
| The canonical version of each page | Parameter and duplicate variants |
| Pages with no noindex tag | Anything carrying noindex or blocked in robots.txt |
| Pages you would be happy to see in results | Thin tag archives, internal search pages, cart and account pages |
Generate the file dynamically so it stays current. WordPress produces one through its SEO plugin, Shopify, Wix and Squarespace produce one automatically, and most frameworks have a build step for it. A hand written file is the one that goes stale.
Reading the report
- Success with a URL count. The file parsed. Discovered URLs counts what the file contains, not what is indexed.
- Could not fetch. Usually the URL, a redirect on the sitemap itself, or a server rule blocking the request. Load it in a browser, then in a private window, then check the server logs.
- Has errors. Open the detail. Invalid dates, URLs on another host, and stray characters before the XML declaration account for most of them.
- Submitted, pages still not indexed. That is a quality and crawl question rather than a sitemap question. Run the URL Inspection tool on a specific page to see what Google did with it, and read how search engines work for the sequence a page has to clear.
A sitemap tells Google which URLs exist and when they changed, so it is a discovery mechanism. Pair it with internal links from pages that already get crawled, which is how a new page gets picked up quickly in practice. Where crawling itself is the bottleneck on a large site, crawl budget optimization is the next step.
Other engines, in one paragraph
The same file serves everybody. Bing Webmaster Tools has its own sitemap submission and imports verified properties from Search Console. IndexNow, published at indexnow.org, is an open protocol for telling participating engines the moment a URL is added or updated, and most major content platforms have a plugin for it. Google's Indexing API is limited to job posting and livestream pages, so for everything else the sitemap and internal links are the route.
This page covers submitting and validating a sitemap for Google. For blocking and allowing crawlers, see the robots.txt guide linked above.
submit a sitemap to Google: what is still unclear
How long does Google take after a sitemap is submitted?
The report usually turns to Success within a day or two. Crawling of the URLs inside it is spread over the following days and weeks, with important and frequently updated pages picked up first.
Do I need to resubmit the sitemap when I publish a page?
No. Submit the URL once. Keep the file generated automatically so new pages and fresh lastmod values appear in it, and Google refetches the file on its own schedule.
Can I submit more than one sitemap?
Yes. Submit several, or submit one sitemap index that lists them. Splitting by section, such as posts, products and pages, makes the report far easier to read, because coverage problems show up by section.
Where should the sitemap live?
At the root of the domain it describes, such as https://example.com/sitemap.xml. A sitemap covers URLs at or below its own location, so a file buried in a subfolder limits what it is allowed to list.
Does submitting a sitemap improve rankings?
It improves discovery, which is the step before everything else. Pages earn their positions on relevance, content and links, so get the sitemap correct and then move on to the work that moves positions.
Is a sitemap worth keeping on a small site?
Yes. It costs nothing, it gives you a Search Console report that tells you when the file or the server breaks, and it covers any page that internal links reach poorly.
Submitted is not the same as quoted
Search Console tells you the sitemap was read and how many URLs were indexed. A buyer then asks an assistant for a recommendation and gets an answer before they ever meet your site. Indexing opens the door, and what the assistant says is a separate event.
Close the loop. A week after the pages are indexed, ask the question they answer in ChatGPT, Gemini and Perplexity. AI Knows Us automates that second report, so indexing and mentions can be read side by side.