Security & HTTPS
Pages served over HTTP
One of the 136 checks Lala SEO runs on every page of a site in a free audit.
- How serious
- Serious. Can stop pages from appearing in Google, or from working for visitors. Fix these first.
- Based on
- Industry standard: Google does not document this one, so the check follows established practice.
What is wrong
Your website is serving pages over HTTP (the unsecured version of the web protocol) instead of HTTPS (the secure version). This means the connection between your visitors' browsers and your server is not encrypted, leaving data vulnerable to interception.
Why it costs you
Google's Chrome browser now marks HTTP sites as "not secure" to visitors, which damages trust and can cause people to leave before they even see your content. Search engines also treat HTTPS as a ranking signal, so HTTP pages are at a disadvantage compared to secure competitors.
How to fix it
You need to obtain an SSL certificate (many hosting providers offer these free) and configure your server to use HTTPS for all pages. Then set up redirects so that any HTTP URLs automatically send visitors to the HTTPS version. This should be done in your server configuration or hosting control panel, not page by page. After the redirects are live, update any internal links in your site templates and navigation to point to HTTPS URLs directly.
What the audit tests
- The page address uses HTTPS rather than plain HTTP
Check your site
Run a free audit of up to 300 pages. No card needed.
Start a free auditOr check a single address with the free tool.
Other security & https checks
- Any website can display this site inside a frame
- Browsers are not told to always use HTTPS
- Forms on secure pages send their contents over plain HTTP
- Secure pages loading scripts or styles over plain HTTP
- The HTTPS certificate expires soon
- The HTTPS certificate has expired or does not validate
- The nosniff security header is not sent