New answers tagged

1

sub-directory is better as sub-domain (if the topical alignment is the same) if you sell something or collect user info - make use of SSL, in case of no-usage you gets minus point. In other cases you don't need SSL - there is nothing to protect and no bounties fom using it.


1

You seem to mix two completely different things. You mention that you don't see the pages indexing in the Search console - but the code you give is the Analytics tracking code - which is completely unrelated to the Search Console. The fact that you messed up your Analytics tracking code will not have an effect on the indexing. That said - your analytics ...


1

It is possible to renew the certificate without doing the challenges again? I have the private key for the certificate, so can't they validate the domains based on that? With the private key you could only prove that you are in the possession of the private key. You could not prove that you own the domain too. But a certificate should be used to ...


0

There's a trade-off here. If you decide to move everything to https then people will have a longer waiting time initially in order for the security certificate to be recognized by the client browser. For now, make one URL the secure version of that URL. Make it start with https:// and run that URL through webpagetest.org and you'll notice either a purple ...


1

For a period, you will see a drop-off in traffic before picking up again. Be prepared for this and make sure that management understands that switching from HTTP to HTTPS comes with a price. In theory, though rarely in practice, HTTP and HTTPS are two separate sites. As the search engine drops the HTTP site and indexes the HTTPS site, there will be a ...


0

Redirecting to the, now, preferred secure version of the same site will have no effect on your ranking. The domain name is the key for search engines. https is the protocol, not the content.


2

as @w3dk mention in the comments, I had to add a R=301 in my .htaccess file. RewriteEngine On RewriteCond %{SERVER_PORT} 80 RewriteRule ^(.*)$ https://%{SERVER_NAME}/$1 [R=301,L] </IfModule> I didn't try Goyllo's answer but I think it's a good one if you don't have access to the server.


4

These are really two separate questions: if you're thinking of implementing AMP, that shouldn't affect your choice between HTTP and HTTPS in any way. So you have two choices to make: "do you want to implement AMP?" (and it sounds like you do); and "do you want to go HTTPS?", for which I've written an answer here.


1

Google Webmaster Tools has no option to set HTTPS as the preferred version. Google takes this automatically from your canonical link tag. <link rel="canonical" href="https://example.com/"> So whenever the Google spider sees this line in your head section, Google automatically indexes the HTTPS version of your site. Nowadays, Google indexes HTTPS ...


1

When the HTTPS page appears in the Google index, they give it a boost. When both are available Google has recently started preferring the HTTPS version in their search index. So when you have both available, Google prefers the HTTPS version and it gets a ranking boost.


3

Any migration carries some degree of risk and short-term consequences; a move to HTTPS is no exception. Rand Fishkin wrote an interesting post on Moz's experience moving to HTTPS. The short version of that story is that they initially lost about 11% of their organic search traffic, but recovered within 3 months. So yes, there can be at least some short-term ...


2

your plugin seems to not recognize, that the whole site runs https. about one hour ago new 3.3 version of your plugin was published - one of the announced news is the support of https. try to update.



Top 50 recent answers are included