How to Submit a Sitemap to Google Search Console

Submitting a sitemap to Google takes under 60 seconds. Open Google Search Console, select your property, go to Indexing > Sitemaps, type your sitemap URL into the “Add a new sitemap” field, and hit Submit. Google fetches the sitemap immediately and begins processing the URLs. But getting the submission right is only one part of the process. The sitemap itself needs to be correctly formatted, contain the right URLs, exclude the wrong ones, and stay updated as your site changes. Most indexing problems we diagnose at ScaleGrowth.Digital trace back to sitemap issues: outdated URLs, missing pages, bloated files with noindexed content, or sitemaps that haven’t been updated in months.

“A sitemap isn’t a set-it-and-forget-it file. It’s a live document that tells Google what you consider important on your site. Every URL in your sitemap is a crawl request. If you’re sending Google to 404 pages, redirect chains, or noindexed content, you’re wasting crawl budget and signaling that your site isn’t well-maintained.”

Hardik Shah, Founder of ScaleGrowth.Digital

This guide covers everything from basic submission to advanced sitemap strategies for large sites. Whether you have a 20-page WordPress site or a 200,000-page e-commerce store, the principles below apply.

Definition: A sitemap is an XML file that lists the URLs on your website you want search engines to crawl and index. It includes metadata like the last modification date, change frequency, and priority for each URL.

Google discovers pages in two ways: by following links from pages it already knows about, and by reading sitemaps you submit directly. For well-linked sites with strong internal architecture, Google can find most pages through crawling alone. But sitemaps become critical in four scenarios:

• New sites with few or no inbound links. Google needs a starting point.
• Large sites with 10,000+ pages. Without a sitemap, deeper pages may never get crawled.
• Sites with isolated content. Pages not linked from your main navigation (landing pages, campaign pages, archived content) won’t be discovered through crawling.
• Sites with rich media. Image and video content benefits from specialized sitemap extensions that provide metadata Google can’t extract from HTML alone.

According to Google’s official documentation, sitemaps are particularly useful for sites that are “really large,” “have a large archive of content pages that are isolated or not well linked to each other,” or “are new and have few external links” (Source: Google Search Central, 2026).

Most CMS platforms generate sitemaps automatically. If you’re on WordPress, plugins like Yoast SEO, Rank Math, or All in One SEO create and maintain your sitemap without manual work. Your sitemap URL is typically yoursite.com/sitemap_index.xml or yoursite.com/sitemap.xml. For custom-built sites or when you need manual control, here’s the standard XML sitemap structure:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/page-1/</loc>
    <lastmod>2026-03-15</lastmod>
  </url>
  <url>
    <loc>https://example.com/page-2/</loc>
    <lastmod>2026-02-20</lastmod>
  </url>
</urlset>

Rules for what to include:

• Only canonical, indexable URLs (200 status code, no noindex tag)
• Use absolute URLs with the correct protocol (https, not http)
• Match the canonical URL exactly (if your canonical is https://example.com/page/ with a trailing slash, the sitemap URL must have the trailing slash too)
• UTF-8 encoding only

Rules for what to exclude:

• URLs returning 3xx, 4xx, or 5xx status codes
• Pages with noindex meta tags or X-Robots-Tag headers
• Non-canonical URL versions (parameter variations, pagination pages that are canonicalized)
• Utility pages (login, cart, checkout, admin) that shouldn’t be indexed

The lastmod tag is optional but valuable. Google uses it to prioritize recrawling pages that have genuinely changed. Only update lastmod when the page content actually changes. Fake lastmod dates (updating daily when nothing changed) erode trust and can cause Google to ignore the tag entirely.

After submitting, Google Search Console shows one of four status messages for your sitemap:

Status	What It Means	Action Required
Success	Sitemap was fetched and parsed without errors	None. Monitor the Pages report for indexing progress.
Has errors	Sitemap was fetched but contains format issues	Click the sitemap to see specific errors. Fix and resubmit.
Couldn’t fetch	Google couldn’t access the sitemap URL	Check the URL is correct, the file exists, and it’s not blocked by robots.txt.
Pending	Sitemap was submitted but not yet processed	Wait 24-48 hours. If still pending, resubmit.

Cross-check with the Pages report. The Sitemaps report tells you Google received the file. The Pages report (Indexing > Pages) tells you what happened to the URLs inside it. Look for the “Indexed, not submitted in sitemap” and “Submitted and indexed” categories to understand the gap between what you submitted and what Google actually indexed. A healthy site typically has 85-95% of its sitemap URLs indexed. If that number is below 70%, you likely have quality or technical issues that need attention.

A single sitemap file is limited to 50,000 URLs or 50MB uncompressed (Source: sitemaps.org protocol specification). For sites that exceed these limits, use a sitemap index file that references multiple individual sitemaps.

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://example.com/sitemap-products.xml</loc>
    <lastmod>2026-03-15</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-blog.xml</loc>
    <lastmod>2026-03-10</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://example.com/sitemap-categories.xml</loc>
    <lastmod>2026-02-28</lastmod>
  </sitemap>
</sitemapindex>

Segment your sitemaps logically. Don’t just split alphabetically. Group URLs by content type: products, blog posts, categories, location pages. This lets Google process each segment independently and makes debugging easier when indexing issues arise. For e-commerce sites with frequent inventory changes, consider updating product sitemaps daily while keeping static sitemaps (about pages, policies) on a monthly cadence. The lastmod date on each sitemap entry in the index file tells Google which segments have changed and need recrawling. Gzip compression is supported and recommended for large sitemaps. A 50MB uncompressed sitemap compresses to roughly 2-5MB, reducing server bandwidth and speeding up Google’s fetch time.

Mistake 1: Including noindexed URLs in the sitemap. If a page has a noindex tag, it shouldn’t be in your sitemap. You’re asking Google to crawl a page you’ve explicitly told it not to index. This sends contradictory signals. The fix: add a sitemap generation rule that excludes any page with noindex. Mistake 2: Never updating the sitemap after launch. We’ve audited sites where the sitemap was generated during the initial launch and never touched again. Three years later, 40% of the URLs returned 404. Google was spending crawl budget on dead pages every single visit. Set up automatic sitemap regeneration through your CMS or build a weekly cron job. Mistake 3: Blocking the sitemap in robots.txt. This sounds obvious, but we see it 2-3 times per year. A robots.txt rule like Disallow: /sitemap or an overly broad Disallow: /*.xml can block Google from reading your sitemap. Always test your robots.txt rules against your sitemap URL. Mistake 4: Submitting one massive sitemap instead of a sitemap index. A single sitemap with 45,000 URLs is technically valid (under the 50,000 limit), but it’s harder to debug, slower to process, and gives you no segmentation. Break it into logical groups of 5,000-10,000 URLs each, referenced from a sitemap index. This mirrors how Google processes them internally. Mistake 5: Ignoring sitemap errors in Search Console. Google reports sitemap errors explicitly. If your Sitemaps report shows “Has errors” or “Couldn’t fetch,” that needs immediate attention. Yet we’ve seen sites go months with broken sitemaps because nobody checks the report. Add a monthly calendar reminder or set up Search Console email notifications.