Check library · Technical and crawl
HTTPS page loads insecure resources
Why it matters
Browsers block or warn on mixed content, breaking the page for some users.
What to do about it
Serve every subresource over HTTPS.
This one is reported rather than applied. It needs a judgement a person has to make, and applying it automatically would be a change to your site that nobody decided on.
How it is weighted
These are the values the scoring actually uses, not a description of them. Priority is derived from all three rather than chosen, which is why a high-impact, low-effort finding surfaces above a severe one that would take a quarter to fix.
- Severity
- high
- Impact
- 50% of the weight this category can carry
- Effort
- 30%, where 100% is a project rather than a change
- Confidence
- 80% that a hit is a real problem rather than a pattern we misread
- Area
- Technical and crawl
Other checks in Technical and crawl
criticalPage is blocked from indexingpage_noindexneeds a decisioncriticalServer errorpage_5xxneeds a decisioncriticalRedirect loopredirect_loopneeds a decisioncriticalrobots.txt blocks a page that should rankrobots_blocks_importantneeds a decisioncriticalPage is not served over HTTPSno_httpsneeds a decisionhighBroken internal linkpage_404_linkedfix writtenhighNo XML sitemap foundno_sitemapfix writtenhighCanonical points to a different pagecanonical_mismatchneeds a decision
Check your own site for this
The whole catalogue over a real crawl, in about four minutes, in your browser. No account and no card.