SuiteCommerce sitemaps: where NetSuite writes them and how search engines find them

NetSuite’s Sitemap Generator writes a SuiteCommerce sitemap as sitemap_<domain>_Index.xml plus numbered files in the site’s hosting root — not as /sitemap.xml — and it does not add a Sitemap: line to robots.txt. Unless you add that line and submit the index in Search Console, a search engine has no reliable way to find it.

Updated September 27, 2026 · By the SuiteAnalytics team

What the Sitemap Generator produces

By default the generator lists the home page, every commerce category and subcategory, and every item published to the web store. You can add Site Management Tools landing pages and up to 10,000 URLs of your own. Site Builder category URLs are not included unless you add them.

Following the sitemap protocol it writes one index file and one sitemap file for every 50,000 URLs, into the domain’s hosting root folder in the File Cabinet — usually Live Hosting Files. A regeneration overwrites the previous files; a failed one leaves them in place and writes an error file with a .txt extension beside the index.

sitemap_www.example.com_Index.xml
sitemap_www.example.com_1695859200_1.xml

The shape of the names: an index, then files named by timestamp and sequence.

Where you run and schedule it: Commerce > Marketing > SEO > Sitemap Generator Oracle documentation

Point robots.txt at it

Because the file is not at /sitemap.xml, the Sitemap: line in robots.txt is how crawlers find it — and the generator does not write that line. Of the six storefronts we validated our crawler against, three had no /sitemap.xml at all.

User-agent: *
Allow: /

Sitemap: https://www.example.com/sitemap_www.example.com_Index.xml

An absolute URL to the index, on the same host as the robots.txt.

robots.txt on SuiteCommerce is a file in the hosting root, not a field on the website record. The file you upload replaces the one NetSuite generates, so copy any rules you want to keep.

In NetSuite: Commerce > Hosting > Website Hosting Files, the robots.txt file in the site's hosting root folder Oracle documentation

Submit it

Oracle’s documentation says the generator notifies Google and Bing after each run. Google retired its sitemap ping endpoint in 2023 (Google Search Central), so do not rely on that for Google: submit the index file once in Search Console and in Bing Webmaster Tools, and keep the robots.txt line current.

What to check in the files

The robots.txt line points at an XML index, on the same host — not at an HTML page listing products, and not at another domain.
Every URL answers 200. A URL that answers 404 is a page you are asking search engines to crawl that no longer exists.
No item URL ends in _2, _3 and so on: that suffix means two items share a URL component — see duplicate URL component suffixes.
No /product/<id> URLs — see product id URLs.
No checkout, My Account, search-result or facet URLs: they are not pages you want ranked.
Your Site Management Tools landing pages are included, if you want them found.

Schedule the generator so the files follow your catalog: an item added after the last run is in no sitemap until the next.

Questions

Where is the sitemap on a SuiteCommerce site?: In the domain’s hosting root, named sitemap_<domain>_Index.xml, with numbered files beside it. The robots.txt Sitemap: line — which you add yourself — is where crawlers should read it from.
Why does /sitemap.xml return 404 on my SuiteCommerce store?: NetSuite’s Sitemap Generator does not write a file with that name. Point robots.txt at the index file it does write, and submit that URL in Search Console.
How many URLs can a SuiteCommerce sitemap hold?: The generator writes one file per 50,000 URLs under a single index, and you can add up to 10,000 URLs of your own on top of categories and items.