# Find Public Claude Artifacts in Google and Unpublish

> Learn how Google indexes public Claude Artifacts, check whether yours are exposed, unpublish safely, and choose protected sharing.

## Public Claude Artifacts Can Appear in Google

TL;DR: `site:claude.ai/public/artifacts` can reveal Google-indexed public Claude Artifact pages.

A public Claude Artifact is not an unlisted private preview. Claude's Publish dialog warns that published artifacts are available to anyone online and may appear in search results. The originating conversation remains private; the artifact does not.

A link sent to one client may still be found and opened through Google, another site, or a forwarded message.

| What remains private | What becomes public |
|---|---|
| Your Claude chat | The published artifact page |
| Unpublished artifact versions | The selected published version |
| Other private conversations | Content visible inside the artifact |

If an artifact should not be public, inspect it in Claude and use **Unpublish**. Read the irreversible-storage warning before confirming.

![Google search for public Claude Artifacts with artifact titles and snippets covered in light gray](/assets/blog/find-public-claude-artifacts-in-google-and-unpublish-yours/01-google-site-claude-public-artifacts.webp)

*The broad site search returned pages under Claude's public artifact path. Artifact details and the signed-in Google profile are covered in light gray.*

## What `site:claude.ai/public/artifacts` Reveals About Public Claude Artifacts

The Google query `site:claude.ai/public/artifacts` finds indexed pages under Claude's public artifact path. On **August 1, 2026**, broad and narrower searches returned public Claude Artifacts.

Google may index a Claude artifact when:

- It has a public `claude.ai/public/artifacts` URL.
- The page requires no sign-in or access gate.
- A search engine discovers, crawls, and indexes it.

Google may discover pages through links, embeds, or normal crawling. A hard-to-guess URL is not private.

This does **not** mean Google indexes every published artifact. Google does not crawl every public page, and its index changes. Results vary by time, location, language, device, and index state. The query is a spot check, not a complete inventory.

Practical lesson: if publishing is safe only while the link stays secret, public publishing is not access control.

## Google Search Queries Tested for Public Claude Artifacts

All five searches returned indexed Claude Artifact pages on August 1. We recorded only whether results appeared; we did not identify, quote, or reproduce unrelated artifacts' titles or contents.

| Query | Purpose | Result from our test |
|---|---|---|
| `site:claude.ai/public/artifacts` | Broad index check | Indexed artifact pages appeared |
| `site:claude.ai/public/artifacts after:2026-07-25` | Roughly the previous 7 days | Indexed artifact pages appeared |
| `site:claude.ai/public/artifacts after:2026-07-18` | Roughly the previous 14 days | Indexed artifact pages appeared |
| `site:claude.ai/public/artifacts "dashboard"` | Topic search | Indexed artifact pages appeared |
| `site:claude.ai/public/artifacts "calculator"` | Topic search | Indexed artifact pages appeared |

![Google search limited to recent public Claude Artifacts with private details covered in light gray](/assets/blog/find-public-claude-artifacts-in-google-and-unpublish-yours/02-google-claude-artifacts-last-seven-days.webp)

*On August 1, `after:2026-07-25` narrowed results to roughly the prior seven days. Result details are covered in light gray.*

Google documents `site:`, quotation marks, exclusions, and date operators in its [search refinement guide](https://support.google.com/websearch/answer/2466433). The `after:` and `before:` dates filter Google's indexed results. They do not precisely reveal an artifact's original publication date.

Use harmless terms from your own work. Do not test indexing with client names, email addresses, API keys, financial details, or other confidential data.

Copyable variations include:

```text
site:claude.ai/public/artifacts "your public product name"
site:claude.ai/public/artifacts dashboard analytics
site:claude.ai/public/artifacts calculator -finance
site:claude.ai/public/artifacts after:2026-07-18 before:2026-08-02
```

An exact phrase can target an already-public brand phrase. Multiple terms require both ideas. A minus sign removes an unwanted meaning. A date range inspects a period within Google's indexing limits.

![Google search for public Claude Artifacts containing dashboard with result details covered in light gray](/assets/blog/find-public-claude-artifacts-in-google-and-unpublish-yours/03-google-claude-artifacts-dashboard-filter.webp)

*Quoted topic filters worked too. The query remains visible; unrelated artifact titles and snippets are covered in light gray.*

## How to Check Your Public Claude Artifacts

Use Google for discovery and your Claude library as the main inventory. Review every artifact that might contain client, business, or personal material.

1. Open Claude and choose **Artifacts** in the left sidebar.
2. Open a library artifact.
3. Inspect the selected version's **Publish/Unpublish** control.
4. **Unpublish** means the artifact is published.
5. Review its interactive views, generated text, downloads, and displayed persistent data.

![Artifacts navigation in Claude](/assets/blog/find-public-claude-artifacts-in-google-and-unpublish-yours/07-claude-artifacts-navigation.webp)

*Select Artifacts in Claude's left sidebar. The crop excludes artifact titles and other private workspace details.*

Record public URLs you intentionally maintain. You can also search your artifact's full URL or pair `site:claude.ai/public/artifacts` with a distinctive public phrase from it.

No Google result does not mean the artifact lacks public access. Anyone who receives or discovers an unindexed published link can still open it.

## How to Unpublish Claude Artifact Content Safely

Claude's [official publishing guide](https://support.claude.com/en/articles/9547008-publish-and-share-artifacts) says that an **Unpublish** button appears after an artifact has been published. Use it to revoke public access to the published Claude artifact.

1. Open Claude and select **Artifacts** in the left sidebar.
2. Open and verify the published artifact.
3. Export or preserve permitted material, especially persistent-storage data.
4. Select **Unpublish** and read the confirmation.
5. Confirm, then test the former URL in a private window.

![Claude Publish artifact dialog warning that the artifact may appear in search engines](/assets/blog/find-public-claude-artifacts-in-google-and-unpublish-yours/09-claude-publish-search-warning-ai-daily-comics.webp)

*Claude warns that published artifacts are available to anyone online and may appear in search results. The `ai-daily-comics.html` artifact name is shown with the owner’s approval.*

Unpublishing has two irreversible effects:

| Effect | What it means |
|---|---|
| The same artifact cannot be published again | You must create a new artifact if you later want another public version |
| Associated persistent storage is permanently deleted | Personal and shared storage used by that artifact cannot be restored through republishing |

I would export authorized material before confirming. Do not store client or personal data insecurely merely to retain it.

Team and Enterprise sharing follows different rules. Those artifacts stay within the organization and use **Unshare**, not public publishing.

## Claude Artifact Google Indexing After Unpublishing

Unpublishing removes Claude access, but Google may show an old result or snippet until recrawling. Search listings and cached information need not update with the source page.

After unpublishing:

- Test the former link signed out to confirm revoked access.
- Repeat the exact Google search later.
- Save the URL and a dated screenshot.
- For sensitive material, check other search engines.

Do not promise instant deindexing. Google says indexing takes time because it cannot revisit every page immediately.

Without control of the `claude.ai` Search Console property, you generally cannot use its owner-only Removals tool for the URL. If the page is gone but an outdated Google listing remains, Google's [Refresh Outdated Content tool](https://support.google.com/webmasters/answer/7041154) may be appropriate. It updates Google Search, not the wider internet, and approval is not guaranteed.

Handle copies, screenshots, or reposts with each site's operator.

## Password Protected Claude Artifact Sharing With Revdoku

Public Claude publishing suits open demos, tutorials, and tools. Controlled external sharing needs a different default.

From the dashboard, put exported browser-ready files in a Revdoku bucket and share them through a password or verified-email gate. A **server-side access gate** protects the content from public exposure.

| Sharing situation | Better default | Reason |
|---|---|---|
| Public educational calculator | Claude public publishing | Broad discovery is intentional |
| Agency dashboard prototype | Revdoku password access | One shared secret controls entry |
| Founder sending an investor deck | Revdoku verified-email access | Only allowed addresses can enter |
| Freelancer updating a client demo | Revdoku protected stable link | Updates do not require a new URL |

For setup ideas, read about [Claude Artifacts for teams versus public AI-built sites](/blog/claude-artifacts-teams-vs-public-ai-built-sites/) and [publishing a Claude-built website](/blog/claude-website-publishing/). The access guides explain how to [password-protect a website](/blog/how-to-password-protect-a-website/) or use [verified-email access](/blog/verified-email-access/) for named recipients.

![Revdoku live website dialog with Password access selected and the password covered in light gray](/assets/blog/find-public-claude-artifacts-in-google-and-unpublish-yours/06-revdoku-password-access.webp)

*Revdoku can protect published files by password or verified email. The bucket identifier and password are covered in light gray.*

Revdoku can notify owners when protected links open and show each visitor's page, click, and download activity. It can record leads and feedback without a separate backend. The same protected URL supports later updates to a sent proposal, presentation, or client demo.

## Pre-Publish Claude Artifact Privacy and Access Checklist

Review the page, source files, stored data, and downloads. A polished interface can hide test values.

| Item | What to check | Why it matters |
|---|---|---|
| **API keys and tokens** | Source, configuration, requests, error messages | A working secret can permit unauthorized use |
| **Client data** | Names, logos, documents, comments, account details | Client material may be covered by contracts or privacy rules |
| **Internal names** | Project codenames, staff names, private URLs | Small clues can expose internal work |
| **Private prompts** | Instructions, examples, pasted research | The artifact may reveal methods or source material |
| **Financial information** | Forecasts, pricing, invoices, fundraising figures | Unpublished numbers can harm negotiations |
| **Customer information** | Email addresses, IDs, support records, analytics | Personal data should not be placed on a public page |
| **Persistent storage** | Saved user entries and shared records | Unpublishing permanently deletes associated storage data |
| **Access choice** | Public, password, or verified email | The access method should match the intended audience |

Use synthetic data for public demonstrations. Before publishing Claude Artifact screenshots in documentation or articles, redact titles, account details, URL identifiers, snippets, and personal information.

Final test: could a stranger, client, and competitor view the page without explanation? If the answer differs for any, use controlled sharing.

## A Safer Claude Artifact Privacy Default

Public Claude Artifacts suit work anyone may view and interact with. Treat them as public web pages upon publishing, indexed or not.

Use `site:claude.ai/public/artifacts` to check discovery, review your library, and unpublish content that should not be accessible. Unpublishing is irreversible for that artifact and permanently removes its persistent storage.

For future client work, match access to intent:

- Publish openly when public discovery is welcome.
- Use a password for a small trusted group.
- Use verified email when access should be limited to named recipients.

Make that choice before sharing the link.

Start publishing for free

Connect this AI to Revdoku so it can store files, create, update, and publish websites for me. Read and follow https://revdoku.com/prompt.md. A Revdoku account is required. If I do not have one, send me https://app.revdoku.com/users/sign_up?utm_source=revdoku.com&utm_medium=ai-chat&utm_campaign=connect_ai_first and wait until I confirm signup is complete. For ChatGPT, Claude, or another cloud AI, connect https://app.revdoku.com/mcp and complete Revdoku OAuth. For a local agent, use Revdoku's browser device sign-in and complete the connection in Revdoku. Never ask me for a password or API key in chat, or for a verification code. When Revdoku tools are connected, verify the connection, tell me you’re ready, and ask what I want to publish.

Copy Prompt

or

Create Free Account

## Frequently asked questions

### Does publishing a Claude Artifact expose my conversation?

No. Your Claude conversation remains private, but the selected artifact version becomes publicly accessible. Review everything the artifact displays, stores, or makes available for download before publishing.

### Does a Google site search find every public Claude Artifact?

No. The query only shows artifact pages currently included in Google’s index. A published artifact can still be opened through its URL even when it does not appear in search results.

### How can I tell whether one of my Claude Artifacts is public?

Open the artifact from the Artifacts library and inspect its publishing control. If the control says **Unpublish**, the artifact is currently published. You should also test its URL while signed out or in a private browser window.

### What happens when I unpublish a Claude Artifact?

Public access to the artifact is revoked, but the same artifact cannot be published again. Its associated personal and shared persistent-storage data is also permanently deleted, so export any permitted information you need before confirming.

### Will an unpublished artifact disappear from Google immediately?

Not necessarily. Google may continue showing an outdated result or snippet until it recrawls the URL. Confirm that the former URL is inaccessible, then recheck search results later and consider Google’s Refresh Outdated Content tool if the listing persists.

### Can I password-protect a publicly published Claude Artifact?

Claude’s public publishing is intended for content anyone may access, rather than password-gated delivery. For client demos, proposals, or investor materials, export the browser-ready files to a service offering server-side password or verified-email access.

### What should I remove before publishing an artifact?

Check for API keys, client or customer data, private prompts, internal URLs, financial details, and saved user records. Use synthetic data for public demonstrations and verify interactive views, downloads, error messages, and persistent storage, not just the visible landing screen.

---

[View the canonical page](https://revdoku.com/blog/find-public-claude-artifacts-in-google-and-unpublish-yours/) · [Browse llms.txt](https://revdoku.com/llms.txt)