How do I update a site I already deployed?

Push again with the same site name - the same URL updates in place. pushd remembers your last site per provider and shows 'Update site' with the existing link so you know before you click.

Can I roll back to an earlier version?

Yes - open History and hit Redeploy on any earlier deploy. pushd keeps a local snapshot of what you deployed (up to ~5MB per deploy) and pushes it again.

My update isn't showing - is it broken?

Usually it's your browser cache showing the old version. Hard-refresh (Ctrl+Shift+R / Cmd+Shift+R) or open the URL in a private window. GitHub Pages also takes up to a minute to rebuild.

What does the Live / Unreachable badge mean?

pushd periodically pings your deployed URLs (about twice a day) and badges them Live or Unreachable. On the free plan it monitors your latest site; Pro monitors everything in history.

Docs

Updating sites, history and rollback

A deployed page is rarely finished. How updates, version history and “undo” work:

Updating a site

Push again with the same site name and the same URL updates in place - that’s the entire mechanism. From an AI chat, hit ↑ Push on the revised page and keep the suggested name (pushd remembers your last site per provider, so it’s usually pre-filled). From files, drop the new version in and keep the name.

Updates are fast - seconds on most providers, up to a minute on GitHub Pages while it rebuilds.

“I updated but still see the old page”: almost always your browser cache. Hard-refresh (Ctrl+Shift+R, Cmd+Shift+R on Mac) or check in a private window before assuming anything failed.

History

Every deploy is recorded locally - the popup’s History tab shows recent ones, and Dashboard → History has the full picture: your last 50 deploys and per-deploy actions:

Copy URL / open
Share / QR - same share kit as the result screen
Redeploy - below
Export CSV - downloads pushd-history.csv with the lot
Clear history - wipes the log (asks twice; your live sites are unaffected)

History lives only in your browser. Nothing is sent anywhere.

Note: this means uninstalling the extension loses your history.

Redeploy - your rollback button

pushd keeps a local snapshot of the content of each deploy. Redeploy on any history row pushes that exact version again - so rolling back a bad update is: find the last good deploy, hit redeploy, done.

Two caveats:

Snapshots are skipped for deploys over ~5MB, so very large sites won’t have a Redeploy button - push those again from the source.
If a deploy has no snapshot you’ll see “No saved copy for this deploy - push it from the source again.”

(On GitHub Pages you additionally get provider-side history - every deploy is a commit in your repo, forever. Details.)

Health checks

pushd can ping your deployed URLs and badge each site Live or Unreachable - handy for spotting a Tiiny site that expired or a host that paused you. Checks run at most about twice a day, and the first check per provider asks for a Chrome permission (so the extension may reach *.netlify.app etc. - one click to grant).

Free plan monitors your latest site; Pro monitors everything in history. If a badge says Unreachable, the troubleshooting page covers likely reasons per provider.

Add pushd to Chrome - it's free All docs