Update your AI-made page without changing its link or QR code

You sent the link to a group chat and printed the QR code on a flyer. Then you notice the wrong date. Sending a second link splits your readers between two pages, and the printed code can't be changed.

Keep the address and change what's behind it. On Convika, the corrected file goes in as the next version of the same page. You check its private preview, then publish it in place of the old one. Every link you sent and every QR code you printed opens the new version.

What stays the same when you publish a new version

• The address. The page's Live URL, such as yourpage.convika.page or an address on a domain you connected, stays the same.
• The QR code. The dashboard's QR code opens the live address. Its panel says the code "still works after you publish a new version."
• Page views and form entries. They belong to the page, not to one version, so the counts carry on and the entries you received stay in the dashboard. You can compare page views before and after the fix in the page's visitor stats.
• Your Convika form. If you added a form in the dashboard and the new file doesn't have it, Convika puts it back near the end of the page and tells you so.
• Who can open it. A page with a password keeps it ("Publishing keeps the password"), and a private link stays private.

Three things change: what the page shows, its version number (v1, v2, v3), and the preview link, which is new for each version.

Ask your AI for the whole corrected page

Ask for the complete file, not just the changed lines. Pasting a fragment into the old file by hand is how closing tags go missing and a section breaks somewhere you didn't touch. In the same ChatGPT, Claude, or Gemini conversation that made the page, send this, with your own changes in the list:

Change only what I list below. Keep everything else exactly as it is.
1. In the "Opening hours" section, change Saturday to 10:00–14:00.
2. In the footer, fix the spelling of "Febuary".

Then give me the complete updated page as one HTML file, from <!DOCTYPE html>
to </html>, with nothing shortened or left out. Keep the CSS and JavaScript
inside the file, and keep every image URL as it is.
After the code, list each change you made in one line.

The list at the end is your checklist for the preview. If the AI changed something you didn't ask for, it shows up there or in the comparison below.

If the conversation is gone, start from the HTML Convika has. On the page's screen, click Upload a new version. The box Latest version (v2) as HTML (with your number) has Download HTML and Copy HTML; the dashboard says to take the current HTML from there "to fix it in your own AI." Paste it into a new chat, then send the prompt above. If you uploaded a version you never published, take the HTML of the row marked Live in Version History instead, so you fix what visitors actually see.

To get a page out of ChatGPT or Claude in the first place, see how to publish ChatGPT HTML and how to share a Claude artifact as a link.

Update the live page in 5 steps

1. Open the page you already published

Sign in at app.convika.com and open the page from your list. Check that the Live URL at the top is the address you shared. Upload the fix here, on this page's screen, not as a new page.

2. Upload the corrected file as a new version

Under Update from an HTML file, click Upload a new version. Choose Upload a file and pick the .html or .htm file (up to 2 MB), or choose Paste code and paste the AI's code. Click Upload as a new version. Uploading uses no AI credits.

Name the file after the change, such as menu-saturday-hours.html (updating a QR code menu works the same way). Convika shows the uploaded file's name under that version in Version History, which makes a list of versions easy to read later.

3. Check the private preview

Preview v2 is ready appears with your new version number, and a line says your address still shows the version that's live now. Click Open preview. Check each item on the AI's change list first, then scroll the whole page on your phone as well: a change near the top can push a button out of place further down.

Nothing public has changed yet. The preview link expires after 3 minutes; click Open preview again for a fresh one.

4. Publish it at the same link

Click Publish v2 at the same link. The dialog says the version goes live at your address and asks Who can open this page?, with the page's current answer already chosen. Click Publish. The page switches to the new version at the same address.

If you closed the result, the page's screen shows "v2 is newer than the live page." beside the live address, with its own Publish button.

5. Open the address you shared

Open the live address on your phone, or scan the printed QR code, and reload. Check the changes once more on the live page. If the page has a form, send one test entry and look for it under View entries: test entries sent from a preview aren't saved.

Compare the new version with the live one

Before you publish, it's worth knowing exactly what changed, especially when the AI rewrote a long file.

• Side by side. Keep the live address open in one tab and the preview in another, and scroll both to the same section.
• Line by line. In Version History, each version has Download HTML and Copy HTML. Download the row marked Live and the new one, then ask your AI: "Here are two versions of my page. List every difference between them, including any text, link, or image that changed." Changes you didn't ask for are the ones to check.
• What came back. If Convika put a form back, the result names it: "Your form (…) wasn't in the new file, so Convika put it back near the end of the page."

Still seeing the old page?

Work down this list.

1. The new version was uploaded but not published. The page's screen shows "v2 is newer than the live page." Click Publish there.
2. You're looking at a tab you opened earlier. An open tab keeps what it loaded. Reload the live address. Convika sends the live page with Cache-Control: private, no-store, which MDN describes as telling caches "of any kind" not to store the response, so a reload fetches the version that's live now.
3. You opened the preview link, not the live address. The preview shows the version you uploaded, and its link expires. Open the Live URL from the page's screen.
4. The fix went to another page. If you uploaded the file from the dashboard's main upload screen, it may have become a page of its own with its own address. See the next section.
5. The AI sent back the old code. Download the Live version's HTML and search it for the words you changed. If they aren't there, ask the AI for the corrected file again.
6. The dashboard says you've reached this month's view limit. While that notice shows, Convika pauses editing and publishing, so a new version can't go up. The notice gives the date the count starts again, and paying brings everything back right away (pricing).

If the fix landed on a new page instead

The dashboard's main upload screen compares the file's <title> with your pages. When the file looks like a new version of one, a card names that page, says whether it's Live and at which address, and when it was last updated. It says "This file looks like a new version of this page" when the title differs only by a version number, such as v1.4 and v1.5, and asks "Is this file a new version of this page?" when the title is exactly the same. For a live page, its button is Update the live page. That puts the file live at the same address right away, with no preview step. The page's screen then says so and offers Go back to v1 (with your version number) in case the new version breaks something. For a page that isn't live, the button is Upload as a new version, which gives you a preview to check first. Make it a separate page and Create a new page instead make a page with a different address.

If you already made a second page, upload the same file to the original page with the 5 steps above, then remove the copy. On every plan, that keeps the address you shared. On Pro or MAX, on Free with Light and fewer than 5 pages live, or in a Free workspace created before October 23, 2026 (Japan time), Publish page on the copy puts it live at its own new address, and the address you shared keeps the old version. In a Free workspace created on or after October 23, 2026 (Japan time) without Light, which has 1 live page at a time, Publish page on the copy makes Convika take it for a new version of your live page, or ask whether it is one, and offer Update the live page (free). Choose that: the address you shared shows the new version, and the copy stays in your pages as a draft. There, Publish it as another page keeps the copy apart: it then needs Light, a paid add-on, to stay live beside the original, or Swap it in for the live page (free), which takes the original back to a draft, and the address you shared stops opening.

Roll back if the new version breaks something

In Version History on the page's screen, find the version you want back and click Roll back to this version. Convika asks "Restore the live page to v1?" (with your number); click Restore. The live page shows that version at the same address. Rolling back works on a page that's live now.

Free keeps the last 10 versions and Pro the last 50, plus the live version and the one behind the current preview. Once a page passes its plan's number, the oldest version is deleted for good, so roll back before you upload many more.

Update it from Claude or ChatGPT over MCP

If your AI client is connected to Convika, the same update can happen in the chat. Ask it to fix your page on Convika. It finds the page, saves the corrected HTML as a new version of that page, and returns a preview link, which expires after 1 hour. It publishes only when you tell it to, and the page keeps its address. To go back, ask it to roll the page back to the version before.

Updating in place or making a new page

Keeping the address when you update is how other hosts work too. Tiiny Host's help, for example, says "Your link name, QR code and custom domain all stay the same when you update a project." On Convika, the step between upload and live is a private preview of the new version, and the publish button names the version that goes live.

Frequently asked questions

How do I update an HTML website without changing the URL?

Upload the corrected file as a new version of the page that's already live, then publish it. On Convika, open the page's screen, click Upload a new version under Update from an HTML file, upload the file, check the preview, and click Publish v2 at the same link (with your version number). The address stays the same.

Will my QR code still work after I update the page?

Yes. The QR code holds the page's address, not its content, and the address doesn't change when you publish a new version. People who scan a printed code see the version that's live when they scan it. For making the code itself, see how to turn an HTML file into a QR code.

Why does my updated page still show the old version?

Usually the new version was uploaded but not published yet: the page's screen shows "v2 is newer than the live page." with a Publish button. If you already published it, reload the live address, since an open tab keeps what it first loaded. Also check that you uploaded to the original page and not as a new page.

Can I go back to the previous version?

Yes, while the page is live. In Version History, click Roll back to this version on the version you want, then Restore. Free keeps the last 10 versions and Pro the last 50, plus the live one.

Do I have to pay to update a published page?

No. Uploading a new version uses no AI credits, and publishing a new version of a Public page on Free shows no order. Free allows 30 publishes a day: uploading and previewing new versions doesn't count, only publishing to the live address.

Does updating reset my page views?

No. Page views and form entries belong to the page, so they carry on across versions. When you open the live page yourself to check it, those page views count too, like anyone else's.

Sources

• Cache-Control (MDN Web Docs), read on October 26, 2026
• If I update a project, does the link change? (Tiiny Host help), read on October 26, 2026