NetSuite Domain-Level Redirects
When someone goes to a URL for a SuiteCommerce application, the system checks for domain-level redirects. Administrators set up domain-level redirects to send incoming URLs to a different location. This redirect works by changing the domain, the path after the domain, or both. This lets you map one URL to another, so when someone visits the original URL, it gets rewritten and processed again.
Domain-level redirects help if you’re moving your site from another platform or upgrading from a pre-Denali version of SuiteCommerce Advanced:
-
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
Remember that NetSuite can only process redirects sent to its sever. NetSuite domain-level redirects work if someone enters the URL in the browser, but if you send them there internally with Backbone, the server-side redirect won't trigger. For more information about domain-level redirects, see SEO and Redirects.
When a NetSuite domain-level redirect completes, the user goes to the right SSP for that URL. The right SSP depends on the touch point you've set in the website setup for the domain. When the user goes to the SSP, the site’s frontend code starts loading, but it can be interrupted if there is a redirect in the SSP’s SuiteScript.