top of page
  • Writer's pictureBrent Payne

URL resolves under both HTTP and HTTPS

When both the HTTP and HTTPS versions of a URL lead to a page with a 200 (OK) status, it implies that the content can be accessed using both protocols.

Why is this important?

Security is the primary issue since the HTTP protocol is not encrypted, which could expose user data to potential risks. Additionally, search engines encountering identical pages under both protocols might lead to duplicate content concerns that can negatively affect a site’s search ranking.

What does the Optimization check?

The following condition will set off this Optimization: any internal link showing a 200 status for both the HTTP and HTTPS versions.

Examples that trigger this Optimization

The starting URL is, thereby opting to review the HTTP version of the site. A given URL, such as, comes back with a 200 HTTP status. If similarly reflects a 200 status, this Optimization is activated. The same applies if the HTTPS protocol was the starting point for the crawl.

How do you resolve this issue?

It is essential for URLs to be exclusive to a single address. If reachable via both HTTP and HTTPS, you have to establish one version as the 'canonical' and redirect the other to it for consistency. Going forward, prefer HTTPS for security and follow a meticulous HTTP to HTTPS migration strategy.

If the website is traditionally served over HTTP and an immediate switch to HTTPS is not viable, consider implementing redirection rules from HTTPS to HTTP.


Recent Posts

See All

ClubReq Gets A Link (Because They Asked)

I am a mentor for Techstars and have been for over 10 years. In those ten years I have mentioned to startups to ask ANYONE and everyone that they meet to link to their site. Yet, in all those times on


bottom of page