• between two calls, the session remains in memory on the server, which results in faster pages
• there is no need to manage session variables manually, making programming easier.

• For each page, it is necessary to reconnect to the database, reload the site status variables, etc.: pages take a little longer to initialize, thus increasing the load on the database server.
• User authentication data, as well as the current session must be kept in the "AWP context" using the WLanguage DeclareAWPContext function. Some complex variables require data serialization, which makes processes even slower.
• As each page has its own accessible address, it is difficult to secure "private" pages within the site. It is therefore necessary to check if a user is logged in and if they are granted access to the page.

Overview

1. Changing the type of site.
2. Choosing the pages that will be SEO-ready.
3. Deleting the AWP context management code.
4. Choosing the images that will be SEO-ready.
5. Modifying the URL generation code.
6. Deleting the connection verification code.

1. Changing the type of site

1. Open the project description window. To do so, go to the "Project" tab, "Project" group, and click "Description".
2. In the "Project" tab of the project description window, in "Type of site", select "Session".
   
3. On the "Advanced" tab, make sure the "Don't disconnect inactive users" option is unchecked. This option is not compatible with pages in SEO-ready session mode.
4. Validate the project description window.

2. Choosing the pages that will be SEO-ready

• all the pages of the store must be directly accessible and be SEO-ready.
• this is not the case for the pages of the "CustomerSectionPage" internal component since it is a private part of the site. This part of the site must be accessible to users only after they log in.
• the pages of the "EcommercePage" internal component make up the conversion funnel (pages used to manage the shopping cart and checkout). Likewise, there is no need to make these pages SEO-ready.

1. Display the page description window: under the "Page" pane, in the "Description" group, click on "Description"..
2. In the "General" tab:
   • Select the page type: "Session".
   • If the page is SEO-ready, check "SEO-ready". If necessary, change the name to be used in the URI.
     
3. Validate.

3. Deleting the AWP context management code

1. The context is initialized with ConfigureAWPContext. For example:
   

   // Declare an AWP context
   ConfigureAWPContext(ctxDisk, ctxIDCookieURL)

2. The variables to be stored in the AWP context are specified with DeclareAWPContext.
   

   // Is there a logged-in client? 
   DeclareAWPContext(gnCurrentClient)

4. Choosing and configuring the images that will be SEO-ready

1. The Image control should not use any compatibility mode. To check the Image control mode:
   • Open the Image control description window.
   • On the "Details" tab, go to the "Compatibility mode" option and change it, if necessary. This option must be set to "None".
2. If the Image control uses a specific display mode (stretched, homothetic, etc.), the browser must calculate the image to make it SEO-ready. Conversely, to prevent an image from being SEO-ready, it must be calculated by the server in the current session.
   • If necessary, open the Image control description window.
   • On the "General" tab, check the image display mode used. If necessary, change the image transformation mode so that the image is transformed on the browser side.

• Image calculated on the server side: The image must be assigned to the control by specifying the path to the image file on disk. To get the image directory, use fDataDir or fWebDir.
  Reminder In this case, the image will not be searchable, as it is calculated by the server in the current session.
• Image calculated on the browser side: The image must be assigned by specifying the URL. You can use:
  • an absolute URL. An absolute URL is a URL that starts with "http://", "https://" or only "://" (to use the same protocol as the page).
  • a relative URL. In this case, WEBDEV interprets the URL as relative to the "_WEB" directory of the project. The images must therefore be stored in this directory (or in a subdirectory).
    In a multilingual application, you can have an image subdirectory per language.

5. Modifying the URL generation code

sLink is string = gsURLPageViewProduct +"?P1="+ nProductID + ...
	"&P2="+nProductVariationID+["&"] + IdentifierAWPContext()

• The IdentifierAWPContext function no longer serves a purpose.
• The identifier of the current session is still required. If this identifier is not present in the URL, a new session will be created on the server.

• a first part automatically stored and transferred in a cookie,
• a second part stored in the URL, in a parameter named "REFID". To stay in the same session, this parameter must not change.

• check if the code contains page URLs built programmatically. Here are the most common cases:
  • a value is assigned to the URL property of certain controls (TreeView, Link, etc.).
  • the code of the Breadcrumb control is specified.
  • call to WLanguage function ScriptDisplay.
  This code must be modified to use PageAddress.
• make sure that the links built lead to "SEO-ready" pages.
  For a page that does not have the "searchable" property activated, access to the page cannot be via a link: it must be made via the PageDisplay function.

6. Deleting the connection verification code

IF bIsLoggedIn() = False THEN
	ScriptDisplay(gsURLLoginPage)
END