Google started rolling out the May 2022 core update last Wednesday, the 25th. It’s the first broad core update since November, and Google says it will take one to two weeks to finish. So we’re partway through, and the rank trackers are doing their usual impression of a heart monitor.
I’ll keep this short, because the most useful thing I can say about a core update in its first week is: don’t do anything drastic yet.
Why I wait
Core updates roll out unevenly. Pages go up, come down, go up again. If you rewrite your category pages on day three because you dropped four places, you’ve muddied the water for working out what actually happened, and you may well have reacted to movement that reverses by day ten.
So my rule is to note the date, keep normal work going, and only start comparing properly once Google confirms the rollout is complete. Then compare a full week or two after against the equivalent period before, in Search Console rather than a rank tracker, with the same days of the week either side.
What I look at on ecommerce sites
When the dust settles, these are the questions I ask, roughly in order:
- Which page types moved? Category pages, product pages, blog content and the homepage tend to behave differently. A drop concentrated on one template tells you far more than a sitewide number.
- Was it rankings or demand? This week has the two Jubilee bank holidays on top of the usual early-summer lull, so any comparison needs care. Check impressions on your brand terms before blaming Google for a sales dip.
- Who replaced you? Look at the pages that now sit above you for the queries you lost. Retailers, publishers, marketplaces, manufacturers? That tells you what Google thinks the searcher wanted.
- Did product reviews content move? Google’s product reviews update in March was aimed at thin “best X” content. If you publish buying guides, look at those separately.
What core updates are about
Google’s guidance on core updates has said the same thing for a couple of years: there’s nothing specific to fix, it’s a reassessment of overall quality and relevance. That’s unsatisfying when you’ve just lost traffic, but I think it’s honest. Their own advice points you back to the old questions about expertise, originality and whether the content actually helps the person searching.
For ecommerce that has a slightly awkward edge. Many shops have hundreds of category pages with a thin block of text bolted on at the top or bottom “for SEO”. Nobody reads it. It was written to have some words on the page. I’ve never been convinced that helps, and each core update makes me less convinced. If I’m going to put words on a category page, they should help someone choose: what the differences are between the products, which size or fit to go for, what to look out for.
Keep a log
The simplest habit I’d recommend to any ecommerce team is a change log: a shared spreadsheet with the date and a line for every meaningful change to the site. Template releases, migrations, big content edits, new apps, tracking changes, plus the dates of Google updates as they’re announced.
When traffic moves, the first question is always “what changed?”, and without a log the answer is a mixture of memory and guesswork. With one, you can line up a dip against a deployment and a core update and see which fits. It takes a couple of minutes a week.
And what I’m not touching
I’m not changing title tags across the board, not deleting content in a panic, and not buying links. If, once the update has finished, a section of a site has clearly lost out to pages that serve the searcher better, then I’ll plan the content work to fix it, and that won’t be quick.
I’ll look again in a couple of weeks once Google says it’s done.