From F&B to fintech, clinics to law firms, startups to enterprise. If your customers search on Google, we make sure they find you first, not your competitors.
One specialist team, focused only on the organic rankings that put you in front of ready-to-buy Singapore customers.
A clear, sequenced path from audit to rankings. You always know what we’re doing and why it matters for your leads.
Quick answer: The Google Search Console submit sitemap step takes about two minutes: open Indexing, then Sitemaps, paste your sitemap URL and click Submit. The real work is keeping that sitemap clean, listing only indexable, canonical pages that return a 200 status, because Google treats a sitemap as a hint, not an instruction.
Most Singapore business owners who search for the Google Search Console submit sitemap steps expect a fiddly technical job. It is not. Submitting takes less time than making a kopi. What decides whether the sitemap helps you is what is inside it, and that is the part almost nobody checks after the first day.
An XML sitemap is a file, written in a machine-readable format called XML (Extensible Markup Language), that lists the pages on your website you want search engines to find. Google Search Console is Google’s free tool for site owners, and its Sitemaps report is where you tell Google where that file lives. This piece covers sitemaps only. It assumes you already have a verified Search Console property; if you want help with the wider crawl and index foundations, our technical SEO service page explains how that work is scoped.
You will learn where to find your sitemap URL on WordPress, Shopify and Wix, how to submit it, what each status message means, why “discovered” is not “indexed”, what to leave out, and when resubmitting is worth doing. Our conclusion runs through every section: submitting is trivial, and a clean sitemap is the whole point.
When you submit a sitemap, you are handing Google a list and saying: these are the pages I consider important, and here is roughly when each one last changed. Google’s own documentation is careful about what happens next. A sitemap helps Google discover URLs, especially on new sites, large sites, or sites where some pages are not well linked internally. It does not guarantee that any page will be crawled, and it certainly does not guarantee that any page will be indexed.
Two plain-English terms matter here. Crawling is Google’s software (Googlebot) fetching a page to read it. Indexing is Google deciding to store that page so it can appear in search results. A sitemap can speed up the first. It has very little say over the second, which depends on the page’s quality, whether it duplicates another page, and whether your own signals tell Google to leave it out.
That is why we describe a sitemap as a hint, not an instruction. Google weighs it alongside everything else it knows about your site: internal links, canonical tags (a line of code telling Google which version of a page is the main one), redirects and robots rules. When the sitemap agrees with those signals, it reinforces them. When it contradicts them, for example by listing a page that carries a noindex tag, Google has to decide which signal to believe, and it learns that your sitemap is not a reliable guide to your site.
In our experience at Singapore SEO Agency, owners overestimate the submission and underestimate the maintenance. A sitemap submitted once and never looked at again slowly fills with URLs that redirect, return errors, or should never have been public. Nothing breaks visibly. Google simply spends a little more of its attention on pages that do nothing for you, and a little less trust on the file itself.
For a small service business with twenty well-linked pages, Google would probably find everything without a sitemap at all. For an online store with hundreds of products, filter pages and seasonal collections, a clean sitemap becomes one of the clearest signals you control. Either way, the submission itself is the easy bit.
Before you can submit anything, you need the exact address of your sitemap. Most website platforms create one automatically, so in most cases your job is to find it, not build it. Type the address into your browser first; if you see a page of URLs wrapped in code, the sitemap exists.
The usual locations are:
yourdomain.com/wp-sitemap.xml.yourdomain.com/sitemap_index.xml. Yoast replaces the core WordPress sitemap with its own.yourdomain.com/sitemap_index.xml, with the sitemap settings found in the plugin’s Sitemap Settings area.yourdomain.com/sitemap.xml. Shopify generates it automatically and splits it into child sitemaps for products, collections, pages and blog posts.yourdomain.com/sitemap.xml, generated automatically once the site is published on a connected domain.Three checks save trouble later. First, use the version of your domain Google actually indexes. If your site loads on https://www. then the sitemap URL must use https://www. as well, not http:// or the bare domain. Second, only use one sitemap source. If an old plugin and a new plugin are both generating sitemaps, pick one and switch the other off, otherwise Google receives two lists that may disagree. Third, if your site was rebuilt on a new platform, the old sitemap address may still be listed in Search Console and may now return an error. Remove it from the report once the new one is submitted.
If you are not sure which platform or plugin your developer used, view the page source of your homepage and search for “Yoast”, “Rank Math”, “Shopify” or “Wix”, or simply try each address above. When we audit a site that has changed hands between developers, finding two competing sitemaps is common, and it is one of the quickest fixes available.
Sitemaps are also listed in the robots.txt file, a small text file at yourdomain.com/robots.txt that gives instructions to crawlers. Many platforms add a line there such as Sitemap: https://www.yourdomain.com/sitemap_index.xml. Checking that line is another fast way to confirm the correct address.
Once you have the address, the submission itself is short. You need Owner or Full user access to the Search Console property; restricted users can view the report but cannot submit.
sitemap_index.xml. For a Domain property you type the full URL.A few points that confuse people. If your sitemap is an index file (a sitemap that lists other sitemaps), submit the index only. Google will read the child sitemaps from it, and they will appear when you click into the index. You do not need to submit each child separately.
The sitemap has to sit within the scope of the property. On a URL-prefix property for https://www.yourdomain.com/, a sitemap hosted on another subdomain will be rejected. This is another reason we recommend Domain properties for most small businesses.
Do not panic if the status does not settle immediately. Processing can take anything from a few minutes to several days. If nothing has changed after a week, that is when to investigate.
Most agencies will tell you that submitting the sitemap is the key indexing step and will list it as a deliverable in month one. That framing frequently backfires, because it makes the submission look like the finished job. The submission is a two-minute admin task. The ongoing value is in what the sitemap contains and in reading the reports it unlocks, which is what the rest of this piece covers. If you would rather someone else kept an eye on this monthly, our small business SEO page shows how that support is usually set up for firms without an in-house marketer.
After submission, every sitemap carries one of three statuses.
Success means Google fetched the file and read it without errors. It does not mean every URL in it is indexed. It only means the file itself is valid.
Has errors means Google could fetch the sitemap and read at least part of it, but found problems. Click the sitemap row to open its details page, which lists the specific issues. Typical causes include an invalid date format in a lastmod field, URLs that do not belong to your property, or a file that turns out to be an HTML page rather than XML. Google will still use the parts it could read, so fix the errors, but do not assume the whole file has been ignored.
Couldn’t fetch means Google could not retrieve the file at all. Start by opening the sitemap URL in your browser. If it does not load, the address is wrong, the file has been removed, or something such as a security plugin, firewall or login wall is blocking it. If it loads in your browser, run the URL through the URL Inspection tool (the search bar at the top of Search Console) with a live test to see what Googlebot receives. On a newly submitted sitemap, this status sometimes lingers for a while even when the file is fine, so give it a few days before rebuilding anything.
The Discovered pages column is the most misread number in the report. It counts the URLs Google found listed in the sitemap. It says nothing about how many of those URLs made it into Google’s index.
To see that, open the Page indexing report under Indexing, then use the filter at the top to switch from “All known pages” to “All submitted pages”, or pick a specific sitemap. The report then splits your submitted URLs into indexed and not indexed, with a reason for each excluded group.
That comparison is where a sitemap earns its keep. If your sitemap lists 300 URLs and Google has indexed most of them, your list and Google’s view of your site agree. If a large share sits under reasons like “Page with redirect”, “Not found (404)” or “Excluded by ‘noindex’ tag”, your sitemap is listing pages you have told Google not to index, and the fix is in the sitemap, not in resubmitting it.
The sitemap should be a list of pages you want people to find through Google. Everything on it should be indexable (no noindex tag, not blocked by robots.txt), canonical (the main version of the page, not a duplicate pointing elsewhere) and should return a 200 status code, which is the server’s way of saying “this page loaded normally”.
That rules out a surprising amount of what platforms include by default:
?colour=blue&size=m, sort orders, tracking codes and session IDs create many addresses for the same content. Only the canonical version belongs in the sitemap.Here is where we disagree with the common advice to “put everything in the sitemap so Google finds it all”. A sitemap is not a coverage target. A bigger sitemap is not a better sitemap. Listing pages you do not want indexed does not make Google index them; it teaches Google that your list is padded.
When we audit online stores, an untidy sitemap is usually a symptom of something larger, typically faceted navigation (the filter menus on category pages) generating crawlable URLs nobody planned for. Cleaning the sitemap is the first visible step, but the underlying fix usually involves robots rules, canonical tags and internal links as well. For catalogue sites, our ecommerce SEO service covers how those pieces are handled together.
A practical test for any URL: if a customer searched Google and landed on this exact address, would you be happy? If the answer is no, it should not be in the sitemap.
This table maps common sitemap problems to where they appear in Search Console and the fix for each.
| Sitemap problem | Symptom in Google Search Console | Fix |
|---|---|---|
| Wrong sitemap URL, or file deleted after a rebuild | Sitemaps report shows “Couldn’t fetch” | Open the URL in a browser, confirm the correct address for your platform, remove the old entry and submit the new one |
| Sitemap blocked by a security plugin, firewall or login | “Couldn’t fetch”, while the file loads for you when logged in | Run a live test in URL Inspection, then allow Googlebot to reach the file |
| Invalid dates, wrong format or URLs outside the property | “Has errors” with a list of issues on the sitemap’s details page | Fix the generator settings or plugin, check the property scope, then resubmit |
| Noindex pages listed | Page indexing, filtered to submitted pages: “Excluded by ‘noindex’ tag” | Exclude that content type in your SEO plugin or platform settings |
| Redirected URLs listed | Submitted pages showing “Page with redirect” | List only the final destination URL |
| Deleted products or pages listed | Submitted pages showing “Not found (404)” | Remove them from the sitemap; redirect to a close match only where one genuinely exists |
| Parameter or duplicate URLs listed | “Duplicate, Google chose different canonical than user” or “Alternate page with proper canonical tag” | List canonical URLs only and fix the canonical tags on the duplicates |
| URLs blocked by robots.txt listed | “Blocked by robots.txt” among submitted pages | Decide whether the page should be indexed; either unblock it or drop it from the sitemap |
| Two plugins or an old platform both generating sitemaps | Two sitemap entries with different discovered page counts | Keep one generator, switch off the other, delete the stale entry from the report |
| lastmod updated on every page every day | No direct error, but lastmod stops helping Google prioritise | Set lastmod to change only when the page content meaningfully changes |
Search Console tells you the symptom, never the cause. “Page with redirect” among submitted URLs is a sitemap problem; the same reason on URLs you never submitted is usually Google following old links and needs no action. Filtering to submitted pages separates the problems you caused from the background noise. If your sector has particular page types that tend to clutter sitemaps, such as listings, menus or practitioner profiles, our industry SEO page shows how priorities differ by sector.
A single sitemap file can hold up to 50,000 URLs and must be no larger than 50MB uncompressed. Very few Singapore SMEs come near that, but large catalogues, property listing sites and directories can. When a site exceeds either limit, the answer is a sitemap index file: one file that lists several smaller sitemaps. Yoast, Rank Math, Shopify and Wix already produce index files, which is why their addresses differ from the plain WordPress one. Splitting by type, for example products, categories and pages, also makes the Search Console data easier to read, because each child sitemap gets its own discovered count.
The lastmod field records when a page last changed. Google has said it uses lastmod as a signal for scheduling recrawls of pages it already knows about, but only when the value is consistently and verifiably accurate. A lastmod that changes because a footer year or a sidebar widget updated is noise. Lastmod honesty matters: if every page claims to have changed today, Google learns to ignore the field for your site. Google has also said it ignores the priority and changefreq fields, so do not spend time tuning them.
The robots.txt Sitemap line is a second way to tell search engines where your sitemap is. Add a line such as Sitemap: https://www.yourdomain.com/sitemap_index.xml to your robots.txt file, using the full URL. This helps other search engines, such as Bing, and any crawler that reads robots.txt. It does not replace Search Console, which is the only place you see the status and discovered counts.
One older method no longer works. Google used to accept a “ping”, a web request that told it a sitemap had changed. In June 2023, Google announced it was deprecating the sitemaps ping endpoint, citing that unauthenticated submissions were mostly spam, and the endpoint stopped working around the end of that year; requests to it now return an error. Any plugin setting or developer script that still pings Google is doing nothing. The supported routes are Search Console and the robots.txt line, with lastmod doing the job the ping used to do.
Google rechecks submitted sitemaps on its own schedule, so you do not need to resubmit after every new page or product. If your platform updates the sitemap automatically, which WordPress, Shopify and Wix all do, Google will pick up changes when it next reads the file. Submitting the same unchanged sitemap repeatedly does not speed anything up.
Resubmission is worth doing in a handful of situations:
For a single new page that matters, a service page you need found quickly, the URL Inspection tool lets you request indexing for that one address. Use it sparingly; it is a request, not a guarantee, just like the sitemap.
What resubmission will not do is fix a dirty sitemap. If the Page indexing report shows many submitted pages excluded for redirects, 404s or noindex tags, resubmitting the same list simply asks Google to read the same problems again. Clean the list first, then resubmit.
We find a light monthly routine is enough for most small sites: open the Sitemaps report, confirm the status still reads Success and the last read date is recent, then filter Page indexing to submitted pages and scan the excluded reasons for anything new. In our experience that ten-minute habit catches broken migrations, plugin conflicts and forgotten promotions long before they affect enquiries. If you are weighing whether to handle this in-house or with help, our pricing page shows how ongoing support is packaged.
Our ecommerce SEO case study documents a 9-month engagement with a Singapore-based B2C ecommerce store selling home and lifestyle products, built on WooCommerce. At the start, the store had 200+ product SKUs but product pages indexed stood at 34% (68 of 200). The initial audit found no XML sitemap, no robots.txt rules blocking faceted navigation parameters, and no structured data of any kind. The baseline showed 1,200 monthly organic visitors, organic monthly revenue of S$8,400 and 12 keywords ranking on page 1.
What the programme did. Phase 1 (Months 1-2), Crawl and Index Repair, is the part that matters here. The team rewrote robots.txt to block the 14 faceted navigation parameter combinations generating duplicate content, submitted a clean XML sitemap covering all canonical product and category URLs, and resolved 200+ redirect chains left by two prior platform migrations. By end of Month 2, product page indexation moved from 34% to 79%. The later phases added Product schema (Months 2-3), a category page strategy covering 15 top-revenue categories (Months 3-5), internal link architecture (Months 4-6) and a blog content programme of 20 product guides and comparison articles (Months 3-9).
The ending position at Month 9. Product pages indexed reached 95%. Monthly organic visitors went from 1,200 to 4,640 (+287%), organic monthly revenue from S$8,400 to S$28,600 (+240%), and keywords ranking on page 1 from 12 to 74. The page reports organic revenue rather than enquiries, as this is a store.
Two points are worth drawing out honestly. First, the sitemap was submitted together with the robots.txt and redirect repairs, as one phase. The sitemap on its own did not move indexation; it worked because the list it carried matched the rest of the site’s signals, canonical URLs only, with the duplicate filter combinations blocked. Second, the traffic and revenue figures came from the whole programme across all five phases, not from the sitemap or from any single tactic.
The lesson for your own submission is the order of operations: decide which URLs deserve to be indexed, make the site agree with that decision, then hand Google a sitemap that lists exactly those URLs. Store owners weighing a similar approach can see how the work is scoped on our ecommerce SEO services in Singapore page.
Field notes: In our ecommerce case study, a Singapore home and lifestyle store on WooCommerce, the initial audit found no XML sitemap at all, while three years of faceted navigation URLs had created thousands of duplicate pages. The fix was not just adding a sitemap. In Phase 1 the team blocked the 14 faceted navigation parameter combinations in robots.txt and submitted a clean XML sitemap covering all canonical product and category URLs, alongside resolving 200+ redirect chains. By end of Month 2, product page indexation moved from 34% to 79%, and it reached 95% by Month 9 as the wider programme continued. The sitemap helped because it only listed pages the rest of the site also said were worth indexing.
The Google Search Console submit sitemap step is the easiest task in SEO. Find your sitemap URL, paste it into the Sitemaps report, click Submit. Two minutes. Everything that makes the sitemap useful happens before and after that click.
Because Google treats a sitemap as a hint rather than an instruction, its value depends on trust. A sitemap that lists only indexable, canonical pages returning a 200 status tells Google exactly where to spend its attention. One padded with redirects, 404s, noindex pages and filter URLs wastes that attention and teaches Google to discount the list. Submit once, check monthly, read the submitted pages filter in Page indexing, and fix the list rather than resubmitting it. If you want to know more about the people behind this advice, our about page explains how we work with Singapore businesses.
Sign in to Search Console, choose your property, and open Sitemaps under Indexing in the left menu. Type your sitemap URL in the “Add a new sitemap” box, for example sitemap_index.xml, and click Submit. The sitemap then appears in the Submitted sitemaps table with its status and discovered pages count. You need Owner or Full user access to submit.
It depends on your platform. WordPress without an SEO plugin uses /wp-sitemap.xml. WordPress with Yoast SEO or Rank Math uses /sitemap_index.xml. Shopify and Wix both use /sitemap.xml. Type the address after your domain in a browser to confirm it loads, and check your robots.txt file, which often lists the sitemap on a line starting with “Sitemap:”.
It means Google could not retrieve the sitemap file. Check the address loads in your browser, then use the URL Inspection tool’s live test to see what Googlebot receives. Common causes are a wrong URL, a deleted file after a rebuild, or a firewall or security plugin blocking Google. On a newly submitted sitemap the status can also linger for a few days before updating.
No. Success only means Google fetched and read the sitemap file without errors. To see how many listed pages are actually indexed, open the Page indexing report and filter it to “All submitted pages” or to a specific sitemap. That view shows indexed and not indexed pages, with a reason for each group that was left out.
Discovered pages is the number of URLs Google found listed in your sitemap. Indexed pages are those Google has decided to store and show in search results. A page can be discovered and never indexed, for example because it redirects, returns a 404 error, carries a noindex tag or duplicates another page. Compare the two numbers to judge how clean your sitemap is.
Leave out anything you would not want a searcher to land on: noindex pages such as thank-you, cart and account pages, redirected URLs, deleted products and other 404 pages, filter and tracking parameter URLs, and thin archive pages like WordPress tags. Every URL in the sitemap should be indexable, canonical and return a normal 200 status.
No. Google rechecks submitted sitemaps on its own, and WordPress, Shopify and Wix update theirs automatically. Resubmit when the sitemap address changes, after a domain or platform move, after fixing errors, or after a large structural change. For one important new page, you can request indexing through the URL Inspection tool instead.
No. Google announced in June 2023 that it was deprecating the sitemaps ping endpoint, and the endpoint stopped working around the end of that year. Requests to it now return an error. Use Search Console and a Sitemap line in robots.txt instead, and keep the lastmod field accurate so Google can tell which pages have genuinely changed.
A single sitemap can list up to 50,000 URLs and must be no more than 50MB uncompressed. Larger sites should use a sitemap index file that lists several smaller sitemaps, then submit only the index in Search Console. Splitting by page type, such as products, categories and pages, also makes the reports easier to read.
Not directly. A sitemap helps Google discover and recrawl pages, but it does not make a page rank higher or force it into the index. Rankings depend on the page’s relevance, quality and links. A clean sitemap supports rankings indirectly by making sure the pages you care about are found and recrawled promptly, rather than buried among URLs that do not matter.
If your Sitemaps report says Success but you are not sure how many of your important pages Google has actually indexed, we are happy to check. A free SEO audit reviews your sitemap, indexing and crawl signals together and shows which pages are being held back, so you know what to fix first.
Natalie leads SEO strategy at Singapore SEO Agency, helping local and regional businesses build organic search programmes that drive qualified leads. She specialises in technical SEO and content-led authority building for Singapore SMEs.
Get a free SEO audit for your Singapore website — we'll show you exactly where you stand, what's holding you back, and what it would take to rank on page 1.
Get Your Free SEO Audit →
Google Search Console submit sitemap steps by platform, what each status means, and what to leave out so Google spends its attention on pages you want found.
Google Search Console help for busy owners: what each email and warning usually means, which ones to ignore, and where to get free help before you pay anyone.
Domain authority is a useful filter for weak sites but a poor sales promise. Learn why scores move on their own and what to ask before you buy links or SEO.
Paying for an SEO keyword research tool? Test its Singapore data on 20 keywords you know, see why KD differs by vendor, and pick one tool you can stick with.
Whats bounce rate, and how is it different from exits, engagement time or dwell time? Learn what each one really answers and what to ask your SEO agency.
Google Analytics website traffic is a consented sample, not a head count. See where visits come from, why tools disagree and which number to trust each month.
Fast, no obligation. We reply within 24 hrs.
Singapore’s specialist SEO agency for SMEs. We rank your business on Google — and only Google. No distractions, just results.
© 2026 Singapore SEO Agency. All rights reserved.