HTTPS

HTTPS in plain English

HTTPS is the secure version of HTTP, the protocol browsers use to load web pages. It encrypts data between the visitor and your site using a TLS certificate, shown as a padlock in most browsers. Google announced in 2014 that HTTPS is a lightweight ranking signal, and browsers now warn visitors when sites aren't secure.

How to check HTTPS on your site

Visit your site with "http://" at the start and check you're sent straight to "https://". Look for the padlock on several pages, especially forms. Mixed content warnings, where an HTTPS page loads HTTP images or scripts, show up in the browser's developer console. Make sure your sitemap and canonical tags use HTTPS URLs.

A worked example

A small B&B's site still loads on HTTP, and Chrome shows a warning beside its booking form. The host enables a free certificate, the developer sets up 301 redirects from every HTTP URL to its HTTPS version and updates internal links. The warning disappears and bookings feel safer.

Where it usually goes wrong

• Leaving HTTP pages accessible without redirects.
• Letting certificates expire.
• Mixing HTTP and HTTPS internal links.
• Forgetting to check the HTTPS version is the one indexed in Search Console.

Why a small site should care

Visitors are wary of "Not secure" warnings, especially on pages with forms. HTTPS is expected for any site in 2026, and most hosts provide free certificates. The SEO risk comes during the switch: if HTTP pages aren't redirected properly, you can lose rankings and links.

For any site that takes enquiries, bookings or payments, it's also about trust and data protection. Visitors expect their details to be sent securely, and browsers make the lack of it obvious.

Connected technical terms

• Site migration: Moving URLs, hosts or platforms while preserving search equity.
• Redirect: Sending users and crawlers from one URL to another.
• UX and SEO: Overlap where usability, speed and clarity support search performance.