Google Panda Update 3.8 On June 25th

Google has announced they pushed out a new refresh to thePanda algorithm recently.

This update “noticeably affects only ~1% of queries worldwide,” said Google on Twitter.

There were earlier rumors of an update over the weekend but Google said the rollout started today and not over the weekend.

The previous Panda update was on June 8th and before that on April 26th. Typically, Google pushes out algorithm updates for Panda and Penguin every month or so. While the last Panda update was just over 2 weeks ago, Google felt they wanted to push out a new refresh.

Here is the tweet:

A Googler

• ✔

@google

Heads up: we're pushing a new Panda data refresh that noticeably affects only ~1% of queries worldwide. More context: goo.gl/HNvCt

26 Jun 12

• Reply
• Retweet
• Favorite

Google said there were no updates to the algorithm or changes in the signals. This was simply a basic data refresh where they ran the algorithm again.

Google Panda 3.7 Update

Google has confirmed the rumors of a Panda refresh happening over the weekend.
Google said this refresh started rolling out on Friday, June 8th and has an impact of less than 1% of search queries in the U.S. and about 1% worldwide.
As I said, the search forums took notice to major changes in the search results, specifically impacting sites that were originally hit by the Panda update. I reached out to Google this morning for a confirmation and they have confirmed the update.
Previously, Google pushed out Panda 3.6 on April 27th, about 6 weeks before this update. Google tends to do Panda and even Penguin refreshes every one to two months.

Link Buidling Plan Post Penguine Update

The Penguin update or Google’s webspam algorithm update, which was launched last April 24, did create massive impact to many online marketers and webmasters’ mindsets on how they should be performing search engine optimization from now on. It’s indeed another game changer, knowing that the update collected several negative reactions from webmasters around the world.
The Penguin update was aimed towards spam tactics, and was said to have affected at least 3.1% of English search queries on its first roll out. It’s expected to grow more as Google will certainly be implementing more changes around this algorithmic update, which is quite similar to the Panda update that lasted for over a year for its enhancements.
So how will you know if you’ve been hit by this update? There are a few things that you can do to see if this update has burned your site:

• If you’ve experienced sudden loss or meltdown in search traffic (especially if there’s a dramatically decrease in your top keywords’ rankings) on and after April 24, 2012.
• If your site is not ranking for its brand name on Google’s search results.

If you haven’t been affected by it, or if you’ve seen some increase in search-related traffic, then it might just mean that your competitors were the victims of this update, which made your site rank higher than its previous search rankings.
Penalized sites or sites that have been affected by this new algorithm update are still in Google’s indices, which mean that there are still ways to get back in the game! However, this will surely take time to get your site back in top form.
Disclaimer: Everything that I’ll be stating below are just several options that I’ll personally be implementing in case I work on a site that has been hit by this recent Penguin update, wherein most are based on my own understanding of how search works, and everything listed here are theoretical and I’m not saying that they will certainly work.
From what most experts have observed, Penguin is an algorithm/ranking factor update that is more focused on link behaviors that allows them to easily identify spam and manipulative signals. Dr. Pete Meyers discussed some of these possible factors on his recent post on SEOmoz:

• Aggressive exact-match anchor text
• Overuse of exact-match domains
• Low-quality article marketing and blog spam
• Keyword stuffing in internal/outbound links

My hunch is that this update is not yet stable (for sure) and will more likely be upgraded to total devaluation of low quality/spam/unnatural links to somehow neutralize the growing fear of Negative SEO. Not allowing these links to pass any value will decrease the rankings of those who have benefitted from it in the past, and will also protect those who might get abused by unethical link attacks in the future (building crap links to competitors).

Anti-Negative SEO

Knowing that link spams will generally be the basis of this recent update from Google in determining sites that are violating their guidelines, Negative SEO will certainly be a growing challenge, as people might take advantage of this loophole to gain and outrank their competitors.
The best way to protect your site from this uncharted territory is through your already existing link profile, especially if you already have obtained great and high value links pointing to your domain, and adding more of these types of links to your site to make it more solid in the eyes of Google, given that they are more to assess your site’s percentage of good vs. bad links based on their historic index.
Eric Siu from Evergreen Search also wrote an in-depth guide on how to protect your site from Negative SEO, you might want to check it out.

Read Complete Article heare>>>

How to get more Likes on Facebook

Responsive Web Design

We love data, and spend a lot of time monitoring the analytics on our websites. Any web developer doing the same will have noticed the increase in traffic from mobile devices of late. Over the past year we’ve seen many key sites garner a significant percentage of pageviews from smartphones and tablets. These represent large numbers of visitors, with sophisticated browsers which support the latest HTML, CSS, and JavaScript, but which also have limited screen space with widths as narrow as 320 pixels. 

Our commitment to accessibility means we strive to provide a good browsing experience for all our users. We faced a stark choice between creating mobile specific websites, or adapting existing sites and new launches to render well on both desktop and mobile. Creating two sites would allow us to better target specific hardware, but maintaining a single shared site preserves a canonical URL, avoiding any complicated redirects, and simplifies the sharing of web addresses. With a mind towards maintainability we leant towards using the same pages for both, and started thinking about how we could fulfill the following guidelines: 

1. Our pages should render legibly at any screen resolution
2. We mark up one set of content, making it viewable on any device
3. We should never show a horizontal scrollbar, whatever the window size

Stacked content, tweaked navigation and rescaled images – Chromebooks

Implementation

As a starting point, simple, semantic markup gives us pages which are more flexible and easier to reflow if the layout needs to be changed. By ensuring the stylesheet enables a liquid layout, we're already on the road to mobile-friendliness. Instead of specifying width for container elements, we started using max-width instead. In place of height we used min-height, so larger fonts or multi-line text don’t break the container’s boundaries. To prevent fixed width images “propping open” liquid columns, we apply the following CSS rule:

img {
  max-width: 100%;
}

Liquid layout is a good start, but can lack a certain finesse. Thankfully media queries are now well-supported in modern browsers including IE9+ and most mobile devices. These can make the difference between a site that degrades well on a mobile browser, vs. one that is enhanced to take advantage of the streamlined UI. But first we have to take into account how smartphones represent themselves to web servers.

Viewports

When is a pixel not a pixel? When it’s on a smartphone. By default, smartphone browsers pretend to be high-resolution desktop browsers, and lay out a page as if you were viewing it on a desktop monitor. This is why you get a tiny-text “overview mode” that’s impossible to read before zooming in. The default viewport width for the default Android browser is 800px, and 980px for iOS, regardless of the number of actual physical pixels on the screen. 

In order to trigger the browser to render your page at a more readable scale, you need to use the viewport meta element: 

Mobile screen resolutions vary widely, but most modern smartphone browsers currently report a standard device-width in the region of 320px. If your mobile device actually has a width of 640 physical pixels, then a 320px wide image would be sized to the full width of the screen, using double the number of pixels in the process. This is also the reason why text looks so much crisper on the small screen – double the pixel density as compared to a standard desktop monitor. 

The useful thing about setting the width to device-width in the viewport meta tag is that it updates when the user changes the orientation of their smartphone or tablet. Combining this with media queries allows you to tweak the layout as the user rotates their device: 

@media screen and (min-width:480px) and (max-width:800px) {
  /* Target landscape smartphones, portrait tablets, narrow desktops

  */
}

@media screen and (max-width:479px) {
  /* Target portrait smartphones */
}

In reality you may find you need to use different breakpoints depending on how your site flows and looks on various devices. You can also use the orientation media query to target specific orientations without referencing pixel dimensions, where supported. 

@media all and (orientation: landscape) {
  /* Target device in landscape mode */
}

@media all and (orientation: portrait) {
  /* Target device in portrait mode */
}

Source : Google Webmaster Central