How to fix it
Change those references to HTTPS.
When it is not a problem
The browser console finds this faster than any crawler when you already suspect it. The value of a scheduled check is that it catches the one template that regressed while nobody was suspecting anything.
How Rankelle handles it
- SeverityWarning. It costs traffic or clarity without stopping anything, which is where most real work lives.
- DetectionDetected on a single page while crawling it, then grouped with the other pages under the same URL pattern.
- GroupingEvery page with this finding under the same URL pattern becomes one cause, with a confidence taken from how much of the pattern is affected. 400 of 400 is a template; 6 of 14 is phrased as a question.
- LandingThe affected URLs stay under cheap watch. When this finding is gone from all of them, the fix is marked landed without anyone reporting the deploy.
- VerdictAt landing, comparable untouched URLs are frozen as a control set. Twenty-eight days later the two are compared, and the fix can come back as having done nothing.
Try it on your own site, free
No card, and the free tier does not expire — the first verdict takes about six weeks to arrive.