Technical audits for SuiteCommerce and SuiteCommerce Advanced
What Google sees on your SuiteCommerce storefront — with the evidence.
We crawl your storefront the way a search engine and a shopper each see it, score it across 6 dimensions — SEO, Exposure, Content, Performance, Accessibility and Platform — and tie every finding to the page, selector or configuration path behind it.
An excerpt from an audit of a storefront we built ourselves, so nothing here belongs to a customer.
84 / 100Overall
SEO64 / 100
46 checks ran · 17 could not
Exposure80 / 100
21 checks ran · 6 could not
Content100 / 100
21 checks ran · 4 could not
Performance98 / 100
13 checks ran · 0 could not
Accessibility93 / 100
10 checks ran · 0 could not
Platform95 / 100
40 checks ran · 12 could not
ErrorSEO
Pages served without prerendering
60 pages were served without prerendering: no version header and no generator body class; no page in this crawl carried either stamp, so this is how the site is served rather than a transient miss. A search engine asking the same way receives the empty shell.
The affected routes as a search engine requests them: the views they render in the generator pass — the theme’s, an extension’s or core’s — and NetSuite support if a bot user agent still receives the shell
How search engines read and index your storefront.
Every indexable page has a non-empty <title>
No two indexable pages share one <title>
Titles are at most 65 characters
63 checks in the sample audit
Exposure
What your storefront reveals to anyone who looks at it.
No secret-shaped value in the public configuration
No credential-shaped value in the public configuration needs review
Public-by-design keys in the configuration are inventoried
27 checks in the sample audit
Content
The titles, descriptions and copy on your item and category records.
Every sampled web-store item carries a Page Title
No two sampled items share a Page Title
Every sampled web-store item carries Meta Tag HTML
25 checks in the sample audit
Performance
How much a visitor downloads before the page is usable.
The JavaScript and CSS a first visit downloads
The compiled templates bundle
The stylesheet a first visit downloads
13 checks in the sample audit
Accessibility
Whether somebody using a screen reader or a keyboard can shop.
The viewport does not ask browsers to forbid zooming
Critical-impact accessibility violations
Serious-impact accessibility violations
10 checks in the sample audit
Platform
The SuiteCommerce release, theme and extensions underneath the site.
The target is a SuiteCommerce storefront
The SSP application is within a year of the current release
The release could be pinned from the served site
52 checks in the sample audit
How it works
From a URL to a fix list
1
Pre-check any storefront
Type an address at the top of this page. We read the page shoppers already receive and tell you the platform, the release and the theme. No account, and no load on the site.
2
Verify your domain
Prove the storefront is yours with a DNS record, a tag in the head, or an email address on its own domain. That is what separates an audit from a stranger crawling a site.
3
Run the audit
Quick, standard or deep — about 9 pages, 60 or 300. One quick audit every 7 days is free.
4
Fix, then re-check
Findings say where in NetSuite to fix them. Pro, Enterprise and Partner re-audit weekly, compare two audits and email you when something regresses.
What makes it different
Three promises, and the proof
Every finding cites its evidence
A finding names the page, the selector or the configuration path it came from. A defect we cannot attribute to your theme, an extension or the platform is reported as unattributed rather than blamed on a guess.
From an example audit
Plain HTTP does not redirect permanently to HTTPS
Site › host → "www.deep-synthetic.example"
A check that could not run is never a pass
When a page was unreachable or a bundle would not parse, the report says which check was skipped and why. A clean score on an audit that could check nothing is the one result this tool will not produce.
From an example audit
RELEASE_METADATA carries no ns_version; the account version cannot be compared against the cached environment
We never keep your keys
Your SC.CONFIGURATION ships to every visitor and often carries third-party API keys. We report the path, the length and the shape so you can rotate it. We do not store the value.
From an example audit
15 configuration leaves, 0 secret-shaped (0 by value format, 0 by key name), 0 candidate, 0 public key
Who it is for
Built for the people who answer for the storefront
You run a SuiteCommerce store
Verify your domain, audit it free, and hand your team a fix list: each item cites where it was found, and says where in NetSuite to change it when the fix lives there. Upgrade for the full report, history and weekly re-checks. Pro adds 1 sandbox to each domain: audit the next release there and see what it introduces and fixes before it ships.
Enterprise covers 3 domains, each with a sandbox, with pooled credits and the public API. Or apply as a partner to audit client and prospect storefronts from one pooled balance, within a daily and monthly new-domain limit.
Technical SEO for NetSuite SuiteCommerce and SCA: prerendering, sitemaps, URLs and canonicals, titles and meta descriptions, structured data, facets and SCA vs SCS.
How NetSuite’s SEO Page Generator serves SuiteCommerce pages to search engines, what Prerender V2 changed in 2026, and how to check what a bot actually receives.
Why Google does not index SuiteCommerce pages, in the order to check: robots.txt, prerendering, noindex, canonicals, the sitemap, internal links and duplicate URLs.
How NetSuite’s Sitemap Generator names and places a SuiteCommerce sitemap, why there is often no /sitemap.xml, the robots.txt line you have to add yourself, and what to check in the files it writes.
Audit the storefront on your NetSuite sandbox, compare it with production, and read what the release introduces, what it fixes and what cannot be compared — before shoppers see it.
Or go straight to the checks library: each thing an audit looks for, and the NetSuite field that fixes it.