Category: Apache

They aren’t giving up so I assume it works to catch the dumb fish. I (again) found “traffic” spikes in Analytics coming from auto-seo-service.com, auto-seo-service.org, autoseo-service.org, resell-seo-services.com only to find that it is our old friends at Semalt. Does this spam even work? Maybe their real purpose it to generate traffic out of your curiosity to visit one of their spam links in Analytics that forwards to their website to improve their Alexa Rank or something. I can’t imagine anyone would do business with someone who uses dirty tricks to advertise “spam advertising” – not cool! So I advise that you don’t give them the benefit of a visit.

For those who won’t visit but are curious, search a bit for other webmaster comments. What I have found (and I’m not visiting their site to see what they are pitching today) is they are reportedly a Ukrainian SEO outfit.

Since this isn’t real traffic (100% bounce rate) you can’t filter them from your analytics. You’ve got to block them at the server. If you have access to your Apache htaccess file, adding this line in mod_rewrite should do it.

RewriteCond %{HTTP_REFERER} ^.*seo-service.* [NC,OR]

HTTPS Should I Go All-In? Does encryption help my search rank?

There was a lot of noise some time ago (August 2014) about how Google would use https as a ranking signal. SERoundTable had this article out shortly thereafter. We finally decided it was time to test this signal.

We tested this very website over several weeks to see if Google treats websites that use HTTPS (SSL encryption) any different. We used forced and unforced https from WordPress and using htaccess (apache).

We saw the greatest drop in traffic using forced https by way of htaccess redirection for all URLs. This caused Google Mobile Friendly test to choke for some reason. We checked all our settings to see if we screwed up some where. But no other service reported issues. Everything worked fine except we saw our queries in Google Webmaster Tools drop to almost zero. Obviously Google does not seem to like this method very much.

The spot of good news was the drop in unwanted bots in logs and other noise from “those” referrers in our Google Analytics – not really worth if we also loose legit traffic.

We then switched to WordPress to do the same all-URLs redirection from within the settings menu. This worked better for Google Mobile Friendly test, but our traffic remained at the lows we experienced using htaccess and our queries as seen in GWM did not rebound.

We then rolled back to only forcing https using htaccess for only those pages requiring SSL encryption. The entire website can be accessed using both http and https. This seemed to be the best solution as our traffic began to return as queries seem to be rising back to normal levels.

Its not expensive to buy a SSL certificate. But considering how difficult it can be to setup SSL on a website – something requiring a bit of experience to get right – there is no reason to switch unless you need encryption. And then only force https on those pages that really need it.

…….January 24…….

After a few weeks and with no further modifications, we noticed that Google Search Console prefers the https property over the others. That means we followed Google’s instructions to setup all possible URLs as properties with https one of them – as seen in this screenshot. As it turns out, Google has chosen to use the https property under which all all dashboard data is displayed. What does it mean? We have seen no significant change in search rank – if even a slight drop in placed.

We’ll report more as we learn more.