If both HTTP and HTTPS URLs directly display the same public content, the priority is to use a consistent canonical URL, not to stop people from sharing HTTPS links. You can use 301 redirects from HTTP to the corresponding HTTPS pages and update internal links and the sitemap accordingly. If multiple versions with identical content need to remain available, consider canonical tags. Before making changes, however, check what each URL displays, whether it redirects, and what changes when a user logs in. A ranking decline alone does not establish that having both HTTP and HTTPS versions is the cause, and consolidating the URLs does not guarantee that rankings will recover.
First, distinguish between two entry points and two duplicate pages
Being able to open both URL versions does not mean that each has an independent copy of the content. An HTTP URL that redirects to HTTPS is different from two versions that each display content directly. A 2019 article by yesharris recommends checking the HTTP, HTTPS, www, and non-www versions individually and verifying their redirects, rather than simply checking whether the website opens.
- Do the HTTP and HTTPS versions of the same path display identical public content?
- Does entering the HTTP URL trigger a redirect? Which URL do you end up at?
- Does logging in change only the protocol, or do the content and access permissions also change?
- Which versions do the internal links, sitemap, and canonical tags point to?
For example, if the HTTP and HTTPS versions of an article both directly display its full text, review the URL consolidation settings. If one version displays a login page, first clarify the page’s purpose rather than treating it as identical content and applying the same approach.
When consolidating public content, align redirects and links
In a 2024 overview, yesharris recommends that HTTPS websites use 301 redirects from old pages to the corresponding HTTPS pages and update their sitemaps and internal links. An article by Da Vinci published that year also recommends using 301 redirects to consolidate duplicate HTTP/HTTPS versions.
For an article page, for example, the HTTP URL should redirect to that article’s HTTPS version. Simply changing internal links to HTTPS while leaving an independently accessible HTTP copy is not enough. If different URLs with identical content must remain available, consider using canonical tags to indicate the preferred version. These steps help consolidate URLs, but do not guarantee indexing or ranking outcomes.
When logged-in users share HTTPS URLs, focus first on consistency and security
When a logged-in user shares an HTTPS URL, first check what someone who is not logged in sees when they open it. If it still displays the same public article, consider using HTTPS consistently for public browsing as well, rather than asking logged-in users to share HTTP URLs instead.
If the content or permissions differ before and after login, you still need to check the site’s security and how its pages behave; SEO settings cannot replace those checks. Relevant public discussions mention the possible use of canonical tags, while noting that sites must also ensure a secure, smooth browsing experience. These are participants’ recommendations, not current official search engine rules. Until the actual configuration has been verified, you can suggest an approach to consolidation, but cannot conclude that both versions have been indexed or that this caused the ranking decline.
HTTP/HTTPS duplicate content and search rankings: perspectives from across the web
How do search engines discover HTTPS URLs used after login?
Public discussions note that search engines may discover HTTPS pages through internal or external links; URLs shared by logged-in users are just one possible route. If a page is crawlable by search engines, it may be indexed, but sharing its URL does not by itself mean that the page has been indexed. Search engines generally do not encounter problems simply because a URL uses HTTPS.
Why might other pages also use HTTPS when you navigate from an HTTPS page?
If a secure page uses relative URLs and does not specify a different protocol through a base tag or another mechanism, its links will generally inherit the current page's HTTPS protocol. A 2011 technical article therefore recommends checking links on crawlable secure pages and using absolute URLs that include the protocol where necessary. Which version those links should actually point to still depends on the website's chosen canonical URL.
Will rankings definitely recover or improve after URLs are consolidated?
There is no guarantee. If HTTP and HTTPS each serve the same content, this may create duplicate content and split ranking signals. A 2024 industry article argues that 301 redirects can help transfer ranking signals, though some may be lost in the process. Another public discussion of a particular case also notes that the actual ranking impact is difficult to determine, so redirects should not be treated as a guarantee of ranking recovery.
If both public URL versions are retained, will canonical tags work across all search engines?
This cannot be assumed across the board. A public discussion suggested using canonical tags to address HTTP/HTTPS issues, but the participant was also unsure how well other search engines supported them. If a website relies on a particular search engine, check that engine's relevant documentation. A canonical tag indicates a preferred version; it should not be treated as a setting that guarantees which version will appear in search results.
References
- HTTPS best practices for SEO and usabilitywebmasters.stackexchange.com — Discusses: If both public URL versions are retained, will canonical tags work across all search engines?
- 5 Easy Steps To Fix Secure Page (https) Duplicate Contentwww.screamingfrog.co.uk · 2011-03-23T14:57:50+00:00 — Discusses: How do search engines discover HTTPS URLs used after login?; Why might other pages also use HTTPS when you navigate from an HTTPS page?
- HTTPS best practices for SEO and usabilitywebmasters.stackexchange.com — Discusses: How do search engines discover HTTPS URLs used after login?
- HTTPS 的威力?「S」對 SEO 與網站經營的五大重要性www.awoo.ai · 2024-07-21T16:03:45+00:00 — Discusses: Will rankings definitely recover or improve after URLs are consolidated?
- 認識SEO排名的殺手,『重複內容』超完整攻略www.yesharris.com · 2019-02-25T14:00:21+08:00 — Source used in the article above.
- 重複內容影響SEO成效, 如何正確使用Canonical?www.da-vinci.com.tw · 2024-08-15T20:49:01+08:00 — Source used in the article above.
- 重複內容會影響SEO排名嗎?避免SEO排名分散的「重複內容」重點整理www.awoo.ai · 2019-05-05T08:22:05+00:00 — Discusses: If both public URL versions are retained, will canonical tags work across all search engines?
- SEO排名優化:23個排名因素解析+優化方法www.yesharris.com · 2024-09-06T15:19:34+08:00 — Source used in the article above.
- HTTPS best practices for SEO and usabilitywebmasters.stackexchange.com — Discusses: Will rankings definitely recover or improve after URLs are consolidated?
- HTTPS best practices for SEO and usabilitywebmasters.stackexchange.com — Source used in the article above.

