Once an attachment has gone out, the only fix is a second e-mail, and a second e-mail is an admission. A tracked link is an address you still control, so the fix is silent: you change what is behind it.
Three ways to do it
All three do exactly the same thing. They differ only in where you are standing when you decide to fix something.
In the dashboard
Open the document and press Replace HTML. A file picker opens straight away; choose the corrected file and it uploads. It accepts .html and .htm files up to 30 MB. Choosing a file with the same name as last time works.
From Claude, or any assistant on the connector
Ask it to update the document and it reads the current page with
get_documentand callsreplace_documentwith the changes. This is the loop the connector exists for: read who stopped where, rewrite that part, put it behind the same links. The connector page lists every tool.Over the API
POST /api/v1/documents/{id}/replacewith the full markup in anhtmlfield. It answers with the new version number andlinks_unchanged: true. The API reference has the rest.
What changes, and what does not
| After a replace | What happens |
|---|---|
| The link address | Unchanged. Every slug you have sent stays exactly as it was, including a name you chose yourself and a custom domain if you use one. |
| Link settings | Unchanged. The password, e-mail gate, expiry date, allowed addresses, the name you gave the link and the download lock belong to the link, and replacing does not touch them. |
| When the reader sees it | On their next open. A page already open in somebody’s browser keeps showing what it loaded until they reload it. |
| Reading already recorded | Kept, in full. Nothing is deleted, and each read records the version the reader saw. |
| The version number | Goes up by one, and a row is added to the version history: number, size, time, who did it, and the filename when it came through the browser. |
| The old file | Left in storage but no longer served. There is no route that serves a previous version to anybody. |
| Attachments on the document | Untouched. Replacing swaps the HTML page only; attached files stay as they are. |
What happens to the section names
This is the part worth understanding before you rewrite a heading, because it is the one place a replace can make an old reading report look different.
HTMLRadar measures reading against the headings in your page, and the document-level chart adds up that time by the heading’s text, not by its position in the page or by any identifier in the markup. So a section that keeps its heading across versions stays one line in the chart, and the time readers of version one and version four spent on it accumulates together. That is what you want: “Spend & results” should be one row whether it was the third section in March or the second in April.
Rename a heading and you get a second line instead. The old name keeps the time it already had and the new name starts at zero, because nothing in the page tells us the two are the same section. Sections with no heading at all fall back to their identifier in the markup, which can change between exports, so give the parts of a document you care about real headings and leave them alone.
The limits, stated plainly
- There is no editor. HTMLRadar does not let you change words inside the browser. You edit the page wherever you wrote it and upload the whole file again, or ask Claude to change it through the connector.
- Every version is a whole document. Through the connector or the API you can send the whole page or only the changes; in the dashboard you upload the whole file. Either way HTMLRadar stores the complete page as the next version.
- There is no rollback. Every version is listed, and no version can be restored with a click. Going back means uploading the earlier file again as a new version, so keep it.
- Uploaded documents only. A document you added by pasting a URL you host has nothing to replace; it changes when you change the page at that address.
- Size. 30 MB through the dashboard, 5 MB through the API and the connector, and HTML only in all three.
- Two replaces at once. Through the API or the connector, if a second replace lands while the first is still in flight, one of them wins and the other is told it lost rather than quietly overwriting the winner.
- Replacing is screened like any upload. Swapping new contents behind a link people already trust is exactly the move the phishing screen exists for, so the new file is checked the same way the first one was.
- It does not un-read what was already read. Anybody who opened the link before you fixed it saw the old version. The dashboard records when each person opened, so you can see who read it before the change.
When to replace, and when to send a new link
Replace when it is the same document: a typo, a wrong number, a section rewritten because the reading report showed four people stopping at it, next month’s edition of a report the same client receives every month. The client keeps one address all year and you keep one running record of their reading.
Create a new document instead when it is a different document that happens to look similar: a proposal for another client, a deck for another round. Reading data is attached to the document, and two unrelated pieces of work sharing one record make both harder to read.