SEO Page Generator Debug Log

This topic applies to

Applies to

Commerce Web Stores

 

The SEO page generator gives you a comprehensive logging feature that lets you analyze page generation data. The log includes memory and CPU usage data for tracking resources. It also includes all subrequests produced by the SEO page generator.

Note

The following procedures are for testing your website on a public domain. You cannot view the website on a local host environment when JavaScript is disabled.


To view the debug log provided by the SEO page generator:

  1. Go to your website home page, for example, http://www.mywebstore.com.

  2. Right click on the page and click View page source.

  3. Modify the URL of the page by appending ?seodebug=T at the end of the URL and then reload the page.

    For example, modified URLs look similar to the following:

    view-source:www.mywebstore.com/?seodebug=T
    view-source:www.mywebstore.com/Salida-Backpack?seodebug=T
  4. Scroll down to the bottom of the source code to view the debug log generated by the SEO page generator.

    A debug log looks similar to the following:

    [05:37:52.328] [ +2290 ms ] Got a response from Prerender
    [05:37:52.331] [    +3 ms ] Memory usage:      14.355469MB
    [05:37:52.331] [    +0 ms ] CPU usage:         0.280000s
    [05:37:52.331] [    +0 ms ] Sub request total: 1.494000s
    [05:37:52.331] [    +0 ms ] Details of 8 sub requests:
                   GET http://www.mywebstore.com/shopping.environment.ssp?lang=en_US&cur=null&X-SC-Touchpoint=shopping&t=1491975947658  [status 200]
                   Requested at 2017-05-30T12:37:50.393Z and responded by 2017-05-30T12:37:51.199Z (which took 806ms)
                   GET http://www.mywebstore.com/languages/shopping_en_US.js?t=1491975947658  [status 200]
                   Requested at 2017-05-30T12:37:50.394Z and responded by 2017-05-30T12:37:50.690Z (which took 296ms)
                   GET http://www.mywebstore.com/javascript/shopping.js?t=1491975947658  [status 200]
                   Requested at 2017-05-30T12:37:50.394Z and responded by 2017-05-30T12:37:51.197Z (which took 803ms)
                   GET http://www.mywebstore.com/cms/2/assets/js/postframe.js  [status 200]
                   Requested at 2017-05-30T12:37:50.395Z and responded by 2017-05-30T12:37:50.995Z (which took 600ms)
                   GET http://www.mywebstore.com/cms/2/cms.js  [status 200]
                   Requested at 2017-05-30T12:37:50.395Z and responded by 2017-05-30T12:37:50.792Z (which took 397ms)
                   GET http://www.mywebstore.com/api/cms/session/domain  [status 200]
                   Requested at 2017-05-30T12:37:51.390Z and responded by 2017-05-30T12:37:51.489Z (which took 99ms)
                   GET http://www.mywebstore.com/api/cms/versions?site_id=2&c=420420  [status 200]
                   Requested at 2017-05-30T12:37:51.492Z and responded by 2017-05-30T12:37:51.589Z (which took 97ms)
                   GET http://www.mywebstore.com/api/cms/pages/contents?c=420420&n=2&page_type=home-page&path=%2&c=420420  [status 200]
                   Requested at 2017-05-30T12:37:51.593Z and responded by 2017-05-30T12:37:51.692Z (which took 99ms)
    

If the website page view that you are investigating is served from cache, the entire debug log is not displayed. In this case, you might see a truncated output similar to the following:

Parameter from url: seodebug=T: 
[23:03:05.713] [    +8 ms ] Requested URL with SEO generator relevant params: http://www.mywebstore.com/?seodebug=T
[23:03:05.713] [    +0 ms ] Source URL: http://www.mywebstore.com/shopping.ssp?seodebug=T
[23:03:05.713] [    +0 ms ] Rewrite Path: /s.nl?sitepath=/shopping.ssp
[23:03:05.723] [   +10 ms ] SEO generator page taken from cache: com.netledger.app.site.ignite.cache.NLIgniteResponseCacheEntry@5430dc72

To generate the debug log when the page is served from cache:

  1. Go back to the website page view that you are investigating.

  2. Add the preview parameter with a unique number at the end of the page view URL and reload the page. The intention here is to give the browser the illusion that it is loading a unique page.

    For example, modified URL look similar to the following:

    http://www.mywebstore.com/Salida-Backpack?seodebug=T&preview=1234

  3. Right click on the page and click View page source.

  4. Scroll down towards the bottom of the source code to see the entire debug log provided by the SEO page generator.

Note

A subsequent request to the same URL is served from cache.