Les nouveautés et Tutoriels de Votre Codeur | SEO | Création de site web | Création de logiciel

salam every one, this is a topic from google web master centrale blog: Written by Nathan Johns, Search Quality Team

All right, you got hacked. It happens to many webmasters, even despite the hard work you devote to prevent this type of thing from happening. Prevention tips include keeping your site updated with the latest software and patches, creating an account with Google Webmaster Tools to see what's being indexed, keeping tabs on your log files to make sure nothing fishy's going on, etc. (There's more information in the Quick Security Checklist we posted last year.)

Remember that you're not alone—hacked sites are becoming increasingly common. Getting hacked can result in your site being infected with badware (more specifically malware, one type of badware). Take a look at StopBadware's recently released report on Trends in Badware 2007 for a comprehensive analysis of threats and trends over the previous year. Check out this post on the Google Online Security Blog which highlights the increasing number of search results containing a URL labeled as harmful. For even more in-depth technical reports on the analysis of web-based malware, see The Ghost in the Browser (pdf) and this technical report (pdf) on drive-by downloads. Read these, and you'll have a much better understanding of the scope of the problem. They also include some real examples for different types of malware.

The first step in any case should be to contact your hosting provider, if you have one. Often times they can handle most of the technical heavy lifting for you. Lots of webmasters use shared hosting, which can make it difficult to do some of the things listed below. Certain tips labeled with an asterisk (*) are cases in which webmasters using shared hosting will most likely require assistance from their hosting provider. In the case that you do have full control over your server, we recommend covering these four bases:

Getting your site off-line
  • Take your site off-line temporarily, at least until you know you've fixed things.*
  • If you can't take it off-line, return a 503 status code to prevent it from being crawled.
  • In the Webmaster Tools, use the URL removal tool to remove any hacked pages or URLs from search results that may have been added. This will prevent the hacked pages from being served to users.

Damage Assessment
  • It's a good idea to figure out exactly what the hacker was after.
    • Were they looking for sensitive information?
    • Did they want to gain control of your site for other purposes?
  • Look for any modified or uploaded files on your web server.
  • Check your server logs for any suspicious activity, such as failed login attempts, command history (especially as root), unknown user accounts, etc.
  • Determine the scope of the problem—do you have other sites that may be affected?

Recovery
  • The absolute best thing to do here is a complete reinstall of the OS from a trusted source. It's the only way to be completely sure you've removed everything the hacker may have done.*
  • After a fresh re-installation, use the latest backup you have to restore your site. Don't forget to make sure the backup is clean and free of hacked content too.*
  • Patch any software packages to the latest version. This includes things such as weblog platforms, content management systems, or any other type of third-party software installed.
  • Change your passwords - https://www.google.com/accounts/PasswordHelp

Restoring your online presence
  • Get your system back online.
  • If you're a Webmaster Tools user, sign in to your account
    • If your site was flagged as having malware, request a review to determine whether your site is clean
    • If you used the URL removal tool on URLs which you do want in the index, request that Webmaster Tools re-include your content by revoking the removal.
  • Keep an eye on things, as the hacker may try to return.

Answers to other questions you may be asking:

Q: Is it better to take my site off-line or use robots.txt to prevent it from being crawled?
A: Taking it off-line is a better way to go; this prevents any malware or badware from being served to users, and prevents hackers from further abusing the system.

Q: Once I've fixed my site, what's the fastest way to get re-crawled?
A: The best way, regardless of whether or not your site got hacked, is to follow the Webmaster Help Center guidelines.

Q: I've cleaned it up, but will Google penalize me if the hacker linked to any bad neighborhoods?
A: We'll try not to. We're pretty good at making sure good sites don't get penalized by actions of hackers and spammers. To be safe, completely remove any links the hackers may have added.

Q: What if this happened on my home machine?
A: All of the above still applies. You'll want to take extra care to clean it up; if you don't, it's likely the same thing will happen again. A complete re-install of the OS is ideal.


Additional resources you may find helpful:

Feel free to leave additional tips you have in the comments.this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
Seo Master present to you: Google Wave was first unveiled at Google I/O in 2009, alongside our first draft of Wave APIs and specifications for the open-source world. We worked hard this past year to bring you a host of new features on our first birthday at Google I/O 2010: open sign-ups, attachments and data APIs and open-sourcing of a significant Wave component, the rich text editor.

From seeing demos in the Wave pod in the Developer Sandbox to having conversations with attendees in person, we were excited to see all of the ways people are using Wave and the Google Wave Federation Protocol inside enterprises. It was extremely valuable for us to hear your questions and feedback in person and via the session waves.

For developers out there who weren't able to attend I/O in-person, we hope you can join in virtually by watching the recorded videos of the various talks.
  • Open source Google Wave: Building your own wave provider - Learn how to get your own Wave server running using the currently open-sourced demos, and watch a demo of SAP Streamwork, Novell Pulse, and Google Wave all federating together.

  • Making smart & scalable Wave robots - Learn how to take advantage of version 2 of the Robots API to build more sophisticated robots, and watch a demo of the Go bot - the first example of a robot running on a non-App Engine server, written in the new open-source programming language.

  • Waving across the web - Learn how to use the APIs outside of Google Wave, including embedding waves for discussions on your site, integrating with the WaveThis service, and using the data APIs to build notifiers and alternative clients.

  • Google Wave Media APIs - Attachments can surf too!: Learn how to use the new media/attachments API for both retrieving and creating attachments, and watch demos of robots that turn waves into Powerpoint presentations -- and back!

  • Google Wave and the enterprise environment - Learn how different enterprises are using Wave today, see a walkthrough of Mr. Release, an extension built for our own software development enterprise use case, and watch a demo of SAP Streamwork, an enterprise collaboration software.

  • Google Wave API design principles - Anatomy of a great extension: Learn how to build gadgets and robots that are user-friendly and collaborative, and watch a demo of ProcessWave, a collaborative UML editor.

  • Fireside chat with the Google Wave team - Watch our answers to questions about integration between Google Wave and other products, future features for robots and gadgets, and much more.
In addition to the linked session titles where you'll find the videos and slides, you can also find all videos for Wave sessions in this YouTube playlist.

We welcome any follow-up questions in our forum for any of the video sessions above. Happy waving, and we look forward to seeing you all at next year’s Google I/O!

2013, By: Seo Master
salam every one, this is a topic from google web master centrale blog: You may have noticed that some search results include a set of links below them to pages within the site. We've just updated our help center with information on how we generate these links, called Sitelinks, and why we show them.

Our process for generating Sitelinks is completely automated. We show them when we think they'll be most useful to searchers, saving them time from hunting through web pages to find the information they are looking for. Over time, we may look for ways to incorporate input from webmasters too.this is a topic published in 2013... to get contents for your blog or your forum, just contact me at: devnasser@gmail.com
Powered by Blogger.