If you’ve built or updated a website and you’re wondering how to submit a sitemap to Google, you’re asking the right question at the right time. But here’s what most guides won’t tell you: the submission itself takes about 30 seconds. The real work is making sure your sitemap is clean, accurate, and not quietly sabotaging your crawl budget.
I’ve seen Singapore businesses lose weeks of indexing time because their sitemap included 2,000 URLs returning 301 redirects. Or because their CMS auto-generated a sitemap stuffed with tag archive pages nobody should ever see. So let’s do this properly, from generation to submission to ongoing maintenance.
What a Sitemap Actually Does (And Doesn’t Do)
A sitemap is an XML file that lists the URLs you want Google to know about. Think of it like the menu at a hawker stall. It tells the customer (Googlebot) exactly what’s available, so they don’t have to wander around the kitchen guessing.
But here’s a critical distinction: submitting a sitemap does not guarantee indexing. Google treats your sitemap as a suggestion, not a command. If a URL in your sitemap has thin content, is blocked by robots.txt, or returns a non-200 status code, Google will simply ignore it.
XML Sitemaps vs HTML Sitemaps vs RSS Feeds
XML sitemaps are what you submit to Google Search Console. They’re machine-readable files with structured data about each URL, including the last modified date and change frequency.
HTML sitemaps are user-facing pages that list your site’s links in a clickable format. They’re useful for UX on large sites but have minimal direct SEO impact in 2026.
RSS and Atom feeds can function as lightweight sitemaps for blogs or news sites with frequent publishing. Google actually recommends combining an XML sitemap with an RSS feed if you publish daily. The XML sitemap covers your full URL inventory, while the RSS feed pings Google about your latest posts within minutes.
Why Submitting a Sitemap to Google Matters for Singapore Businesses
If your site has fewer than 50 pages and strong internal linking, Google will probably find everything on its own. But most business websites aren’t that simple.
Here’s when a sitemap becomes essential:
- Your site has 500+ pages (common for e-commerce sites selling products across Singapore and Southeast Asia).
- You’ve just launched a new site or migrated domains.
- You have orphan pages with no internal links pointing to them.
- You publish content frequently and want faster discovery.
- Your site has sections behind JavaScript rendering that Googlebot might struggle with.
I worked with a Singapore-based fintech company that had 1,200 pages but only 340 indexed. The problem? Their sitemap included every URL variant, including paginated results, filtered views, and staging URLs that had accidentally gone live. After cleaning the sitemap down to 780 legitimate URLs and resubmitting, indexed pages jumped to 720 within three weeks. That’s a 112% increase in indexed pages from sitemap hygiene alone.
Step-by-Step: How to Submit a Sitemap to Google Search Console
Step 1: Generate a Clean Sitemap
Before you submit anything, you need a sitemap worth submitting. Here’s how to generate one depending on your setup:
WordPress sites: Install Yoast SEO or Rank Math. Both auto-generate XML sitemaps. In Yoast, go to SEO → General → Features and ensure “XML Sitemaps” is toggled on. Your sitemap will live at yoursite.com/sitemap_index.xml.
Custom or non-WordPress sites: Use Screaming Frog SEO Spider. Crawl your entire site, then go to Sitemaps → Create XML Sitemap. This gives you granular control over what’s included.
Small static sites: Use a free generator like XML-Sitemaps.com for sites under 500 pages.
Before moving to step 2, open your generated sitemap in a browser and manually check for these problems:
- URLs returning 301, 302, 404, or 410 status codes.
- URLs with noindex meta tags (these contradict the purpose of a sitemap).
- URLs blocked by robots.txt.
- Duplicate URLs with trailing slashes and without, or HTTP and HTTPS variants.
- Parameter URLs like ?sort=price or ?page=3.
Every URL in your sitemap should return a 200 status code and be the canonical version of that page. No exceptions.
Step 2: Verify Your Site in Google Search Console
You can’t submit a sitemap without verified ownership of your property in Google Search Console (GSC). If you haven’t done this yet, here’s the process:
Go to search.google.com/search-console and click “Add Property.” You’ll see two options:
Domain property: Covers all subdomains, protocols, and paths. Requires DNS verification through your domain registrar (Namecheap, GoDaddy, Cloudflare, etc.). This is the recommended option for most businesses.
URL-prefix property: Covers only the exact URL pattern you enter (e.g., https://www.yoursite.com). Offers more verification methods including HTML file upload, meta tag, Google Analytics, or Google Tag Manager.
For most Singapore businesses, I recommend the domain-level property. It gives you a complete picture of your search performance across www and non-www, HTTP and HTTPS.
Once you’ve added the DNS TXT record or uploaded the HTML file, click Verify. GSC usually confirms within a few minutes, though DNS propagation can take up to 48 hours.
Step 3: Submit the Sitemap
This is the easy part:
- In Google Search Console, select your verified property.
- In the left sidebar, click “Sitemaps” under the Indexing section.
- In the “Add a new sitemap” field, type your sitemap path. For most WordPress sites, this is
sitemap_index.xmlorsitemap.xml. - Click Submit.
GSC will fetch the file and display a status. You want to see “Success” with the number of discovered URLs. If it shows “Couldn’t fetch,” double-check that the URL is accessible in your browser and not blocked by your robots.txt file.
Step 4: Cross-Reference with robots.txt
This step gets skipped constantly, and it causes real problems. Open your robots.txt file (yoursite.com/robots.txt) and confirm two things:
First, your sitemap URL should be declared at the bottom of the file:
Sitemap: https://www.yoursite.com/sitemap_index.xml
Second, none of the URLs in your sitemap should be disallowed by robots.txt rules. If your robots.txt blocks /products/ but your sitemap includes product URLs, you’re sending Google contradictory signals. Google will respect the robots.txt block and ignore the sitemap entry.
Step 5: Monitor and Maintain
Submitting your sitemap is not a set-and-forget task. Check back in GSC after 48 to 72 hours and review the “Coverage” or “Pages” report. Look specifically at:
- Discovered but not indexed: Google found the URL but chose not to index it. This often means thin content or duplicate content issues.
- Crawled but not indexed: Google fetched the page but still didn’t index it. Usually a quality signal problem.
- Excluded by noindex tag: You’re telling Google not to index a page that’s in your sitemap. Pick one. Either remove the noindex tag or remove the URL from your sitemap.
Set a calendar reminder to audit your sitemap quarterly. Every time you add a major section, delete pages, or change URL structures, regenerate and resubmit.
Common Sitemap Errors and How to Fix Them
Invalid XML Format
Even one unclosed tag or illegal character will cause the entire sitemap to fail validation. Run your sitemap through the XML Sitemap Validator before submitting. Common culprits include ampersands (&) that should be encoded as & and URLs with spaces or special characters.
Sitemap Too Large
Google enforces a hard limit: 50MB uncompressed or 50,000 URLs per sitemap file. If your site exceeds this, split your sitemap into multiple files and reference them from a sitemap index file. Most CMS plugins handle this automatically, but verify it if your site has grown significantly.
Including Non-Canonical URLs
This is the most common mistake I see on Singapore e-commerce sites. If page A has a canonical tag pointing to page B, only page B should appear in your sitemap. Including both creates confusion and wastes crawl budget. Run a Screaming Frog crawl, filter by “Canonical Link Element 1” not matching the URL, and remove every mismatched entry from your sitemap.
Stale lastmod Dates
If every URL in your sitemap shows the same lastmod date, or if the dates never change even when content is updated, Google may start ignoring your lastmod values entirely. Only update lastmod when the page content has genuinely changed. Don’t fake it.
Advanced Sitemap Practices Worth Knowing
Sitemap segmentation is something I recommend for any site above 200 pages. Instead of one monolithic sitemap, create separate sitemaps for different content types: one for blog posts, one for product pages, one for location pages. This lets you monitor indexing rates per content type in GSC and quickly spot problems.
For sites with images or videos that you want indexed in Google Image Search or Video Search, consider dedicated image and video sitemaps. These use extended XML tags to provide Google with metadata like image captions, video duration, and thumbnail URLs.
If you serve content in multiple languages (common for Singapore businesses targeting English, Chinese, and Malay audiences), your sitemap should include hreflang annotations. This tells Google which language version to serve to which audience, preventing duplicate content issues across language variants.
Frequently Asked Questions
Does a small website need a sitemap?
If your site has fewer than 50 pages and every page is reachable through internal links, a sitemap isn’t strictly necessary. But it takes five minutes to set up and gives you visibility into indexing issues through GSC. There’s no reason not to have one.
How long after submitting does Google index my pages?
There’s no guaranteed timeline. For established domains with good crawl history, new URLs can be indexed within hours. For newer sites, it can take days or weeks. Submitting a sitemap speeds up discovery but doesn’t control Google’s indexing queue.
Can I submit multiple sitemaps for one website?
Yes. You can submit up to 500 sitemaps per property in Google Search Console. Use a sitemap index file to organise them, or submit each one individually through the Sitemaps tool.
What if my sitemap shows “Couldn’t fetch” in Search Console?
Check three things: Is the URL accessible in a browser? Is it blocked in robots.txt? Is your server returning a 200 status code for the sitemap URL? If your site is behind Cloudflare or another CDN, ensure the CDN isn’t blocking Googlebot’s user agent.
Should I include pages with noindex tags in my sitemap?
No. A sitemap says “please crawl and index these.” A noindex tag says “please don’t index this.” Sending both signals for the same URL is contradictory. Google has confirmed they find this confusing. Remove noindexed URLs from your sitemap.
Get Your Technical SEO Foundations Right
Knowing how to submit a sitemap to Google is one piece of a much larger technical SEO puzzle. If you’re finding indexing gaps, crawl errors, or pages that just won’t rank despite good content, the issue is often deeper than the sitemap itself.
If you’d like a second pair of eyes on your site’s technical health, grab a free 30-minute strategy session with our team. We’ll review your sitemap, crawl data, and indexing status, then tell you exactly where the gaps are. No obligations, just clarity on what to fix first.