If you monitor your own privacy policy, terms of service or DPA with PageCrawl, you can publish the revision history back onto that page as a small embedded widget. Visitors see a dated list of what changed and when, in the same shape as a public tracked page's timeline.
What does the widget show?
A "last updated" line under the heading, then a dated row per detected edit, newest first, each with a one-line summary of what changed. Where AI summaries are enabled the summary describes the edit in plain language. Without them the row names the part of the page that changed, so the list stays accurate rather than guessing.
Optionally it also shows an importance label on each row.
Any row with more to say expands in place to show the full summary, which parts of the page changed, and the exact time the change was detected. Expanding needs no JavaScript, so it works even where scripts are blocked.
Can visitors follow the page themselves?
Yes, three ways, though the third is offered only on a monitor you have also made public, because it takes the visitor to a setup screen showing the page address. They can enter their email in the widget, which adds the page to their own PageCrawl account once they confirm it. They can subscribe to the Atom feed if they would rather follow it in a reader with no account: the feed address is shown in full so it can be selected and copied without leaving the page, and an RSS link sits in the widget footer. Or they can open the normal setup flow with the page already filled in.
The subscribe box is collapsed behind a "Get notified" button in the widget's top right corner, so the list stays the focus.
In every case the page address is resolved on our side, so it never appears in the widget's markup. Note: a visitor who chooses "set it up yourself" is taken to a prefilled setup screen, which does show them the address of the page being monitored.
What does it publish, and what stays private?
By default the widget publishes the dates, the summaries, and the names you gave the tracked parts of the page. It does not publish screenshots, the monitored URL, or anything about your account.
Set Detail to "Show what changed" and it also publishes the edited wording itself, shown as struck-through old text next to the new. That is a deliberate choice about your own page, so it is stored on the monitor rather than set in the embed code: nobody can turn it on by editing the snippet or the address.
The heading is yours to set. If you leave it blank it reads "Changelog", except on a monitor you have also made public, where it falls back to the monitor's name.
This is a separate switch from making a page's full monitoring history public. Turning the changelog on does not open the full history page, the screenshot archive or the history export. The two settings are independent in both directions.
How do you turn it on?
- Open the monitored page in PageCrawl and choose Share.
- Under Changelog embed, switch on Enable embed.
- Pick the number of rows, the theme, the date format, the accent colour and whether to show importance labels. Set Detail to "Show what changed" if you want the edited wording published, not just a summary of it.
- Copy the embed code and paste it into your policy page.
There are two embed codes to choose from. The script snippet is the one to prefer: it sizes the widget to its content automatically, so the box never ends up with an inner scrollbar or a gap beneath it. The plain iframe is there for sites that do not allow third-party scripts, and takes a fixed height you choose.
Does the widget set cookies on my page?
No. Loading the widget sets no cookie, which matters because it is designed to sit on privacy policy and cookie policy pages. It is also marked so that search engines do not index it separately from your own page.
The widget itself sets no cookie, and its expanding rows work without any JavaScript.
Two things do load a script, and only where they are needed. The script snippet adds a small height reporter so the widget can size itself to its content; it reads nothing from your page. And where the subscribe box is shown, Cloudflare Turnstile runs invisibly to keep bots off the email field, which means a script from Cloudflare loads on that page. Turn the subscribe box off and neither is present: the widget then loads nothing beyond its own markup and styles.
A visitor who submits their email is taking an explicit action, and gets a confirmation email before anything is monitored.
Is the embed id safe to publish?
Yes, and it is deliberately not the same id as your public page link. The embed id is minted separately the first time you switch the embed on, and it only ever opens the changelog. Your public page link, which also opens the full history and its export, uses a different id that never appears in the embed.
Both ids are 32 random characters from a cryptographic random source, so neither can be guessed.
How is the email field protected from bots?
Two layers, neither of which asks a visitor to do anything. Cloudflare Turnstile runs in invisible mode, so a human sees no challenge and no checkbox. Separately, the submitting address is checked against a reputation database of reported abusive networks.
The reputation check fails open on purpose: if that service is slow, rate limited, or down, the signup goes through rather than turning away a real person. There is also a hidden honeypot field that quietly absorbs the simplest bots.
How quickly does turning it off take effect?
Immediately at our end: the moment you switch it off, the widget address stops serving your changelog. A visitor whose browser already loaded the widget may keep showing the cached copy for up to 15 minutes.
Can I style it myself?
Yes. You can set an accent colour, a corner radius, a light, dark or visitor-matched theme, comfortable or compact row spacing, a custom heading, and the date format. You can also turn off the border, the importance labels, the RSS link, or the subscribe box, so the widget can be as plain as a list of dates.
The accent applies to the button and the RSS link, and the button's own text colour is worked out from it, so a pale accent never ends up with unreadable white text on it.
If you would rather render the list with your own markup, the dates and summaries are available as JSON at the same address with /json on the end, so you can fetch them and lay them out to match your site. The JSON carries the same rows as the widget; the expanded detail (the sections that changed and the detection time) is in the Atom feed and the widget itself.