When a Claude artifact unpublishes and will not come back.

What the message actually means

The wording people hit is some version of "this artifact was unpublished and cannot be republished." It is not a bug or a transient error you can retry past. Per Anthropic's documentation, unpublishing an artifact is permanent for that published version: the public link stops working, the Publish control for it is deactivated, and if the artifact relied on persistent storage, the associated data, personal and shared, is deleted. The published version is simply gone.

That can happen because you unpublished it deliberately, or because an artifact's lifecycle ended, and the result is the same: you are looking at a page you can no longer bring back at the address it used to have.

Republishing gives you a new link, not the old one

The documented path forward is to create a new artifact, or publish an updated version of the existing one. Either way you get a fresh link. That is fine if nobody had the old one yet. It is a problem the moment the old URL was already out in the world.

Think about where that link tends to live: a message to a client, a row in a project doc, a teammate's bookmark, a Slack thread from last week. When republishing mints a new URL and the old one cannot be repointed, every one of those references quietly breaks. The person who clicks gets nothing, and you may not even hear about it.

The deeper issue: the link is not yours

None of this is a knock on artifacts for what they are good at, fast, in-context pages you build without leaving Claude. It is a consequence of the publish model: the link belongs to the artifact's lifecycle, not to you. You do not control whether it stays stable, you cannot redirect it, and unpublishing is a one-way door that can take data with it. For something you tried once and discarded, that is fine. For anything you shared and expected to keep working, it is the wrong contract.

The question worth asking is not "how do I republish this artifact," because you cannot. It is "how do I share an agent-made page so the link does not depend on a publish state I do not own."

The fix: a stable link you control

Full disclosure: we build Stacktree, so this is us describing where we fit. Host the page on a service where the URL is yours and the content is replaceable in place, and the failure above stops existing. With Stacktree you publish the artifact's HTML, export it to a self-contained file or have your agent publish it directly, and you get a private, unguessable link. When you change the page, update_site swaps the content under the same URL, so the link you already shared keeps working. Taking a page down is your choice, reversible by republishing to the same slug, not a permanent deactivation. You can add a password or an email-domain gate, set an expiry, or put it on your own domain.

The trade is scope: Stacktree hosts static HTML, so if your artifact depended on Claude's persistent storage or live server behaviour, that part does not move with it. But for the common case, a page you want to share and keep reachable at a stable address, hosting it yourself turns "unpublished and cannot be republished" into a problem you never have.