SuiteCommerce SEO: the technical guide for SuiteCommerce Advanced and Standard

SuiteCommerce SEO starts with one fact: the storefront is a JavaScript application, and search engines receive it through NetSuite’s SEO Page Generator. Get that right, then the rest is where SuiteCommerce keeps each signal — robots.txt and the sitemap as files in the hosting root, URLs from the item’s URL component, titles and meta descriptions from item and category fields, structured data from one configuration setting.

Updated September 27, 2026 · By the SuiteAnalytics team

What makes SuiteCommerce different

A SuiteCommerce page is assembled in the browser: the title, canonical, content and even the status code are set by the application after it loads. The SEO Page Generator runs that application on NetSuite’s side and serves the finished HTML, and since January 2026 it does so with Prerender V2. When it is not applied, a crawler receives the application shell: a 200 with an empty title and no canonical.

So the first question for any SuiteCommerce SEO problem is not "what does the page say" but "what did the crawler receive". Everything below assumes the answer is the prerendered page.

Crawling: robots.txt and the sitemap

Both are files in the domain’s hosting root. robots.txt replaces NetSuite’s generated one as soon as you upload it. The Sitemap Generator writes sitemap_<domain>_Index.xml rather than /sitemap.xml, and it does not add the Sitemap: line to robots.txt — you do. See SuiteCommerce sitemaps and robots.txt without a sitemap line.

URLs and canonicals

On SuiteCommerce Advanced a product URL is / plus the item’s URL component. An item without one is published at /product/<internal id> — see product id URLs — and two items sharing one get a numeric suffix — see duplicate URL component suffixes. On SuiteCommerce Standard the URL comes from the item’s canonical URL instead.

Category and facet pages build their canonical from the category’s canonical field (or its full URL) plus the selected facets in sorted order. A canonical on another host — a sandbox left in a field — asks search engines to drop the page: see cross-host canonicals.

Faceted navigation

Facets multiply URLs. SuiteCommerce’s Facets SEO limits control how deep a crawlable facet link may go, but only by not linking to deeper combinations in the prerendered page: nothing adds noindex, and those URLs still answer 200 if anything links to them. Decide which facet pages you want indexed and use canonicals and robots.txt for the rest.

Titles and meta descriptions

A product page’s title comes from the item’s Page Title, falling back to its store display name and then its display name.
A product page’s meta description comes only from the item’s Meta Tag HTML field, unless a Site Management Tools page supplies one.
A category page with no Page Title is titled with its breadcrumb joined by " > " — see categories with no Page Title.
A Site Management Tools page can set the title, meta description and head of the route it decorates.

Structured data and social tags

SuiteCommerce adds a Product node in JSON-LD to product detail pages when the configuration’s Markup Type is set to JSON-LD, and a page is either microdata or JSON-LD, never both — see Product structured data. Product list pages get no product markup from core.

The Open Graph price and availability tags are read from microdata in the rendered page, so a JSON-LD theme publishes them as the word "undefined" — see Open Graph price "undefined".

Multiple languages

SuiteCommerce serves each language from its own host and sets <html lang> from the current locale, but core has no hreflang mechanism. A multi-language store needs an extension or head field to declare its alternates.

Performance and accessibility

Core Web Vitals are measured on real visits, so the prerendered HTML a crawler gets is only half the story: the core bundle, every extension bundle, the templates and third-party scripts all load for shoppers. And the viewport SuiteCommerce ships forbids pinch-zoom — see the zoom lock.

SuiteCommerce Advanced vs Standard, for SEO

On SuiteCommerce Advanced you own the SSP application, the core and the theme: shopping.ssp — the viewport, the head — is yours to change and redeploy.
On SuiteCommerce Standard NetSuite owns the SSP application and core and upgrades them for you; you own the theme and the extensions. A fix in shopping.ssp is a support case.
Product URLs come from the URL component on SCA and the canonical URL on SCS.
The site-type setting does not tell them apart; the release metadata does.

Checking all of it

Each section above is one or more checks in our checks library. An audit runs them against what a crawler and a shopper each receive and ties every finding to the page, the element or the NetSuite field behind it.

Questions

Is SuiteCommerce good for SEO?: It can be. The platform prerenders pages for search engines and gives you fields for titles, meta descriptions, URLs and structured data. Most SuiteCommerce SEO problems come from those fields being empty, from pages served without prerendering, or from sitemaps search engines are never told about.
What is the difference between SuiteCommerce and SuiteCommerce Advanced for SEO?: The SEO signals are the same. What differs is who can change them: on Advanced you own shopping.ssp and the core, on Standard NetSuite does. Product URLs also come from different item fields.
Does SuiteCommerce support hreflang?: Not in core. Each language is served from its own host, and hreflang has to be added by an extension or a head field.