Strange Google Analytics URL

Most likely you’re seeing someone that’s trying to see if your site has a vulnerability in handling URL requests – they’re basically crafting query strings in the url request to see if they can hack a site. If it’s a worry for you, consider using a firewall/proxy server setup to block malicious requests – something like https://sucuri.net/website-antivirus/.

@ Bemdesign, i dont think that is the case, because multiple people visit the link. And i dont think all of these people wanna check for hacking it.

Visitor came from HTTP URL, Google was trying to sniff the source of visitor, HTTPS protocol stopped that. Thats why it became odd. It can happen with the search engine crawlers.

Additionally your SSL setup minor issues — https://www.ssllabs.com/ssltest/analyze.html?d=stijnspreekt.nl&s=109.72.85.122&latest You should fix them. Your server is possibly shared, I would suggest you virtual server/cloud server. I checked your IP and it appeared to me as shared host. European hosts does not cost huge for 1 GB cloud server. It is preferable to use a dedicated IP for one domain or share between your own multiple domains. You can see Low End Box for review for the server part.

Actually, there are four websites against one domain – https://example.com, https://www.example.com, https://example.com and https://www.example.com with distinct headers. HTTPS obviously increases security. It is HTTP GET request which works efficiently on HTTPS from cross domain than javascript. If you old URLs still indexed by Google search was :

https://example.com/where-is-the/post

it was actually a pretty URL of https://example.com/?p=123

Now when the redirection is happening from HTTP to HTTPS, it becomes hugely complicated. No cookie info is shared between HTTP to HTTPS redirection over TLS. From outside it simple –

https://example.com/where-is-the/post HTTP 301 -> https://example.com/where-is-the/post

But basically it is complicated situation with cache plugins and permalink. That odd stuff is out HTTP to HTTPS redirection plus Google Analytics setup and itself Google Analytics on HTTPS related issue. You can perform web search with Google Analytics HTTPS Errors like key phrases and you’ll get lot of persons like you, some has described own fixes.

For now, use wp-statistics Plugin to properly track. It does not have external javascript.

It is better to claim the HTTPS version on Google Webmaster Tools and submit the sitemap on HTTPS location. Read about that here – google.com/webmasters/answer. Because if all URLs of source becomes HTTPS on search (other sources), it becomes easier.

Also perform a web search on how to setup Google Analytics on HTTPS website. This is for this webpage’s Google Analytics code, notice the ga.src line :

<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-52447-1']);
_gaq.push(['_setDomainName', 'www.ads-software.com']);
_gaq.push(['_trackPageview']);
(function() {
	var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
	ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'https://www') + '.google-analytics.com/ga.js';
	var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
function recordOutboundLink(link, category, action) {
	_gaq.push(['_trackEvent', category, action])
	setTimeout('document.location = "' + link.href + '"', 100);
}
</script> 

You have lot of To Dos —

1. Use wp-statistics for proper tracking for practical reasons
2. Solve SSL server related minor issues
3. Check webmaster tools for HTTPS site & sitemap submission
4. Check Google Analytics docs for HTTPS site setup
5. Better to upgrade to a virtual dedicated

Upgrading to HTTPS initially gives some pain but it worths in long term for various reasons.