ubricHelp

What is an HSTS header and do you need one?

Rubric check: missing HSTS header (check id hdr_hsts)

An HSTS header (Strict-Transport-Security) tells browsers to use https for your site every time, even if someone types or clicks an http:// link. Without it, a visitor's first request can still go out over plain http. It's a security step, not a search factor. Response headers are set once for the whole site, in your server, host or CDN settings (on Cloudflare, a Transform Rule), so this is one site-wide fix, not a page-by-page one.

Free, no card. Your report opens with this check first.

Why it matters for SEO

Google and Bing don't rank pages on this header. What they do care about is https itself: Google prefers https URLs, and a site that redirects every http address to https already covers most of the search benefit.

HSTS adds protection for visitors on public Wi-Fi, where that first unencrypted request can be intercepted.

Does this matter for ChatGPT and AI Overviews?

There's no public evidence that ChatGPT, AI Overviews or other AI tools check for HSTS before citing a page. They fetch your pages over https either way.

Rubric includes this check as a small sign of a maintained site, inside a capped allowance shared with the other security header checks.

How Rubric scores it

MinorMinor checks cost a quarter to a half of a standard check when they fail.

Why this tier: A security step that keeps every visit on https; not a search factor.

It is read from your home page's response headers, and compared with a few other pages the crawl already fetched. Headers are set once for the whole site, so this is a site-wide finding.

Every Rubric score starts at 100. When this check fails, it takes up to 3 points off. Even one failing page costs at least 1.5 points (half of the most), and the rest comes off as the share of affected pages grows. A warning costs less than a failure.

This is one of 4 security header checks. Together they can take off at most 9 points, so a site isn't marked down many times for one kind of problem.

All the minor checks share one limit: together they can take off at most 25 points, however many of them fail.

This check doesn't cap your score. It only takes off its own points.

From the engine's scoring files, scoring 2026-v2.1 (engine d5c591d).

How common it is

Found on 97 of 300 sites where Rubric could judge it (32%). That is 89 of 287 judged sites in Rubric's 313-site test set and 8 of 13 sites audited on Rubric between 11 Nov 2026 and 17 Nov 2026 under the current check rules (scoring 2026-11k or later). Measured 17 Nov 2026 with scoring 2026-v2.1.

32% of the sites Rubric could judge have this problem. Check yours.

Free, no card. Your report opens with this check first.

How accurate the check is

Lab test: passed. On test pages built with this problem, it caught 3 of 3. On clean test pages, it stayed quiet 2 of 2 times. (Engine build bbcec7c.)

Real sites: people checked 11 of its findings by hand and 1 was wrong (9.1%). Last checked 14 Nov 2026. That's a small sample, so treat the rate as rough.

Holdout test 5 (sites the check had never seen): 0 of 32 findings judged wrong.

Lab as of 16 Nov 2026; judged findings as of 15 Nov 2026.

How to fix it

WordPress

  1. First make sure every page loads on https and http redirects to https. Many hosts have a Force HTTPS switch in their control panel.
  2. Add the header with a security headers plugin, your host's control panel, or on Apache with this line in .htaccess: Header always set Strict-Transport-Security "max-age=31536000"
  3. Clear any page cache and re-run the audit.

Behind Cloudflare? Set it once there instead, for every page at the same time: see the Cloudflare steps under Custom code.

Shopify

Shopify serves every storefront over https and sets the response headers itself, and you can't add your own. If Rubric reports this on a Shopify store, check whether a proxy or CDN on your domain sits in front of Shopify and drops the header. If nothing does, there's no setting to change.

Webflow

Webflow hosting serves sites over https and sends the HSTS header on hosted sites. Extra options for subdomains and preload sit in Site settings > Publishing > Advanced publishing options. Only turn those on if every subdomain works on https. If Rubric still reports it, check for a proxy in front of Webflow, or ask Webflow support.

Custom code

Send it on https responses, once every page works on https. Nginx:

nginx
add_header Strict-Transport-Security "max-age=31536000" always;

Start with a shorter max-age (for example a day) if you're unsure. Add includeSubDomains only when every subdomain supports https.

On Cloudflare (one rule covers every page):

  1. In the Cloudflare dashboard, open your domain and go to SSL/TLS > Edge Certificates.
  2. Under HTTP Strict Transport Security (HSTS), select Enable HSTS.
  3. Pick a short Max Age first, leave subdomains and preload off unless every subdomain works on https, and save.
  4. Re-run the audit.

More security checks · The full AI SEO glossary

Free, no card. Your report opens with this check first.