Pages served to search engines without prerendering
A SuiteCommerce page that is not prerendered reaches a crawler as the application shell: a 200 response with <title></title>, no canonical link and an empty main area, because all of those are written by JavaScript the crawler does not run. The check fetches each sampled page as a crawler, asks a shell response a second time, and reports the pages that stay unprerendered.
Updated · By the SuiteAnalytics team
What we detect
A prerendered page carries the header x-prerender-version: V2, a real title, a canonical link and the page content. We report a page when the response is the shell instead — and only after asking again, because the same URL can come back as the shell once from a cold cache and prerendered the next time. A shell that turns into a prerendered page on the second request is reported as a transient, not a defect.
Why it matters
To a crawler that does not render JavaScript — most of them, including the fetchers answer engines use — every shell page is the same blank document: no title to show, no canonical to consolidate duplicates, nothing to index. Google may render it later, on its own schedule, and sees the page only if the render completes.
How to fix it
- Open one of the pages named in the report with
?seodebug=Tin a logged-out session and read the generator’s debug log at the end of the page source. - Fix the JavaScript errors it lists — most come from extension bundles — and exclude scripts that never settle (chat widgets, trackers) from the generator pass.
- If the log is clean and the shell is still served, raise a case with NetSuite Support with the URLs, times and response headers: the generator is NetSuite’s service.
- Re-run the audit and confirm the pages come back prerendered.
The SEO Page Generator guide walks through the debug log.
Questions
- Why does my SuiteCommerce page have an empty title in the page source?
- The source you are reading is the application shell. The title is set by JavaScript in the browser, and a crawler receives it only when the SEO Page Generator prerendered the page.