Serve your site over HTTPS
Your page is served over plain HTTP. Every mainstream crawler treats HTTPS as a baseline quality signal, browsers warn users away from insecure pages, and AI assistants rarely cite HTTP sources. In 2026 this fix is free and usually takes under an hour.
Why do AI systems care about HTTPS?
Trust filtering. Systems choosing which sources to quote apply cheap quality gates first, and “is the connection secure” is the cheapest gate there is. An HTTP-only site signals unmaintained infrastructure - exactly what answer engines screen out.
How do you enable HTTPS?
Modern hosting makes it nearly automatic:
- Managed hosts and platforms (Netlify, Vercel, Shopify, Squarespace, WordPress.com) provision certificates automatically - check your domain settings and toggle it on.
- Self-managed servers can use Let’s Encrypt with certbot for free auto-renewing certificates.
- Behind a CDN like Cloudflare, enable “Full (strict)” TLS so the connection is encrypted end to end, not just to the edge.
What must you do after enabling it?
Redirect and update. Add a 301 redirect from http:// to https:// for every URL, update your canonical tags and your XML sitemap to the https versions, and fix any hard-coded http:// asset links to avoid mixed-content warnings. Then rescan - the secure versions of your pages inherit all your existing signals through the redirects.
See where your site stands. The free scan takes about fifteen seconds and shows every fix.
Run a free AI visibility scan