> ## Documentation Index
> Fetch the complete documentation index at: https://00doc-web.vercel.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Updating a document

> Push a new version without changing your share link — from the dashboard or MCP.

# Updating a document

Every publish creates a **new version** on the **same document**. Your public URL does not change.

## From the dashboard

<Steps>
  <Step title="Open the document">
    In the [dashboard](https://unfurl.pub/dashboard), select the document you want to update.
  </Step>

  <Step title="Upload new HTML">
    Drag a fresh `.html` file onto the drop zone. This appends a version.
  </Step>

  <Step title="Optional note">
    Add a version note when the UI offers it — short strings help you scan history later.
  </Step>
</Steps>

## From MCP (`publish_document`)

Include the **`document_id`** you received when the document was first created:

<CodeGroup>
  ```text Example theme={null}
  publish_document
    document_id: "your-uuid-here"
    title: "Same title or an updated one"
    html: "<!DOCTYPE html>..."
    note: "Fixed table totals"
  ```
</CodeGroup>

Omit `document_id` only when you intend to create a **new** document with a **new** link.

## Same link, new content

Recipients refresh the same URL and see the latest **published** version. You do not re-send a different address.

<Tip>
  **Version notes:** Use the present tense and a noun phrase — "Add ROI section", "Legal wording v2". Avoid empty notes; future you will thank you.
</Tip>

<CardGroup cols={2}>
  <Card title="Live links" icon="link" href="/core-concepts/live-links" />

  <Card title="Version history" icon="clock-rotate-left" href="/guides/version-history-rollback" />
</CardGroup>
