Mixed content

Why it matters

An insecure part can be changed on the way, and a script then runs on your page. Browsers therefore block it, so parts of the page can disappear or stop working. Visitors also lose the padlock.

How Snaglist checks it

This is part of the security check, a separate check next to the crawl, in Studio and Bureau, and only on a site you have verified. Snaglist only looks at what any visitor can see from outside. It never logs in, guesses no passwords and sends no attacks. It reads the homepage and lists every script, stylesheet, image and frame that is loaded over http.

Common causes

• Addresses in old content still start with http
• A theme or plugin with a fixed http address
• An external service that is only linked over http

How to fix it

1. Change the addresses to https in the content and the theme.
2. In WordPress, a search and replace in the database does that in one go.
3. Replace an external service that does not offer https.
4. Run the security check again to confirm.

How it shows in the report

In the report for your client this appears under the heading "Your secure page loads insecure parts". When everything is in order, the report says: "Everything on the homepage loads over https".