Mobile app version of vmapp.org
Login or Join
Sarah324

: Why do HTTPS referrers from Google sometimes still contain keywords? Nowadays it is normal to not get any keywords anymore in referrals from Google. However, when somebody uses Google in HTTPS

@Sarah324

Posted in: #GoogleSearch #Keywords #Referrer

Nowadays it is normal to not get any keywords anymore in referrals from Google. However, when somebody uses Google in HTTPS mode, I still occasionally get referers like: www.google.de/search?q=key+word.
Why does that happen? I thought that in HTTPS mode, Google would not send keywords in the referer anymore.

10.02% popularity Vote Up Vote Down


Login to follow query

More posts by @Sarah324

2 Comments

Sorted by latest first Latest Oldest Best

 

@Caterina187

@user82217 noted that it could be faked.

I suspect that it is.

Google doesn't send traffic directly to your site when a link is clicked they send the user through some redirects (for tracking I assume) that eventually lands them on your site, so the chances of Google leaking referrer info accidentally are probably non-existent.

In the last few months, I have noticed a new referral spam technique where they domain listed as the referrer is valid such as twitter, reddit, google, etc.

But the actual content (the "referring page") is non-existent or is in someway hacked. I've also seen forged "organic keywords".

That said, Google does seem to pass branded keywords much more frequently than generic keywords so maybe that's related as well.

This question has been puzzling me for a while too...mainly because HTTPS sites still often show up in my GA traffic sources reports for HTTP sites and I didn't think that was supposed to happen at all.

10% popularity Vote Up Vote Down


 

@Ogunnowo487

Check the User-Agent that correspond to these requests - is it an old browser?

Google uses a referrer meta tag in the head section of the SERPs of the form:

<meta content="origin" name="referrer">


So, regardless of whether the target site in the SERPs is HTTPS or HTTP, only the www.google.de/ part (ie. scheme + hostname) of the HTTP Referer is sent by the browser.

But, what if the browser doesn't support this meta tag?

I guess the Referer header could also be "fake", or the user has some kind of browser plugin that "interferes" with it (or even removed the meta tag??)?


I thought that in HTTPS mode, Google would not send keywords in the referer anymore.


Google only uses HTTPS these days.

Without the meta tag described above (or some other intervention) then the full Referer would be passed (query string and all) when navigating to another HTTPS site.

However, if your site was HTTP then ordinarily the browser wouldn't send the Referer header at all (when navigating from HTTPS to HTTP) if it wasn't for the meta tag.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme