Chrome 154 HTTP interstitial: stop gambling on plaintext ad landings

According to Landian News, Google will strengthen “always use secure connections” from Chrome 154 in October 2026: visiting HTTP sites shows a security prompt, defaulting toward going back; users must confirm to continue. The same site won’t nag after confirmation until site data is cleared.

In one line: paid clicks are already expensive—don’t add a “Continue to HTTP?” gate.

1. What the policy does

Item	Detail (via Landian)
Milestone	Chrome 154 (from Oct 2026)
Behavior	HTTP warning; bias to return, not continue
Effect	Near-zero chance of silently loading plaintext
Memory	Per-site remember; clear data → reconfirm
Goal	Cut MITM / hijack risk on cleartext

This is harsher than a gray “Not secure” badge—it inserts a click on the critical path.

2. How overseas landings get hurt

First hop HTTP → bounce after the interstitial;
HTTPS page with HTTP assets → broken media/scripts;
Redirect chain downgrade (short link → tracker → HTTP landing);
Preview/review crawlers hitting odd failures.

3. One-week checklist

Final, display, and deep links are https://;
Every hop in short-link/tracking chains has valid TLS;
No http:// static assets (use CSP / mixed-content reports);
Form actions, pixels, tag containers on HTTPS;
HSTS on (preload carefully);
Walk the ad preview chain in latest Chrome Incognito;
Backup/parking domains also full HTTPS.

Put HTTP→HTTPS 301 at the CDN edge, not deep in the app.

4. Relation to traffic filtering

HTTPS is transport trust, not audience quality. Fix protocol first, then visitor rules.

5. Takeaways

Landian’s Chrome 154 note is a clear signal for advertisers: from Oct 2026, plaintext landings publicly punish conversion paths. A week of HTTPS hygiene beats explaining “users clicked Back.”

Further reading: Facebook vs Google Ads, Edge decision docs.