{"id":24250,"date":"2009-11-26T00:00:00","date_gmt":"2009-11-26T00:00:00","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/generic-cialis-on-my-website-i-think-my-site-has-been-hacked\/"},"modified":"2009-11-26T00:00:00","modified_gmt":"2009-11-26T00:00:00","slug":"generic-cialis-on-my-website-i-think-my-site-has-been-hacked","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/generic-cialis-on-my-website-i-think-my-site-has-been-hacked\/","title":{"rendered":"Generic Cialis on my website? I think my site has been hacked!"},"content":{"rendered":"

Thursday, November 26, 2009<\/p>\n

This post is the first part of the How to use “Fetch as Googlebot” series<\/i><\/p>\n

\n Has your site ever dropped suddenly from the index or disappeared mysteriously from search
\n results? Have you ever received a notice that your site is using cloaking techniques?
\n Unfortunately, sometimes a malicious party “hacks” a website: they penetrate the security of a
\n site and insert undesirable content. Sophisticated attackers can camouflage this spammy or
\n dangerous content so that it doesn’t appear for normal users, and appears only to Googlebot,
\n which could negatively impact your site in Google’s results.\n<\/p>\n

\n In such cases it used to be very difficult to detect the problem, because the site would appear
\n normal in the eyes of the user. It may be possible that only requests with a
\n User-agent:<\/code> of Googlebot and coming from
\n Googlebot’s IP<\/a>
\n could see the hidden content. But that’s over: with
\n Fetch as Googlebot<\/a>,
\n the new Labs feature in Webmaster Tools, you can see exactly what Googlebot is seeing, and avoid
\n any kind of cloaking problems. We’ll show you how:\n<\/p>\n

\n Let’s imagine that the administrator of www.example.com<\/code> is searching for their site, but they
\n find this instead:\n<\/p>\n

\"search<\/p>\n

\n That’s strange, because when they look at the source code of www.example.com<\/code>, it
\n looks fine:\n<\/p>\n

\"the<\/p>\n

\n With much surprise, the site owner may receive a notice from Google warning them that their site
\n is not complying with Google’s quality guidelines. Fortunately they registered their site with
\n Webmaster Tools. Let’s see how they can check what Googlebot sees:\n<\/p>\n

\n First, they log into Webmaster Tools and select www.example.com<\/code>. The Fetch as
\n Googlebot feature will be at the bottom of the navigation menu, in the Labs section:\n<\/p>\n

\"the<\/p>\n

\n The page will contain a field where you can insert the URL to fetch. It can also be left blank to
\n fetch the home page.\n<\/p>\n

\"the<\/p>\n

\n They can simply click Fetch and wait a few seconds. After refreshing the page, they can see the
\n status of the fetch request. If it succeeds, they can click on the “Success” link…\n<\/p>\n

\"the<\/p>\n

…and that will show the details, with the content of the fetched page:<\/p>\n

\"the<\/p>\n

\n Aha! There’s the spammy content! Now they can be certain that www.example.com<\/code> has
\n been hacked.\n<\/p>\n

\n Confirming that the website has been hacked (and perhaps is still hacked) is an important step.
\n It is, however, only the beginning. For more information, we strongly suggest getting help from
\n your server administrator or hoster and reading our previous blog posts on the subject of hacked
\n sites:\n<\/p>\n