In Neova Runs from the crawl itself: nothing to set up.
Rule last reviewed October 17, 2026 · Guide updated July 1, 2026
Internal links on HTTPS pages should point to the HTTPS URL directly, not to an HTTP URL that redirects.
How Neova Finds It
Neova reads the HTML of every page it crawls and looks for this.
Why It Matters
Security issues affect trust signals and can result in browser warnings.
The Ticket It Writes
SE-002B · HTTPS URL Links to an HTTP URL
How to Check the Fix: 1. Run the check again in Neova 2. Spot-check sample URLs across affected templates 3. Record the re-check date and period label next to the baseline
Neova writes this ticket for every affected page group and sends it to Jira, Linear, Asana and the rest, after you approve it.
The Full Guide
TL;DR: This check flags secure HTTPS pages that link to insecure http:// URLs. Those links trigger extra redirects, can produce mixed content warnings when the resource loads on the page, leak referrer data, and quietly signal a sloppy migration. Point every internal link and asset at HTTPS.
Severity
Medium to high
Worst case
Blocked assets
Common source
Hardcoded http links
Fix
Rewrite to https
Detect with
Screaming Frog
What This Check Means
Your page is served over HTTPS, but somewhere in its HTML it links to an http:// address. That link might be a navigation link, a citation, an image, a script, or a stylesheet. The check does not care whether the destination happens to redirect to HTTPS. It flags the fact that the link as written starts on the insecure protocol, because that has real consequences depending on what kind of link it is.
There are two flavors, and it is worth keeping them straight. A hyperlink to an http URL (an anchor a user clicks) is a navigation and referrer problem. A subresource loaded over http (an image, script, iframe, or stylesheet embedded in the page) is a mixed content problem, and browsers treat it far more harshly.
Why It Matters
The impact ranges from a minor tax to a broken page, so do not wave it off.
Mixed content. When an HTTPS page loads an active subresource (script, iframe, stylesheet) over http, browsers block it outright. Passive content like images may load with a warning. Either way the page is degraded and the padlock can break.
Extra redirect hops. Most http URLs now 301 to HTTPS. Every link that starts at http forces an extra round trip: request http, get redirected, request https. On a link heavy page that adds up in latency and crawl overhead.
Referrer leakage. Navigating from HTTPS to a plain http destination can strip the referrer, so the destination loses attribution. It also just looks careless to anyone inspecting the traffic.
Trust and quality signals. Google has pushed HTTPS as a baseline for years. A secure site riddled with http links reads as an incomplete migration, and users who see a broken padlock lose confidence fast.
Wasted crawl budget. Search engines follow the http link, hit the redirect, then fetch the https target. That is two fetches for one destination, multiplied across the site.
What the Browser Does With Each Type
HTTPS page links to httpHyperlink (anchor to click)Subresource (loaded on page)Follows redirect to https,extra hop + referrer riskImage: loadswith warningScript or iframe:blockedactive mixed content
Where These Links Come From
After a migration to HTTPS, the certificate and redirects usually get handled, but the links inside the content often do not. Typical sources:
Hardcoded http:// URLs in old posts, page builders, and templates.
Image and media references saved with the full http path in the database.
Third party embeds, widgets, and scripts still pointing at http endpoints.
Theme and plugin defaults, canonical tags, or sitemaps generated before the switch.
Internal links copied from an older version of the site.
How to Detect It
Screaming Frog: crawl the site, then check the "Security" tab for the "HTTP URLs" and "Mixed Content" filters. It lists every insecure link and the pages they sit on.
Browser DevTools: open the Console and Security panels on a page. Mixed content is reported explicitly, with the exact offending resource.
Sitebulb: its security hints surface insecure links and mixed content, grouped so you can gauge scale.
Search Console: watch the Pages report for HTTPS related issues, and use URL Inspection to see how a page renders.
Server logs: a spike of internal requests hitting http then redirecting to https confirms the links are live and being followed.
How to Fix It, Step by Step
Inventory every http link with a full crawl. Separate hyperlinks from subresources, because subresources are the urgent ones.
Fix subresources first. Any script, stylesheet, image, or iframe loaded over http must be switched to https or replaced. Active mixed content is being blocked right now.
Rewrite internal links to https. For a database driven site, a careful search and replace of http://yourdomain.com to https://yourdomain.com handles the bulk. Back up first.
Update external links where the target supports HTTPS. If a linked site offers https, link to it directly rather than relying on its redirect.
Keep the site wide http to https redirect in place. It is your safety net for anything you missed and for old inbound links, but it is not an excuse to leave http links in your own code.
Consider HSTS. An HTTP Strict Transport Security header tells browsers to always use https for your domain, closing the door on downgrade attempts.
Re crawl and confirm zero. Verify the Security tab is clean and DevTools shows no mixed content warnings.
Do vs Don't
DO
Link internally to https directly
Fix http subresources as the top priority
Search and replace http links after migration
Keep a site wide http to https redirect as backup
Add HSTS once you are fully on https
DON'T
Rely on redirects to hide http links in your code
Ignore mixed content warnings in the console
Leave hardcoded http image paths in the database
Load scripts or iframes over http
Assume the migration is done once the cert is live
Link Type, Browser Behavior, Priority
HTTP Link Type
Browser Behavior
Fix Priority
Script / iframe (active)
Blocked, breaks functionality
Critical
Stylesheet (active)
Blocked, layout breaks
Critical
Image / media (passive)
Loads with a warning, padlock breaks
High
Hyperlink (anchor)
Extra redirect hop, referrer risk
Medium
What "Good" Looks Like
Every internal link, image, script, and stylesheet on the site uses https. The Security tab in a fresh crawl is empty, DevTools shows no mixed content warnings, and the padlock is intact on every page. The site wide http to https redirect still stands as a safety net for old inbound links, but your own pages never trigger it. External links point at https wherever the destination supports it. If you have gone the extra step, an HSTS header enforces https before a request even leaves the browser.
FAQ
The HTTP Link Just Redirects to HTTPS, so Why Fix It?
Because the redirect is a cost, not a solution. It adds a round trip for every user and crawler, and for subresources it can still trigger mixed content before the redirect resolves. Linking straight to https removes the tax entirely.
What Is the Difference Between Active and Passive Mixed Content?
Active content (scripts, iframes, stylesheets) can alter the whole page, so browsers block it. Passive content (images, media) has limited reach, so it usually loads but throws a warning and breaks the padlock.
Do External HTTP Links Hurt My SEO?
The direct ranking impact is small, but they add redirect overhead, can strip referrer data, and read as a careless migration. Point them at https when the destination supports it.
How Do I Find Them All Quickly?
Crawl with Screaming Frog and use the Security tab filters for HTTP URLs and Mixed Content. Cross check individual pages in browser DevTools, which names the exact offending resource.
Migration left insecure links behind?
Mixed content and stray http links are exactly the kind of leftover a technical audit catches, along with the redirect chains and duplicate URLs hiding next to them.