Browsers are not told to stay on HTTPS

tragent reports this at the “Sign in” stage. The question there is “Can it sign in to an account?” Saved baskets, order history and returns all sit behind a sign-in wall.

Agents get through, but your store reads less clearly to them than it could. It is worth fixing once the higher-severity issues are gone.

Send Strict-Transport-Security on HTTPS responses.

Run the check that reported HSTS_MISSING again after the change. The scan needs no account; an issue found during an AI shopping test needs that test run again.

$ npx @tragent/cli scan https://your-store.com

• An agent cannot sign in on a customer's behalf

All nine stages · Every issue