Who changed what? How to keep a record of website edits, from version history to audit logs

By Ranjit Bhinge, founder of Blur Studio · Updated · 10 min read

Short answer: An audit log is a list of who did what on your website and when, and it is not the same as version history, which only lets you go back to an earlier copy of a page. Most small-business plans give you version history but no true audit log: Webflow, a visual website builder, limits its Site Activity log to Enterprise customers and partners, and WordPress, the open-source website software, keeps content revisions but does not log settings changes by default. For a small team, the practical answer is named logins for everyone, version history switched on, and a simple change log you keep yourself.

Ranjit Bhinge

You need a record of who edited and published what on your website, and you want to know what each platform keeps and what you must keep yourself.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

Three different records get called "the history". Version history saves copies of your content so you can undo. An audit log records the people and tools that took actions, and when. Git history records every code change with an author and a message, using Git, the standard tool developers use to track code. You often need two of the three, and the one that answers "who changed what" is rarely the one included in a cheap plan.

This page shows what each platform's own pages say it records, as of November 2026, how long it keeps the record, and how to fill the gaps with a simple log of your own. It also covers the case where a client blocks a tool until security is approved, and you need clear written answers. Plan features change, so check each vendor's page before you buy. Nothing here is legal advice: if a contract or a regulator requires records, check local law and your contract.

This page may contain affiliate links from which Blur Studio earns commissions.

Three records that answer different questions

RecordAnswersDoes not answer
Version history"What did this page look like last Tuesday, and can I go back?"Who made the change, in most tools
Audit log"Which person or tool published, deleted or changed settings, and when?"Often not the text of the edit
Git history"Which line of code changed, who wrote it, and why?"Changes made outside the code, such as in a visual editor

A client asking for "an audit trail" usually wants the second one, plus proof you can undo mistakes, which is the first one. Ask which they mean before you promise anything.

What each platform's own pages say

PlatformWhat it recordsWho or what is namedUndoRetention as stated
WebflowSite Activity log: publishing, CMS (content management system) items, page settings, custom code, backups and moreTime, member, branch and a source: a person, Webflow AI or a connected MCP tool (MCP is a standard way for AI tools to connect to software)Separate backups and restoreHelp page says the log history does not expire
WordPress (core)Revisions of title, author, content and excerpt on each saved draft or updateContent revisions only; plugin settings and media are not coveredRestore a revisionKeeps every revision by default; you can cap it
Framer, a website builder with a design editorVersion History snapshots about every ten minutes while editingNot described as a who-did-what logRestore layers or sections from an older versionNot stated
Ploy, an AI platform that builds and hosts business websitesAutomatic versions while editing; every publish is an immutable snapshot; a publish panel shows the last publish time and memberPublishes by Ploy's Agent are marked with the Ploy markRestore from Versions, then publishSnapshot retention not stated; the Enterprise audit log keeps one year
Wix and SquarespaceCheck each vendor's help center for site history and activity logsCheck the vendorCheck the vendorCheck the vendor

Webflow: the log is an Enterprise feature

Webflow's help page says the Site Activity log is available to Enterprise customers and Enterprise partners. Anyone with content editor site access or above can read it. It records entries only when work is saved, shows 50 entries before you press "Load more", and does not track descriptions of changes to classes, components or code. It also does not track Workspace settings. The ordinary site plans many small businesses use are Basic ($15 a month billed yearly, $25 billed monthly) and Premium ($25 yearly, $39 monthly) on Webflow's pricing page as of November 2026, and neither is the plan that carries this log. The free Starter plan does not either.

WordPress: content yes, settings no

WordPress's documentation says it stores each saved draft or update as a revision and lets you restore one. By default it tracks the title, author, content and excerpt. It does not log changes to plugin settings or media, and WordPress has no built-in screen for deleting old revisions, only a function. A plugin that logs activity can fill the gap, but its retention and detail depend on the plugin, so read the plugin's own page before you rely on it.

When an AI tool made the change

This is the new gap. If an AI agent edits and publishes pages, a log that only says "the account owner published" hides who decided what. Two platforms now try to label it. Webflow's log carries a source for each entry, human, Webflow AI or MCP-connected tool, but Webflow's help page says the source filter is not retroactive to earlier entries. Ploy marks publishes made by its Agent in the publish panel, and its Enterprise audit log records what "people and agents" did, including publishes, membership changes and integration activity.

For your own records, add a column that says who or what drafted the change, and who approved it. AI-written pages need human review before they go live, and the log is where you prove the review happened.

A change log you keep yourself (copy this)

If your plan has no audit log, a shared sheet with one row per change gives you most of the value. Keep it short enough that people actually use it.

  • Date and time
  • Site and page address
  • Who made the change, and whether a person or an AI tool drafted it
  • What changed, in one line
  • Why (the request, ticket or client email)
  • Who approved it
  • Link to the version or snapshot you can restore
  • Reverted or kept

Pair the sheet with three habits. Give every person their own login, because a shared login makes any log useless. Remove access the day someone leaves, using the rules in team seats, roles and client access. And turn on any version history your plan includes. For how to show a client the real version before it goes live, see getting client approval on a real version.

Git basics, for sites that have code

Git is the standard tool developers use to track code changes. A commit is a saved change with an author, a date and a message. A pull request is a proposal to merge a change that someone reviews first. GitHub's documentation (GitHub is a service that hosts Git projects) says a protected branch can require approving reviews and passing checks before a merge, and blocks force pushes by default, which means history cannot be quietly rewritten. When two people edit the same line, Git does not pick a winner: you must resolve the conflict before merging.

Git covers code only. A page edited in a visual editor may not appear in Git unless the platform syncs it. Ploy's docs describe a Code Sync feature that connects one site to a GitHub repository, where each commit has a message so changes can be reviewed like any other pull request. Check which Ploy plan you need for the connection you want, because the docs describe different rules for different routes. Treat Git as one layer, not the whole record.

Where Ploy fits, as one option

Ploy is an AI platform that builds, hosts and improves a business website through a chat with an AI agent. For the question on this page, its public docs give three layers. Versions are saved automatically as you work and every publish is a complete snapshot you can restore. The publish panel shows who published last. On the Enterprise plan, which is quote-only, its docs describe an organization audit log: it shows what people and agents did, keeps one year of history, can be filtered by time, workspace, action, actor and origin, and can export up to 10,000 entries as CSV. Only owners and admins can open it.

Ploy's Enterprise page also lists single sign-on through OIDC (a standard way to sign in with your company identity provider), owner, admin and member roles, a data processing agreement on request, and a Trust Center. Its pricing page says it does not train AI on your data on any plan. Plans as of November 2026: Free $0, Starter $50 a month, Pro $300 a month, Enterprise by quote. Credits, the points spent on AI work, do not roll over.

Things to ask before you promise a client anything. Ploy's pages do not state how long deploy snapshots are kept. On SOC 2, a type of independent security audit, the pages differ: Ploy's Trust Center lists a Type 1 report file, one feature page says Type II, and the pricing and enterprise pages say only "SOC 2". Ask for the actual report and its date. Code and data export terms should also be confirmed in writing; see who owns your website and content. If you want to see the version history and publish panel yourself, open a free Ploy workspace, make an edit and check what is recorded; the audit log itself is Enterprise only.

If a client blocks the tool until security is approved

This happens often with larger clients. The fix is to answer in writing, with the vendor's own words.

  1. Collect the client's questions, such as "Do you keep an audit log, for how long, and can we export it?"
  2. Send the same questions to each vendor you are considering, in writing.
  3. Record each answer, with the date and the page or person it came from.
  4. Mark gaps as "not stated" instead of guessing.
  5. Let the client decide, using your answers sheet.

The ten-question list in data security questions to ask any website or marketing platform covers the wider review, and keeping a site healthy after launch covers backups.

Worked example with made-up numbers

An agency runs 6 client sites and 4 people edit them. A new client asks, "Can you show who published changes in the last 12 months?" The agency checks its tools. Two sites sit on a plan with version history only. One site's platform has an audit log only on Enterprise, which the agency does not need for the other clients. The agency takes three steps: it moves everyone to named logins, it starts the change log sheet (about 2 minutes per change, 5 changes a week, so roughly 10 minutes a week), and it exports version links monthly. For the one client who needs a platform audit log, it asks the vendor for an Enterprise quote and passes the cost to that client. The point: match the record to what the client actually asked, not to the strongest feature on a list.

Who needs less of this

  • A solo owner with one site needs version history and a backup, not an audit log.
  • Your site rarely changes. A monthly note of what was changed is enough.
  • Your site is a simple page on a platform with no log tier. Use the sheet, and do not pay for Enterprise for this alone.

Pick a platform with an audit log when a contract, an insurer or a regulated client requires it, or when several people publish to the live site every week. Pick Git when developers work on the code. Pick a custom, client-hosted build when you need to set the controls yourself.

Test plan with pass and fail criteria

  1. Make a harmless edit on a test page and publish it. Pass: you can find the change in the platform's history within five minutes. Fail: it is not listed.
  2. Check the record names the right person. Pass: your name, not a shared login. Fail: "admin".
  3. Restore the earlier version. Pass: the old text returns and you can re-publish it. Fail: a step is missing.
  4. Ask the vendor how long the record is kept and in what format it can be exported. Pass: a written answer with a date. Fail: no answer.
  5. Remove a test user. Pass: they can no longer publish and the removal is recorded. Fail: access remains.

How I'd approach this

I would not pay for an audit log to answer a question a sheet can answer. I would pay when a client or contract names it, and then I would choose the platform by what it states in writing about retention and export, not by the feature name. I would also treat AI edits as a separate line in the log, because that is the part clients ask about next.

First week plan: on day 1, list every site, who can publish to it, and whether each person has their own login. On day 2, turn on version history and check what each platform keeps. On day 3, create the change log sheet from the template above. On day 4, run the test plan on one site. On day 5, write down the vendor questions you could not answer from public pages and send them. If a client needs a custom, client-hosted build with controls you set, such as your own audit log, access rules and retention, Blur Studio builds that. See what a custom build includes.

Questions people ask

What is the difference between version history and an audit log?

Version history stores earlier copies of your content so you can go back. An audit log records who or what took an action and when. You can have the first without the second, which is the case on many small-business plans.

Does Webflow have an audit log on every plan?

No. Webflow's help page says the Site Activity log is available to Enterprise customers and Enterprise partners. Its normal site plans, such as Basic and Premium, do not carry it. Check Webflow's current plans page.

Does WordPress log who changed what?

Core WordPress keeps revisions of content fields such as title, author, content and excerpt, and lets you restore one. It does not log plugin or settings changes by default. An activity log plugin can add that, but read its own page for what it records and how long it keeps it.

How long does Ploy keep its audit log?

Ploy's docs say its organization audit log keeps one year of history, is available on Enterprise plans, and can export up to 10,000 entries as CSV. Deploy snapshot retention is not stated on its pages, so ask Ploy in writing. See what Ploy connects to for other plan limits.

How do I know whether an AI tool changed my site?

Look for a source or actor field. Webflow's log labels entries as a person, Webflow AI or a connected MCP tool, and Ploy marks publishes made by its Agent. Add your own column in the change log for who drafted and who approved.

Is Git history enough as a record?

Only for code. A commit records author, date and message, but changes made in a visual editor may not reach Git unless the platform syncs them. Use Git for code and a platform log or your own sheet for everything else.

What should I send a client who asks for a security review?

Send written answers from each vendor, dated, with gaps marked as not stated. Use the question list in data security questions to ask any website platform, and ask for any SOC 2 report itself rather than relying on a label.

Do I need an audit log for a small business site?

Usually not. Named logins, version history and a simple change log cover most small sites. Pay for a platform audit log when a client contract, insurer or regulator requires it, or when many people publish to the live site.

More in this topic: Websites: agency billing, partners and team workflows (6 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…