Welcome to WebmasterWorld Guest from 220.127.116.11
joined:Feb 2, 2017
It is usually pretty common to lose some rank while implementing HTTPSNo it's not common.
I have read many stories of https rank drops. Just google it and you will see.How many of these "stories" have actually proved to be caused by HTTPS?
Where are you getting this "filter" information seoskunk? Please post link to authority source.I had exactly the same reaction when I read the post. The amount of misinformation and misinterpretation out there boggles the mind.
To support HSTS, use a web server that supports HTTP Strict Transport Security (HSTS) and enable HSTS.
HSTS adds complexity to your rollback strategy. We recommend enabling HSTS this way:
- Roll out your HTTPS pages without HSTS first.
- Start sending HSTS headers with a short max-age. Monitor your traffic both from users and other clients, and also dependents' performance, such as ads.
- Slowly increase the HSTS max-age.
- If HSTS doesn't affect your users and search engines negatively, you can, if you wish, ask your site to be added to the Chrome HSTS preload list.
What's not clear is why you keep insisting otherwise. It simply is not true.
I have been reluctant to add fuel to the fire on what may very well have been a coincidence (we only have one site). However, I get the impression that Apache is the preferred platform around here, so mention of IIS might be important.
So if there was a ranking loss, there has to be another, maybe related, reason. Most likely something that was done at your server. What that is needs to be determined.What a great idea. Now can we get on with that?