大网数据广告活动
网站运营与故障问答

Will installing SSL certificate cause duplicate content penalty?

· 52CE 我爱测

I'm running a VPS server and for so many years, I've been using http:// for my main website. In fact, to even avoid www and non-www issue, duplicate content issues, etc. in search engines, I even have the below code in my .htacce…

问题原文

原帖链接 · Yagami · CC BY-SA 3.0

I'm running a VPS server and for so many years, I've been using http:// for my main website. In fact, to even avoid www and non-www issue, duplicate content issues, etc. in search engines, I even have the below code in my .htaccess currently:

RewriteEngine On
Options +FollowSymlinks
RewriteBase /
RewriteCond %{HTTP_HOST} !^www.example.com$ [NC]
RewriteCond %{REQUEST_URI} !^/[0-9]+\..+\.cpaneldcv$
RewriteCond %{REQUEST_URI} !^/[A-F0-9]{32}\.txt(?:\ Comodo\ DCV)?$
RewriteRule ^(.*)$ http://www.example.com/$1 [L,R=301]

Aside from the above, I use absolute path showing http:// for internal links to deter content scrapers.

Now, recently, due to an update in WHM/cPanel, and because Comodo/cPanel is now issuing free SSL certificates, and AutoSSL is enabled by default, I noticed that I can now access the https:// version of my site. That is, if I type https:// manually, the browser will state it is secure. For one, that is a good thing, since I'm planning to migrate to https:// in the future and I believe my site is ready for that I believe. But I don't plan to do the migration now, since that would be a very time consuming process.

Given my conditions above, if I just leave AutoSSL enabled by default and the free Cpanel certificate installed in my domain name, will this cause duplicate content issues for many search engines since I believe they see http and https as different sites? Because I'm not very sure if major search engines are smart enough to think that although the https:// version of my site is apparently accessible, my links are still all http:// . What is your suggestion?

已采纳解答

原帖链接 · closetnoc · CC BY-SA 3.0

You will run into duplicate content issues sooner or later. It is just a matter of time.

You have two choices, three actually, but really just two.

1] Redirect HTTP to HTTPS or HTTPS to HTTP. I recommend HTTP to HTTPS since you seem to have what you need, however I understand not taking the leap. HTTPS adds an additional Trust factor. However, not wanting to take the leap today, which is perfectly understandable, you can just make sure that there is a redirect from HTTPS to HTTP.

2] Add a canonical tag in each page that points to the same page using either HTTP or HTTPS. Since you seem to prefer HTTP for now I suggest pointing to HTTP.

3] Do nothing. I do not recommend option 3. [insert cheesy grin]

Of the options, option 1 is the easiest. Redirecting HTTPS to HTTP for now will solve the problem quickly.

Here is a Q&A on just your scenario: https://stackoverflow.com/questions/12999910/https-to-http-redirect-using-htaccess

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Webmasters Stack Exchange
适用范围
以原帖系统、软件版本与发布日期为准(2017-03-05)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。