See: http://webcache.googleusercontent.com/search?q=cache:luh_7FDdlsoJ:www.jancvanderheide.com/component/content/article/46-horoscoop-en-voorspellingen/368-2016-voorspellingen-2016&hl=nl&gl=pl&strip=0&vwsrc=1
Trying to go here I get an alert: http://www.jancvanderheide.com/component/content/article/46-horoscoop-en-voorspellingen/368-2016-voorspellingen-2016
Probably you cannot visit site. 403 Security Issue.
Here I can see the contents: http://www.domxssscanner.com/scan?url=http%3A%2F%2Fwww.jancvanderheide.com%2Findex.php
Via a webproxy I can normally visit the site: http://proxhow.com/service/page.php?u=U16dc%2B0UoYPwJ2CZURzI4ZZHjmzbvYo13sdii%2FYu47l9%2Bo74&b=0&f=norefer
See: http://www.dnsinspect.com/jancvanderheide.com/1451162799
Checked for cloaking and that is the case: http://isithacked.com/check/http%3A%2F%2Fwww.jancvanderheide.com%2Findex.php
Difference between GoogleBot and Google and different return codes.
Checking http://www.jancvanderheide.com/index.php
Xmark
Checking for cloaking
There is a difference of 104855 bytes between the version of the page you serve to Chrome and the version you serve to GoogleBot. This probably means some code is running on your site that’s trying to hide from browsers but make Google think there’s something else on the page. show.
Xmark
Status codes
These should normally all be the same.
GoogleBot returned code 403
Google Chrome returned code 200
About that issue: https://productforums.google.com/forum/?hl=en#!category-topic/webmasters/crawling-indexing--ranking/-GU-ZsBgKCg
These things generally take care of themselves, so we’ll generally return to the site and attempt to access it without you having to do anything special.
polonus