May Core Update: How to Analyze Your Traffic Changes

What is the May core update and when did it roll out?

The May core update is a broad change to Google's ranking systems. According to the Google Search Status Dashboard, it began on 21 May 2026 and finished on about 2 June 2026, after roughly 12 days. It does not target specific sites; it adjusts how ranking works in general.

Google's note on the dashboard was short. It said the update had been released and that the rollout could take up to two weeks. Our team confirmed the dates directly on the dashboard, using the timestamps under that note.

Even if you read this months after the rollout, the topic has not aged. Many sites still try to explain their May traffic swings today. Below, we walk through how to read your own data, step by step.

How did Google officially announce the May core update?

Google announced the update on the Search Status Dashboard. That page lists the start and end times of every ranking event in one place. So when you need to verify an update, start there rather than with social media.

As far as we could see, Google did not publish a companion blog post or explain its goals. As a result, nobody outside Google knows exactly what changed. Saying this openly is simply the honest position.

Be careful here. However, plenty of commentary claims the update hit this or that industry. However, most of it rests on small private samples, not official data.

What we can state with confidence:

• The update started on 21 May 2026.
• It finished on about 2 June 2026.
• It belongs to the core update class, not the spam update class.
• Google did not say it targeted any particular group of sites.

What is the difference between a core update and a spam update?

A core update recalibrates how ranking systems judge helpful, reliable content. A spam update targets techniques that break Google's spam policies. The two work differently, so the fixes differ as well.

You cannot call a core update a penalty. Google's own guidance makes this clear: core updates do not target specific sites or pages. If you lost rankings, other pages are usually answering the query better.

A spam update is different. If you broke a policy, affected pages can drop. For that side of the story, read our guide on how Google spam updates work and how to protect your site.

How does the May core update differ from the March update?

The March update started on 27 March 2026 and ran for 12 days and 4 hours. The May update started on 21 May and ran for 11 days and 21 hours. Both appear as core updates on the dashboard, so the mechanism is the same and only the timing differs.

We covered the March rollout in a separate post: March core update complete, what to do next. We will not repeat it here.

This article answers a different question. How do you read the data from both updates together? For example, a page that fell in March and recovered in May may not be a coincidence. The reverse also holds: a page that gained in March and gave it back in May may share one content problem.

That is why we suggest placing both date ranges side by side. Looking at a single update shows only half of the story.

When you compare the two periods, track three numbers per page: clicks after March, clicks after May, and the total change. This small table shows which pages are stable and which swing. Stable pages then become your reference point, because you can learn what you did right on them.

What should you do first if your traffic changed?

Wait. Google recommends waiting at least one full week after the update completes before you analyze Search Console. Rankings move while an update rolls out, so early data misleads you, and you may react to noise.

After the waiting period, the job is simple. Compare the week after the update ended with the week before it began. That is Google's own suggested method.

Panic moves often do harm. For example, deleting hundreds of pages in a hurry can remove the traffic you still have. On our team, we calm the data first and build a hypothesis second.

At this stage, answer three questions:

1. Did the drop hit the whole site or only some sections?
2. Did it hit specific queries or all of them?
3. Does the drop date match the update dates?

How do you set up the right comparison in Search Console?

Open the Performance report and use the compare option in the date filter. First, put the week after the update on one side and the week before on the other. Then you see clicks, impressions, CTR and average position differences in one table.

Do not trust average position alone. When new queries enter the list, the average can shift for reasons unrelated to quality. Therefore, check the query and page breakdowns separately.

Before you start, review the basics in what Google Search Console is and how to use it. It also helps to read the report next to Google's Performance report documentation.

A few practical tips:

• Compare two periods with the same number of days.
• Match the same weekdays, because weekend traffic behaves differently.
• Filter brand queries out in a separate view.
• Check country and device breakdowns too.

Why should you analyze brand queries separately?

Brand queries are searches from people who already know you. A core update rarely affects them, because the user is looking for you directly. If you mix brand traffic into the total, you hide the real loss or gain.

For example, your total clicks may look flat. Yet brand clicks could have grown while non-brand clicks fell. In that case, the real problem stays hidden. So trusting the total and saying "no issue" can be expensive.

In Search Console, add a query filter with your brand name and choose "does not contain". Then run the same comparison again. Often the true picture appears on this second look.

Also, non-brand traffic is where your content competes with others. It is also where you measure the effect of a core update best. For that reason, non-brand data should form the main body of your report. Brand queries go in an appendix, where you only read the trend in awareness.

Was it the May core update or something else?

Not every drop comes from an update. A technical error, a site migration, a robots.txt change or plain seasonality can produce the same chart. So rule out these alternatives first, then blame the update.

There is an extra source of confusion for May. The dashboard shows that the June spam update started on 24 June 2026. It arrived about three weeks after the core update finished, and it can blur your data.

Apply this table to your own site:

To rule out the technical side, see how to find unindexed pages in Search Console.

Which pages does a core update usually affect?

We cannot give you a fixed list, because Google did not publish one. However, you can find the affected pages on your own site with data. First, group your pages by type and calculate the change for each group.

For most sites, the groups look like this: home page, product or service pages, blog posts and category pages. For each group, write the click change as a percentage.

Next, rank the groups. The group that lost most is the likely center of the problem. The group that gained most shows where the update worked in your favor.

For example, if blog posts fell while service pages stayed flat, the problem is not site-wide. Then you focus on old and weak posts. This split saves both time and effort. It also gives your team a clear to-do list, because you can say "fix these ten pages" instead of "fix everything".

You can do this work in a spreadsheet. Export the page data from Search Console and filter by type. Once the table is ready, you also hold clear evidence for your manager.

If you prefer a quick first look, try our SEO checker tool on single pages.

What does Google's helpful content guidance say here?

Google's guidance tells you to write for people, not for search engines. Core updates surface pages that follow this principle better. So you need to read your own content through the eyes of a reader.

Google's core update page sums up the approach like this: offer helpful, reliable, people-first content, and avoid content written mainly for algorithms. For details, read Google's guidance on creating helpful content.

To make this concrete, ask yourself:

• Does the page answer the real intent of the query directly?
• Is it clear who wrote it and from what experience?
• Does it contain something original that competitors lack?
• After reading, does the visitor need another search?

For a wider view on trust signals, see what E-E-A-T is and how Google trust criteria work.

How do you prioritize the pages that lost traffic?

You cannot fix every falling page at once. So build a simple priority list using impact and effort. Start with the pages that lost the most traffic, because they are easiest to justify.

On our team, the order is as follows. First, we look at the commercial value: does the page bring sales or enquiries? Then we weigh the size of the loss. Finally, we estimate the effort.

1. High sales value and a big loss: work on these now.
2. Sales pages with a small loss: watch them weekly.
3. Low sales value but a big loss: strengthen or merge the content.
4. Low value and a small loss: leave them for now.

Even if you have hundreds of pages, the top ten usually carry most of the traffic. Limit your list to ten and start there. This order spends limited resources in the right place. Moreover, each decision has a reason, so you can answer "why this page?" when your manager asks.

How do you fix weak content step by step?

When you fix a falling page, first compare it with the results on page one for the same query. Note which questions they answer better and what information they offer that you do not. Then close that gap, because that gap is your real brief.

For example, the fix usually consists of these jobs:

• Shorten the intro and answer the question in the first paragraph.
• Update old facts and show the update date.
• Add author details and source links.
• Simplify repeated sections.
• Add an original example, table or checklist.

Google does not suggest deletion as a first fix; instead, treat it as a last option when a page cannot be saved. Still, if you have dozens of weak posts on a similar topic, our content pruning guide helps you decide.

How long does recovery take?

According to Google, some improvements take effect within days, while others need months for its systems to reassess the whole site. If you see no improvement after several months, you may have to wait for the next core update.

This statement sets realistic expectations. Do not expect today's fix to work tomorrow. Patience is part of the job. Keep a weekly note of which change you made and when; this makes it easy to connect cause and effect later.

Two mistakes are common here. First, teams try a new strategy every week and measure none of them. Second, some do nothing and waiting for the next update.

The right path is clear: form a hypothesis, apply the fix, wait a set period and read the result with the same metric. For a realistic frame on timing, see how long SEO takes to work.

Here is an example (illustrative calculation, not real client data). A page drops from 1,000 to 800 monthly clicks, a 20 percent loss. That alone is not an alarm; it gains meaning when other pages of the same type fell by a similar amount.

How do you avoid mistaking normal fluctuation for an update?

Rankings move a little every day, so noise is normal. If you read that movement as an update, you make needless changes. Therefore, set a threshold that decides when a change counts as real.

We usually look for two conditions, because one alone misleads. First, the change should last for several weeks. Second, it should concentrate on a specific group of queries.

Without both conditions, you are most likely seeing normal fluctuation. For a fuller framework, read why SEO rankings fluctuate and when to act.

In addition, following the steps in how to diagnose a traffic drop and SERP losses in Search Console makes clear which loss is real.

How do AI search results change this picture?

AI-powered search experiences were also in the news during the update. However, do not mix the two topics. A core update concerns ranking systems, while AI summaries change how the results page looks.

So if your clicks fall while your position stays flat, look for another cause. When impressions hold steady but clicks drop, something new may sit above your result.

To measure this, check CTR by query. If position is stable and CTR is low, the problem is the layout of the results page, not content quality. Then sharper titles and descriptions, and becoming a cited source in AI summaries, gain priority.

For help, see how to write content for AI Overviews and our AI SEO and GEO service.

Do titles and meta descriptions play a role in the drop?

A core update does not directly punish title tags, however. Still, once your ranking changes, your look on the results page matters more. A weak title stops you from turning position into clicks.

So review the titles and descriptions of the pages that fell. Clear, question-style titles with an obvious promise usually read better.

Before you change anything, use a Google SERP preview tool to see whether the title gets cut off. A truncated title hides half your promise from the reader.

Also keep these points in mind:

• Move the main keyword closer to the start of the title.
• In the description, state the page's promise and the benefit to the reader.
• Do not reuse the same title on several pages.

How do you read the May core update on ecommerce and service sites?

We cannot say what this update did to any given industry, because no official industry data exists. Your reading method, however, changes slightly by site type. For example, ecommerce sites should track product and category pages separately.

On ecommerce sites, trouble often appears on thin category pages. On service sites, city or service variation pages tend to share near-identical text. In both cases, the issue is that the page gives the reader nothing original.

Build your page type breakdown with these groups:

• Product or service detail pages
• Category and listing pages
• Blog and guide content
• City, region or variation pages

For details specific to shops, see our guide to ecommerce SEO for product and category pages.

What should you check technically after the update?

A core update is not a technical update. Still, if your site has a technical problem, you will blame the update and miss the real cause. So run a short technical check in every analysis.

These four checks are enough:

1. Is there a sudden jump or drop in the index coverage report?
2. Are server errors and redirect chains clean?
3. Have page speed and Core Web Vitals got worse?
4. Did someone change robots.txt or noindex tags by mistake?

For speed and experience metrics, read what Core Web Vitals are: LCP, INP and CLS. If the technical side is clean, content and competition remain. That way you narrow the diagnosis.

How do you report the May core update to your manager?

Managers want to hear business impact, not SEO terms, because they decide on budgets. So start the story with "which revenue line was affected", not "traffic fell by X percent". Then add the cause and the plan.

So be honest in the story. If Google did not explain its goals, say so and mention that you are making an informed guess. Sounding certain may look confident, but it damages trust when you turn out to be wrong.

Keep three sentences ready for the meeting:

• What happened: which page group changed, when and by how much.
• Why it may have happened: what the update dates and page type data show.
• What we do next: priority pages, owners and a measurement date.

This structure keeps the talk on the plan instead of blame. In addition, set an owner and a date for every item before the meeting ends.

Which mistakes come up most often after an update?

The most common mistake we see in the field is deciding too early. People who delete content before the update ends often see rankings return later. To avoid this, set a waiting rule.

The second mistake is judging the whole site from one page. A single page falling does not mean the site has a general problem. So always think in groups.

The third mistake is never looking at competitors. Ranking is relative: even if you did not change, a competitor's improvement can push you down. For that comparison, use how to do SEO competitor analysis.

In short, the list looks like this:

• Deciding before a week has passed.
• Mixing brand traffic into the total.
• Blaming content before ruling out technical issues.
• Making dozens of changes with no measurement date.

What is a short checklist you can use after any update?

Read this section as the summary of the article. If you follow the steps in order, you read your data with confidence and avoid needless changes. We suggest adding the list to your team's calendar.

1. Verify the dates on the Search Status Dashboard.
2. Wait at least one week after the update ends.
3. Compare the week after with the week before.
4. Keep brand queries separate.
5. Break the loss down by page type and find the concentrated group.
6. Check technical health and rule out other causes.
7. Improve pages in priority order and note the date.
8. Read the result again after a few weeks with the same metric.

These eight steps hold for any update, so treat the list as a lasting routine instead of a one-off for May.

The main lesson of the May update is to rely on official sources and to wait. A single update does not decide your site's fate; your habit of producing helpful content does. Because Google did not explain its goals, treat every claim of the form "this industry definitely lost" with suspicion, and lean on your own data.

How do you prepare for the next core update?

Google releases core updates several times a year, according to its own documentation. So instead of waiting for the next one, keep your site in good shape all the time. Preparation starts before the update, not after it.

With our clients, we suggest this routine:

1. Export and archive Search Console data every month.
2. Run a content audit every quarter.
3. Refresh your main pages at least once a year.
4. Follow the Search Status Dashboard and add update dates to your notes.

An archive of older data becomes your most valuable asset at the next update. You can only say whether a drop is real if you hold data to compare against.

Also consider tying the routine from our guide to content freshness and update strategy to your calendar. Keep the routine small so it lasts. One hour of archiving per month and half a day of content review per quarter is a good start for most businesses.

When do you need professional support?

Get support if you cannot read your data or cannot find the cause of a drop. The cost of a wrong move is high, especially when most revenue comes from organic traffic. In that case, an outside view speeds up your work.

On our team, these audits focus on three things: measurement accuracy, the page type breakdown and a content comparison against competitors. You can read about the scope on our SEO consulting service page.

One more point: no consultant can guarantee recovery within a set time after a core update. Stay away from anyone who does. If you contact us, prepare your Search Console access and six months of data, and the first call will be much more concrete.

Finally, remember that update news is often louder than the reality. If you stay calm and rely on official dates, your own data and Google's written guidance, you avoid both needless panic and false hope.