3 ms·
Sorry to hear that, but academically very interesting. Did you try to recover the traffic? If yes, what did you try and did it work? Also, after setting the p
by webtechgal 10y ago
Sorry to hear that, but academically very interesting.
Did you try to recover the traffic? If yes, what did you try and did it work?
Also, after setting the permanent redirect, I believe it would be a good idea to update the internal navigation of the site so that all links are formed with https. That way, both the crawlers and the web server will have less work to do and eventually, the entire site will be indexed/updated in the search engines with the https protocol.
- akerro 10y agoI updated all navigation, RSS, links to images, menu, search, sitemap, everything. Dump of my site didn't contain any 'http' link to the same domain. nginx was redirecting everything with 301. I let once website work on http and https and made most links protocol-independent, only site map and search results are forced to https. There was a thread about it on reddit where a few more people said the same. I slightly recovered from it, got 101 UU yesterday.
- webtechgal 10y agoHow long since you changed to https? It may take Google a few weeks to fully recognize the changed/redirected URLs. During this period, the rankings frequently drop but once everything settles down, the rankings and traffic should gradually come back to normal. If it has been a while (at least a month or two) since the changes were made and the traffic has not returned, that would be a cause for concern.
- akerro 10y agoI switched to full HTTPS in January/February (depends which domain), by end of April I had less than 100UU/day from search results.
- webtechgal 10y agoAnd before the switch, the traffic used to be around 3k UV/day? If so, this is definitely a (big) problem. If you share your URL, I'll take a look and give you some input.