Indexability and crawling

How to fix mixed content warnings

These secure pages load images, scripts, or stylesheets over plain http. Browsers block or downgrade those requests, so parts of the page may not appear, and the padlock is lost.

What it is, and what it costs

Mixed content is an https:// page pulling resources from http://. Browsers flag the page as not fully secure and often refuse to load the insecure parts, which can break layout or functionality. It undermines the trust signal HTTPS is there to provide.

How to fix it

Change every resource URL on the page to https:// (or protocol-relative //), so everything loads securely.

  • WordPress: a search-replace plugin, or Really Simple SSL, rewrites old http:// asset URLs across the database.
  • Hand-coded: update the src and href of images, scripts, and stylesheets to https.

How to check your site

Open the page and watch the browser console for "mixed content" warnings, or look for a broken padlock in the address bar.

Questions people ask

Why did this appear after moving to HTTPS?
Migrations often leave old hard-coded http:// asset URLs behind. A site-wide search-replace is the usual cleanup.

Does your site have this?

Check your site to find secure pages loading insecure resources.

See also

All SEO checks →