WordPress change history, across the whole site, not one post.
WordPress keeps revisions for each post — but nothing gives you a site-wide record of what was published or updated, and when. CoNote will put every publish and content change on one shared timeline, beside the deploys and campaigns from the same day.
WordPresspublished a changePublished “Summer Sale 2026” landing page
WordPress· 11:30
Summer sale campaign launched — $300/day
Google Ads· 12:00
Finding your history
Your WordPress change history: today, and once CoNote is live
The manual way · inside WordPress
Where to find it today
Some of it’s tracked — the rest you reconstruct:
- 1
Open the post or page
In wp-admin, open the content you’re curious about — revision history is kept per item, not for the site as a whole.
- 2
Open its Revisions
In the editor sidebar, Revisions lets you compare and restore past saves of that one post or page, with the author and time of each.
- 3
Check the Updates screen
Dashboard → Updates shows what plugin and theme updates are available now — but not a dated log of what was updated in the past.
- 4
Add a plugin for an activity log
To get a site-wide feed of publishes, updates, and logins, you install and maintain an activity-log plugin — it isn’t built in.
- 5
Piece the site timeline together yourself
Nothing lines publishes up across posts — or against your deploys and campaigns — so you assemble that by hand.
The CoNote way · coming soon
Where you’ll find it once it’s live
Connect WordPress once. After that it’ll be seconds:
- 1
Open your CoNote timeline
Every publish and update will be in one feed — no post-by-post revision digging.
- 2
Jump to the day traffic moved
Scan the day a page’s traffic shifted; the publish or update will be stamped right there.
- 3
See it beside everything else
The content change will sit next to that day’s deploys, campaigns, and SEO events — the cause is obvious.
Sound familiar?
WordPress tracks the post — not the site.
Sara09:20
Mia09:24
Sara09:27
Mia09:31
Revisions are per post — there’s no feed of the whole site.
Revisions answer “what changed in this one post?” — never the question you actually have: “what was published or updated across the whole site around the day my traffic moved?”
- Revisions are per post — no site-wide feed
- Plugin and theme updates aren’t logged with dates
- Locked inside wp-admin, where marketing and leadership rarely look
- Never lined up against the deploy or campaign from the same day
Once WordPress is connected, the change will already be on the timeline — “Published ‘Summer Sale 2026’ landing page” — stamped to the minute, next to every other change from that day.
How it works
Connect once. Then it’ll log itself.
- 01
Connect WordPress
A one-time connection — no theme edits, no developer time. CoNote will receive the publish and update events you choose to track.
- 02
Every change logs itself
From then on, each published or updated post and page lands on the timeline with its title and the moment it happened — “Published ‘Summer Sale 2026’ landing page”.
- 03
Read it in context
The content change sits beside that day’s deploys, campaigns, and SEO events. When traffic moves, you scan one page instead of post-by-post revisions.
What lands on your timeline
- Posts and pages published
- Updates to existing content
- The title and the moment it went live
In your week
What teams will use it for.
Traffic dropped — did we edit the page?
A key page loses traffic. The update to it sits on the day it happened, so you can tell a content edit from an algorithm change at a glance.
When did this actually go live?
Marketing wants the publish time of a landing page. It’s on the timeline next to the campaign — no asking around.
Give the team a publishing log they can read
No wp-admin access needed. Everyone sees “Published ‘Summer Sale 2026’ landing page” in plain language, beside the rest of the company’s work.
One feed across every author
Several editors, one timeline. Every publish and update lands in the same place, in order.
Side by side
Native revisions vs. your logbook.
See content changes
WordPress revisions
CoNote
A site-wide feed of publishes
WordPress revisions
CoNote
Plugin and theme updates logged with dates
WordPress revisions
CoNote
Lined up against deploys, campaigns, SEO
WordPress revisions
CoNote
Visible to the whole team
WordPress revisions
CoNote
Setup
WordPress revisions
CoNote
On the timeline
The publish in context.
A publish on its own is a row in wp-admin. Next to the campaign and the traffic bump from the same day, it’s an answer.
Tuesday, June 9
Published “Summer Sale 2026” landing page
WordPress· 11:30
Summer sale campaign launched — $300/day
Google Ads· 12:00
New landing page indexed
Search Console· 16:40
Questions
WordPress change tracking, answered.
Partly. Each post and page keeps a revision history in the editor that lets you compare and restore past saves, with the author and time. But there’s no built-in site-wide feed of publishes, and plugin or theme updates aren’t logged with dates unless you add an activity-log plugin.
Not yet — it’s coming soon. You can start your CoNote logbook now and connect the tools that are already live; we’ll switch WordPress on automatically the day it ships.
No. Connecting WordPress will be a one-time connection — no theme edits and no developer time.
Posts and pages that are published or updated — each as a plain-language entry with its title and the time it happened. CoNote reads the events you choose; it never changes your site.
No — it logs publishes and updates to live content, not every autosave or draft, so the timeline stays a record of what actually went out.
Revisions cover one post, inside wp-admin. CoNote will put publishes and updates across the whole site on a shared timeline next to your deploys, campaigns, and SEO events — so the team can line a content change up against the day a metric moved.
Only your team. Every entry is scoped to your team, and connecting WordPress 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