Google’s March 2026 Core Update Is Rolling Out: What to Watch

Have your rankings or traffic started moving this week? The March 2026 core update is the most likely reason. Google began rolling it out on 27 March 2026, and it is still going. My advice for most site owners right now is simple. Watch, take notes, and hold off on big changes until the rollout is complete.

This guide covers what Google has confirmed so far and what a core update does and doesn’t do. It also covers how to track it calmly while it rolls out, and the steps to follow once Google says it has finished.

What Google Has Confirmed About the March 2026 Core Update

Here is what’s on the record as of 28 March:

• Start: the Search Status Dashboard lists the rollout as starting at 02:00 PDT on 27 March 2026 (09:00 UTC). Google posted its release note at 02:14 PDT.
• Length: Google says the rollout “may take up to 2 weeks to complete.” Counting from the start, that puts the likely finish around 10 April. Google hasn’t promised a date, though.
• Scope: it’s a broad core update, the first of 2026. Like other core updates, it isn’t aimed at one niche, one language or one type of site.
• Purpose: in its announcement, Google Search Central called it “a regular update designed to better surface relevant, satisfying content for searchers from all types of sites.”

Google hasn’t said which signals changed, and it rarely does for core updates. Be careful with any post that claims to know exactly what this update “targets”. Nobody outside Google knows that, least of all two days into the rollout. I skip those posts.

What a Core Update Actually Is

A core update is a broad change to the systems Google uses to rank results. Google runs several a year. The goal is to improve how its systems judge which pages best answer a search overall. It is not meant to punish particular sites.

That difference matters. If your pages drop during a core update, Google says there is usually nothing “wrong” with them. Other pages are now judged more useful for those searches, and the ranking order has been shuffled to match.

Here is how I explain it to people. Picture a list of the best books on a topic, updated once a year. A book that drops from third to seventh hasn’t got worse. New books came out, or the people making the list changed how they weigh things. Core updates work the same way. For the bigger picture of how ranking fits next to crawling and indexing, see our guide to how Google Search works in 2026.

Core Updates vs Smaller Ranking Changes

Google also makes smaller core updates all the time without telling anyone. It doesn’t announce them because most people wouldn’t notice their effect. A named core update like this one is different. Google announces it because many sites are likely to see movement.

Where You Might See Changes

Core updates mainly affect normal web results. But the effects can show up anywhere Google uses the same quality systems. That includes Google Discover, featured snippets, and image or video results. If Discover sends you a lot of traffic, watch it on its own.

What Google Says You Should (and Shouldn’t) Do About It

Google’s advice on core updates has stayed the same for years, and it applies to this one too.

There’s No Specific Fix

A traffic drop after a core update isn’t a manual action or a penalty. So there is nothing to “fix” and no reconsideration request to file. Google says most sites don’t need to do anything at all. Its advice also warns against quick fixes, like removing parts of a page because someone thinks they hurt SEO.

Focus on People-First Content

What Google points to instead is content that is “helpful, reliable, and people first.” In practice, that means content made mainly to help real readers, not mainly to pull in search traffic.

Google lists several warning signs of content made for search engines first:

• publishing on lots of unrelated topics in the hope that some of them rank
• mostly summarising what others have written without adding anything new
• writing to a set word count because you think Google prefers it (it doesn’t)
• changing a page’s date to look fresh when nothing important changed
• leaning heavily on automation to produce content in bulk

Use the Self-Assessment Questions

Google publishes a set of self-check questions in its guide to creating helpful, reliable, people-first content. They are grouped around content quality, expertise, page experience, and whether the content is people-first. Some examples, in my own words:

• Does the page offer original information, reporting, research or analysis?
• Does it go past the obvious and add real value compared with other pages in the results?
• Is it clear who wrote it, and is there proof they know the subject?
• Does it have mistakes a reader could easily spot?
• Would someone leave the page feeling they learned enough to reach their goal?

Google also asks you to think about “Who, How and Why”. Who made the content? How was it made, including any big use of automation or AI? And why does it exist? The authorship and trust questions overlap a lot with the ideas of experience, expertise and trust that Google’s quality advice keeps coming back to.

Google suggests these questions are easier to answer honestly if someone outside the site works through them. In other words, don’t mark your own homework. I agree. Site owners are almost always too kind to their own pages.

How to Monitor Rankings While the Update Rolls Out

Rankings often swing back and forth during a core update. A page can drop on day two and come back by day nine. So checking day to day tells you very little. What helps is a steady record you can compare against once the rollout ends.

Separate It From the March 2026 Spam Update

This week brought two separate updates, and it’s easy to blame the wrong one.

Google released the March 2026 spam update at 12:18 PDT on 24 March and said it was complete on 25 March. The core update didn’t start until 02:00 PDT on 27 March. So there’s a clear gap between the two.

Did your traffic fall sharply between 24 and 26 March, before the core update started? Then the spam update is the more likely cause. Our breakdown of what the March 2026 spam update targeted explains what to check. If the change began on or after 27 March, it’s more likely the core update. The two can overlap in your data, though, so keep notes on exact dates.

Set Up Your Search Console Comparisons Now

Search Console is the most reliable record of how Google sees your site. A few minutes of setup now makes the review after the update much faster.

• Record your baseline. In the Performance report, note clicks, impressions and average position for the week before the rollout, 20 to 26 March. Export it. The spam update falls inside that window, and you’ll want a clean record of it. This is always the first thing I do when an update starts.
• Note your top pages and queries. Export the pages and queries that bring most of your clicks. Then you can track the ones that matter, not the whole site.
• Split by search type. Check Web, Image, Video and News on their own, and check the Discover report if you have one. A drop in one place can be hidden by steady numbers in another.
• Note your own changes. If you launch anything during the rollout, like a redesign, a site move or a batch of new pages, write down the date or add a GA4 annotation. Otherwise you won’t be able to tell your changes apart from Google’s.

Would you rather build these views by describing them than by clicking through filters? Our guide to Search Console’s AI report builder explains how to use that tool.

Wait Until the Rollout Is Complete

Google advises against drawing conclusions in the middle of a rollout. Its process starts with checking that the update has finished on the Search Status Dashboard. Then you wait at least a full week before comparing data. That gives the new rankings time to settle. It also gives you a full week of data from after the update, not a mix of before and after. I gave the same advice while the June 2025 core update was rolling out.

Keep checking the dashboard. The core update entry will be marked complete when Google confirms it has finished.

Rule Out the Boring Explanations

Not every drop this week is down to Google. Before you blame the update, check the everyday causes:

• a site change: new templates, robots.txt edits, noindex tags, broken redirects
• seasons: Easter falls on 5 April this year, which can shift demand in travel, retail and events
• tracking problems: a broken analytics tag can look like a traffic drop when Search Console shows nothing changed
• demand shifts: impressions falling for a search across the board may just mean fewer people are searching for it

What Not to Do While the Update Is Rolling Out

In my experience, the costliest mistakes during a core update come from acting too early. Avoid these until the rollout has finished and you’ve looked at the data:

1. Don’t rewrite or delete content based on a few days of data. Rankings may come back on their own before the rollout finishes. Google calls deleting content a last resort, not a first step.
2. Don’t change pages that are still doing well. Google clearly warns against changing content that already ranks well. If a page slipped from second to fourth, that’s normal movement. It’s not a reason to rebuild it.
3. Don’t chase “update recovery” tricks. Buying links, adding FAQ blocks stuffed with keywords, changing publish dates in bulk, or deleting sections because of rumours won’t change how core systems judge your site. Some of these can break the spam policies.
4. Don’t launch big site changes if you can avoid it. A site move, a new URL structure or a CMS switch in the middle of a core update makes it almost impossible to tell what caused what.
5. Don’t read too much into tracking tools. Third-party volatility trackers show that something is happening across many sites. They can’t tell you why your own site moved.

Keeping up normal work is fine. Publish what you planned, fix real technical bugs, and keep serving your readers. The point is to avoid panic changes that muddy your analysis later.

How to Assess the Impact After the Update Finishes

Once Google marks the March 2026 core update complete and a full week has passed, you can compare the data properly. Follow these steps.

1. Check the dates. Look at the Search Status Dashboard for the official start and end of the rollout.
2. Compare the right weeks. In the Search Console Performance report, compare the full week after the rollout ended with the week before it began. Don’t compare against the rollout period itself.
3. Sort by the biggest changes. Look at your top pages and queries and sort by change in clicks. Find where most of the change sits: a handful of pages, one section, or the whole site.
4. Judge the size of the drop. Google draws a clear line here. A small move, like position 2 to 4, doesn’t call for drastic action. A big one, like position 4 to 29, calls for a closer look at that content.
5. Check each search type. Repeat the comparison for Web, Image, Video, News and Discover, so you know which one actually moved.
6. Review the site as a whole. If the drop is big and lasts, check the whole site against Google’s self-check questions, not just the affected pages. Ideally, get someone outside the business to do it.
7. Look at what replaced you. Search your most affected queries and look honestly at the pages that now rank above you. Ask what they give the searcher that your page doesn’t. I find this step teaches more than any tool.

A Practical Example

Imagine you run a home improvement site. After the update, your guide on fixing a leaking tap drops from position 3 to position 22. The rest of the site barely moves.

You search the query. The pages now above you have step-by-step photos, notes on different tap types, and authors who are clearly working plumbers. Your page is a 400-word overview with no author and advice you could find anywhere. That’s a content quality gap, not a technical problem. The answer is to make the page truly more useful.

Now compare that with a site where traffic fell by 10% across hundreds of pages, each slipping a position or two. Google’s advice there is to avoid drastic changes. That’s the kind of reshuffle core updates often cause.

Make Meaningful Improvements, Not Cosmetic Ones

Where you do find real weak spots, Google recommends lasting improvements. That means rewriting content to be clearer and more useful, and reorganising it so readers can find what they need. It also means adding the first-hand knowledge or original detail that’s missing. Remove or rework sections only if they exist mainly to attract search traffic, not to help people.

Your answers now show up in AI features as well as blue links. So it’s also worth checking how your pages appear there. Our comparison of how AI Overviews and AI Mode pick their sources explains what each one looks for.

How Long Recovery Can Take

Set expectations early, especially if you report to clients or a boss. Google says some improvements can have an effect within days. But its systems can take several months to confirm that a site keeps producing helpful content. I cover realistic timelines in my guide to how long SEO takes.

Google also says that if you’ve made changes and seen no effect after a few months, you may need to wait for the next core update. Improvements aren’t guaranteed to bring rankings back. Other sites are improving too, and search demand keeps changing.

For the full process in Google’s own words, read the Search Central page on what site owners should know about Google’s core updates.

Conclusion: What to Do About the March 2026 Core Update This Week

The March 2026 core update is rolling out now and could take up to two weeks. For most sites, the right move this week is to record a baseline in Search Console and separate out any effects from the 24 and 25 March spam update. Then avoid panic changes until Google confirms the rollout is complete.

Once it finishes, wait a full week, compare like with like, and judge any losses honestly against Google’s people-first advice. If I were using the waiting time well, I’d read our guide to E-E-A-T and start reviewing my most important pages through that lens.