Skip to content
puluno

Agencies & clients

Rollback recent fixes

When Apply breaks something — how to revert meta, images, or Pulse fixes and where the Center timeline lives.

Typical symptom

After Apply the site is worse, the client calls, or Verify shows a lower score than before the fix.

Puluno modules

SEOImagesPulse

Undo change

Yes — undo in Center

What you see

  • After Puluno Apply the site is worse (layout, meta, images).
  • Verify failed but the change is already live.
  • Client: “Put it back like yesterday.”
  • Agency needs an audit trail — who changed what and when.

Why it happens

Apply touches production data. Without rollback, the fallback is “restore the whole DB” — slow and expensive.

Why Verify fails:

  • Apply on the wrong template (global instead of one page).
  • Conflict with another plugin (cache, minify).
  • Hero replaced with aggressive compression.
  • Pulse defer broke a slider.

What Puluno supports today

ModuleRollback today
SEOCenter — restore meta / title per page or last batch
Imagesrevert single file (before/after preview)
Pulserollback safe fixes batch where supported

Center → Overview → Recent Apply and rollback — one timeline (Pulse, Health, Images, SEO indexability). Undo still happens in the module — the ledger is read-only history.

Step by step

  1. Do not touch hosting or full DB until you know scope.
  2. Stop further Apply — rollback only.
  3. SEO: Center → history / page editor → restore previous title, meta, canonical.
  4. Images: on the attachment Restore original.
  5. Pulse: rollback last safe fixes batch.
  6. Verify: Explorer on the same URL as before the incident.
  7. Log in the ticket: what was reverted, what was not (for the future ledger).

Workflow: Apply → Verify — rollback is step 4 of the loop.

Rollback — undo the change

This article is rollback — use the modules above.

Before bulk Apply for a client: DB backup + meta CSV export.

When it is not Puluno

  • Breakage from manual theme / PHP edits — git revert, not the SEO plugin.
  • Hosting served stale cache after rollback — purge cache, then Verify.
  • Client wants changes older than 30 days back without backup — hosting backup, not Puluno.

Related situations

Module manual

Client-facing report →