How to update or delete shared HTML without changing the public URL

You can replace shared HTML without sending reviewers a new public URL. The public link identifies the share; the private management URL proves authority to change or delete it. Save the management URL when publishing because an anonymous share cannot recover a lost management token.

Two URLs have different jobs

URL	Send to reviewers?	What it can do
Public share URL	Yes	Open the current published result until it expires or is deleted
Private management URL	No	Replace content, change supported settings, or delete the share

Do not paste the private URL into the same chat, email, issue, or document as the public link. Its fragment contains a management secret. Anyone who receives it may be able to change the share.

Update the same share safely

1. Open the private management URL on a trusted device.
2. Confirm that the displayed public slug matches the link already sent.
3. Remove API keys, personal data, internal addresses, and unpublished customer information from the replacement HTML.
4. Replace the content and save.
5. Open the public URL in a private window.
6. Verify the visible revision, scripts, assets, expiry, and password state.
7. Tell reviewers that the same link now contains a new revision.

The update changes the content version behind the existing slug. It does not recall screenshots, downloads, or copies made from the older version.

Delete instead of waiting for expiry

Use immediate deletion when the wrong file was published, a secret may be present, or review has ended early. Expiry limits future access after a scheduled time; deletion ends access as soon as the service accepts the management request.

After deletion:

• verify the public link no longer returns the original content;
• rotate any credential that appeared in the page;
• notify recipients when they may have copied sensitive content;
• keep an incident record without copying the exposed secret into it.

Deleting the share cannot delete a recipient’s screenshot or downloaded file.

If the management URL is lost

An anonymous management token is stored only as a verifier, not as recoverable plaintext. The service cannot email or display the original token later. This prevents a support channel from becoming a token-recovery bypass.

Create a new sanitized share if the old content is harmless and will expire soon. If it contains sensitive information, treat the content as exposed and rotate the affected secret. Account-owned product capabilities may change how shares are listed, but they do not make an already lost anonymous token reappear.

Use one revision message

Tell reviewers what changed, not only that the page changed:

Revision 3 is live at the same URL. The chart labels and mobile layout changed. Please review before 16:00 KST; the link expires at 17:00 KST.

That message prevents people from reviewing an old browser tab without context. For high-stakes approval, include a visible revision ID inside the HTML.

Create the initial page with the HTML-to-URL tool, keep the private management URL outside recipient channels, and delete the share when its short review job is finished.