How to Submit a Sitemap to Google Search Console (Step-by-Step Guide)

· About

How to Submit a Sitemap to Google Search Console (Step-by-Step Guide)

A sitemap tells search engines which URLs exist on your site and, optionally, when they were last updated. Submitting one to Google Search Console (GSC) does not guarantee indexing, but it removes guesswork from discovery — especially on new sites, large catalogs, and pages with weak internal linking. This guide walks through creating, validating, and submitting a sitemap the right way.

What a Sitemap Does (and Does Not Do)

A sitemap is a structured list of URLs, usually in XML format. It helps Google:

  • Discover pages that are not well linked internally.
  • Understand which URLs you consider important.
  • Learn last-modified dates and change frequency (when provided).

It does not:

  • Force Google to index every listed URL.
  • Improve rankings directly.
  • Override robots.txt blocks or noindex directives.

Sitemap Formats

XML Sitemap (Most Common)

The standard format defined at sitemaps.org. A minimal example:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://www.example.com/</loc>
    <lastmod>2026-06-01T10:00:00Z</lastmod>
  </url>
  <url>
    <loc>https://www.example.com/about</loc>
    <lastmod>2026-05-15T08:30:00Z</lastmod>
  </url>
</urlset>

Sitemap Index

If you have more than 50,000 URLs or your sitemap file exceeds 50 MB uncompressed, split URLs into multiple sitemaps and reference them from a sitemap index file:

<?xml version="1.0" encoding="UTF-8"?>
<sitemapindex xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <sitemap>
    <loc>https://www.example.com/sitemap-posts.xml</loc>
    <lastmod>2026-06-01T10:00:00Z</lastmod>
  </sitemap>
  <sitemap>
    <loc>https://www.example.com/sitemap-pages.xml</loc>
    <lastmod>2026-06-01T10:00:00Z</lastmod>
  </sitemap>
</sitemapindex>

RSS/Atom Feeds (Blogger and CMS Platforms)

Platforms like Blogger automatically expose feeds at /feeds/posts/default. Google can use these as sitemap sources, but a dedicated XML sitemap at /sitemap.xml gives you more control over which URLs are included.

Creating Your Sitemap

Static Sites and Custom Builds

Generate sitemaps at build time using your framework's plugin (Next.js, Hugo, Jekyll, etc.) or a standalone script that walks your output directory.

WordPress

Plugins like Yoast SEO, Rank Math, and All in One SEO generate sitemaps automatically at /sitemap_index.xml.

Blogger

Blogger generates a basic sitemap at https://yourblog.blogspot.com/sitemap.xml (or your custom domain equivalent). It lists published post URLs. For AdSense and SEO readiness, ensure your custom domain is properly configured so the sitemap reflects production URLs, not the.blogspot.com addresses.

Validate Before Submitting

Common sitemap errors that cause Google to ignore entries:

  • URLs return 404, 301 to unrelated pages, or soft 404.
  • URLs blocked by robots.txt.
  • URLs with noindex meta tags (wasted crawl budget).
  • Non-canonical URLs that redirect elsewhere.
  • Invalid XML syntax (unescaped ampersands, missing closing tags).
  • HTTP URLs listed when HTTPS is the canonical version.

Use the Sitemaps report in GSC after submission to catch "Couldn't fetch" or "URL not allowed" errors.

How to Submit in Google Search Console

  1. Open Google Search Console.
  2. Select the correct property (Domain or URL-prefix).
  3. In the left sidebar, go to Indexing → Sitemaps.
  4. Under "Add a new sitemap," enter the path (e.g., sitemap.xml or sitemap_index.xml).
  5. Click Submit.

Google will show the submission date, last read date, and status (Success, Has errors, Couldn't fetch).

Also Reference in robots.txt

Add a Sitemap directive so other crawlers and Googlebot can find it without relying solely on GSC submission:

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

Place this at the top or bottom of your robots.txt file at the domain root.

Best Practices

  • Include only indexable URLs. Exclude admin pages, thank-you pages, paginated duplicates, and parameter-heavy filter URLs unless they are genuinely valuable landing pages.
  • Keep lastmod accurate. Update timestamps only when content actually changes. Fake daily updates erode trust.
  • Resubmit after major migrations. Domain changes, HTTPS switches, and CMS migrations warrant a fresh submission.
  • Monitor the report weekly. New errors often appear after template changes or plugin updates.
  • One sitemap per property is fine for small sites. Do not over-engineer sitemap architecture until you exceed a few hundred URLs.

Troubleshooting

"Couldn't fetch"

Check server availability, firewall rules, CDN caching, and whether the sitemap URL requires authentication.

"Sitemap is HTML"

Your server returned an HTML error page instead of XML. Verify the file exists and returns Content-Type: application/xml.

Submitted but URLs not indexed

Sitemap submission aids discovery, not indexing. Review content quality, internal links, and the Page indexing report for specific URL statuses.

Related Links

No comments