Matan · SEO · Technical

HTTPS

The page must be served over TLS so browsers, Google and AI crawlers treat it as a safe document.

Pass condition in our engine: The tested URL uses the https: protocol.

1. Problem description

HTTP leaves cookies, forms and URL parameters visible on the network. Chrome marks the site as “Not secure”, and search engines treat HTTPS as a ranking and trust baseline. Mixed or missing TLS also blocks modern APIs (service workers, geolocation) and HSTS.

2. Most common causes

  • No TLS certificate is installed on the origin or CDN.
  • The certificate expired or does not cover the requested hostname (www vs apex).
  • The site still answers on port 80 without a redirect to HTTPS.
  • An old origin is linked internally with http:// URLs.

3. How to fix it

  1. Issue a certificate (Let’s Encrypt, Cloudflare, or your host’s one-click TLS).
  2. Force HTTPS in the web server or load balancer (301 from http:// to https://).
  3. Update canonicals, sitemaps and internal links to https://.
  4. Enable HSTS once HTTPS is stable across the whole host.

Test this check

We fetch only this URL (plus robots.txt / llms.txt at the domain root when the check needs them). We do not crawl the rest of the site like a full report.

Scoring rules for the full site crawl are documented in methodology. Want every category at once? Generate a free report.

Get your free SEO & GEO report

Enter your URL and receive a full audit with scoring and recommendations. No sign-up required.

Generate a free reportView sample report