Google May Day Update (April 2010): What Changed and How to Recover

The Google May Day update was an algorithm change that ran from 28 April to 3 May 2010 and changed how Google judged which sites best matched long-tail searches. It hit sites relying on long-tail traffic hardest, especially large e-commerce sites with many thin product pages and few strong inbound links. The takeaway: May Day was an early version of the thinking behind Panda, and recovery meant making individual pages worth ranking.

May Day sits between the infrastructure changes and the big quality updates in my full list of Google algorithm updates. If you run a large catalogue site, it is the update most worth understanding from this period, because the same weakness still costs shops traffic today.

What the May Day update changed

May Day changed how Google assessed which sites were the best match for long-tail queries: the longer, more specific searches such as a model number plus a feature, or a detailed question. Before it, a large site could pick up a lot of long-tail traffic simply by having a page for almost every variation, even if each page said very little.

Matt Cutts confirmed the change at a conference and made two points that are still useful. First, it was an algorithmic change, not a penalty that could be lifted on request. Second, it was not related to Caffeine, which was finishing its rollout around the same time and was getting the blame on forums. Search Engine Land reported that head terms were less affected; the losses were in the long tail.

Timeline

• 28 April 2010: rollout began, per Search Engine Land.
• 3 May 2010: rollout ended. The name comes from its timing around 1 May.
• After the rollout: Matt Cutts confirmed the change at a conference and separated it from Caffeine.
• 8 June 2010: Caffeine was announced as complete, which is why the two are often confused.

Who was affected

As reported, the sites that lost most were those relying on long-tail traffic, particularly large e-commerce sites with many product pages but few strong inbound links. Bruce Clay’s history, citing Search Engine Land, describes those sites as the hardest hit. Some affected site owners told Search Engine Land their traffic fell by around 50%; those were reader reports, not measured data, but they show how serious it was for some shops.

How to tell if the May Day update hit your site

May Day had a clear shape: total traffic fell, but the losses were spread thinly across thousands of deep pages rather than concentrated on a few important ones. Here is how to find that pattern in your own data today:

1. Segment by page type. In Search Console’s Performance report, filter pages by URL pattern (for example /product/ versus /category/ versus /blog/). If product pages lost a large share while category pages held, that matches.
2. Count pages with clicks. Compare the number of pages getting at least one click in the period before and after. A May Day-type drop shows fewer pages earning any traffic, not just less traffic per page.
3. Check query length. Export queries and look at those with four words or more. If they fell much harder than short queries, the long tail is the problem.
4. Read a sample of the losing pages. If they share a manufacturer’s description, have one paragraph of text, or differ only by colour or size, you have found the cause.
5. Rule out the obvious. Make sure product pages were not de-indexed by a template change, a noindex tag or a robots.txt rule, and that the season did not change.

How to recover from the May Day update

Google did not reverse May Day. Recovery required quality improvements, and Matt Cutts suggested site owners ask whether people actually consider their site an authority. For a catalogue site, I would work through it in this order:

I would not try to rewrite every page at once. Start with the products and categories that make the most money, measure, then extend. This is the core of my e-commerce SEO services, and the page-level work is covered in my on-page optimisation services.

Is it still relevant today?

Yes, through what came after it. May Day’s approach to long-tail quality was absorbed into later quality systems, chiefly Panda in 2011, which itself became part of Google’s core ranking systems. The specific May Day update is history, but the idea that each page must be worth ranking on its own, and that thin pages at scale are a liability, is very much alive. I still see shops with tens of thousands of copied product descriptions wondering why only their home page ranks.

Frequently asked questions

Sources

• Search Engine Land: Google confirms Mayday update impacts long-tail traffic
• Search Engine Land: Google algorithm updates
• Bruce Clay: Google updates, a history of SEO from 2000 to 2010
• Sistrix: Google updates and algorithm changes
• Wikipedia: Timeline of Google Search

If your shop’s long-tail traffic has been falling and you suspect thin product pages, request a free audit. My SEO audit service identifies which page types are losing traffic and which pages to improve, merge or remove first.