• Docs >
  • 5. Onboarding website checks

5. Onboarding website checks

Below are a list of checks to verify that the website works properly.

5.1. Confirm installation

  • Check that the etc/hosts is changed to point to the IP address of the server from where ShimmerCat is running. Check here for more info on how to edit your hosts file.

  • If you get the warning “Your connection is not private” when you access the site, this is because the certificate has not yet been installed. Just click “Advanced” and then choose to proceed to the site.

  • If you get “NET::ERR_CERT_AUTHORITY_INVALID”, check here.

5.2. Verify that the site works properly

  • Check that all resources of the site are properly loaded and do not show any error codes. This can be done by browsing the site while looking at e.g. style sheets, javascripts, images.

  • Double check that static assets are served as “static” or “generated” by looking at the sc-note response header that ShimmerCat produces. This check can for example be done with Dev Tools.

  • Check that the order flow works properly. Add products to the cart and proceed to make a purchase. Note that sometimes security policies on your backend, or for the payment providers, can block requests from ShimmerCat when the DNS are not pointing to our server.

  • Check that the connection to external services work properly and do not show any error statuses:

    • Payment providers, e.g. Klarna, Credit cards, Bank transfers, etc.

    • Third-party integrations, e.g. chat systems, tracking systems. etc.

    • Shipping agencies, e.g. PostNord, Schenker, DHL, UPS, etc.

5.3. Additional checks

  • If there is an Admin area, log in and check that everything works as expected.

  • Check that image and file uploads work.

  • If you have some kind of feed (e.g. price comparison, robots.txt, etc) in formats csv/txt/xml it might need some kind of special treatment and mime type from the file extension, so check that it works as expected.

  • Collect a list of the third-party integrations that the website use. If you know the IP addresses, you can inform us to whitelist them from the bot blocking mechanism, or you can use the web API if you have received your authentication token.

  • Access a page URL that does not exist and that should create a “Status 404” to verify that the 404 Error page works as expected.

5.4. Test live traffic

  • Together with the ShimmerCat team, plan a time window to drive live traffic to the edge servers. The purpose of putting the site live is to test the data collection and collect logs to check for unreported integrations and bots that might affect the site.

  • Update the DNS records to point to the edge servers with ShimmerCat, see more info here.

  • Browse the site and double check that everything works as expected.

  • Verify the certificate over Qualys SSL, see https://www.ssllabs.com/ssltest/.

  • Create a test order to verify that everything works.

5.5. Go live

  • After confirmation, update the DNS records to the edge servers with ShimmerCat, see more info here.

  • Make sure to monitor the site the first few days when the service goes online.

  • ShimmerCat will provide increased support for the first week and to help regarding this.