Webflow change history, on a timeline the whole company can read.
Webflow keeps backups and publish points — but they live in the Designer, where only the people building the site look. CoNote will put each site publish and CMS change on one shared timeline, beside the campaigns and deploys from the same day.
Site published — pricing page updated
Webflow· 12:15
Pricing campaign launched — $300/day
Google Ads· 12:40
Finding your history
Your Webflow change history: today, and once CoNote is live
The manual way · inside Webflow
Where to find it today
Some of it’s tracked — the rest you reconstruct:
- 1
Open the project in the Designer
Pick the site you’re curious about — publish and backup history is kept per site, inside the Designer.
- 2
Open the Backups panel
Webflow auto-saves backups and marks publish points, so you can see and restore an earlier state of the site.
- 3
Read the publish indicator
The Designer shows when the site was last published and to which domain — but not an easy, shared log of every publish over time.
- 4
Hunt down CMS item changes
CMS Collection items don’t keep a rich change history, so to see when an item changed you rely on memory or your own notes.
- 5
Piece the site timeline together yourself
Nothing lines publishes and CMS changes up against your campaigns or deploys — so you assemble that by hand.
The CoNote way · coming soon
Where you’ll find it once it’s live
Connect Webflow once. After that it’ll be seconds:
- 1
Open your CoNote timeline
Every site publish and CMS change will be in one feed — no Designer access, readable by anyone.
- 2
Jump to the day it moved
Scan the day traffic or conversion shifted; the publish will be stamped right there.
- 3
See it beside everything else
The change will sit next to that day’s campaigns, deploys, and SEO events — the cause is obvious.
Sound familiar?
Webflow’s history lives in the Designer.
Mia09:25
Sara09:29
Mia09:32
Sara09:36
The publish history lives where only builders can reach it.
Backups answer “what did the site look like before?” — never the question the rest of the company has: “what was published or changed around the day my numbers moved?”
- Publish and backup history is locked in the Designer
- CMS item changes barely keep a history at all
- Only people who build the site can reach it
- Never lined up against the campaign or deploy from the same day
Once Webflow is connected, the publish will already be on the timeline — “Site published — pricing page updated” — stamped to the minute, next to every other change from that day.
How it works
Connect once. Then it’ll log itself.
- 01
Add a Webflow webhook
Point a Webflow site-publish webhook at CoNote — no code, no Designer changes, no engineering sprint.
- 02
Every publish logs itself
From then on, each site publish and tracked CMS change lands on the timeline with a readable title — “Site published — pricing page updated” — the moment it happens.
- 03
Read it in context
The change sits beside that day’s campaigns, deploys, and SEO events. When a metric moves, you scan one page instead of the Designer.
What lands on your timeline
- Site publishes — and the domain they went to
- CMS item changes you choose to track
- A readable title and the moment it went live
In your week
What teams will use it for.
Conversion dropped — was it a publish?
A page loses conversion. The site publish sits on the day it happened, so you can tell a site change from a traffic or campaign change at a glance.
Did the page publish before the ads?
The publish sits next to the campaign launch, so you can confirm the landing page went live first — no opening the Designer.
Give marketing a publish log they can read
No Designer access needed. Everyone sees “Site published — pricing page updated” in plain language, beside the rest of the company’s work.
One feed across publishes and CMS changes
Design publishes and content edits land on one timeline, in order — instead of split between the Designer and people’s memory.
Side by side
Native history vs. your logbook.
See site publishes
Webflow backups
CoNote
A shared log of every publish
Webflow backups
CoNote
Track CMS item changes
Webflow backups
CoNote
Lined up against campaigns, deploys, SEO
Webflow backups
CoNote
Readable without Designer access
Webflow backups
CoNote
Setup
Webflow backups
CoNote
On the timeline
The publish in context.
A site publish on its own is a green dot in the Designer. Next to the campaign and the conversion dip from the same day, it’s an answer.
Tuesday, June 9
Site published — pricing page updated
Webflow· 12:15
Pricing campaign launched — $300/day
Google Ads· 12:40
Pricing-page conversion dropped 16%
Uptime· 15:30
Questions
Webflow change tracking, answered.
Partly. The Designer auto-saves backups and marks publish points so you can restore an earlier state of the site, and it shows when the site was last published. But there’s no easy shared log of every publish over time, and CMS items keep little change history.
Not yet — it’s coming soon. You can start your CoNote logbook now and connect the tools that are already live; we’ll switch Webflow on automatically the day it ships.
No. Connecting Webflow will be adding a site-publish webhook — no code and no Designer changes.
Site publishes, and the CMS item changes you choose to track, each as a plain-language entry with the time it happened. CoNote reads the events you send it; it never changes your site.
Yes — for the collections you choose, CMS item changes land on the timeline alongside site publishes, which Webflow itself barely keeps a history of.
Backups live in the Designer, reachable only by people who build the site. CoNote will put site publishes and CMS changes on a shared timeline next to your campaigns, deploys, and SEO events — so the whole team can line a change up against the day a metric moved.
Only your team. Every entry is scoped to your team, and connecting Webflow won’t expose your site to anyone outside it.
Keep digging
Track the rest of your stack.
Open the logbook.
Free plan, no card. The next time someone asks “what changed?”, the answer is one search away.
Start your logbook