Blog / Technical SEO /
After Google’s May 2026 core update: checking pages before changing them
After a core update, the urge is to open the biggest traffic-loss report and start rewriting. Resist it. A page can move for reasons that have nothing to do with a flaw in its copy, and a rushed edit makes later analysis harder.
Google’s May 2026 core update began on 21 May and finished on 2 June, per the Search Status Dashboard. Use the rollout as a comparison boundary, then inspect page groups carefully before deciding what to change.
Wait and define the question
Google recommends waiting at least a full week after a core update completes before analysing Search Console performance. Once that’s passed, compare the post-rollout week with a representative period before the rollout began.
Then ask something specific. Did a product category lose impressions? Did one page type lose clicks? Did a few queries change position? Keep device, country and search type aligned, and note any promotions, inventory shifts, redesigns or tracking changes that overlapped the update.
Look beyond the top-line chart
Segment the data by landing page and query, then compare pages that serve similar intent. A broad average can hide gains and losses that cancel out.
Check that the page still matches the product or service you actually offer, that key information is easy to find and that technical access is healthy. Look at the search results to see what users see, but don’t infer one algorithmic reason from how a competitor appears. Search Console is useful evidence, not a full explanation of how every search was served.
Make one reasoned improvement
If you find a verified content gap, an outdated fact, a confusing journey or a technical defect, fix it and document the change. Don’t add paragraphs just to make a page longer. Length is not a quality signal, and padding makes a decent page worse. If a page already answers the question, leave it alone.
Keep content that’s still useful, and avoid drastic edits to pages with only small movements. Google’s systems keep changing, so there’s no guaranteed recovery date. Set a sensible review point and watch the same page group. A week of calm data after your fix tells you more than a day of excitement.
Put the process into practice
Keep a change log: which pages changed, what you changed and what evidence motivated the work. If you edit several page groups, stage the work so you can tell what helped. An undiagnosed bulk rewrite teaches you nothing.
Ask whether a page is genuinely less useful, or just exposed to a different mix of searches. When I audit after an update, I check the technical reports and the rendered content before I blame the text, because a rendering or indexing fault is cheaper to find and fix than a rewrite.
When you report back, share findings as observations, hypotheses and decisions, and label each one. That stops a correlation turning into an internal story everyone later repeats as fact.
Close the loop
If the first review shows no clear defect, leave the page alone and keep watching. Don’t invent a content task to look busy. Note what evidence is missing and when you can revisit it.
I’d rather report an honest unresolved question than a confident explanation built from timing alone.
A short checklist for one page
Before I edit any page that dropped, I run through the same few questions.
- Does it still match what the searcher wanted, or has the intent shifted?
- Is the key information easy to find without scrolling past filler?
- Are the facts current: prices, specifications, dates, policies?
- Is it crawlable and indexable, and does it render properly on a phone?
- Did anything else change on that page or its template around the same dates?
If all five come back clean, the page probably doesn’t need an edit. It may just be competing in a different mix of results than it was before.
A final sense check
Make the record easy to continue: scope, comparison period, filters, gaps and a next action. Where a dependency sits with another team, note the handoff.
And choose one example page for each group, so the expected result is concrete and checkable.
Related reading
- The March 2026 core update: a measured post-rollout review
- The March 2025 core update: what store owners can check
- Orphan pages: how to find them and give them links
Which page has an observable user problem you could fix independently of the update?