Claude Artifacts on Google: How to Check and Remove Yours

By Thomas Echezabal, AI Automation Coach, thomasknows.ai

On July 26 and 27, 2026, people started running a simple search — site:claude.ai/public/artifacts — and finding other people's work: internal dashboards, pricing spreadsheets, client lists, resumes with home addresses on them. None of it was stolen. Every one of those pages was published on purpose by someone who thought "anyone with the link" meant the link would stay between them and the person they sent it to.

That gap between what people thought publishing meant and what it actually does is the whole story, and it matters most to the owners who have been doing this right. If you've handed Claude your proposal drafts, your onboarding paperwork, or a dashboard built from real client numbers, the audit below takes about fifteen minutes and protects all of it. I'll show you what is genuinely at risk, what never was, how to unpublish without losing work, and how to get something out of Google once it's already there.

Key Takeaways

In this guide, you'll learn:

• Why publishing an artifact puts it on the open web, and why that is different from sending someone a private link
• The difference between a published artifact and a shared chat, and why only one of them is blocked from search engines
• How to audit everything you've ever published from the Artifacts section in your Claude sidebar
• The one-way warning nobody is mentioning: unpublishing an artifact is permanent and deletes its stored data
• Why the Search Console removal tool everyone is recommending will not work for you, and the three tools that will
• What was never exposed, so you can stop worrying about the parts that were always private
• The habits that keep this from happening again without giving up artifacts entirely

Table of Contents

• What Actually Happened, and What Didn't
• Published vs. Shared: Two Different Things
• Step 1: Find Everything You've Published
• Step 2: Unpublish, but Read This First
• Step 3: Get It Out of Google
• Step 4: Check Your Shared Chats
• How to Keep This From Happening Again
• FAQ

What Actually Happened, and What Didn't

Nothing was breached. When you click Publish on an artifact, Claude does exactly what Anthropic's documentation says it does: on the Free, Pro, and Max plans, publishing "makes your artifact publicly available," and "anyone with the link can view and interact with it." Someone who lands on your published artifact doesn't need a Claude account, doesn't need to sign up, and doesn't need permission from you.

The part that caught people out is that a public web page is a public web page whether or not you advertise it. Google doesn't need you to submit a link; it finds pages by following links and crawling what it's allowed to crawl. Once a published artifact URL appears anywhere — a Slack message that got archived publicly, a forum post, a directory of Claude creations — it becomes a candidate for the index like any other page on the internet.

Here's the detail I think is the most useful thing in this guide, because it's the difference between an accident and a decision. Claude's own instructions to search engines, which live in a file at claude.ai/robots.txt, tell crawlers to stay out of chats, shared chat links, settings, and several other areas. I checked that file directly on July 27, 2026, and it contains no instruction at all about published artifacts. Shared chats are walled off from search engines; published artifacts are wide open to them.

That asymmetry has a history. In September 2025, Forbes reported that hundreds of Claude chat transcripts had turned up in Google, and Anthropic responded by blocking crawlers from those shared chat links. The fix worked and it's still in place, which is precisely why shared chats are protected today and artifacts are not. Search visibility here is a product choice rather than an unavoidable side effect of making something public, and the choice simply never got extended from one feature to the other.

One more thing worth being precise about, since a lot of the coverage this week has been loose with it. Claude pages were observed in Google results, and many shared-chat results later stopped appearing. Neither complete removal nor who acted has been publicly confirmed, and I haven't found an official Anthropic statement about the artifact side of it. What I can confirm from checking directly is that published artifacts remain crawlable right now, so treat this as a live situation rather than one that resolved itself over the weekend.

Published vs. Shared: Two Different Things

Claude has two separate features that both feel like "sending someone a link," and they behave very differently. Knowing which one you used tells you how worried to be.

Two details in that table deserve a note. If you're on a Team or Enterprise plan, artifacts created on your account can only be shared inside your organization and cannot be published publicly at all, so your exposure here is limited to anything you published from a personal Free, Pro, or Max account. And live artifacts created in Claude Cowork follow the stricter rule on every plan: they can be shared within an organization, never published to the open web.

Step 1: Find Everything You've Published

Publishing an artifact adds it to an Artifacts section in your Claude sidebar, which exists so you can find these again outside the conversation that created them. That list is your audit, and it's the fastest fifteen minutes you'll spend this month.

Open it and read the whole list rather than skimming for things you remember. The risky ones are almost never the artifact you published this week; they're the dashboard you built in March from a real client export, or the pricing calculator you published to show one person and forgot about. Ask of each one: if a competitor, a client, or a candidate you rejected read this page top to bottom, would anything in it embarrass you or breach a confidence?

To find out whether Google has already picked one up, take a distinctive string out of the artifact — an unusual sentence, a client's company name, your own pricing tier names — and search it in Google inside quotation marks. If a claude.ai/public/artifacts result comes back, that page is indexed and you'll need Step 3 as well as Step 2. You can also search site:claude.ai/public/artifacts on its own, though that shows you everyone's published artifacts rather than yours specifically.

Step 2: Unpublish, but Read This First

Unpublishing is one click. Open the artifact, click Unpublish, and public access is revoked. Before you start clicking, though, there's a consequence buried in Anthropic's documentation that almost none of this week's coverage has mentioned, and it's the kind of thing that turns a tidy afternoon into a bad one.

The practical order, then, is copy first and unpublish second. Open anything you're about to retire, copy out the code, the content, and any stored data you'd miss, and save it somewhere you control before you touch the button. If the artifact is something you genuinely want to keep public in a cleaned-up form, build a fresh version with the sensitive material stripped out and publish that one, because you won't get to republish the original.

For anything that was never meant to be public in the first place, none of that applies. Unpublish it immediately and worry about reconstructing it later.

Step 3: Get It Out of Google

Unpublishing kills the live page, but it doesn't reach into Google's index and pull the old listing out. This is where most of the advice circulating this week is actively wrong, and following it wastes an afternoon on a tool you can't even open.

The advice to ignore: "Use the Removals tool in Google Search Console." That tool only works on a website you've verified you control, and you don't control claude.ai — Anthropic does. Its blocks are also temporary, expiring after roughly six months. It isn't available to you here.

The tool that actually works for a page on someone else's site is Google's Refresh Outdated Content tool. Anyone can use it, no site ownership required. The catch is that it only succeeds once the live page has stopped serving the content, which is why the order in this guide matters: unpublish in Claude first, confirm the URL no longer loads your artifact, then paste that URL into the tool. Submitting while the page is still live gets the request rejected, so doing these two steps out of order costs you the round trip.

If personal information was exposed, you have a third and stronger option. Google accepts removal requests for personal information on live pages — home addresses, phone numbers, email addresses, government ID numbers, financial or medical records, and login credentials all qualify. This one can apply even before the page comes down, which matters if the artifact belongs to a client and you're waiting on them to act. These requests are reviewed rather than granted automatically, so submit it and keep unpublishing in parallel rather than treating it as a substitute.

One last expectation to set: even after Anthropic blocks crawlers from a section of their site, that alone doesn't clear anything already indexed. Google's own guidance is explicit that a crawl block is not a removal mechanism, and a blocked URL that other pages link to can linger as a bare listing with no description. Waiting for a platform-side fix isn't a plan for a page with your client's numbers on it.

Step 4: Check Your Shared Chats

Shared chats are the lower-risk sibling here, since they're already blocked from search engines, but they're still public to anyone holding the link and worth ten minutes of your time.

Go to Settings → Privacy, find the Privacy settings section, and click Manage next to Shared chats. You'll get a list of every chat snapshot you've shared with its title, the date, and the link, and an Unshare button beside each one. If you've never shared a chat, the list will simply tell you there's no shared content.

Two things about these snapshots should lower your blood pressure before you panic-unshare everything. Files you attached to a conversation are not included in the snapshot and stay private, and the raw data Claude pulled back through any connected tool stays hidden too. A snapshot also freezes at the moment you shared it, so messages you sent afterward remain private unless you unshare and share again.

The caveat that keeps this honest: while the file itself isn't in the snapshot, Claude's visible replies are, and those replies routinely quote and summarize what was in the file. If you uploaded a client contract and Claude walked through its payment terms in the chat, those terms are in the shared snapshot even though the contract isn't. Read what Claude actually said, not just what you attached.

How to Keep This From Happening Again

The fix isn't to stop using artifacts, which remain one of the most useful things Claude does for a small business. The fix is a clearer mental model plus two or three habits.

Treat Publish the way you'd treat posting a page on your own website: assume a stranger will read it, because that is the feature working correctly rather than failing. Sharing a link with one person and publishing to the open web feel identical when you're clicking, and they aren't the same act at all.

From there, a few habits carry most of the weight:

• Build with placeholder data when the artifact is going to be public. A pricing calculator demonstrates itself just as well with "Client A" and round numbers as it does with your actual book of business.
• Keep client-specific work inside a Project rather than publishing it. Projects stay private and cannot be made publicly accessible at all, which makes them the right home for the material you were never going to publish anyway.
• Put the audit on a calendar. Once a quarter, open the Artifacts list and the Shared chats list and clear out anything that has outlived its purpose. This whole story comes down to things people published once and stopped thinking about.
• Check before you send, not after. If you're publishing something so one person can look at it, ask whether emailing them a file would do the same job without creating a permanent public page.

If you want the broader picture of how artifacts, Projects, and the rest of Claude fit together for a business, the complete guide to using Claude AI for your small business covers the whole stack. And if this episode has you thinking harder about which parts of your business knowledge live inside tools you don't control, building an AI second brain you own is the natural next move.

FAQ

Are my private Claude chats showing up on Google?

No. Only content you actively published or shared was ever involved. Conversations you never shared, artifacts you never published, and material stored inside a Project are not public and were not part of this. If you've never clicked Publish or Share, there is nothing for you to clean up.

How do I check if my Claude artifact is on Google?

Copy a distinctive phrase from the artifact — an unusual sentence, a client or product name, your own pricing labels — and search it in Google inside quotation marks. A result pointing to claude.ai/public/artifacts means that page is indexed. Searching site:claude.ai/public/artifacts on its own works too, but it returns everyone's published artifacts rather than only yours.

Where do I find everything I've published in Claude?

Publishing an artifact adds it to the Artifacts section in your Claude sidebar, which is designed to let you find published artifacts outside the conversation that created them. Shared chats live in a separate place: Settings → Privacy → Shared chats → Manage.

Can I republish an artifact after I unpublish it?

No. Anthropic's documentation is direct about this: once you unpublish an artifact you cannot publish that same artifact again, and you'll need to create a new one if you want a public version later. Unpublishing also permanently deletes any data the artifact had stored. Copy out anything you want to keep before you unpublish.

Why are shared Claude chats blocked from Google but published artifacts aren't?

Claude's instructions to search engines block crawlers from shared chat links but say nothing about published artifacts, which I verified directly on July 27, 2026. The chat block dates back to a September 2025 incident when Claude transcripts appeared in search results and Anthropic blocked crawling of those links. That protection was never extended to the artifact side.

Does unpublishing remove the artifact from Google right away?

Not by itself. Unpublishing takes the live page down, but the old search listing can linger until Google recrawls. To speed that up, submit the URL to Google's Refresh Outdated Content tool after you unpublish. That tool only accepts pages that have already stopped serving the content, so the order matters.

Can I use Google Search Console to remove a Claude page?

No. The Removals tool in Search Console only works on websites you've verified you own, and Anthropic owns claude.ai. Use the public Refresh Outdated Content tool instead, or a personal information removal request if the page exposed personal or financial details.

Are Team and Enterprise accounts affected?

Much less. Artifacts created on Team or Enterprise accounts can only be shared inside your organization and cannot be published publicly at all, and viewers have to sign in with an account from that organization. Anything you published from a personal Free, Pro, or Max account is still worth auditing.

Summary

• What Actually Happened, and What Didn't — publishing works as documented, but a public artifact is a public web page and search engines are not blocked from it
• Published vs. Shared: Two Different Things — shared chats are walled off from crawlers, published artifacts are not
• Step 1: Find Everything You've Published — the Artifacts section in your sidebar is the audit list
• Step 2: Unpublish, but Read This First — it's permanent and it deletes stored data, so copy before you click
• Step 3: Get It Out of Google — Search Console won't help you, but Refresh Outdated Content and personal information removal will
• Step 4: Check Your Shared Chats — lower risk, still worth ten minutes, and Claude's replies can quote files the snapshot excludes
• How to Keep This From Happening Again — placeholder data for public artifacts, Projects for client work, and a quarterly sweep

If you'd rather have someone look at this with you than work through it alone, I go through the audit with small business owners and set up the boundaries so client material never ends up in a published artifact in the first place — book a 1:1 session with me and we'll go through what you've published together.

About the Author

Thomas Echezabal helps small business owners automate their busywork with AI and get real hours back each week. He has worked with small businesses his entire career, including 200+ clients on Fiverr.