XML Sitemap Create Singapore: The Complete Website Guide

Quick answer: To XML sitemap create Singapore site owners need a machine readable list of every page they want found, published at a fixed address and submitted to Google Search Console. Most platforms generate it automatically. The real value is not ranking power, it is the indexing report you get back.

Almost every Singapore business owner we speak to has heard the phrase “submit your sitemap” and assumes it is a switch that makes Google pay attention. It is not. An XML sitemap is closer to a delivery manifest than a marketing tool, and understanding that difference is what separates people who use it well from people who upload a file once and never look at it again. The word XML stands for Extensible Markup Language, which is simply a structured text format that software reads easily and humans read badly. A sitemap written in that format lists the addresses of the pages on your website, along with optional notes about when each one last changed. Google, Bing and other search engines read that list and use it as a starting point for crawling. What follows is a full walkthrough: what a sitemap is, exactly how to generate one on the platforms Singapore SMEs actually run, what belongs in it and what must never go in it, and the one use most site owners miss entirely. If you want the broader picture of how crawling and indexing fit together, our technical SEO work covers the surrounding ground.

What an XML Sitemap Actually Is, in Plain English

Strip away the acronyms and a sitemap is a text file containing a list of web addresses. Each entry sits inside a pair of tags that tell the search engine what it is looking at. The core tag is <loc>, which holds the full address of a page including the https prefix and the domain. Around it you may optionally see <lastmod>, which records the date the page last changed in a standard format, and historically <changefreq> and <priority>, which suggested how often a page changes and how important it is relative to other pages on the same site.

Two of those four tags no longer matter. Google has stated publicly that it ignores the changefreq and priority values, because site owners overwhelmingly set every page to the highest priority and a daily change frequency, which made the signal useless. The lastmod date still carries weight, but only if it is honest. If your content management system rewrites the lastmod value every night because a plugin touched the database, you have trained the crawler to distrust the entire file.

The file lives at a fixed, publicly reachable address, most commonly something like yourdomain.com.sg/sitemap.xml or /sitemap_index.xml. It is not hidden and it is not private. Anyone, including your competitors, can open yours in a browser right now, and you can open theirs. That transparency is useful. In our experience, one of the fastest ways to understand a competitor’s content strategy in a niche like aesthetics or renovation is to read their sitemap and count how many service pages and location pages they publish.

A sitemap can also be split into several files joined by a parent file called a sitemap index. This is standard on larger sites, because a single sitemap file is capped at fifty thousand addresses or 50MB uncompressed, whichever comes first. Most Singapore SME sites sit far under that ceiling, but e-commerce catalogues and property listing portals routinely exceed it, which is why platforms serving those businesses split by content type automatically. Smaller property sites still need the file kept current: in our real estate case study, the sitemap was rebuilt to include all the new agent and district URLs.

A sitemap is a suggestion, not an instruction. Nothing in the file obliges a search engine to crawl a page, index a page, or rank a page. It offers a list. What the crawler does with that list is decided elsewhere.

What a Sitemap Does Not Do, and Why That Matters

This is where most of the disappointment comes from, so it is worth being blunt. Submitting a sitemap does not cause your pages to be indexed. It does not improve rankings for pages already indexed. It does not override a noindex tag, a robots.txt block, a canonical tag pointing elsewhere, or a quality judgement that your page is not worth storing.

The conventional wisdom in a lot of cheap SEO advice is that if a page is not showing up in Google, you should resubmit the sitemap. We have seen business owners resubmit the same file weekly for months while the underlying problem, usually a thin page or a duplicate, went untouched. Resubmission changes nothing if the page was already discovered. Google has almost certainly seen the address. It has chosen not to store it, and that choice is about the page, not the file.

What a sitemap genuinely helps with is discovery on sites where internal linking is weak. If a page is not linked from anywhere else on your site, a crawler following links will never reach it. A sitemap is the only way that page gets found. This is common on Singapore SME sites in a few specific shapes: service pages built for a paid campaign and never added to the navigation, older landing pages orphaned during a redesign, and blog archives where pagination stops after a few pages. Owner operated businesses with no in-house marketer are the most exposed, which is why orphan page discovery is an early step in our small business SEO engagements.

It also helps with large or fast changing sites. A property listing site adding and removing units daily, or a retailer rotating seasonal stock, benefits from a sitemap that reflects the current state. For a five page corporate brochure site with a clear menu, the sitemap adds close to nothing in discovery terms.

The second genuine benefit, and the one this article is really about, is diagnostic. Once you submit a sitemap, Google Search Console tells you how many of those specific addresses it has indexed. That comparison, submitted versus indexed, is the single most useful number available to a small site owner, and it is invisible without a sitemap. For catalogue heavy businesses this comparison surfaces problems long before traffic drops, which is why it forms an early step in our e-commerce SEO audits.

How to XML Sitemap Create Singapore Site Owners Should Follow, Platform by Platform

The honest answer is that on most modern platforms you do not create a sitemap at all. The platform creates it and you simply need to find the address. Building one by hand is only necessary for custom builds and legacy sites. Here is how the main options compare for the platforms we most often see in Singapore.

For WordPress, which still runs the majority of Singapore SME sites we audit, install one reputable SEO plugin and let it handle the file. Then go into its settings and turn off anything you do not want listed. Tag archives, author archives, attachment pages and date archives are the usual culprits. A five person company does not need an author archive for each staff member, and those pages dilute the picture of what your site is about.

For Shopify, you cannot edit the sitemap, and that is a genuine constraint rather than a failing. Your lever is product and collection visibility. If a product should not be listed, unpublish it rather than hoping to strip it from a file you do not control.

For a custom build, the risk is neglect. A hand written sitemap uploaded once in 2021 is worse than no sitemap at all, because it advertises a set of addresses that may no longer exist and teaches the crawler that your file is unreliable. Make generation part of the deployment process so it cannot drift.

The Rules That Decide What Goes In and What Stays Out

The principle is simple and almost nobody follows it: your sitemap should contain every page you want indexed, and only pages you want indexed. Every entry that fails that test weakens the file as a signal and ruins it as a diagnostic.

Pages that should be excluded, in rough order of how often we find them wrongly included:

Pages carrying a noindex tag. Listing a page you have explicitly told Google not to index is a contradiction. Search Console will flag it, and you will spend an afternoon chasing a warning that you created yourself.

Non canonical duplicates. If two addresses show the same content and one carries a canonical tag pointing at the other, only the canonical version belongs in the sitemap. Product variant addresses with colour or size parameters are the standard offender on Singapore retail sites.

Redirected addresses. A page that now returns a 301 redirect should be removed. The sitemap should list the destination, not the old address.

Anything returning an error. A 404 in a sitemap is a wasted crawl and a small credibility hit.

Utility pages with no search value. Thank you pages, cart and checkout pages, internal search result pages, login screens, and print stylesheets add nothing. In our experience the thank you page is the one most often forgotten, and it occasionally ends up ranking for a brand search, which is a poor first impression.

Staging and development addresses. We have opened live sitemaps that still listed a staging subdomain from the original build. That is both an SEO problem and a mild security embarrassment, and it is one of the first things we look for when a new client comes through our about page enquiry form asking why their traffic stalled.

Pages that should be included and often are not: service pages built for paid campaigns, location pages, case studies, category pages that carry real commercial intent, and long form guides buried several clicks deep. For a multi location Singapore business, the location pages are usually the highest value entries in the whole file, and they are exactly the ones a theme designer leaves out of the menu. Our local SEO work treats those pages as primary assets rather than afterthoughts.

Submitting the Sitemap and Actually Reading the Report

Submission is the easy part. In Google Search Console, select your property, open the Sitemaps section, enter the path to your sitemap relative to the domain, and submit. Bing Webmaster Tools accepts the same file through an equivalent screen, and for many Singapore B2B sites Bing traffic is a small but genuinely converting slice worth claiming. You should also reference the sitemap address inside your robots.txt file, which is the plain text file at the root of your domain, using a Sitemap line. That covers crawlers that never visit Search Console at all.

Then comes the part almost everyone skips. A day or two later, return to the same screen and open the report. You will see the number of addresses discovered from that file. Cross reference it with the Pages report, which splits your site into indexed and not indexed, with a reason attached to each group.

The comparison is where the value sits. If you submitted 120 addresses and 118 are indexed, your site is healthy and your time is better spent on content. If you submitted 120 and 47 are indexed, you have a real problem and the reason column tells you which one. Crawled, currently not indexed usually means Google looked and judged the page not worth storing, which is a quality and uniqueness issue. Discovered, currently not indexed usually means crawl capacity or perceived low value, common on very large catalogues. Duplicate without user selected canonical means you are publishing near identical pages. Excluded by noindex tag means the answer is in your own settings.

Those categories turn a vague worry into a specific task list. We recommend checking this screen monthly rather than daily, because index status fluctuates naturally and reacting to normal noise wastes effort. For businesses publishing regularly, a slow drift downwards in the indexed count over three months is a far more meaningful signal than a single bad week.

Sitemap Index Files, Media Sitemaps and Bilingual Singapore Sites

Once a site grows past a few hundred pages, a single file becomes unwieldy and unhelpful. The answer is a sitemap index, a small parent file that lists the addresses of several child sitemaps. Most SEO plugins produce this by default, splitting by content type: one for pages, one for posts, one for products, one for each taxonomy.

This split is not cosmetic. It is what makes the Search Console report genuinely useful, because you can submit each child file separately and see indexation rates per content type. Discovering that 98 percent of your service pages are indexed but only 40 percent of your product pages are tells you exactly where to work. A single combined file hides that entirely.

Image sitemaps list the images associated with each page and can help image discovery on sites where photography is commercially important, such as interior design portfolios (see our interior design case study), food businesses and property listings. Video sitemaps do the same job for hosted video and matter mainly if video is genuinely central to your offer. Most Singapore SMEs do not need either, and adding them because a checklist said so adds maintenance for negligible return.

The case worth special attention locally is bilingual and multilingual sites. Plenty of Singapore businesses publish an English site alongside a Simplified Chinese version, and some add Malay or Tamil pages for public facing services. Bilingual search behaviour is strong in food and beverage in particular, where a diner may search in English and a parent may search the same dish in Chinese, a pattern we work with constantly in restaurant SEO. The correct technical handling is hreflang annotation, which is a set of tags telling search engines that two pages are language variants of the same content rather than duplicates. Hreflang can be declared inside the sitemap, which is often cleaner than adding tags to every page head, particularly when the two language versions are managed by different people. The rule to remember is that hreflang must be reciprocal: if the English page points to the Chinese one, the Chinese one must point back. One directional hreflang is ignored, and we find it broken more often than we find it working.

The Mistakes We See Most Often in Singapore Audits

Submitting a sitemap that no longer matches the site. A redesign happens, the address structure changes, and the sitemap is regenerated but the old one is still submitted in Search Console. Two files, one accurate, one full of 404s.

Blocking the sitemap in robots.txt. Usually collateral damage from a broad disallow rule written to block a folder. The crawler is told the file is off limits, then the site owner wonders why nothing was discovered.

Including every paginated archive page. Page two, page three and page forty of a blog archive rarely deserve indexation and almost never rank. They bulk out the file and drag the indexed percentage down.

Leaving out the pages that matter most. The commercially critical page is frequently the one built outside the normal template, and it is exactly the one the plugin does not pick up.

Treating the file as a one time task. A sitemap is a live representation of a live site. It goes stale the moment the site changes.

Chasing a 100 percent indexation rate. This is the one that costs the most time for the least return. On a healthy site with a clean file you should expect a high rate, but a handful of excluded pages is normal and not a defect. Most agencies will sell you a project to fix it. In our experience, the three pages that never index on a 200 page site are almost always three pages that should not have been published in the first place, and the correct fix is to delete or merge them.

Field notes: The sitemap faults we see most often follow a redesign: the file is generated correctly at launch and then never checked again while pages are published, unpublished and renamed underneath it. In our B2B e-commerce case study, a wholesale kitchenware supplier in Ubi, the single catalogue was rebuilt into 14 category pages and 6 industry vertical pages, and the sitemap was rebuilt to include all of them as part of the technical work. All 14 category pages and 6 vertical pages were indexed in Months 1 to 3, and monthly trade enquiries grew from 5 to 28 by Month 8. Whenever your site structure changes, your sitemap has to change with it.

Our Take

An XML sitemap is not a growth lever and should never be sold as one. It is a discovery aid for pages your internal linking fails to reach, and a diagnostic instrument that turns a vague sense that Google is not seeing your site into a specific, countable list of pages with reasons attached. Treated that way, the ten minutes a month it costs you is among the best value technical work a Singapore SME can do. Treated as a ranking tactic, it will disappoint you.

Generate the file with your platform rather than by hand, exclude everything you do not want indexed, submit it to Search Console and Bing, reference it in robots.txt, and then actually open the report. If the submitted and indexed numbers diverge, the answer to why is already sitting in the Pages report waiting for you. If you want a second pair of eyes on what your file is currently telling Google, that is exactly the kind of question our SEO audit and consulting engagements are built to answer, and the findings usually cost far less to fix than owners expect.

Frequently Asked Questions

Do I really need an XML sitemap if my site only has eight pages?

Strictly speaking, no. A small site with a clear navigation menu will be crawled fully without one, because every page is reachable by following links. That said, the file costs nothing on any modern platform and it unlocks the Search Console sitemap report, which tells you how many of your pages are actually indexed. For eight pages that report takes thirty seconds to read and can surface a problem you would otherwise never notice. We recommend having one regardless of size.

How often should I resubmit my sitemap to Google?

You should not need to resubmit at all. Once a sitemap is submitted, Google rechecks it periodically on its own schedule, and a correctly configured platform updates the file automatically whenever you publish or unpublish. The only times resubmission makes sense are when the sitemap address itself changes, or when you have made a large structural change and want to prompt a recheck. Repeated resubmission of an unchanged file achieves nothing.

Why does Search Console say pages are discovered but not indexed?

This usually means Google found the address in your sitemap but has not spent crawl capacity fetching it, often because the site has many pages relative to its authority, or because similar pages already in the index did not perform well. It is most common on large e-commerce catalogues. The fix is rarely technical. It is usually about reducing the number of near identical pages and strengthening internal links to the ones that matter commercially.

Should my Singapore site have separate sitemaps for English and Chinese pages?

You can split them, and on larger bilingual sites it helps you see indexation rates per language. The more important point is hreflang annotation, which tells search engines the two pages are language variants rather than duplicates. Declaring hreflang inside the sitemap is often tidier than adding tags to every page, particularly when different team members maintain each language. Whichever method you choose, the references must point both ways or they are ignored.

Can a sitemap hurt my SEO?

Not directly, but a bad one wastes crawl effort and destroys the file’s diagnostic value. Listing redirected addresses, 404 pages, noindexed pages and staging URLs teaches the crawler that the file is unreliable and makes the indexed versus submitted comparison meaningless. It will not trigger a penalty. It will quietly stop you from spotting real problems, which in practice costs more.

What is the difference between an XML sitemap and an HTML sitemap?

An XML sitemap is written for machines and lives at a fixed address for crawlers to read. An HTML sitemap is a normal web page listing links to your content, written for humans, usually linked from the footer. They serve different purposes and neither replaces the other. HTML sitemaps are genuinely useful on large sites with deep structures, because they create real internal links that pass authority, which an XML file does not do.

Does the lastmod date in my sitemap matter?

Yes, provided it is truthful. Google uses lastmod as a hint about whether a page is worth recrawling. The problem is that many setups rewrite the date whenever anything touches the database, including plugin updates that change nothing visible. If every page claims to have changed yesterday, the signal is discarded. Check whether your platform updates lastmod only on genuine content changes.

My developer says the sitemap is handled. How do I verify that myself?

Open your browser and go to your domain followed by /sitemap.xml, then try /sitemap_index.xml and /wp-sitemap.xml. One of them will usually load. Read through the addresses and look for anything unexpected: staging URLs, thank you pages, old blog tags. Then check Google Search Console to confirm a sitemap is actually submitted there. Those two checks take five minutes and require no technical skill.

Should out of stock products stay in my sitemap?

It depends on whether the product is coming back. If stock is temporarily unavailable, keep the page live and in the sitemap, because it has accumulated history and links. If the product is permanently discontinued, redirect it to the closest alternative or the parent category and remove it from the file. Repeatedly adding and removing the same addresses is the pattern that causes the most confusion in the indexation report.

Is there a limit to how many pages a sitemap can list?

A single sitemap file can hold up to 50,000 addresses or 50MB uncompressed, whichever is reached first. Beyond that you need multiple files joined by a sitemap index. Most Singapore SME sites are nowhere near those limits, but property portals, marketplaces and large retailers do hit them. Even well under the ceiling, splitting by content type is worth doing because it makes the Search Console report far easier to act on.