--- title: "Claude Artifact Says Page Not Found or Cannot Be Republished: Causes and Fixes" slug: /blog/claude-artifact-page-not-found-cannot-republish publishedAt: "2026-10-14" updatedAt: "2026-10-14" author: ott description: "Why a shared Claude artifact link fails for a reader, and why an artifact will not update or publish again. We connect each cause to Anthropic's documentation. Checked 14 October 2026." --- # Why does a Claude artifact say "Page not found" or refuse to republish? > **TL;DR:** Anthropic does not document the "Page not found" screen. Three documented settings can stop a reader. The sender shared the artifact only inside a Claude organization, and the reader is not a member. An Owner turned off external sharing. Or the sender unpublished the artifact. You cannot publish an unpublished legacy chat artifact again. In Claude Code, a new session without the URL of the artifact creates a new artifact and does not update the old one. To give readers a link that does not depend on these settings, publish the HTML to Display (display.dev). Display is our product. We checked the causes against the Claude Help Center and the Claude Code documentation on 14 October 2026. Users report the exact text of the error screens. Anthropic does not document it, unless we say so. --- ## "Page not found" for a reader Do the checks in this order. | Cause | How to check | Fix | Documented by Anthropic | | ------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | ------------------------------------- | | The sender shared the artifact inside an organization, and the reader is not a member | Ask the sender which audience they chose. "Only people invited" and "Anyone at \[organization]" need a signed-in member | The sender invites the reader by email (beta), or publishes the HTML on a different host | Yes | | The reader uses a different Claude account | Tell the reader to open the link in a private window, then sign in with the invited address | Sign in with the invited address | Yes. An invitation is for one address | | An Owner turned off External sharing | Ask an Owner to check Organization settings, Artifacts. When the setting is off, existing public links stop working | The Owner turns it on, or allows that one artifact | Yes | | An Owner turned off outside email invitations | Same settings page. When the setting is off, people who are already invited cannot open the artifact | The Owner turns it on | Yes | | The invitation expired | Pending invitations expire after 30 days. Accepted invitations do not expire | The sender sends a new invitation | Yes | | The sender unpublished or deleted the artifact | The sender checks the Artifacts tab | Unpublishing a legacy chat artifact is permanent. Make a new artifact | Yes | | The text of the screen | Users report "Page not found" for several of the causes above | None | No | --- ## "Cannot republish" or "the link changed" | Cause | What happens | Fix | | -------------------------------------------------- | ---------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | | Someone unpublished a legacy chat artifact | You cannot publish it again. Unpublishing also deletes its stored data | Create a new artifact. The old link stays broken | | A new Claude Code session did not get the old URL | The session creates a new artifact | Give Claude the URL, or attach the artifact with `/artifacts`. Then ask for the update | | An editor published a newer version | Claude Code refuses a publish that it built on the older copy | Claude merges its changes onto the newer version and publishes again | | The session is not signed in | Claude Code prints `Artifacts need a claude.ai login` | Sign in with `/login` | | Plan mode, or a publish that declares capabilities | Claude Code asks before it publishes | Approve the prompt | | The page is too large | The publish or the share fails on large pages | Read [Claude artifact too large to share](/blog/claude-artifact-too-large-to-share) | --- ## Stop depending on the share state A link on claude.ai depends on three things: the audience setting, the policy of the organization and the publish state of the artifact. Each one can change after you send the link. For a page that readers must open again and again, publish the HTML to Display. 1. Add Display from [claude.ai/directory/display](https://claude.ai/directory/display). 2. Tell Claude: "Publish this artifact to Display as a Company page." 3. Send the Display link. Readers sign in with their company email. For a client, publish the page as Private and invite the client by email. The client enters a one-time password and can view the page. Clients cannot comment yet. 4. To change the page, tell Claude: "Update the page at the same link." The link stays the same, and paid plans keep the earlier versions. When the link is on your own host, a change to the Claude sharing settings cannot break it. Read [How to share a Claude artifact privately](/share-claude-artifact). --- ## FAQ **Can I publish an unpublished Claude artifact again?** Not a legacy chat artifact. Anthropic says that you cannot publish it again. Make a new artifact. **Does unpublishing delete data?** Yes, for a legacy chat artifact that used storage. Unpublishing permanently deletes its personal and shared storage data. **Why does my link work for me but not for my client?** You are a member of the organization. Your client is not. Read the first table. **Why did a public link stop working when nobody changed the artifact?** An Owner possibly turned off External sharing. Existing public links stop working until an Owner turns it on again. **Does a Display link break if I cancel my Claude plan?** No. Display stores the page, and the URL continues to work.