NetSuite Domain-Level Redirects
When a user accesses a URL that points to a SuiteCommerce application, the URL is processed to see if there are any domain-level redirects. Domain-level redirects are configured by administrators who want to take an incoming URL and direct it to a different location. This redirect is achieved by changing the domain part of the URL, the URL path after the domain, or a combination of both. This means you can create a map between two URLs so that accessing the original incoming URL rewrites the requested URL and processes it again.
Domain-level redirects are useful if you’re migrating your website from a different platform or if you have upgraded your Commerce website application from a pre-Denali version of SuiteCommerce Advanced to a modern version. For example:
-
shopflow.example.com → shop.example.com
-
shop.example.com/my-old-landing-page → shop.example.com/my-new-landing-page
-
shop.example.com/product-that-doesnt-exist-anymore → shop.example.com
Keep in mind that the NetSuite application can only process redirects that are sent to the NetSuite sever. NetSuite domain-level redirects work if a user enters the URL into a browser address bar. But if you internally direct a user to that URL using Backbone, the server-side redirect does not trigger. For more information about domain-level redirects, see SEO and Redirects.
When a NetSuite domain-level redirect completes, the user is then directed to the correct SSP for that URL. The correct SSP is determined by the touch point you have set in the website setup record for the domain. When the user is directed to the SSP, the site’s frontend code begins to load. But, that process can be interrupted if there is a redirect in the SSP’s SuiteScript.