SuiteCommerce pages not indexed: a troubleshooting checklist
When SuiteCommerce pages are not indexed, the cause is usually one of seven things: robots.txt blocks them, the crawler receives the unprerendered shell, a noindex reaches the page, the canonical points elsewhere, the sitemap is missing or undiscoverable, nothing links to them, or they are duplicates of another URL. Check them in that order — each one hides the ones after it.
Updated · By the SuiteAnalytics team
1. Is the page allowed?
Open /robots.txt on the domain and test the URL against it. On SuiteCommerce the file is not a setting: it is a file in the site’s hosting root, and a file you upload replaces the one NetSuite generates. A rule written for another domain, or for a development site, is a common way for a whole path to disappear.
Where the file lives: Commerce > Hosting > Website Hosting Files, the robots.txt file in the site's hosting root folder Oracle documentation
2. Does the crawler receive the page, or the shell?
Request the URL with a crawler’s user agent and read the raw HTML. A prerendered page carries x-prerender-version: V2, a real <title> and a canonical link. The application shell carries an empty title and no canonical — to a crawler that does not run JavaScript it is a blank page.
Ask twice before concluding: the prerendered copy is cached, and the same URL can come back as the shell once and prerendered the next time. See the SEO Page Generator guide for reading its debug log.
3. Does a noindex reach the page?
SuiteCommerce core ships no robots meta tag on storefront pages. On SuiteCommerce Advanced releases before 2019.2, Oracle documents a defect: when prerendering failed, the noindex,nofollow tag in shopping.ssp was not removed, so those pages were dropped. Oracle publishes a patch for those releases, and 2019.2 and later are fixed.
On a current release, a noindex comes from something added to the site — a theme template, an extension, or an "add to head" field on a Site Management Tools page or a commerce category. Look at the prerendered HTML, not the page in a browser.
4. Does the canonical point somewhere else?
A canonical asks search engines to index another URL instead. Two SuiteCommerce patterns to look for: a canonical on another host — a sandbox or a retired domain, see cross-host canonicals — and category canonicals that carry ?page=1, observed on SuiteCommerce Standard.
Category and facet canonicals are built from the category’s canonical field or its full URL plus the facets in sorted order; a Site Management Tools page can override the canonical of the route it decorates.
5. Is the page in a sitemap search engines can find?
NetSuite’s Sitemap Generator does not write a /sitemap.xml: its index is named after the domain, and it does not add the Sitemap: line to robots.txt. A search engine not told where the sitemap is has no way to guess. See sitemaps on SuiteCommerce.
6. Does anything link to the page?
A page nothing links to is found only through the sitemap, and ranks accordingly. Two SuiteCommerce behaviors remove links on purpose: Facets SEO limits drop links to facet combinations beyond the configured depth in the prerendered page, and hidden categories drop out of the navigation. Menu entries that lead to an error page waste the links you have.
7. Is the page a duplicate of another?
- Items published at
/product/<id>because their URL component is empty — see product id URLs. - Items whose URL component collides with another, published with a
_2suffix — see duplicate URL component suffixes. - Categories titled with their breadcrumb because the Page Title is empty — see categories with no Page Title.
- Product pages with no meta description because Meta Tag HTML is empty — see Meta Tag HTML.
Confirm what Google decided
Search Console’s URL Inspection shows whether a URL is indexed, which canonical Google chose, and — with the live test — the HTML Google’s renderer received. Compare it with the prerendered HTML you fetched in step 2.
Questions
- Why is my SuiteCommerce site not showing up on Google at all?
- Start with robots.txt on the domain — an uploaded file replaces NetSuite’s — and then fetch the home page with a crawler user agent. A blocked path or an unprerendered shell explains a whole site; the other causes usually explain some pages.
- Does SuiteCommerce add noindex to pages?
- Core ships no robots meta tag on current releases. SuiteCommerce Advanced releases before 2019.2 could leave
noindex,nofollowin place when prerendering failed; Oracle publishes a patch. A noindex on a current site comes from a theme, an extension or a head field.