Welcome to WebmasterWorld Guest from 35.171.146.16

Forum Moderators: Robert Charlton & goodroi

Message Too Old, No Replies

HTTPS - ssl expired what impact on AMP if any?

     
2:23 am on Sep 23, 2017 (gmt 0)

Senior Member

WebmasterWorld Senior Member Top Contributors Of The Month

joined:Apr 1, 2016
posts:2683
votes: 814


I made a mistake while renewing my Letsencrypt ssl certificate. I wasn't sure whether the renew action I did worked. Then I checked on "ssllab" and it showed all was fine, but since the certificate hadn't expired yet I wasn't sure if it was the old one that was fine or the new one. So I waited until the certificate expired today and re-tested it with "ssllab" and I got a score of "T". I quickly re-did the renew process, sorted out the issue. The issue was that I needed to stop the server while I was renewing the certificate for it to work.

Now all is fine, except that the site is in AMP site. Will the fact that I let the certificate expire for a few hours have any impact on my AMP indexing?

I see no messages or errors reported in GSC.
8:21 pm on Sept 23, 2017 (gmt 0)

Senior Member

WebmasterWorld Senior Member aristotle is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month

joined:Aug 4, 2008
posts:3650
votes: 368


You should try to find a way to get the certificate re-newed automatically. Some browsers will show a popup security warning if the certificate has expired. A popup warning could scare visitors away.
9:12 pm on Sept 23, 2017 (gmt 0)

Senior Member

WebmasterWorld Senior Member Top Contributors Of The Month

joined:Apr 1, 2016
posts:2683
votes: 814


There is a script that one can implement that can update the cert automatically, I just haven't gotten around to implementing it yet. I currently only have 2 sites to worry about so it is not such a big deal and both a very little traffic.
9:18 pm on Sept 23, 2017 (gmt 0)

Senior Member

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month

joined:Sept 25, 2005
posts:2091
votes: 370


needed to stop the server while I was renewing the certificate for it to work.

Ouch. That shouldn't be necessary. On my systems the certificate path is a symbolic link to the actual certificate, and only that link is updated upon renewal. If you're using the certbot, make sure you take advantage of the --dry-run and --renew-hook options to smoothen the process. Upon renewal, it reloads my nginx configuration to begin serving the new certificate, and I get an e-mail notifying me of the renewal.

As for your AMP indexing, it's probably not much different from regular indexing in this regard. The pages have probably already been recrawled since. And I don't think invalid certificates stop Googlebot from crawling your content.
11:24 pm on Sept 23, 2017 (gmt 0)

Senior Member

WebmasterWorld Senior Member Top Contributors Of The Month

joined:Apr 1, 2016
posts:2683
votes: 814


Thanks Robzilla for the tips. I will look into it. I am using Letsencrypt.

As for AMP I am not too concerned about the crawling. I am more wondering whether Google will dump the pages from the amp-cache if they find an invalid cert?
 

Join The Conversation

Moderators and Top Contributors

Hot Threads This Week

Featured Threads

Free SEO Tools

Hire Expert Members