New answers tagged

1

Yes it does. It affects adsense big time. Google does not make SSL compliancy mandatory for Adwords and third party ad networks. HTTPS-enabled sites require that all content on the page, including the ads, be SSL-compliant. As such, AdSense will remove all non-SSL compliant ads from competing in the auction on these pages. If you do decide to convert ...


0

You may have the same address but http and https work on different ports and should return different things unless they're configured otherwise. This is a server or Wordpress mis-configuration and I don't know anything about Microsoft crap so I can't help with that either.


1

The HTTPS doesn't always show alongside links with breadcrumbs. If you search and hover your mouse over the links, you can see the destination. For example: You see here that the destination URL includes HTTPS, even though it doesn't show in the result itself.


0

No, there's no need to re-submit for the SSL domain. You've already disavowed links for the HTTP version; in other words they're no longer taken "into account when [Google] assesses your site". Consequently, the negative effect can't be passed to the the new site (HTTPS): it's already been dealt with. The fact that subdomains and protocols are added ...


1

As a work around, I am proxying the web service: My SSL Hosting (Angular Project + Newly created proxy web service) AWS (Old Web service + MySql Database) From angularJS i call newly created proxy (that just uses cURL). This cURL code passes request to AWS server over HTTP.


1

This will use for both www or non-www If you try to open link with www then url redirect to https with www Example: http://domain.com redirect to https://domain.com or If you try to open link with non-www then url redirect to https with non-www Example: http://www.domain.com redirect to https://www.domain.com RewriteEngine on RewriteCond ...


1

This is a difficult question to answer simply because there is no direct answer to this question. So let's see if we can work through the process. Let's assume a few things. The first of which is a blanket 301 redirect from one site, HTTP, to another, HTTPS. The second is that there are links to the HTTP site and not to the HTTPS site. What we know. The ...


0

In the disavow file, domain:example.com covers all cases of www cname(s) and all subdomains, under http:// and https://. So no matter what their domain runs as, or what subs are running, it'll be disavowed https://support.google.com/webmasters/answer/2648487?hl=en says: If you want Google to ignore all links from an entire domain (like example.com), ...


1

The answer is - which one is Google indexing? It will only index one version. That's the one you disavow. Do it with the root domain (domain:example.com) and you don't even need to specify a protocol.


2

As Steffen metioned it is not possible to do the renewals without domain re-validation. BUT even without SSH access it is possible to automate the Let's Encrypt renewal request which shoould solve your manual validation problem. Have a look at: Lescript on GitHub The challenges are completed by creating the files and folders using PHP. The only thing you ...


2

Here is the shorter version of your code : RewriteEngine on RewriteCond %{HTTPS} off [OR] RewriteCond %{HTTP_HOST} !^www\. RewriteRule ^ https://www.%{HTTP_HOST}%{REQUEST_URI} [NE,L,R]



Top 50 recent answers are included