2026-09-14 08:12 UTCExample
Clicks for 'emergency plumber leeds' fell 38% after a competitor put opening hours first. Rewrote the title and added today's hours to the top of the page. Checked live.
Sister product
After the restore, Unpushed runs the site.
Reflogged brings the site back. Unpushed is the sister product that looks after it from then on: it reads how the site is doing in search, fixes what's slipping, and checks every change on the live page.
01
What Unpushed is
Unpushed is auto-SEO for a site you already have. It reads your Search Console, your visitors and the search results every day, decides what to fix, makes the change, and checks it landed. You stay about 99% hands off.
Changes go into the site's own code, not a plugin or a layer on top. The site can live on Cloudflare with its pages in GitHub, and that repository is yours.
No plugins, no tracking pixels, nothing to update.
02
What it reads
Search Console
Queries, pages, clicks, and what Google stopped showing.
Your visitors
First-party analytics, how people actually use the pages.
Competitors
Who took your position, and with what page.
The search results
What a stranger sees for your queries today.
03
What it does
- 01
Read
- 02
Decide
- 03
Ship
- 04
Check
Each change comes with the reason behind it. You approve it, Unpushed ships it into the site's code and reopens it if the live page doesn't match.
04
Why a restored site needs this
- A restore brings back the pages as they were. It doesn't bring back the years of attention that made them rank.
- A site that has been offline has lost rankings, and some pages link to things that no longer exist.
- For an acquired domain, the old text belongs to someone else and needs rewriting before it's yours.
- Unpushed is built for the ongoing part: noticing what slipped, fixing it and checking it.
05
What Reflogged sends to Unpushed
Stays in Reflogged
- The stored archive
- The report
- The run history
Goes to Unpushed
- Domain
- Vintage (the point in time you restored)
- Strategy
- Rights
- Page, asset and redirect counts
- Completeness (Wayback pages, Common Crawl text pages, missing)
- The manifest (every URL with its capture time and source)
- Links to the stored files
- The buy/skip verdict if you ran a report
Files travel as private, time-limited download links, not as a public copy.
06
Choose how Unpushed treats the old site
Keep
“The restored pages are the site.”
Best when you own the site and want it back as it was, with the same URLs.
Extend
“The restored pages are the base. New pages are added around them.”
Best for an acquired domain you'll rebuild over time.
Wipe
“The restore is reference only. The new site starts fresh.”
Best when the old content isn't yours to reuse or doesn't fit what you're building.
I own this site → defaults to KeepI acquired this domain → defaults to Extend
Buying a domain doesn't transfer the old site's copyright. If you acquired it, plan to rewrite what you keep.
07
What happens after you press Send
- accepted
Unpushed has the handover and starts pulling the files.
- seeding
It creates the site and repository, stores your strategy, and builds a first plan from the old URL structure and what the site used to rank for.
- ready
You get a link to the site in Unpushed.
- failed
You see the reason. The restore stays exactly as it was, and you can send again. Sending twice never creates two sites.
08
What stays with you
- Your domain
- Your repository
- Every release
- Your data
If you leave Unpushed, the site and its history leave with you.
09
Who does what
Reflogged
- Checks the domain
- Restores the vintage
- Stores the archive
- Writes the report
Unpushed
- Creates the site
- Runs the SEO
- Ships and checks changes
- Handles access and billing
—