Does your secure site link to plain HTTP pages?
It finds internal links written with an insecure scheme on a site served over HTTPS.
What Check Engine measures
The check stops when the site is not served over HTTPS. On a secure site it scans indexable pages for internal links beginning with http. Pages with such links enter a low-severity finding, with an example destination. Even a working redirect can leave the site's own links using the older scheme. Those links can qualify without a failed destination.
The check uses the site's security status and internal links read from pages intended for search. It compares the URL schemes. You need to review the response and final destination separately.
How to read the result
The finding is low severity. It describes the spelling of internal destinations, not proof that the final page remains insecure after redirects or that every visitor receives an error.
Why it matters
A secure page can still send a visitor through a plain-scheme address in its links. Reviewing the source link makes it possible to align the site's own navigation with its intended secure address policy.
How to fix it
Update internal destinations to the correct secure final URLs. Check shared menus and templates before editing repeated links individually. Confirm that the destination works over HTTPS and preserve paths and queries that identify the content. Review the redirect policy separately so that old external links still reach the intended page.
How to redirect http:// to https://
What we found in field audits
Problems in Links were found on 14 of the 14 sites we audited. These are area totals. Read the field-audit method.
Method note
backend/seo_engine/checks/links.py, insecure_links, revision 0bb8e8d3.
Common questions
Can an HTTP internal link be reported even when it redirects successfully?
Yes. A failed destination is not required. An HTTP link on a secure site can qualify even when a redirect reaches the right page.
Does the HTTP internal-link check run on an HTTP-only site?
No. This test applies to a site served over HTTPS. Plain-HTTP sites do not enter the internal-scheme comparison.
How serious are HTTP internal links on an HTTPS site?
The finding has low severity. It reports the address spelling rather than establishing that the final response remains insecure.