How to Submit a Sitemap to Google in 4 Easy Steps

Last updated: November 2026.

Submitting a sitemap to Google takes four steps in Search Console: verify your site, find your sitemap URL, open Indexing then Sitemaps, and submit it. DigiFix walks Melbourne businesses through the same four steps below, plus the platform URLs and the error messages that stop a sitemap being read.

What is an XML sitemap?

An XML sitemap is a file that lists the URLs on your site, plus optional detail about when each one last changed. It is a discovery aid: Google can find pages by following links, and a sitemap simply tells it which URLs exist so it does not have to guess.

Google supports XML, RSS and plain text sitemaps, plus specialised formats for images, video and news. A sitemap is not a ranking factor and submitting one does not guarantee indexing. What it does is make a large, new or poorly linked site easier to crawl, which is why the Search Console guidance recommends them for big sites and treats them as optional for a small, well-linked one.

The file lives at a predictable address. On this site, for example, digifix.com.au/sitemap_index.xml returns a sitemap index, which points to the sitemaps underneath it. An index file is just a sitemap of sitemaps, used when a site has more URLs than one file is allowed to hold.

Do you actually need a sitemap?

Google’s own position is that a sitemap helps most when a site is large, new, or light on internal links, and matters less when a site is small and every page is two clicks from the home page. That is worth knowing before you spend a week on one.

You should have one if any of these apply:

• You have a lot of pages. A site of 500 or more URLs benefits, because crawlers will not discover every page by following links alone.
• Your site is new. Nothing links to it yet, so a sitemap is one of the few reliable signals of what exists.
• Your pages are poorly linked. Orphan pages, paginated archives and isolated landing pages are all easy to miss.
• You publish often. A news or blog site wants new URLs found within hours, not weeks.
• You have rich media. Image, video and news sitemaps carry metadata that a plain URL list cannot.

If your site has 40 pages, all linked from the menu, a sitemap will not change much. Submit it anyway if one is already generated for you, because it costs nothing and occasionally catches a page your menu does not.

How do you submit a sitemap to Google?

Everything happens in Search Console, and the whole job takes about ten minutes once your property is verified. If you have not set up Search Console yet, our Search Console guide covers the setup, and the enterprise Search Console guide covers running it across many properties and users.

Step 1: verify your site in Search Console

Open Search Console and add your property. A domain property covers every subdomain and both protocols, and needs a DNS record. A URL prefix property covers one exact address and can be verified with an HTML tag, an HTML file or a DNS record. Choose domain if you can edit DNS, because it survives a change of host and catches www and non-www traffic in one place.

Step 2: find your sitemap URL

Most platforms generate one automatically, and you rarely need to build it by hand. Try the platform’s documented address first, then check robots.txt, which often names the sitemap in a Sitemap line. The table further down lists the address for each platform.

Step 3: open Indexing, then Sitemaps

In the left hand menu, open Indexing and choose Sitemaps. Google’s Sitemaps report help describes the same route. The report lists every sitemap already submitted, with the status of the last fetch for each one.

Step 4: submit and check the status

Type the sitemap path into the Add a new sitemap box and click Submit. Google fetches it immediately, though crawling the URLs inside can take longer. Then wait and read the status: Success means it was fetched and read cleanly, and anything else needs the fixes in the error section below.

Where do you find your sitemap on each platform?

These are the addresses each platform publishes, taken from the vendor documentation rather than guessed. Replace the example domain with your own.

Two platform quirks are worth knowing. Wix requires a Premium plan and a connected domain before it can link your site to Search Console, so a free Wix site’s sitemap will not be submitted for you. Squarespace assigns its own priority values, at 1.00 for the home page, 0.75 for other pages and 0.50 for blog posts, and Google ignores all of them, so do not read anything into the numbers.

Site structure affects how much a sitemap can do. If your category pages are buried four clicks deep, fixing the navigation helps more than resubmitting the file. Our site architecture guide covers that, and URL slug structure covers the addresses themselves.

Which other tools accept a sitemap?

Google is not the only destination, and it is no longer the only engine worth telling. These are the routes that still work in 2026.

Robots.txt

Add a line to the top of robots.txt naming the sitemap, in the form Sitemap: followed by the full URL. This is the lightest option and it covers every crawler that reads robots.txt, without any per-engine submission. You can do this alongside Search Console rather than instead of it.

Search Console API

For agencies managing many properties, the Search Console API accepts sitemap submissions programmatically, which is how large sites and multi-site groups keep dozens of properties in sync without a person clicking through each one.

Bing Webmaster Tools and IndexNow

Bing Webmaster Tools accepts sitemaps in the same way Search Console does. Beyond that, IndexNow pushes individual URLs to participating engines as they change, and it is already built into several content platforms and SEO plugins, so you may be using it without knowing. For a site that publishes daily, IndexNow is often faster than waiting for a crawl.

Google retired its sitemap ping endpoint, the old trick of hitting a URL to announce a sitemap. Google’s own announcement in June 2023 said the endpoint was being deprecated for ineffectiveness and association with spam, and that requests to it would return a 404. If a tutorial still tells you to ping Google, it is out of date.

What do sitemap status errors mean?

Search Console shows one status per sitemap, describing the most recent fetch. The four states below cover almost every case, along with the usual cause and the fix.

Two failures are worth calling out because they look like something else. A site behind a firewall that challenges unknown clients will serve a 403 to Googlebot, which reads as Couldn’t fetch even though the URL works in your browser. And a sitemap listing noindexed or redirected URLs will be read successfully while most of its contents are quietly discarded, so check what is inside the file, not just whether it was fetched.

If the site is large enough that sitemap errors keep returning, the problem is usually structural rather than cosmetic. Our technical SEO guide covers the crawl and index issues that sit behind it, and an SEO audit is the faster route when you cannot see the cause.

What belongs in a sitemap?

A sitemap should list canonical, indexable, 200 status URLs. That sounds obvious, and it is the rule most sites break. Anything you would not want a stranger to land on probably does not belong.

What to include

• Canonical URLs only, so one page appears once, in the form you want indexed.
• Pages that return HTTP 200 and are not blocked by a noindex tag.
• Blog posts, service pages, location pages and case studies, which are the pages that earn traffic.
• An accurate lastmod date per URL, since that is the one tag Google says it uses.
• Image, video or news sitemaps where you have that content and want the extra metadata.

What to leave out

• Redirects, 404s and 5xx pages, which waste crawl budget and clutter the report.
• Noindexed pages, including most tag archives, internal search results and thank you pages.
• Duplicate URLs that differ only by tracking parameters, sorting or session IDs.
• Admin, cart and checkout URLs, which are no value to a search crawler.
• Every URL on the site just because it exists. A short accurate file beats a long noisy one.

As for HTML sitemaps, the old advice that they are pointless for SEO oversimplifies. They do not replace an XML sitemap and Google does not treat them as one, but a well-built HTML sitemap helps real visitors find pages, spreads internal links, and is a useful fallback for a site with weak navigation. Build the XML file first, then treat the HTML one as a usability feature.

What does the fix look like in practice?

A Melbourne ecommerce client came to us with 1,900 product URLs indexed and 4,100 in the sitemap. The sitemap status read Success, which is why nobody had looked at it for a year. The file was listing variant URLs, filtered category pages and out-of-stock products that redirected to their parent category.

In order: we rebuilt the sitemap so it carried only canonical product and category URLs, added accurate lastmod values from the CMS, set the out-of-stock rules to stop emitting redirects, then resubmitted. Over the following eight weeks the discovered-URL count fell to 2,050, the indexed count rose, and crawl requests dropped. Nothing about the site’s content changed. The crawl budget had simply been going to pages that could never rank.

That is the pattern to expect. A sitemap cleanup rarely produces a dramatic traffic spike on its own. It stops waste, which shows up later as faster indexing of the pages you actually care about.

What do people ask about submitting a sitemap?

How long does it take Google to read a new sitemap?

Google usually fetches the file within minutes of submission, but reading it is not the same as indexing its URLs. A small site can see new pages indexed within days, while a large site or a low-authority domain can wait weeks. The Sitemaps report shows how many URLs were discovered, and the Pages report shows what was actually indexed, which is the number that matters.

Do I need to resubmit a sitemap after changing pages?

No, provided the same sitemap URL keeps serving an updated file. Google refetches submitted sitemaps periodically, and a correct lastmod value encourages a quicker visit. Resubmit only if the sitemap address itself changes, or if the file has been unreadable and you want to trigger a fresh fetch after fixing it.

Why does Search Console say my sitemap could not be fetched?

The most common causes are a mistyped URL, a redirect, a WAF or firewall challenge blocking Googlebot, or a server error on that path. Open the exact sitemap URL in a private browser window and confirm it returns 200 with XML content. If it does and Search Console still fails, check whether your host is challenging the Googlebot user agent specifically.

Can a sitemap hurt my rankings?

Not directly, but a badly built one wastes crawl budget that could have gone to pages that can rank. Listing redirected, noindexed or duplicate URLs means Google spends its visits on dead ends. There is no penalty for having a sitemap, and no ranking benefit from submitting one either: it is a discovery tool, nothing more.

Should I submit my sitemap to Bing as well?

Yes, and it takes minutes. Bing Webmaster Tools accepts sitemaps the same way Search Console does, and you can import your Search Console properties into it directly. For sites that publish frequently, enabling IndexNow as well pushes new URLs to participating engines as they change, rather than waiting for the next crawl.

How many URLs can one sitemap hold?

Up to 50,000 URLs or 50MB uncompressed, whichever comes first, per Google’s own documentation. Larger sites split the URLs across several sitemaps and submit an index file that lists them, which is what most SEO plugins do automatically. Compressed .gz files are allowed, and the 50MB limit applies to the uncompressed size.