How to Update an OpenClaw Website Without Changing Its URL

The key to a stable OpenClaw website URL is simple: revise the original project and publish it to the existing Revdoku website. A new project or new website produces a new URL.

This guide focuses on that update loop. For initial setup, hosted MCP commands, and password access, start with the OpenClaw website-hosting guide.

Understand what keeps the URL stable

A Revdoku URL belongs to a website, not to one specific copy of index.html. Your first local publish associates the project folder with that website. Later publishes from the same bound folder replace its files while keeping the website identity and URL.

The safe loop is:

1. Build in one dedicated folder.
2. Sign in and save that folder as a private draft.
3. Review a temporary preview.
4. Publish the main website when it is ready.
5. Save the live URL and keep the project’s Revdoku binding.
6. Edit the files in place.
7. Publish the same bound folder again.

Revdoku requires authentication before storing files. The review preview is noindex, lasts 15 minutes, and does not change the main website.

Step 1: keep one project folder

Ask OpenClaw to create the static site in a clearly named directory. The folder should contain the site’s entry file and all relative assets:

project-status-site/
├── index.html
├── styles.css
├── app.js
└── assets/

A framework project may have a source directory and a generated output directory such as dist or build. In that case, publish the generated static output—not the framework source or a development server.

Step 2: preview the first version

From the directory that contains the static output:

revdoku preview .

If credentials are missing, complete browser sign-in and create a Free account there if needed. Save the returned preview URL.

A useful instruction for OpenClaw is:

Save this folder to Revdoku as a private draft and return a temporary preview URL. After I approve it, publish the main website. Keep this folder associated with that website so future revisions update the same URL.

Open the website URL and verify that HTML, styles, scripts, and images load before making more changes.

Step 3: publish after review

The preview expires after 15 minutes. Run the preview command again if more review time is needed. When the site is approved, run revdoku p . to publish the main website.

Step 4: revise the original project

Give OpenClaw a specific change while naming the existing project:

In the existing project-status-site folder, change the heading to “Launch readiness,” add a three-item checklist, rebuild if required, and do not create a new Revdoku website.

Before publishing, test the generated output locally when practical. Revdoku is static hosting, so server-only routes, private environment variables, and background processes will not run there.

Step 5: publish the bound folder again

Run the same command in the same output directory:

revdoku p .

The command should update the existing website. Compare the returned URL with the URL saved from the first publish. They should match.

Reload the original link in a private browser window or perform a hard refresh so cached CSS or JavaScript does not hide the update.

Step 6: verify access settings

If the website uses Password access, confirm it after the update:

1. Open the original URL in a private window.
2. Confirm the password screen appears.
3. Enter the password and verify the revised page loads.
4. Keep the password out of the published files and public prompts.

Republishing content should update the website files rather than create a separate public copy. Still, checking the access screen after a significant change is a good release habit.

If OpenClaw returned a different URL

Work through these checks in order.

Confirm the folder

Make sure OpenClaw published the original bound output directory. A copied folder may not carry the website association you expected.

Confirm the command location

Run pwd before revdoku p . and compare the path with the initial project directory. Framework users should also confirm they are publishing the same generated output folder.

Confirm the intended website

For hosted MCP, tell OpenClaw to list or inspect existing Revdoku websites and select the original website before changing files. Do not ask it to “create a site” for a revision.

Do not discard the working copy

A cleanup step that removes all project metadata can break the local association. Preserve the project folder or reconnect it intentionally before the next publish.

Compare IDs as well as URLs

When the tool returns a website or bucket identifier, save it with the URL. An exact identifier is less ambiguous than a title such as “Project status.”

If the page did not change

A stable URL with old content usually means one of four things:

• OpenClaw edited the source, but did not rebuild the static output.
• The wrong output directory was published.
• The browser is showing cached assets.
• The updated file has a different name or path than the live page uses.

Add a visibly unique test string, rebuild, republish, and check the page source. Remove the test after the path is confirmed.

A reusable OpenClaw update prompt

Open the existing project at [path]. Make these changes: [changes]. Run its static production build if it has one. Publish the same Revdoku-bound output folder and confirm the returned website URL exactly matches [saved URL]. Do not create a new website. Then summarize the files changed and the live URL.

That prompt states the project, build step, existing identity, expected URL, and verification requirement. Those details make accidental duplicate sites much less likely.

Final checklist

Before sending the revised link:

• The original URL opens.
• The visible change appears.
• Images and fonts load.
• No secret or local-only file was published.
• The expected access screen appears.
• The result is static and does not depend on a development server.
• OpenClaw reports the same website URL.

Once this loop works, future revisions become routine: edit, build, publish the existing site, and verify the same link.

codex mcp add revdoku --url https://app.revdoku.com/mcp
codex mcp login revdoku

claude mcp add --transport http revdoku https://app.revdoku.com/mcp
claude mcp login revdoku