WordPress Byethost

Monday, February 8th, 2010 at 11:43 pm

Downtime can be a nightmare

Originally posted here: Naperville Web Design

We are happy to be back in the land of the tubes. The last two weeks has made an incredible experience to get our backup site and the development of the finer points of our host.

Before we get into that part, however, probably should explain why we were down ...

As we often point out, that are received by Byethost. They and Bluehost are two hosting companies we have come to rely on most shared server space. Unfortunately, we have found a plugin that is used for food was not well accepted by neighbors on the server. We were capturing all of our food with the WordPress plugin WP-o-matic. I do not know is that this plugin causes of the leak important in some server side, and when the shared space, bandwidth, damage neighbors ... OOPS!

We honestly never considered that a plug-in widely used is the cause of these issues, but after test has shown that there could have been anything else. Due to excessive bandwidth, resources, and memory that wp-o-matic was stripped of shared space, we start a Virtual Private Server ... That is ... Banished Degaba System.

It took a week negotiations, but was willing to resolve Byethost speech once assured us that it had to be the plugin that is causing all the problems it. A week later, we're back and on the road again .... Needless to say, our channels will no longer run through WP-O-Matic.

Now, the sob-story

Although only a day and return the IP for a week, Google took a lot of notice. Our impressions were an average of 1.000 / day to 22 tonight. Our traffic went from an average of 200/day at 30 tonight.

The last week of being a backup is representative of the total downtime in the SERPs.

Notice in the screenshot that the exact date being down is visible, and the subsequent fight with Google ranking.

While this is a very strong upside in the short term, we will return to our previous position fairly quickly. We have encountered similar situations with client sites, but I never thought I'd have to do damage control of our own.

These are the next steps to be taken directly after an event like this.

1. Immediate impetus for the back-links-During the month of downtime like this the need for websites to verify their existence is crucial. The pages that Google tries and tracking can be put on back burners for a period of time. Making a strong push of the links and recognition can get a faster shot to crawl pages that probably would otherwise.

2. Add more content. We all know that the best way to attract the attention of Google is to give something new to watch. Although several different blogs feed on this site who also enjoy our own content added regularly on his pertinent now add more than you would normally. The additional content of the signal that the site is not dead and is actually very alive and active.

3. In addition to adding the content, make sure that Google is aware of what was said. To bring home this point, we submit sitemaps ... Several sitemaps.
XML to ROR, high to present all possible formats of map available. Some may think this a bit eccentric, but in the terrible moments like these, can be the difference between being degraded by weeks or months. WordPress For additional sitemaps, we suggest you use the following

Sitemap Index - a virtual PHP site map built with each update.
Google News Sitemap XML - Automatically generate an XML sitemap for inclusion in Google News 2.0
XML Sitemap Feed - Create a source complies with the XML site map

We also have some made in xml-format sitemaps.com in url.txt and rss.ror.

Our experience in implementing now will see how long it will take to return to traffic and ranking it had last month. We will share this experience with you and welcome any suggestions or thoughts you would like to add.

About the Author

Build your website for free - WordPress (Part One)