Google's May 2026 core update finished rolling out on June 2, closing an 11-day window that reshuffled a lot of WordPress traffic between May 21 and early June. The same argument played out in Slack channels and client emails all through the following weeks: revert the content you shipped in the run-up, or leave it alone and wait for the next crawl to reprice the site.
Both instincts are defensible. Both are wrong about half the time. The useful question is which of the two moves fits the specific drop you're staring at, not which camp you belong to.
Two Instincts Point in Two Very Different Directions
The rollback instinct treats a core update like a verdict on the last thing you changed. You shipped a redesigned service page in April, traffic to it fell in late May, so you restore the March version and hope the next recrawl forgives you. It's fast, it feels decisive, and WordPress makes it almost trivial to do.
The sit-still instinct reads the same drop as a repricing of the whole site against a new bar. Nothing you did last month caused it; the bar moved. Reverting a good page to an older, weaker version locks in yesterday's quality signals for a system that has already stopped grading on yesterday's curve.
The trap is picking a camp before you've read the drop. A rollback on the wrong page erases weeks of legitimate improvement. Sitting still on a page that genuinely got worse, thinner, more templated, more obviously written for the algorithm, extends the bleed.
Rolling Back Earns Its Keep in a Narrow Set of Cases
Reverting content is the right move in a narrow set of situations. The common thread: you can point to a specific change, on a specific URL, that made the page worse for a real reader.
WordPress handles the mechanical part for you. The built-in Revisions panel lets you load and restore any prior version of a post, page, or template block, and the official walkthrough covers the exact clicks. The hard part is deciding which revision to restore, not how to restore it.
Sometimes Sitting Still Beats Doing Something
Sitting still is the harder discipline, because it feels like inaction while revenue is down. It's usually the right call when the drop is broad, when your recent changes were genuine improvements, or when the URLs that fell aren't the ones you touched.
Google has been consistent for years that core updates aren't penalties and that pages have no fixed position waiting to be restored. The core updates guidance is blunt about it: improvements don't guarantee recovery, and the fix is rarely a single lever you can pull. Reverting a stronger page to a weaker one to chase yesterday's rankings is exactly the move that guidance warns against.
Helpful content signals now run continuously inside the core system, so pages get re-evaluated as they're recrawled between updates. A genuinely improved page will get its shot without a rollback. You just have to let the crawl reach it. If your April rewrites were real work, sitting still is how they pay off.
Read the Drop Before You Touch the Site
Spend a day on diagnosis before either move. Segment the losses by URL, by template, by intent, and by the date each page last changed. If the drop clusters on pages you rewrote, the rewrite is a suspect. If it's spread evenly across pages you never touched, the rewrite isn't the story and rolling it back accomplishes nothing.
Open the current and prior versions side by side and ask which one you'd rather land on as a stranger with the query in mind. If the honest answer is the older version, restore it. If the honest answer is the newer version, the drop is about how the whole site is being weighed now, and the work is editorial, not mechanical. For WordPress operators specifically, an analysis of the algorithm update for an analysis of the algorithm update for WordPress walks through the quality signals the current core system is leaning on and where site owners tend to misread them.
Most Owners Skip the Move That Actually Works
A third option gets skipped because it's slower than a revert and less dramatic than sitting still: a targeted forward edit. Keep the new page's structure, restore the specific sections of the old version that answered the query best, and ship the merged page as the current version. You're carrying forward what worked, not rolling back.
This is where WordPress's revision history stops being a safety net and starts being a source. Open the prior revision in one tab, the current page in another, and lift the paragraphs, examples, and internal links that made the old version rank. Most of the time the fix isn't the whole page. It's two or three sections that got cut for length or replaced with something more generic.
Rollback and patience aren't opposing philosophies. They're two tools for two different diagnoses, and the operators who recover fastest are the ones who pick per URL instead of per site.
