Why this matters
That "Not Secure" warning scares customers off before they read a word — many assume the site is broken or unsafe and leave. AI assistants also prefer secure sites; some won't even crawl an HTTP-only site. This is the single most urgent fix on your report: it affects every visitor, not just AI.
Who fixes this
This is a hosting fix, not a website-content fix — you don't do it in your page editor. Who you call depends on your platform:
Wix, Squarespace, or Shopify
HTTPS is supposed to be automatic on these platforms. If it's not working, something is misconfigured — contact their support directly and say: "HTTPS isn't working on my site — my visitors see a Not Secure warning. Can you fix my SSL certificate?" They'll sort it out; it's their infrastructure.
WordPress (or any other host)
Call or chat with your hosting company (the company you pay for web hosting — e.g. Bluehost, GoDaddy, SiteGround) and say exactly this:
"Hi — my website doesn't have HTTPS working. Could you install a free SSL certificate on my site and set it to redirect all HTTP traffic to HTTPS? My visitors are seeing a Not Secure warning."
Most hosts do this free and take a few minutes. The SSL certificate itself is free (via Let's Encrypt) — if a host tries to charge you a large fee for it, that's a red flag; consider switching hosts.
After it's fixed
Visit your site and check the browser address bar shows a padlock (no "Not Secure" warning). Then run a new CrawlReady scan — it will scan the secure version and the flag will clear.